Apache OpenOffice (AOO) Bugzilla – Issue 7215
install fails on Windows 2000 SP3
Last modified: 2013-08-07 15:26:39 UTC
Install fails on Windows 2000 SP3 during registry update phase. It cannot register .dll files in the registry.
James thanks for posting. Could you please attach the setup.log to this issue? It should be located in <path to OO>\program\setup.log. Could you also describe the hardware OO is running on ( video, processor, motherboard, etc ). Thanks.
Created attachment 2591 [details] setup log from failed install
Processor: 1.8 GH Pentium IV Video: NVidia Geforce2 MX 100/200 RAM: 640 MB
*** Issue 8360 has been marked as a duplicate of this issue. ***
*** Issue 8444 has been marked as a duplicate of this issue. ***
We still can't reproduce this error. The only hint I can give is, that we have seen this once on a W2K machine with a defective Fat32 partition. We don't know how to damage a Fat32 this way to reproduce. BTW: If this case is right, I would prefer to see this as a 'not an OOo problem'. I know also that this not very satisfying, but up to now I can't help it.
I got this issue too on my system. I found if I only installed the Writer part of OO I was able to get the Installer to complete.
*** Issue 8525 has been marked as a duplicate of this issue. ***
*** Issue 8689 has been marked as a duplicate of this issue. ***
I also have this issue with Windows XP Home edition.
I recently tried reinstalling under userid=Administrator and it worked! My original install was using a userid with blanks in the userid (with admin privilege), so my guess is that OO install doesn't like blanks in the userid.
Hi James, Thanks for you help. I've tried to reproduce and created a user with a login with a blank. But OOo won't crash. Do you have any special characters like "§$%&" in your account name?
*** Issue 9864 has been marked as a duplicate of this issue. ***
*** Issue 10107 has been marked as a duplicate of this issue. ***
Hi James, thanks for your support. I still can't reproduce. OOo 1.0.1 and 1.0.2 are working fine, even with blanks or special characters in login name.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.