…and in a sick way, it was really kind of cool.
I’ve been playing with Google Chrome for a couple days.
But because Chrome is only available (natively) for Windows right now, I have to run a Windows XP virtual machine on my Linux machine (which still runs openSUSE).
And since I hardly ever need to use Windows anymore, the VM needed several updates, see?
So, I’m a-browsin’ and a-updatin’, and really enjoying how well the browser performs–especially with AJAX–while wondering how much the snappiness will decrease when Chrome is laden with more full set of browser features…
…and then Windows Update completes its work and tells me to reboot.
So, I click the “Close” option and skip the “Restart” so that I can do a Shutdown-and-Apply-Updates instead, because that’s how I want to do it, see?
But Chrome doesn’t want to close down. In fact, it stops responding altogether. Now Google Chrome is in a stare down with Windows shutdown.
Well, you know what Windows does to programs that don’t stop. That’s right, it puts up dialog messages. This one essentially says, “He don’t wanna go, boss. Can I kill’im?”
But before I can even respond, Chrome frickin’ blue screens Windows. As the kids say these days, >Snap!<
Next thing I know, I’m watching the VMware POST process emulation, and hoping that my VM is not hopelessly corrupted.
Good old nostalgia…I haven’t seen a Blue Screen of Death on my own machine in ages.