OS X 10.6 can't mount DVD-Rs adhering to ISO 9660 (1999) ?!

In article <>,
Joerg Schilling <> wrote:

>>Is there anything I can do to read 4+ GB files from the DVDs already
>>burned though, on this damn MacBook Pro?
>
>
>If you really used exactly the command line you mentioned, these files
>are not on the medium, they never have been added to the filesystem.

Just an additional hint: the fork does not support large files and
the option -allow-limited-size from the fork probably just prevents the
fork from aborting because it cannot archive large files. I expect that
(in case there are no other problem in the fork that affect you) the smaller
files are on the medium.

In any case, I recommend you to upgrade to a recent original mkisofs as the fork
is known to create unreadable Joliet sessions under some conditions. If
Mac OS X prefers to mount the Joliet session, this may be the reason for your
problems.

--
EMail: (home) Jörg Schilling D-13353 Berlin
(uni)
(work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

On Nov 3, 12:31*am, j...@cs.tu-berlin.de (Joerg Schilling) wrote:
> In article <c1f9aa1d-0595-40ad-9afe-bf2391488...@y28g2000prd.googlegroups..com>,
> Alex Miller *<alex.etc.mil...@gmail.com> wrote:
>
>
>
> >On Nov 2, 2:14=A0pm, j...@cs.tu-berlin.de (Joerg Schilling) wrote:
> >> >FWIW, I used the following under Linux to prepare the disk images:
>
> >> >mkisofs -allow-limited-size -gui -iso-level 4 -J -joliet-long -r
> >> >some_files > foo.iso
>
> >> You are not using mkisofs but a broken and unmaintained fork from a 5 yea=
> >r old
> >> version of the original software.
> >Wow. I did not expect an answer from the author of mkisofs et. al. !
>
> >Debian/Ubuntu screwed up again?! I'll be more careful when burning new
> >DVDs in the future.
>
> >Is there anything I can do to read 4+ GB files from the DVDs already
> >burned though, on this damn MacBook Pro?
>
> If you really used exactly the command line you mentioned, these files
> are not on the medium, they never have been added to the filesystem.
>

Debian 4 and OS X 10.6 indeed have problems reading those big files.
Debian sees about 300MB of it. However, Ubuntu 8.04 can read the file
fine, so it's definitely on the file system. The mkisofs used to
create the image was from Ubuntu 8.04 as well.

In article <eadaa1ce-191d-45ec-a48f->,
Alex Miller <> wrote:

>Debian 4 and OS X 10.6 indeed have problems reading those big files.
>Debian sees about 300MB of it. However, Ubuntu 8.04 can read the file
>fine, so it's definitely on the file system. The mkisofs used to
>create the image was from Ubuntu 8.04 as well.

With the command line you showed, it is impossible that you have the file
on the medium (in a usable way) as the fork does not support files >= 4GB.

BTW: Ubuntu has no mkisofs but the broken fork.

Note that the fork does not include the whole file in a usable form.
The option "-allow-limited-size" which is only in the defective fork
is an option to allow broken data on the filesystem. The size you see
in this case is typically the real file size modulo 2 GB or 4 GB.

Also note that it is impossible to code a numer > 4 GB in 32 bits.
To allow larger files, there needs to be more than one directory entry
for the file and this is what the fork cannot do.

A working mkisofs in part of the cdrtools package:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

--
EMail: (home) Jörg Schilling D-13353 Berlin
(uni)
(work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

On Nov 7, 8:01*am, j...@cs.tu-berlin.de (Joerg Schilling) wrote:
> In article <eadaa1ce-191d-45ec-a48f-2e2b76d3f...@u25g2000prh.googlegroups..com>,
> Alex Miller *<alex.etc.mil...@gmail.com> wrote:
>
> >Debian 4 and OS X 10.6 indeed have problems reading those big files.
> >Debian sees about 300MB of it. However, Ubuntu 8.04 can read the file
> >fine, so it's definitely on the file system. The mkisofs used to
> >create the image was from Ubuntu 8.04 as well.
>
> With the command line you showed, it is impossible that you have the file
> on the medium (in a usable way) as the fork does not support files >= 4GB.
>
> BTW: Ubuntu has no mkisofs but the broken fork.
>
> Note that the fork does not include the whole file in a usable form.
> The option "-allow-limited-size" which is only in the defective fork
> is an option to allow broken data on the filesystem. The size you see
> in this case is typically the real file size modulo 2 GB or 4 GB.
>
> Also note that it is impossible to code a numer > 4 GB in 32 bits.
> To allow larger files, there needs to be more than one directory entry
> for the file and this is what the fork cannot do.
>
> A working mkisofs in part of the cdrtools package:
>
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
>

All I can say is that I haven't noticed any breakage if the files are
read in Ubuntu, and I examined several of these cases. Are you sure
the Ubuntu fork didn't implement the functionality in some way?

If you'd like to reproduce the (surprising?) behavior, you may want to
install Ubuntu 8.04 with latest updates (easy in a VM), make an ISO
image from a 4.3GB file, following my recipe, and see if you get the
same file back after mounting the ISO.

Followup to a Linux group set (I don't read it, but we are getting OT
here).