Menu

#1 files 4GiB and over size no go into ISO

open
nobody
None
5
2008-05-19
2008-05-19
No

files >=4,294,967,296 bytes (2^32) do not make it into the ISO without an error message.

I was hoping I could make an ISO with FILES larger than that, say with system backups DVD sized.
ISOCreator cannot do this.

Discussion

  • Jim Michaels

    Jim Michaels - 2008-05-21

    Logged In: YES
    user_id=1476673
    Originator: YES

    Multi-Extents is what we want on ISO's. ISO level 3 has no restrictions on file size. maybe this is what you shoule be using.
    "From the mkisofs man page:

    -iso-level <level>

    Set the iso9660 conformance level. Valid numbers are 1..3 and 4. [...]

    With level 3, no restrictions (other than ISO-9660:1988) do apply.
    Starting with this level, mkisofs also allows files to be larger than 4 GB
    by implementing ISO-9660 multi-extent files.

    With all iso9660 levels from 1..3, all filenames are restricted to upper
    case letters, numbers and the underscore (_). The maximum filename length
    is restricted to 31 characters, the directory nesting level is restricted
    to 8 and the maximum path length is limited to 255 characters.

    Level 4 officially does not exists but mkisofs maps it to ISO-9660:1999
    which is ISO-9660 version 2.
    "

     
  • Jim Michaels

    Jim Michaels - 2008-05-23

    Logged In: YES
    user_id=1476673
    Originator: YES

    I believe I've tracked down the bug (maybe some of it).
    UInt32 is consistently being used in IsoCreator.cs in the function Folder2Iso() in calculating extents.
    Since I did not write the code, I am not sure what to change without breaking the code.

     
  • Jim Michaels

    Jim Michaels - 2008-05-23

    Logged In: YES
    user_id=1476673
    Originator: YES

    WriteVolumeDescriptors() in the same file has the same problem, so does VolumeDescriptorWrapper.cs

     

Log in to post a comment.