[EMAIL PROTECTED] wrote:
Thanks for the tips.
After I posted, I did some more searching in the groups and
found that the cause of some OO problems is leaving bits of old installs in
the system.
Perhaps showing my lack of knowledge of modern Windows systems, I find
this a little odd. From Windows NT onwards the only thing that should
kill the system completely as you described is severe system problems
such as an OS bug or hardware error, but an error in a user application
like OOo should be trapped and prevented from affecting the system or
any other running applications.
I was thinking your problem may be an error in physical memory, but now
I'm wondering if you have a bad disk block. I just don't know if this is
enough to kill Windows, or whether XP (or NTFS or the disk driver) can
automatically mark bad disk blocks as not unusable.
Have you tried running XP's disk check and defragment tool?
Ross
So, I made sure the previous version was uninstalled and old oo files
removed.
Then I rebooted then re-installed 2.0.4.
I rebooted once more after the install just because - and I can use the
menu bar.
I vaguely remember having to do this some time ago on another OO version.
Thanks again.
--regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
