Author Topic: forget. I just lost 5 hours of work.  (Read 1480 times)

I was working for the last 5 hours on a C++/F#/Lua database system and server communication thing in Visual Studio,  I took a break to play Warzone 2100 with Talent74, then the game shut off, Visual Basic shut off (Without saving) and the laptop said "forget YOU, I UPDATE MYSELF WITH stuff YOU DON'T EVEN USE", it installed about 5gb of grab from Sony Care, Microsoft Visio Viewer 2010 (What the forget is this stuff), IE8 updates (I don't have IE8 installed) and some stuffty Best Buy bloatware that came with the laptop.

Disabled automatic updating, uninstalled most of the stuff that came with the laptop.

I'm. loving. Pissed.

I always disable automatic updates and have it set to "download everything but install when I want".  Then it'll prompt you if you want to install updates then shutdown when you shut down.

Save early, save often.


I've lost over 12 hours of work before, weirdest part is I got over it the next day

Save early, save often.

I didn't think my laptop would choose to forget itself sideways with a cactus today, I installed updates about 5 minutes before I started.

Windows Live Essentials 2011 does this kind of stuff to me too. I'd be playing TF2 and having a good time with my buddies, then my computer would stuff all over itself. It would crash, so I would have to turn it back on, and I find out that Windows Live Essentials 2011 is the cause.

No offense but how do you work for five hours and never save?

No offense but how do you work for five hours and never save?

When I'm coding, I don't think about saving. I think about coding.

Get into the habit of pressing Ctrl+S so often you don't feel complete when you don't.

Get into the habit of pressing Ctrl+S so often you don't feel complete when you don't.
This.

I know your pain, but all that can be said is to save often

I know your pain, but all that can be said is to save often
This.

Well this is completely your fault for not saving. Especially since Visual Studio will autosave the project for you if you even try to compile anything no matter how bad.

I would say to do CTRL+S after each line of coding.