It's too bad that Windows isn't like AmigaOS in the sense that your game can completely takeover the system while it's running (I think there's a seldom used Windows API function called 'CriticalCodeFollows()' or something like that. Not sure if it does the same thing) and then return control back to the OS when it's done. What do you need background tasks for anyways when you're playing a fullscreen FPS? It'd be nice if you could at least force Windows into 'safe mode' before running your game, eh? This would at least reduce the amount of nonessential crappola running in the background and stealing cycles...
Russell
Russell