Click on the windows XP start button...then click on run...at the pop up box asking for a EXE to execute type in "dxdiag"
This is a little utility to diagnose DX problems, there are a couple of tests that it will run to check for capability with several of the latest DX versions (your new system might have issues with DX7, which is what Blitz requires)
Generaly when a program (say your game) tries to do something in DX, and DX for whatever reason cannot get the hardware to comply...then DX uses a software backup routine instead, usualy DX will tell you it's doing this...but Blitz doesn't have any way to check that (I'm guessing that debug mode does and tells DX to use other meathods...while your game EXE doesn't have that option, and without an answer DX just does it's best with the software backup routines)...you can find out all about this stuff on the DX website and through the DX SDK.
This is a little utility to diagnose DX problems, there are a couple of tests that it will run to check for capability with several of the latest DX versions (your new system might have issues with DX7, which is what Blitz requires)
Generaly when a program (say your game) tries to do something in DX, and DX for whatever reason cannot get the hardware to comply...then DX uses a software backup routine instead, usualy DX will tell you it's doing this...but Blitz doesn't have any way to check that (I'm guessing that debug mode does and tells DX to use other meathods...while your game EXE doesn't have that option, and without an answer DX just does it's best with the software backup routines)...you can find out all about this stuff on the DX website and through the DX SDK.