All off topic discussions go here. Everything from the funny thing your cat did to your favorite tv shows. Non-programming computer questions are ok too.
Now why on earth is there a registry key to enable a manual BSOD? For debugging the BSOD itself, I guess... but still it seems a slightly odd thing to leave in RTM code.
Midas wrote:Now why on earth is there a registry key to enable a manual BSOD? For debugging the BSOD itself, I guess... but still it seems a slightly odd thing to leave in RTM code.
Yes, it's for debugging. During blue screen, system dumps memory to harddisk (in windows folder), so it could be useful dor debugging, or stealing information
Midas wrote:Now why on earth is there a registry key to enable a manual BSOD? For debugging the BSOD itself, I guess... but still it seems a slightly odd thing to leave in RTM code.
Yes, it's for debugging. During blue screen, system dumps memory to harddisk (in windows folder), so it could be useful dor debugging, or stealing information
Thanks. But I think one of us (possibly me) is misunderstanding the other. I know what a BSOD is - it just seemed an odd thing to want to cause the computer to crash - unless, of course, you wanted to debug the error reporting system (as I said). In the case that it was for debugging, why leave it in the release-to-market code?
Well, If you want BSOD, MS have anohter "approved" solution
Dump Swicth !
I've got an ISA card dump switch, it came from an old NCR server, I thought it was just for NCR's UNIX that was installed. Has AT&T copywrite printed on the board.
It would be a really useful thing for OS developing I think.