Well, I at last have a working PC and a good backup. Acronis True Image 10 is awesome.

Moving swiftly on, delay loaded DLLs are also awesome. My "engine" now supports delay loading of D3D and D3DX and gives pretty errors if either DLL is AWOL. Well, it does for D3DX, I don't have any PCs withouth D3D9.dll on them to test...

Next up, I'd like to get some call stacks logged in my memory manager, which would be nice, and would mean I can get rid of my NEW macro (Which logs the current file, line and function, then calls new) completely.

I also need to get my timer class working, which will use QueryPerformanceCounter. Which means I need to deal with all the associated problems it has, such as the timer skipping backwards or forwards several seconds, it returning different results when running on multiprocessor or dual core systems, etc.
Should I really lock my main thread to CPU 1? That seems to be the usual way to do it, but it sounds like a terrible waste of the main thread...

timeBeginPeriod(1);

timeEndPeriod(1);