Corrupt Files

[Kothnok]

Somehow I managed to corrupt WoW so badly that it reverted to 2.0.0.

The patch from 2.0.0 to 2.2.x is 450megs.  Maybe I'll be on later... maybe....

[fiere redfern]

Owies =( Good luck, Koth! Hopefully I'll see you in game when I get a spare moment or three...

(yet another all-nighter in the ECE labs. Whoooooo!)

[un4]

Hope to see you soon

[Jandris]

Ouch - feel your pain Kothnok. Hope everything gets fixed quickly.

[Buzan]

Dang Koth that sucks .

Hope it will be a fast and smooth fix for you .

[Threlin]

Hope things are improving, Koth! Sorry about your difficulties. 

[Kothnok]

got it back up and working, thx all 

[Buzan]

Hehe good to hear how did you manage to mess it up so bad though ?

[Kothnok]

... how did you manage to mess it up so bad though ?

How can I explain that one easily?  Hrm...  let me just say what I learned from the experience...

• When swapping hard drives, always shut down the OS (no sleep, no hibernate)
• When swapping hard drives, ensure you remove the battery
• Failure to do both of the above keeps the OS alive, but asleep, in memory
• Every OS I've worked with when encountering the above situation will crash, but nothing more serious than needing to reboot
• MS Vista, unlike it's predecessors, will try to wake up even if the hard drive it went to sleep on is completely different
• Vista eventually pukes once it realizes it no longer exists on the hard drive
• Vista's infinite wisdom dictated that I needed to save it's puke and it dumped memory to the hard drive
• Vista caches what it thought the hard drive should look like, so when it dumped the contents of my memory, it did so based on a folder structure completely alien to the drive that is actually present.

End result: 2Gigs of my hard drive was overwritten in random spots, corrupting a unknown bunch of files (most of which happened to be WoW related)