|
|||||||
| Windows XP / 2000 / NT / 9x Forum Discussion for Windows operating systems from XP right back to the very beginnings! |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
DriverHeaven Newbie
Join Date: Aug 2006
Posts: 10
Rep Power: 0 ![]() |
Windows 2003 issues with 3DMark 2001
When i try to run it it says i need DirectX 8.0 and i have DirectX 9.0c installed. I already used the patch for it but the error keeps hapenning. When i go look at the error.log it says i have DirectX 6.0 and in 3DMark 03 it says i have DirectX 6.0 too !
In Windows XP Pro it both runs fine. |
|
|
|
|
|
#2 |
|
Delete Me
Join Date: Mar 2004
Posts: 14,648
Rep Power: 0 ![]() ![]() ![]() ![]() ![]() ![]() |
you don't have video accelleration enabled, as it's off by default in 2003, due to it's being a server OS.
In system properties, set processor and memory to optimize for Programs, instead of Cache [default for both is cache/background apps] Then in advanced display properties, set hardware accelleration to full. Reboot. Run "dxdiag", and enable DirectDraw Accell., Direct3D Accell, and if yer card supports it [non Intel IGP], AGP Texture Accell. NOW, you should be off to the races ![]() Oh, and when askign questions like that, you'll get a lot fo answers like "server 2003 isn't for that"....that is not the case. Server 2003 is tuned for other things out fo the box, but is actually a newer kernel revision of the NT kernel, and other then that, is just a stripped down to the bone fast as all get out version of XP. NOTE - Sound is also disabled by default in Server 2003...open audiop properties to enable it [requires reboot] |
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Aug 2006
Posts: 10
Rep Power: 0 ![]() |
Quote:
|
|
|
|
|
|
|
#4 |
|
Member
Join Date: Mar 2003
Posts: 5,989
Rep Power: 71 ![]() ![]() ![]() ![]() |
what i have seen people saying is that they couldn't run 3D Mark 2001 on the OS with DX9.0c, they said, according to futuremark it messes up the version check and an error will occur when they're trying to load the program... but haven't yet seen a solution that's going to fix it.
|
|
|
|
![]() |
| Thread Tools | |
|
|