I've had great success using 3Dmark 2001se on modern hardware, but i have not tried anything older, Though i know if you have more than 3gb's of system ram you will get an error but it's skip able.

Hrm, I haven't tried it on Win7, but I did get it working in XP with my 9800GX2, did not try with my 580, so I think it's probably an issue with how much ram the video card has. I don't have my installer handy or I would have a look and see if I can get it to run. It's probably a simple patch to allow it to do so.

Was able to get 3dMark 99 Max running via the instructions here...
http://community.futuremark.com/forum/showthr … l=1#post1281703
...though 7zip will now also extract the installer exe.

Still hoping for a fix for 3dMark2000.

I got 3dMark 2000 to work on my 3 GB 7970 by modifying SystemInfomfc.dll. Just put the file into the benchmark directory. You'll have to use Win 98 compatibility mode and accessing the systeminfo menu will result in a crash.

I created a new version with working systeminfo menu.

Thanks teleguy.

With your patch I no longer get the "4MB or more video memory" error but instead get a similar error "3dMark2000 requires 64MB of memory to be able to run."

Any chance you can further patch it to work around systems with multiple gigabytes of memory?

kolano wrote:

Thanks teleguy.

With your patch I no longer get the "4MB or more video memory" error but instead get a similar error "3dMark2000 requires 64MB of memory to be able to run."

Any chance you can further patch it to work around systems with multiple gigabytes of memory?

Using Windows 98 or XP compatibility should fix that.

Thanks again. I was able to get it running again this afternoon thanks to you, "37700 3D marks".

So the issue was that I'm also trying to run it off of a network share. Apparently the Compatibility Mode settings can't be applied to apps on network shares. I found a few "workarounds" but none of them actually seem to work, which is why I though it was still broken in Win98 mode.

Not sure if anyone has a working workaround. Thus far I've tried...

• Launching with a bat file that has Compatibility Mode set on it:
  http://www.sevenforums.com/network-sharing/14 … -drive-app.html
  Copy code to clipboard

  1@echo off
  2start V:\Demos\Commercial\Futuremark\3DMark2000\3DMark2000.exe
  3exit 
  

• Launching with a bat file that sets an environment variable to set Compatibility Mode:
  http://netport.org/?p=1616
  Copy code to clipboard

  1@echo off
  2set __COMPAT_LAYER=WIN98
  3V:\Demos\Commercial\Futuremark\3DMark2000\3DMark2000.exe
  4exit
  

  or
  Copy code to clipboard

  1@echo off
  2set __COMPAT_LAYER=WIN98
  3start V:\Demos\Commercial\Futuremark\3DMark2000\3DMark2000.exe
  4exit
  

  This seems to no longer work /w Windows 7. Though it might up to Vista.
• Setting Compatibility Mode for the app directly in the registry:
  https://www.corelan.be/index.php/2009/04/27/f … ws-2008-server/

Since it seems as though it may not be possible, I may just break down to a revised bat that would copy things to a local drive and run them from there though it's not really the approach I'd prefer.

Two other bits of feedback on the patch.

• The 64Mb texture test fails to run.
• It would be nice if some additional resolutions (i.e. above 1280x720 and 16b color) could be made available.

It's possible to apply compatibility mode to apps on network shares through Microsoft's Application Compatibility Toolkit. Actually you don't even need the full Windows compatibility mode, just "GlobalMemoryStatusLie" and a parameter of 1536 for instance should be enough.

kolano wrote:

Two other bits of feedback on the patch. […]
Show full quote

Two other bits of feedback on the patch.

• The 64Mb texture test fails to run.
• It would be nice if some additional resolutions (i.e. above 1280x720 and 16b color) could be made available.

The texture test fails because there is not enough AGP memory. Currently I don't know how to fix that.

Resolutions seem to be dependant on (video) memory size. XP compatibility mode allocates more memory than 98 compatibility mode so more resolutions are availabe.

My motherboard has an option for "Optimize for Legacy Benchmark Programs" wonder if that would fix it.

I managed to remove the restrictions for the texture rendering tests.

teleguy wrote:

I managed to remove the restrictions for the texture rendering tests.

I can confirm 64Mb Texture test now works with my nVidia GeForce 580.

I was able to get an expanded resolution list /w WinXP instead of Win98 mode, but there seem to be a number of remaining oddities...

• My native 2560x1600x16/2560x1600x32 modes aren't shown.
• 2560x1440x16 mode is shown, but selecting that mode results in "3DMark could not initialize your 3d Accelerator. Try to downgrade your display settings. DirectX Error Message: Create Device: DDERR_INVALIDOBJECT".
• The highest 16b color mode that will run is 2048x1536.
• 32b color modes top out at 1920x1200, which does run at least.
• CPU test is unable to run in 32b color modes (Though perhaps this was always the case).

kolano wrote:

I can confirm 64Mb Texture test now works with my nVidia GeForce 580. […]
Show full quote

I can confirm 64Mb Texture test now works with my nVidia GeForce 580.

I was able to get an expanded resolution list /w WinXP instead of Win98 mode, but there seem to be a number of remaining oddities...

• My native 2560x1600x16/2560x1600x32 modes aren't shown.
• 2560x1440x16 mode is shown, but selecting that mode results in "3DMark could not initialize your 3d Accelerator. Try to downgrade your display settings. DirectX Error Message: Create Device: DDERR_INVALIDOBJECT".
• The highest 16b color mode that will run is 2048x1536.
• 32b color modes top out at 1920x1200, which does run at least.

Same here. No idea why that happens.

Edit: Apparently that's the highest resolution DirectX 7 allows. The only way to go any higher is using a wrapper or replacing the renderer.
https://www.google.de/search?q=directx+7++204 … OOpM8rDPISWgKgM

CPU test is unable to run in 32b color modes (Though perhaps this was always the case).

I think it's supposed to be like that. I'll be able to test the benchmark on a few older systems on monday and see what happens.

(Deleted)

Just for the records I guess the "you have to have at least 64 MB of memory" error could be fixed just with one of these

New version with a few modifications.

-system memory checks removed->compatibility mode should no longer be required
-4 MB vram message bypassed in a different way so that the patched SystemInfomfc.dll is no longer needed->settings menu should now reflect the actual video memory size
-all possible resolutions should now be available

teleguy wrote:

New version with a few modifications. […]
Show full quote

New version with a few modifications.

-system memory checks removed->compatibility mode should no longer be required
-4 MB vram message bypassed in a different way so that the patched SystemInfomfc.dll is no longer needed->settings menu should now reflect the actual video memory size
-all possible resolutions should now be available

Thanks for your work here,teleguy.

• Can confirm things now seems to run fine without compatibility mode.
• All resolutions are now listed. Though it might be better to limit them to those that are 2048px or less in dimention, as the "DDERR_INVALIDOBJECT" error still occurs if attempting to use higher resolutions (i.e. 2560x1600).

teleguy wrote:

New version with a few modifications. […]
Show full quote

New version with a few modifications.

-system memory checks removed->compatibility mode should no longer be required
-4 MB vram message bypassed in a different way so that the patched SystemInfomfc.dll is no longer needed->settings menu should now reflect the actual video memory size
-all possible resolutions should now be available

Thank you very much for the patch !
And you can do the same patch for 3DMark 2001SE? When it starts not written a mistake and did not include compatibility mode?