Error Opening file for Writing 2.4.1 Upgrade Submitted by pjamme on July 17, 2008 - 9:13am
I have downloaded the 2.4.1 version twice and tried to install it on two different USB 2GB sticks with 40 to 50% free. I get the same error all four attempts to upgrade the 2.4.0 version. ( categories: )
|
%TEMP%
Probably your drive C: lacks free space, as I mentioned in another thread.
Error Opening file for Writing 2.4.1 Upgrade
r.andom,
thanks for the response, but my C: drive has 111GB free.
The free space calculation issue ...
... is related to the drive where Your install target is.
So please check if there is enough space available on Your USB drives (240 MB for 2.4.1)
You've paid for Software more or less?
What You need is OSS!
Error Opening file for Writing 2.4.1 Upgrade
That would be about 800MB. Should I uninstall 2.4 first?
Corruption
This can sometimes be caused by corruption on the drive or something locking that file. Your best bet is to first check your drive for errors. Then delete the OpenOfficePortable\App\openoffice directory to remove your current OOP install without deleting your preferences (if you have any custom fonts or dictionaries, you'll need to manually back those up). Then install 2.4.1.
Live with purpose.
Error Opening file for Writing 2.4.1 Upgrade
John,
I have 2 2GB USB sticks I use and I had the same problem on both. That is why I downloaded again.
both sticks have basically the same stuff on them except one is bootable to Linux. Perhaps some installed program is the culprit.
Chkdsk result?
Did you check your drives for errors as John suggested? What did CHKDSK tell you?
Error Opening file for Writing 2.4.1 Upgrade
No problems with the oldest USB stick. It is FAT32
Error Opening file for Writing 2.4.1 Upgrade
Thanks John,
Deleting the directory on one USB worked. I'll try the other when I get a chance.
Second USB didn't go as smooth. I couldn't run chkdsk and I couldn't delete the culprit (schart.idx directory same file the install died on so I probably had a corrupt directory all along) even in safe mode so I formatted and started over.