i could not install any of the libre versions using next prerelease version3 platfom/manage app/install new app (i also tried with earlier platform versions and same error); error: "extract error writing to file th_nb_NO_v2.dat." only problem w/ libre, all other apps installed ok. help/thanks.
You are here
Please Help Support Us
Please help support us by making a donation so we can keep bringing you awesome free software. We accept credit card, wire transfer, PayPal, cryptocurrency, and more.
If you recently donated, thank you!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Where is your platform installed? If it's in a place other than the root of the drive, it may fail. LibreOffice has very long paths and subdirectory names and if you try to install to an already long location, it will fail.
Sometimes, the impossible can become possible, if you're awesome!
i tried both d:\PortableApps\LibreOfficePortable and d:\LibreOfficePortable. neither worked (i.e., "error writing to file th_nb_NO_v2.dat"). i have windows vista-premium 64 with AMD dualcore machine. the platform is in root (i.e., d:\PortableApps). i also tried to install w/ norton AV turned off. any ideas/thanks
t tran
If it's not a path issue and antivirus is off, it's nearly always drive errors that causes that error message
Sometimes, the impossible can become possible, if you're awesome!
i'm stumped. i tried on two different machines: vista-premium 64 and windows 7 professional, that have second d: HD (2 HDs machines); also, tried on a usb drive. all err: "error writing to file th_nb_NO_v2.dat." give up for now and try again when the next libre version is out.
t tran
Have you tried it to a different drive? If it works elsewhere, it's a drive issue.
Sometimes, the impossible can become possible, if you're awesome!
I remember a thread in the PA.c Forums a while back (
IDKhow long ago) where somebody had a similar problem and it ended up that the issue was not enough Free Space on the Drive on which%TEMP%resides (IIRCit was a RAMDrive that was too small in that thread).If you open a Command Prompt window, and run
ECHO %TEMP%it'll tell you where your%TEMP%directory is (note the Drive Letter at the beginning, e.g.X:), then you can openMy Computer, Right-Click on the Drive on which%TEMP%resides, Click "Properties", and tell us how much "Free Space" it reports in that window.~3D1T0R
thanks. that solved it. i do have ram-drive \temp (300 MB) installed with the SSD c: on both machines. i increased the ram-drive to 500 MB and it worked.
t tran