Closed GoogleCodeExporter closed 9 years ago
Without an example file, I can do nothing.
Original comment by paracel...@gmail.com
on 13 Oct 2009 at 2:52
I have the same problem. Im trying to unrar a file that is 4,5 gb. *.avi
Original comment by john...@gmail.com
on 28 Mar 2010 at 7:32
Once again, without the file, I can do nothing.
Original comment by paracel...@gmail.com
on 29 Mar 2010 at 4:49
Actually, this error can only happen when writing to the disk fails.
Were you very low on disk space when this happened? In that case, you probably
just ran out.
Original comment by paracel...@gmail.com
on 12 Apr 2010 at 10:33
This error happens whenever there is an empty file inside the archive. I guess
The Unarchiver should just make a touch instead of trying to uncompress it.
Attached an example.
Original comment by mleite.a...@gmail.com
on 23 Jun 2010 at 12:15
Attachments:
Empty files should unpack just fine, and this file also expands for me.
What version are you using?
And what filesystem are you unpacking to?
Original comment by paracel...@gmail.com
on 23 Jun 2010 at 2:10
CFBundleVersion 2.3. Tested on both Mac OS Extended (Journaled) and Windows NT
Filesystem (compressed) with Paragon NTFS for Mac OS X. Same error.
Original comment by mleite.a...@gmail.com
on 23 Jun 2010 at 3:18
Oops.... I just gave you wrong info... problem only occurs with the NTFS
partition. Uncompressing to HFS works ok...
Original comment by mleite.a...@gmail.com
on 23 Jun 2010 at 3:24
Well, that sounds like a good hint.
Now I need to figure out a way to test it, and also find out if it's a bug in
The Unarchiver or Paragon NTFS.
Original comment by paracel...@gmail.com
on 23 Jun 2010 at 9:34
I can confirm that test.zip extracts well on "Desktop" (Mac OS Extended -
Journaled) and reports the error on a NTSF (Paragon NTFS Driver) partition.
Original comment by rigid...@gmail.com
on 24 Jun 2010 at 7:04
Original comment by paracel...@gmail.com
on 24 Jun 2010 at 11:53
All right, I finally managed to confirm this behavior. Paragon NTFS is
apparently buggy, and will fail when you attempt a write of zero bytes.
I added a workaround to The Unarchiver to avoid doing that, even though it is
entirely legal, so hopefully it should work now.
Original comment by paracel...@gmail.com
on 10 Jul 2010 at 1:39
Same problem extracting to a FAT32 partition.
Original comment by MatthewBrown
on 19 Dec 2010 at 7:04
Which version of The Unarchiver? This should be fixed in the latest.
Original comment by paracel...@gmail.com
on 19 Dec 2010 at 7:21
Original issue reported on code.google.com by
rigid...@gmail.com
on 11 Oct 2009 at 5:42