• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Does DX10 run on windows XP ?

Now I'm really confused as the last processors I used on this test were AMD twin cores namely the 4400 and the 4800
and both of them got between 1 and 2 frames as well
so this means a quad core running at the same frequancy as the 4800 can only match it in performance ?
and the 4400 was 200 Mhz slower yet pretty much matched the 4800 and now it seems the q6600 isn't that mutch better maybe half a frame

most interesting and a bit disheartening
Repeat after me, benchmarks are not games, benchmarks are not games, benchmarks are not games :p

The framerates in 3D Mark CPU test are about as useful an indicator of CPU performance as measuring the top speed of a car by visually observing it driving round a race track.
 
There is a modded dx10 you can install on xp. Google it.

Hopefully my blog post over at OCN will clear up the misunderstandings about being able to run DX10 on Windows XP. In short you can't.

t4ct1c47 said:
Take a seat everybody, uncle t4ct1c47 is going to give you a brief history of why misinformed people think that DX10 will work on XP.

When Vista was first released, Microsoft tried to take advantage of every possible selling point. When they released Halo 2 they made it so that the game would only work with Vista. Halo 2 never needed DX10, Microsoft simply wanted another reason to persuade people to upgrade from XP.

When you first install most programs the installation process will perform a few basic checks to make sure that your system is of sufficient spec. For example, when you try to install Crytek's Far Cry onto an old Windows 95 machine you will get an error message saying that the operting system isn't supported. In the case of Far Cry, this was true, as the game needed DX8 to run and Windows 95 doesn't support DX8.

In the case of Halo 2, a game that was originally released on Microsoft's X-Box which didn't use DX10, there is a similar check to make sure that the operating system is Vista. However, as you've no doubt guessed if the original console game didn't use DX10, then the PC version won't need it either. The only reason Halo 2 doesn't work on XP is because of one of the checks performed when you attempt to install the game. There is crack available, that bypasses this system check, and allows you to play Halo 2 on XP.

Pretty much since that crack came out people started to think; "If one game that requires DX10 can work on XP so can others". But that's the point, Halo 2 never required DX10. Now when it comes to people who claim that they were able to install the D3D10 API onto Windows XP, there is a big difference between physically copying the files to the machine's HDD and actually getting the operating system to run them. Although there is a way to make it so Windows XP's DXDIAG reports the DirectX version as DX10, it doesn't mean that the machine is actually running DX10.

The Direct3D API was specifically designed to run on Vista. Attempting to migrate an entire API from one system to another is no mean feat, if this was the case, Linux would not still be relying on OpenGL. I hope that is a clear enough explanation for you.

http://www.overclock.net/blogs/t4ct1c47/641-dx10-windows-xp.html
 
There are several fallacies in your quoted post above...

Just because a game doesn't use DX10 on a console doesn't mean they didn't decide to implement it using that on the PC.

And the reason most other APIs like Direct3D haven't been ported to linux is much more than just the complications of porting an API, theres a bucket load of legal issues amongst other things.

Actually - there are "working" ports of DX10 to XP... however (a) they break some native windows XP compatibility - tho thats something that could be worked around with clever programming. (b) they only support a limited number of features and methods and take quite a lot of title specific hacking to get it working - last I checked there were application specific builds for XP but to run another DX10 title you'd have to install an entirely seperate build.

So yes in short at the moment (and for the foreseeable future) you can't really run a useful build of DX10 on XP - its not impossible someone will put in the leg work to get it running.
 
Back
Top Bottom