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.
F:\PortableApps\OpenOfficePortabele\App\openoffice\help\en\schart.idx\LINKNAMES
Click Abort to stop the installation,
Retry to try again, or
Ignore to skip this file.
I have aborted each time, should I try Ignore or is there a problem with the new version installer? Or is there something else I am missing?
You are here
Error Opening file for Writing 2.4.1 Upgrade
July 17, 2008 - 9:13am
#1
Error Opening file for Writing 2.4.1 Upgrade
Probably your drive C: lacks free space, as I mentioned in another thread.
r.andom,
thanks for the response, but my C: drive has 111GB free.
... 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)
Paid for Software more or less?
What You need is OSS!
That would be about 800MB. Should I uninstall 2.4 first?
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.
Sometimes, the impossible can become possible, if you're awesome!
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.
Did you check your drives for errors as John suggested? What did CHKDSK tell you?
No problems with the oldest USB stick. It is FAT32
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.