Forum: UltraISO
Topic: File Size
started by: PJChem

Posted by PJChem on Nov. 16 2007,19:22
Well, I have this problem:
I have an ISO already made by other appz. In that iso I have a single file with 4GB with other small files. I open the iso without problems. I put some other files there and when I save I get this message - ISOIMAGE FILE 'DATA2.CAB' SIZE ERROR.
The size of this file is 4GB.

(even if I don't put files there the same error appears is I save)

Ultra Iso 8.6.3

This problem already appear some weeks ago on another case I had to use another appz and other method, but I want to know if with UltraIso I can save or make an ISO that have a single file with that size for instance.

Thanks in Advanced



Posted by xoben on Nov. 17 2007,08:21
Thank you PJChem for your bug report.

Please send the first 1MB of the ISO image to service@ezbsystems.com for detailed checking.

PS: A small tool at < http://dw.ezbsys.net/filecut.exe > may help you to cut an ISO image.

Posted by PJChem on Nov. 17 2007,20:07
Well, I manage to get it work, but it's weird.
Like I said if I open an ISO already made with a single file with 4G (I don't know what size the error occur) and then try to save the same error appears: ISOIMAGE FILE 'DATA2.CAB' SIZE ERROR.
The weird things is this part. I mount the iso on Daemon tools. Then open ultraiso and choose to create a new iso. When I select all the files from my original ISO that I mount on Daemon Tools (the 4GB file included) the appz automatic change the format to a UDF DVD - it's normal because with big files this format is what I use on Nero too). Then I choose Save as and it works. I put the files I want there too. If I close the appz, and then open this new ISO and try to put some new files there the same error appears again:

Conclusion: I can't open and work on an ISO already made with a 4GB files but if I choose to create a new one and put the same files there and choose to save as it works. Of course after saving that one I can't reopen the same iso again

Posted by xoben on Nov. 17 2007,22:01
Hello PJChem, please check your PM for an answer.
Posted by xoben on Dec. 07 2007,09:06
This bug has been fixed since version 8.6.5.2160.