konc wrote on 2026-09-23, 12:46:

So I'm revisiting this to ask if anyone knows if any other solution has been found since then? A newer game patch maybe, a file replaced, some setting?

I doubt it. Year or two ago I did some heavy duty googling trying to solve a different issue I was having with CMR2 and I never saw anything that could help with that. In fact I found very little in general, not the most talked about game out there.

My issue was the game crashed on Win98SE at launch without exception with ATI X700 Pro. I couldn't find any solution to that, until by chance I happened to notice one No-CD crack claiming to fix "dual headed VGA" or something like that. That crack didn't work on my system of course, but it did lead me to try to disable secondary video output in device manager, which fixed the issue completely.

So yeah, the game has some quirks. The only thing I can think of which could have even a remote chance of helping you is while the last official patch they released is 1.09, it's not actually the most up to date version out there. Some rereleases shipped as version 1.11. I've never seen any kind of patch notes for it so I don't know how 1.11 differs from 1.09. Honestly something tells me it probably wouldn't help you, but if you can get your hands on that version it wouldn't hurt to try it.

Thanks for the info, I'm afraid you are right.

The 1.11 version apparently has copy protection removed and was the one of budget re-releases like the "Sold Out Software". It's supposed to only have copy protection removed so I again agree with you that it'll probably won't change anything. It doesn't hurt hunting and trying this version too though.

I've always felt the last "Voodoo Series" drivers that supported Voodoo3 broke a lot of games, i've always stuck to the older pre-Voodoo5 drivers.

Yeah as expected the later 1.11 version doesn't make any difference for this particular issue, but it's nice to have it anyway. The disc can be read+copied without special tools, there is no cd check and no patching necessary. With all this new convenience I think I'll end up downgrading to older drivers and if new issues occur hopefully they will be easier to deal with.

If the problem has not been resolved at the level of the game itself or the driver for so many years, I would consider another option as a last resort: first, find out which specific driver files resolve this issue. It may turn out that only 1-2 files need to be replaced (but it could be more). After that, you can create a BAT file that:

1. initiates a reboot in MS-DOS mode;
2. replaces these problematic files with working versions;
3. returns to Windows.
4. will launch the game and wait in the background for it to finish;
5. after exiting the game, it will repeat steps 1-3, but will restore the previous files.

Yes, I understand that this is a rather crude method, but if there’s no other solution, it’s quite viable in many cases - when a specific game requires a special version of the video driver that isn’t optimal for the majority of commonly used applications.