Lucky you, I've had several. Listening to Security Now, it appears the most secure and stable way of running windows XP (or Vista when it comes out) is under OSX.Plus you get the great Apple hardware etc.When I have a spare couple if thousand pounds I'll be gettin' me a MBP. Or maybe the next time I fly to the states. Whichever comes first.
Alright, you are an idiot. I mean at BEST you're an idiot. At worst, you may have a severe form of retardation. First of all, Windows XP is rebooting immediately in the background. Parallels simply isn't showing you that. I'm not sure why, but they're not. Moreover, setting Windows to automatically reboot upon a blue-screen is quite literally the most useless feature ever inserted into the code. If the machine reboots before you can see where the error is, how are you to diagnose the issue? I mention this because I had a server configured that way, and it was impossible to find what driver was causing the hang.So, you should go in for a checkup. You know, just to get the retardation thing sorted.
"Ok. So Parallels causes a BSOD. I haven't seen one on a PC for years. I think it has more to do with implementation than a problem with XP. In this case, anyway."I think he forced it for the video, there is a registry tweak you can to to control BSODs for testing purposesParallels didn't cause it
"Moreover, setting Windows to automatically reboot upon a blue-screen is quite literally the most useless feature ever inserted into the code."Uhh, what if you have a machine that needs to stay up unattended? What are you going to do?"If the machine reboots before you can see where the error is, how are you to diagnose the issue?"Load the crash dump into WinDbg.
Closed AccountOct 3, 2006Submitter
thanks for the clarification ---
kevnacaOct 3, 2006
Apparently you haven't heard about the Mac Mini or Mac Pro. You don't have to buy expensive Apple monitors my friend.
Closed AccountOct 3, 2006
I have the BSOD once a week or so, its always something new, when i least expect it on the windows box
philukOct 3, 2006
Lucky you, I've had several. Listening to Security Now, it appears the most secure and stable way of running windows XP (or Vista when it comes out) is under OSX.Plus you get the great Apple hardware etc.When I have a spare couple if thousand pounds I'll be gettin' me a MBP. Or maybe the next time I fly to the states. Whichever comes first.
drdabblesOct 3, 2006
Alright, you are an idiot. I mean at BEST you're an idiot. At worst, you may have a severe form of retardation. First of all, Windows XP is rebooting immediately in the background. Parallels simply isn't showing you that. I'm not sure why, but they're not. Moreover, setting Windows to automatically reboot upon a blue-screen is quite literally the most useless feature ever inserted into the code. If the machine reboots before you can see where the error is, how are you to diagnose the issue? I mention this because I had a server configured that way, and it was impossible to find what driver was causing the hang.So, you should go in for a checkup. You know, just to get the retardation thing sorted.
wasternOct 3, 2006
"Ok. So Parallels causes a BSOD. I haven't seen one on a PC for years. I think it has more to do with implementation than a problem with XP. In this case, anyway."I think he forced it for the video, there is a registry tweak you can to to control BSODs for testing purposesParallels didn't cause it
mancatOct 4, 2006
"Moreover, setting Windows to automatically reboot upon a blue-screen is quite literally the most useless feature ever inserted into the code."Uhh, what if you have a machine that needs to stay up unattended? What are you going to do?"If the machine reboots before you can see where the error is, how are you to diagnose the issue?"Load the crash dump into WinDbg.