That message is not the problem, it's skippable. What's necessary to make the benchmark run is limiting it to a single core.
Here's a compatibility fix that does that.
To install it run install.bat. It can be uninstalled from the controlpanel, look for "3DM2001SE Compatibility Fix".
They're just simple proxy DLLs that remove the check from system d3dim/d3dim700 DLLs at runtime. There are cases where proxy DLLs aren't picked up and it would be better to preload system DLLs from proxy ddraw.dll and patch 'em from there. Given there are already existent ddraw.dll wrappers out there that don't rely on newer APIs for graphical output, that code could be added to one of them.
Arthur Schopenhauer wrote:
A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.
This profile removes the framelock 3DMark2000 suffers from on Windows 10 (and Windows 8?).
Extract it to wherever you want and run install.bat with admin rights.
Windows 10 Enterprise x64 Build 15063. I run install.bat with administrator rights, but it did not help. The "Adventure" test shows 60 fps. The Vsync is turned off in the control panel of the NVidia.
This profile removes the framelock 3DMark2000 suffers from on Windows 10 (and Windows 8?).
Extract it to wherever you want and run install.bat with admin rights.
Windows 10 Enterprise x64 Build 15063. I run install.bat with administrator rights, but it did not help. The "Adventure" test shows 60 fps. The Vsync is turned off in the control panel of the NVidia.
Thanks, now works FIX !
And you can do the same patch for 3DMark 99 Max? When it starts not written a mistake and did not include compatibility mode?
In my opinion, in 3DMark 99 Maх too something is blocked, since in Windows 7 x64 showed great results than in Windows 10 x64: (3DMark Score: 6084, CPU Score: 141991)
For me, dgVoodoo2 was the best solution. The score went up from 30 000 to 88000 on Windows 10. (no patches needed)
1 x PLCC-68 / 2 x PGA132 / 5 x Skt 3 / 9 x Skt 7 / 12 x SS7 / 1 x Skt 8 / 14 x Slot 1 / 5 x Slot A
5 x Skt 370 / 8 x Skt A / 2 x Skt 478 / 2 x Skt 754 / 3 x Skt 939 / 7 x LGA775 / 1 x LGA1155
Current PC: Ryzen 7 5800X3D
Backup PC: Core i7 7700k
Error: No visible errors reported. The program appears to launch, but no GUI pops up whatsoever. 3DMark2000test4.exe keeps running in the background, constantly eating an entire CPU core. I've waited for 3-4 minutes with no changes, then killed the process. Tried it 3 or 4 times.
Error: Program appears to attempt initialization of fullscreen upon launch (screen turns black), then runs into an error reporting that it's missing the MMX instruction set extension:
After that, I tried Win98/Me compatibility mode on both machines to no avail. The symptoms don't change. Same after creating exceptions for 3DMark2000test4.exe in Comodo AV on XP x64. Am I supposed to do anything on top of extracting the patch into the 3DM2000 directory and running 3DMark2000test4.exe (right next to where 3DMark2000.exe is)? My apologies if I'm doing it wrong somehow..
Proud User of a 3dfx Voodoo5 6000 AGP (HiNT Rev.A3 3400) prototype
Edit: Also attached the file here. There indeed seems to be an issue with Ryzen cpus.
Thank you very much teleguy! Results: 3DMark2000mmxchecknegative.exe shows the same MMX error, while 3DMark2000mmxcheckpositive.exe starts up the GUI and benchmarking initially works, but crashes after the helicopter benchmarks.
The demo mode (the thing I'm actually after, because I love the 3DM2000 demo mode!) crashes in the exact same way upon startup. It shows several errors like this one:
The only thing that changes between the error messages is the hex number. I'm thinking the data shouldn't be corrupted, it's the same installer I've always used. I ran a quick MD5 on the setup program: