While not OP's issue, I think it's worth mentioning that Call of Duty 1 / UO and other games based on Quake 3's engine that haven't been updated have the famous crash bug that happens at startup when the game tries to output GL_EXTENSIONS string in the console. The string may not fit into game's buffer and no bounds checking is done, so it may crash; you get buffer overrun error.
It can happen on newer graphics cards where the GL_EXTENSIONS string is longer than on older cards (since they have more OpenGL features). Some drivers do handle Call of Duty 1 (and some other games) specially and truncate GL_EXTENSIONS string. Such is the case with NVIDIA's drivers where a special setting is exposed to truncate the string which can be seen with NVIDIA Profile Inspector.
The easiest workaround, should the buffer overrun error pop-up, is opening the .exe with some hex editor and locating the following string:
GL_EXTENSIONS: %s
Change it to:
GL_EXTENSIONS: %p
Googolplex wrote:many compatibility modes and fixes
Compatibility modes make the most difference when the game relies on some specific quirks of the APIs it calls. CoD isn't special in that regard.
Although with fancier monitors/display resolutions, one may need to disable display scaling at high DPI settings (on Windows 10: Change high DPI settings button on Compatibility tab, set "Override high DPI scaling behavior..." to "Application").
Googolplex wrote:
It's an OpenGL game, so dgVoodoo cannot effect it much. DirectDraw is only used to get amount of video memory to determine default graphics settings preset.
Googolplex wrote:Hmm, maybe I have to test version 1.0, but why should the patches break the game?
They shouldn't. In some games, some feature gets broken with some patch, but I'm not aware of anything bad in this case.
Googolplex wrote:The latest patches don't make changes to the exe.
They update the multiplayer parts, including the multiplayer .exe. Multiplayer .exe does not have a CD check anyway, so it can be tried to rule out bad noCD patch (which probably isn't an issue here).
Googolplex wrote:My game is the german version and the crack is for the english version. The menu texts are still in german, but maybe there are different exes for different languages and that's why the game stopped working.
There should be one .exe for all versions.
Can you open the properties of the shortcut you use to launch CoD with the right click, go to Shortcut tab and modify Target field to make it look like this:
"C:\Program Files (x86)\Call of Duty\CoDSP.exe" +set developer 1 +set logfile 1
Obviously don't change the path if you have the game installed elsewhere, just add those parameters after CoDSP.exe as written. Start the game and quit it. Log file console.log will appear in Call of Duty\main folder. Post its content here so we can see if there are any clues there. Before you just copy-paste it, you might want to delete/change the line containing your Windows account user name if it's something you don't want to be seen publicly.