Unless it's an SSD...
And SP1 failed to install on the VM after that little experiment so I don't know if it did more permanent damage that just isn't immediately obvious...
Well I definitely wouldn't trust it after that anyway.
Unless it's an SSD...
And SP1 failed to install on the VM after that little experiment so I don't know if it did more permanent damage that just isn't immediately obvious...
Well I definitely wouldn't trust it after that anyway.
What OS are you doing this on, Nothinman?
That has to be the best commit in history.
I'd put the race condition that caused the 2003 Northeast blackout that affected > 50M people ahead too.Well, maybe third, after the metric-to-english conversion error that sent Mars Lander into the planet's surface at orbital velocities, and the missing semi-colon that brought down AT&T's whole network back in the 80's.
Well, maybe third, after the metric-to-english conversion error that sent Mars Lander into the planet's surface at orbital velocities, and the missing semi-colon that brought down AT&T's whole network back in the 80's.
I've always suspected the metric-to-Imperial bug was just smoke covering up some even-more-embarrassing SNAFU on NASA's part. No evidence to offer, but it seems like the kind of thing that would be caught pretty damn early.
The bug that caused F22 Raptor's all systems to go down when crossing the international date line was also quite a funny one. Talk about the importance of testing corner cases 😛
http://www.dailytech.com/Lockheeds+F22+Raptor+Gets+Zapped+by+International+Date+Line/article6225.htm