Reply 40 of 81, by Scali
I'd have to see what happens if I run it on one of my faster 8088 systems. I don't have a V20.
Some parts might look wrong because of timing issues. Some parts do their own music timing, they may run too fast, but nothing should actually crash or loop forever.
The parts that I developed (sprites and polygons) are not very speed-sensitive at any rate. The music is timer-driven, and the graphics don't rely on cycle-exactness.
One thing you could experiment with is this:
If you open 8088MPH.EXE with a hex editor, you'll see that there's a script at the end of the file:
8088mph.001|0|
8088mph.002|0|
8088mph.003|16|welcome to~4.77 mhz!~ ~welcome to cga!~ ~what's a~bitplane?
8088mph.004|0|and now i see~with eyes serene~the very heart~of the machine
8088mph.005|0|no copper!~no vic-ii!~what are we~supposed to do?
8088mph.006|13|dots are~my favours...~except~when they're~saviour's.
8088mph.007|28|sprites?~where we're~going,~we don't~need sprites
8088mph.008|25|you may want to~close your eyes~for this
8088mph.009|18|
8088mph.00a|30|race the beam~ ~on your mark...~get set...~go!
8088mph.00b|44|if my~calculations~are correct,~when this baby~hits 8088 miles~per hour,~you're going to~see some~serious *!?*
8088mph.00c|8|and now we must~bid you farewell~ ~no paula...~no sid...~no problem
8088mph.00d|0|
You can try deleting lines from that list to skip certain parts.
Eg, if I'm not mistaken, 8088MPH.000 is the 'old/new CGA' image, 8088MPH.001 is the calibration screen and 8088MPH.002 is the moire part.
So delete the 8088MPH.002 line, and it will skip over that part.
See how much of the demo you can get running that way, and we'll know which parts of the demo might need a fix, and which don't 😀