Phil Ashby wrote:
Hi everyone,
I've just upgraded to OOo 1.1.5 from 1.1.1, and wanted to draw people's
attention to an odd issue that caused me several minutes grief before I
found out what was going on:
I downloaded, and unzipped the install archive as a normal user on my
Win32 (XP/SP1) platform, then I logged in as the Administrator to
perform the upgrade, which promptly crashed after the initial dialog :(
Only after I deleted the install folder, and unzipped the install
archive again as Administrator did the setup program run without
crashing. I'll blame Windoze hideous file permissions mechanisms for
now, but it might be nice if the setup program explained why it couldn't
do it's job rather than just bombing out :)
Cheers,
Phil.
It is a function of the OS to trap and report errors at that level. If
no error code is returned to the program calling for a service (hard to
do when the OS crashes the system), how do you propose that OOo or any
other apps report the cause? Also, and correct me if I'm wrong, the msi
installer is from Redmond not OOo. Seems to me you're blaming the wrong
folks for the cause of your installation problem.
If you have a solution to the problem of reporting errors from an OS
that has seized, I can think of at least one purveryor of bloatware that
would probably make you very rich. That is, if they didn't just sue you
for exposing yet another weakness in their products.
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
