you need to copy ddraw.dll from the same System32 folder from WinFLP and copy in the 3DMark folder

user8989 wrote:

Now I do know that at this point that old version of 3dmark will complain about he wrong of directx and that this issue can be resolved by placing a copy of the 'ddraw.ddl' into the 3dmark folder.

That's misleading information. 3DMark 99 has a bad check for DirectX version, which can be avoided by either setting Windows 98 compatibility mode or using patched files that also solve some other issues. They can be downloaded from here.

Also, VirtualBox virtual machines don't support 3D acceleration for Direct3D 7 and older, so even if you solve ddraw.dll problem, it won't work unless you find the replacement ddraw.dll that converts DirectDraw/Direct3D 6 calls to something else.

weldum wrote:

you need to copy ddraw.dll from the same System32 folder from WinFLP and copy in the 3DMark folder

What's that supposed to do? ddraw.dll will be loaded from System32 anyway if it's not found in 3D Mark folder.

in my experience, in all NT based versions of windows 3dmark 99 will not load the file from system32

It loads just fine on a system that functions properly.

UCyborg wrote:

That's misleading information. 3DMark 99 has a bad check for DirectX version, which can be avoided by either setting Windows 98 […]
Show full quote

user8989 wrote:

Now I do know that at this point that old version of 3dmark will complain about he wrong of directx and that this issue can be resolved by placing a copy of the 'ddraw.ddl' into the 3dmark folder.

That's misleading information. 3DMark 99 has a bad check for DirectX version, which can be avoided by either setting Windows 98 compatibility mode or using patched files that also solve some other issues. They can be downloaded from here.

Also, VirtualBox virtual machines don't support 3D acceleration for Direct3D 7 and older, so even if you solve ddraw.dll problem, it won't work unless you find the replacement ddraw.dll that converts DirectDraw/Direct3D 6 calls to something else.

weldum wrote:

you need to copy ddraw.dll from the same System32 folder from WinFLP and copy in the 3DMark folder

What's that supposed to do? ddraw.dll will be loaded from System32 anyway if it's not found in 3D Mark folder.

Thank you for that one hint.
However when I did try to run 3DMark 99 it returned a message telling me that it needs Directx 6.1.
Strange part about it is that the version of ddraw.dll is 5.3.2600.5512

@UCyborg thank you for that screen shoot of your working XP machine 3dmark machine.
Can you please share with us if VM which version of XP that is ?
Home, Pro, or FLP
which SP major is installed on it.
So I know which bits I need to maybe reconstruct eg built my own VM.
thx,user8989

I just tried that 3dmark Patchpack and replaced all files provided for 3dmark99.
however 3dmark kept telling me 'Memory dump only available in debug builds'
Also when I do open the properties for the 3dmark.exe file I do not see any compatibility tab.
I that normal in Winflp ?I do not remember anymore.
thx,user8989

user8989 wrote:

Strange part about it is that the version of ddraw.dll is 5.3.2600.5512

A lot of system components have the operating system's internal version number.

user8989 wrote:

Can you please share with us if VM which version of XP that is ?

XP Pro SP3

Also tested on FLP with SP2. I copied its files (which include my patched files) from my main installation. Only issues were the usual glitches due to running in a virtual machine.

user8989 wrote:

however 3dmark kept telling me 'Memory dump only available in debug builds'

I've never seen this one before. Usually, if you tried it in VirtualBox, it would complain something along the lines of graphics accelerator not supporting DirectX 6.1.

user8989 wrote:

Also when I do open the properties for the 3dmark.exe file I do not see any compatibility tab.
I that normal in Winflp ?

Yes. Read my post in this thread on MSFN.