Rar file extracting ISO at 100% ISO
-
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
-
@yop:
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
Sorry, NOT confirmed here. :confused:
I tried with a Zip of a DVD - zip filesize 4.04 GB (4,345,357,872 bytes)
Then tried a zip containing two movie files - zip filesize 1.66 GB (1,784,405,346 bytes)
Then tried a ZIP file of 980MB.All extracted with no problems in PA 9.5 beta 7.
Note: there was a “known” problem with PA not showing error message on insufficient disk space when using ZIP format, but this was fixed in PA 9.5 beta 7.
However, Atonement said he has 20 GB free (and is using RAR anyway) :confused: -
I created a zip file (1.5GB-named test.zip) using Beta 7. I was able to unzip without any problems. I also tested the archive and it tested fine. I created 758MB (330files) archive and it also checked out fine.
-
All files over 1gb which is strange because i have 20gb free.
I do not have a 1GB iso file. However I do have one 340MB iso.
So I made copies.4 iso files -> RAR 1.29 GB (1,386,471,671 bytes)
“Extract to folder” via shell (using PA 9.5 beta 7)
No problems encountered.My drive C: only has 1.5 GB free but my “working” drive D: has 20GB free - (Note: I activated PA “use current folder as temp” to avoid possible free disk space problem on Drive C:).
-
The problem was extracted it was 4gb and i was on my fat32 formated drive so i just converted back to NTSF( something like that)
-
OK
Thanks for coming back and telling us. -
Explains why we couldn’t reproduce it. :)
-
But there’s still a bug here - an error message should be displayed.
-
But there’s still a bug here - an error message should be displayed.
Yes, but the problem is that Windows cannot handle files of this size.
So the error message should be from Windows - not PowerArchiver. -
I’m not 100% sure, but I believe that what happens is that when a program tries to write past the 4GB file limit on a FAT32 partition the API returns an ERROR_DISK_FULL result to the calling program.
This often leads to a confusing error message (since there can be more than 4GB available on the partition), so PA may want to present it as “The disk is full or the file is too large for the destination file system.” Or something.
But in any case, it should not fail silently.
(edited)
-
We will check it out later on, thanks for clarification, although in reality move to NTFS people!!!
:-)





