boxpressed wrote:

233Mhz it too fast for Jazz on my SE440BX-2. I thought the same thing that you did until I discovered a Slot 1 233MHz PII that I'd forgotten about. I got the runtime error with Jazz and Tyrian setup.

I'm pretty sure I've managed to get it going on slightly faster systems. It might take a couple of tries (odd as that sounds).

One Must Fall runs way too fast at this speed.

One Must Fall has its own speed setting in its option menu.

I believe that you will need to adjust multipliers in order to get a Slot 1 build to work with these Epic games, and I don't know if that is possible.

Like I said, Runtime Error 200 is generally fixed with any number of simple patching utilities. (Note that in the case of Jazz Jackrabbit, you actually need to patch FILE0001.EXE and not JAZZ.EXE or whatever the actual startup command is.)

Jorpho wrote:

I'm pretty sure I've managed to get it going on slightly faster systems. It might take a couple of tries (odd as that sounds). […]
Show full quote

boxpressed wrote:

233Mhz it too fast for Jazz on my SE440BX-2. I thought the same thing that you did until I discovered a Slot 1 233MHz PII that I'd forgotten about. I got the runtime error with Jazz and Tyrian setup.

I'm pretty sure I've managed to get it going on slightly faster systems. It might take a couple of tries (odd as that sounds).

One Must Fall runs way too fast at this speed.

One Must Fall has its own speed setting in its option menu.

I believe that you will need to adjust multipliers in order to get a Slot 1 build to work with these Epic games, and I don't know if that is possible.

Like I said, Runtime Error 200 is generally fixed with any number of simple patching utilities. (Note that in the case of Jazz Jackrabbit, you actually need to patch FILE0001.EXE and not JAZZ.EXE or whatever the actual startup command is.)

This is one of the best things with the PC-Chips M577 VIA MVP3 motherboard I use in the retro system in my signature. With an AMD K6-2 @500MHz CPU the system is slow enough in the Borland Pascal speed test to never trigger the runtime error 200, at least not from within Windows 98. The board dosnt seem slower than other VIA MVP3 boards running the actual games. I played through most of Unreal Gold for example with better FPS than Phil got with his K6-3+ system in his new video.

I have no good explanation why this system wont trigger the bug while all my other systems will as soon as I use a CPU at a greater speed than ~200-233 MHz.

Skyscraper wrote:

This is one of the best things with the PC-Chips M577 VIA MVP3 motherboard I use in the retro system in my signature. With an AMD K6-2 @500MHz CPU the system is slow enough in the Borland Pascal speed test to never trigger the runtime error 200, at least not from within Windows 98.

It's not the board, it's the CPU. AMD K6 CPUs don't trigger the Borland runtime 200 bug. You're safe up to ~500 MHz.

5u3 wrote:

Skyscraper wrote:

This is one of the best things with the PC-Chips M577 VIA MVP3 motherboard I use in the retro system in my signature. With an AMD K6-2 @500MHz CPU the system is slow enough in the Borland Pascal speed test to never trigger the runtime error 200, at least not from within Windows 98.

It's not the board, it's the CPU. AMD K6 CPUs don't trigger the Borland runtime 200 bug. You're safe up to ~500 MHz.

Ah that explains it, its the only K6-X system I have used for playing old DOS games. My other Socket-7 systems in use are running Pentium MMX CPUs.

I wonder if the K6-3+ is as forgiving? I bet it isnt.

Skyscraper wrote:

I wonder if the K6-3+ is as forgiving? I bet it isnt.

My K6-3+ doesn't trigger it at 500 MHz, but i get the error at 550 MHz. K6+ is a very retro-friendly CPU 😀

I've seen K6-2 500's trigger the runtime error thing before though, requiring many many many starts for it to work. I still suspect it's FSB related.