Runtime error 100 is "disk read error" whyever that may occur here.

I'll do other tests with virtual pc and a real dos environment too. I'm curious to see the overall behaviour.

edit: testing with virtual pc now. using start.bat from cdrom gave the same Runtime error 100 at 0000:0089 error (probably the game cannot be started directly from cdrom). the game installs with no errors and using start.bat from hd only gave the old irritating "not enough memory to run the game" (536kb free is not enough for this bastard!)... but this is another problem (the fight with autoexec and config settings). I will do other tests with dosbox too.

Maybe try loadfix or disabling ems/xms/sound/etc.

536kb ??

yep. but because I'm trying to run it using virtual pc, because I got weird error messages using dosbox and I want to check the differences. I'll have to check my autoexec and config 😉

What the hell are you loading so that you have only 536 K free? Cut down on TSRs, dude! And use DOS=HIGH.

Finally, it works now. I abandoned the virtual pc and after a dos installation from zero on an old p200 mmx I installed and played the game there without errors. The game however runs too fast (the game was designed for 386 and 486 cpus), the car is fast as hell! 😄' but that is another problem. So the test with virtualpc/legacy pc is over.

when in dosbox how have you mounted it?

mount d f:\ -t cdrom -label CDLABELIDONTREMEMBERIT -ioctl_mci

f is my real cdrom drive letter

wd wrote:

Runtime error 100 is "disk read error" whyever that may occur here.

It occurs when I try to start the game from cdrom, instead of installing it.
It gives this error in a real dos environment too.

And the c-drive?

mount c c:\directorywhereIstoremygames

Why are you using the mci cd interface which doesn't provide sector access?

Yep, there is a reason: I use it when I have cdroms with audiotracks, it's the only setting I found to hear audiotracks perfectly. the default setting give me audio interruptions every random seconds (blocksize or prebuffer or too old pc specs who knows). I tried with other ioctl methods too however. thanks for the advices guys, dosbox is a formidable piece of code and runs very well 99% of my old titles and in the future it can only improve. I will not cry if this game will not work 😉

This thread is confusing and utterly pointless.

First, the OP should make up his friggin' mind whether he wants to run the game in DOSBox or on a legacy PC. Depending on this choice, he should then describe his problems, preferrably in seperate posts in the appropriate subforums. Furthermore he should add (in both cases) detailed information about his system and about how he installed the game (and about how DOSBox is setup).

Only after following these simple and self-evident procedures there's a chance of actually achieving something. Until then this thread will just ramble on uselessly, jumping back and forth between problems.

As suggested I updated the first post to make all clearer, more readable.

So to clarify, you never got this running in dosbox? I am having this same issue currently, so it would be nice to know if a solution was discovered.

yeah, I actually never succeeded (in dosbox). And I abandoned the idea. sorry

The game has to be installed, but the method of installation is not obvious. Also, there is a bug in one of the game executables that is likely to occur in DOSBox, but it has a workaround.

First, in DOSBox copy COMMAND.COM from the Z: drive to the root of your emulated C: drive. This is necessary because the installer does not use the COMSPEC environment variable like it should.

Second, switch to to the RALLY subdir on the cdrom and run GO.EXE to install (really obvious). Choose the appropriate CPU speed and sound options to match what is configured in DOSBox before selecting the "INSTALL" option. The installer suggests C:\RACE as a working directory, so use that or something similar and the necessary files will be copied there.

Lastly, modify START.BAT in the install dir to:

1@ECHO OFF
2POSIX
3D:
4CD \RALLY
5RACECD

This is assuming that your cdrom is the D: drive, change if needs be. Switching to the cdrom drive and directory is the additional part, and is needed because of a bug in the POSIX.EXE program. The program relies on a pre-existing memory value for the length of the cdrom drive and path string, which produces arbitrary success or failure depending on the length being "long enough", but tends to fail in DOSBox because its memory is initially zero values.

The game should then work when you run START.BAT from the install dir. Note that the game has doc-check copy protection in addition to requiring the cdrom in the drive.

Just in case anyone else comes across this, as I was searching for info on the game before I capture it, I found using F3 and F4 can slow the framerate to make it playable on PCs that are too fast. Either that or set DOSBox cycles to between 15000 - 30000 (depending on what is playable)!

It's a bit of a shame, as the game runs much smoother on Amiga (see YouTube clips) than PC. If you try to get the same framerate on PC it runs too quick to be playable.