Crash kills over two hours of work

I was putting the finishing touches on the blog entry that was supposed to go here when I finally opened up one link too many and the system froze, taking down not only the web browser I was using to post, but the copy buffer containing the full copy of the text as well.

It's my own fault; I had been doing some game-playing before I started writing, so I was still in Microsoft Windows, and I chose to start writing from there rather than rebooting to do it. I know better.

Still, I hate hate hate hate hate hate hate hate Microsoft. You'd think that just killing an application wouldn't kill the copy buffer for the OS. I had a full copy in memory from a few minutes prior, and could have recovered if I had been allowed to paste into Notepad or anything else. Anything I tried to paste into froze as well. So much for my simple attempt to safeguard myself against exactly this. Lesson for the day: if it's not completely flushed to disk, it might as well not exist.

It's this kind of thing that leaves you completely disheartened about writing. Two and a half hours represents about a third of my daily free time.

Trackback URL for this post:

http://www.resonant.org/trackback/472

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

none

" completely flushed to disk, it might as well not exist"...???
You've been listening to too many Johnny Cochran closing arguments!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.