Original Post
Will ignore grammar and try to convey the point with short sentences.
I log in as administrator, run program. Program changes resolution, then crashes, but does not exit. I multitask. Resolution remains messed up. I try to terminate the application, which is "not responding". Program pops up error message, which cannot be viewed because the resolution is messed up. In fact, no window can be viewed - just the taskbar is visible - the program (or whatever) is rendering a gray image over the rest of the screen. Program will simply not exit. I try to treminate program''s process. OS gives me error: "access denied". I press down power off until computer shuts down.
Erm... why? This happens to both perfectly normal (legitimate) applications as well as sometimes to my own programs (usually still in the debugging phase). Pressing power off is the only solution because then Windows will run an ultra-quick shutdown procedure and will restore nicely when booted up the next time. Pressing reset would exit unconditionally and probably cause several disk errors, which could easily mess up the OS as well as any data on the hard drive.
What angers me most is that the process cannot be killed because I, the administrator, do not have the access rights, and it won''t time out on its own either. Basically, the computer just locks up because you pretty darn much can''t do anything afterwards... Running a Win2k here. Any suggestions what to do in such a case? Could this be some debugger conflict?
