beermat: (Default)
greg elkin ([personal profile] beermat) wrote2003-11-04 11:39 am

(no subject)

argh, fecking Word just aborted "memory could not be read" and took my last 3 hours of edits with it.
grumble rumble grrr. lost. gone. It's in my head but they were nicely down and made sense.
this Win2K system is really overdue for a total re-install. And this time I'm not furkling around with logomanager / nokia PC suite / bluetooth drivers on it...

And I guess I should turn autosave back on ...

[identity profile] hazeii.livejournal.com 2003-11-04 04:17 am (UTC)(link)
Word is completely lethal these days, it just seems to explode for no reason from time to time. Mind you, not everyone has the problem and I'm pretty sure it's down to changing *any* of the default options. In particular, I know if you turn off all the auto features, it'll ocasionally detonate when you backspace at the start of a line.

I guess it's down to the way they code...write crap and test extensively, fixing up the problems as they surface. So if you go down any of the less tested paths, you get to test the bits they couldn't be bothered to.

[identity profile] orddu.livejournal.com 2003-11-04 10:06 am (UTC)(link)
Excel, on the other hand, is actually a decent product and 99.99999% of the time does exactly what it's meant to. I hardly ever crash it, and I really *do try*!

[identity profile] hazeii.livejournal.com 2003-11-04 03:28 pm (UTC)(link)
To each their own...personally, I find Excel to be a completely useless product.

But then, maybe that's because I stopped using spreadsheets with Lotus 123 :)

[identity profile] hazeii.livejournal.com 2003-11-04 03:30 pm (UTC)(link)
It's almost worse if the explosions are sporadic. At least if it explodes reliably, you remember to save a lot. But Microsoft can't even get that right.

Oh, rely on 'autosave'? Ha. Ha.