Quote: "Which is the one used by DBPro 6.6b. So it should work."
It does!
Moreover, I really hope that DBP-6.7 or
whatever-it'll-be-named will use d3dx_31.dll too, because there are some annoying bugs in buglist that I hope will be fixed!
Quote: "But who's still using Windows 98 these days anyway? Man, it's ten years old!"
SE-edition (the working one) of win98 is less then ten years old!
And it's just 1.5 years older that xp... And why not use it? It's more finalized than xp (xp is still at beta-stage, IMO)... It's compatible with DOS, win16 and even with win-98 (unlike xp)!
There are lots of working projects to make it compatible with artificial xp-only limitations like non-working installers and drivers for USB-junk... (Example:
http://www.msfn.org/board/Windows-9x-Member-Projects-f91.html)
Besides, there are not so many people among my friends who use xp or (yack!) vista... Only those who were stupid enough to buy a new computer without asking for a good advice about hardware-compatibility!
But, I went off-topic... Back to Computer_Might-detection...
IMHO, checking of users CPU and it's MHz-speed is useless... Because of different CPU-architectures MHz-speed may not show the real power of the system... For example, in most tests my P-III-1266 with win98SE is as fast as P-IV-2000 with xp... Besides, games or 3D-demos usually require more GPU-power than CPU! I think that it's better to measure power of PC with FPS-count test with some sort of heavy 3D-demo... Such test will be compatible with any win32-OS and will not scare users... IMNSHO, of course...
~~~/\==/\-