Directx 10 Descargar Windows 64 Bits
Kanisha Dezarn
DirectX 10 RPC - this is a new patch allowing to increase compatibility of new games and programs with Windows XP and achieve noticeable increase in speed and quality graphics in games. The same patch corrects mistakes with the launch of games requiring files DirectX 9.0s and earlier versions. Just when there graphics card with support for DX10 makes those options are available, the next-generation games that before the installation of these libraries were inaccessible. In the version of RPC added new library and corrected many errors, that finally allowed to reach full DirectX 10 for Windows XP.
to the OP - no it isnt possible to use dx10 in xp, but your originaly problem is an error that is caused by a hardware fault, moving to xp will NOT solve this issue. you need to test your hardware for faults, be that ram, graphics card, PSU or motherboard. a quick google will show you how to test for that, if you are unsure how to test these then just ask here.
when xp was in its prime, before vista launched any one that was running windows 95 on a gaming pc would get laughed at. xp is now in the same position windows 95 was in compared to xp. unless your PC isnt capable, it is strongly advised to get windows 7 running on it. and if it isnt capable of running windows 7 you can forget any directx 11 or even direct10 game as they all require modern hardware.
ok, that motherboard wont be the best for overclocking, but it is possible. all you need to do is make sure you are monitoring the temperatures of your cpu and yur motherboard, a program like everest home edition will tell you these temperatures. then you need to download prime95. you restart the pc and go into the BIOS, up the FSB (front side bus) by 5 mhz, save it and exit. boot into windows and run a prime 95 stress test for 20 minutes. if it works fine and doesnt crash, reboot and go into the bios and up another 5mhz then test again. do this untill it gets too hot (dont let your motherboard go above 60, and your cpu above 75) or untill it crashes. if it crashes then go back to the last overclock that was stable. any prob;ems ask on here. dont change any voltages and there is no risk of breaking anything. if you overclock it and it crashes and doesnt boot windows, you can reset the BIOS with the CLRCMOS jumper. the manual for your motherboard will tell you how to do this.
Some time ago I wanted create ISO with drivers and other support software for Virtual Win 95/98/Me. Also, I wanted include Mesa3D and WineD3D to run OpenGL and DirectX application and games (maybe slowly but they'll run). It wasn't as simple as I thought, I hit a wall a few times, but result is a bit complex package contain VGA driver, OpenGL driver (software or hardware), WineD3D wrapper (translating DX to OpenGL) and OpenGlide wrapper (translating Glide to OpenGL).
Software rendering is accelerated by LLVMpipe driver in Mesa3D and hardware rendering is possible in VirtualBox 7.0 and 6.1 though VMSvga/VboxSVGA video adapter (in theory it can work in VMWare and Qemu, but maybe need some work).
To use hardware rendering in VirtualBox you must set Video adapter to VMSvga (switch VM type to Linux because VirtualBox GUI forbids it). Set video memory to 128 MB and check Enable 3D Acceleration. Last step is turn off GPU10 feature, by this command:
If I find some time in those busy times, I'll test this with my Core i3-12100F on both VirtualBox (was always the worst option for 9x, maybe this will change things) and VMware.
EDIT: And maybe I'll throw in my Core 2 Duo E8600 with GeForce 7900 GTX for some native testing...wished the Core i3 worked natively ?
Amazing progress! glchecker.exe says I have hardware acceleration here in VirtualBox 6.0, wonder if using 6.0 could cause additional compatibility issues. Like, many OpenGL and Direct3D apps work, but dxdiag from DirectX 9.0c doesn't show much 3D graphics through its Direct3D tests in Windows 98SE.
I was also reminded why I don't like using virtualization software for games. I tried playing Baldur's Gate II because I would actually prefer to play it in a VM if it could provide a decent experience, but high audio and input latency just makes it a pretty bad experience.
Maybe VMWare is better (or maybe AC97 works better than SB), but last I tried that had audio issues too. At least with Magpie you can use custom scaling algorithms and shaders, which used to be one of the disadvantages of gaming with virtualization software.
SoftGPU is pack of relatively independent components - you can combine VBEMP 9x driver and use my Mesa9x ( ) for OpenGL rendering and my Wine9x ( ) to DirectX -> OpenGL transport. OpenGL rendering will be software only, but on native HW it will be faster than in VM, VBEMP 9x also not having ICD feature, so you must replace opengl32.dll in system. Unfortunately, it will be still slower than your 7900 GTX.
I got a bit confused about the VirtualBox versions - version 6.0 has choose of VGA adapter, so HW acceleration can work (version 5.1 hasn't it). Please try latest version of SoftGPU, you may have encountered the R5G6B5 bug, newer version may work well.
Version 1.7.x was last which were WineD3D was compatible with 2000/XP, and it is closer to 9x, than try to port something newer. Newer versions using accelerated GDI access and can use Vulcan rendering, but it is useless on 9x. Next problem is OpenGL version, newer Wine are faster but needs more advanced OpenGL, but my actual driver has only 2.1 when is HW acceleration is on.
Tested Need for Speed: Hot Pursuit 2 (DX8, 2002). Without -nomovie command line argument it soon freezes, with -nomovie it draws 3D graphics and freezes later when I try to proceed to a race. Same results with Mesa9x. This game can be launched in a window by editing the rendercaps.ini file in My Documents\EA Games. The game doesn't freeze with wine9x dll's put into the exe's folder on Windows XP with VirtualBox Guest Additions installed.
I have successfully installed SoftGpu on Windows 98 VM in Virtual Box 7 (full 3d acceleration) but some actions are very slow, i.e: maximizing and minimizing windows, opening the start menu and other small things like every time a tool tip appears on the close, minimize or maximize window buttons.
Actually, I think I found the solution...just leaving it here for others: modern processors are too fast for Windows 98 (obviously) and setting the processor cap at around 85 or 90% helps with the slowdowns.
I already seen it, problem can be, as you mention it, with too fast CPU to set system timer correctly. But also, I think that problem can be in frequency boost in modern CPU - CPU is sometime very fast and sometime very slow and system timer become confused.