Rar file extracting ISO at 100% ISO

[Atonement]

When extracting a ISO normaly you see the iso file while it is extracting and at the end just click it but mine just disappears after extraction no warning.

[TBGBe]

Sorry, but I have no idea what your problem is.
Can you give a “step by step” description of what you are doing - trying to do?

A link to the rar/iso file would also help.

Also, which version of PA and which OS would be useful.

[Atonement]

Windows Xp SP1 the problem is simple really when it extracts from the rar file the ISO disappears at 100% so i get no extracted file i have used current BETA’s and old versions the same thing.

[amh209]

Does it happen on all rar files or just one?

[Atonement]

Does it happen on all rar files or just one?

All files over 1gb which is strange because i have 20gb free.

[TBGBe]

Over 1GB is a strange size limitation - and not easy to find for doing quick tests.
(2GB would make more sense - e.g. 16 bit limitations).

Do you mean that you have a single rar archive (not split) which is over 1GB containing a single ISO file?
Or is the ISO file itself over 1GB ?

Is the problem only with ISO files inside RAR…
or any RAR archive which is over 1GB…
or only when RAR archive contains a file which is over 1GB?

Do you know how the RAR was created (which version of RAR)?

Exactly how are you trying to extract it in PA 9.5 beta 7?

[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

[TBGBe]

@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.

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)

[amh209]

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.

[TBGBe]

@Atonement:

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 has 20GB free - (Note: I activated PA “use current folder as temp” to avoid possible free disk space problem on Drive C:).

[Atonement]

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)

[TBGBe]

OK
Thanks for coming back and telling us.

[amh209]

Explains why we couldn’t reproduce it.

[mwb1100]

But there’s still a bug here - an error message should be displayed.

[TBGBe]

@mwb1100:

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.

[mwb1100]

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)

[spwolf]

We will check it out later on, thanks for clarification, although in reality move to NTFS people!!!