Re: CD burnt with MAC unreadable by PC's

Laszlo Lebrun <lazlo_lebrun@xxxxxxxxxxxxxx> wrote:

On 28.01.10 16:56, Wayne C. Morris wrote:

Normally the Mac is supposed to write CD's using the Joliet file system,
which is not proprietary, is it?.

No, Joliet is how *Windows* writes CDs. It's Microsoft's proprietary
extension to allow long filenames on ISO 9660 CDs.

You are right, I meant ISO 9660.
I just made a "Get Info" on that disk, which returned "Format Mac OSX
Extended".

Disk utility gave:
Disk Identifier : disk1s1s2
Mount Point : /Volumes/Mapplethorpe Black Book
File System : Mac OS Extended
Connection Bus : ATA
Device Tree : /PCI0@0/PATA@1F,1/PRIM@0/@0:2
Writable : No
Universal Unique Identifier : A97C9EAF-E18F-3BE3-80CD-8A8C6FB6E8E7
Capacity : 43,4 MB (45.531.136 Bytes)
Used : 43,4 MB (45.531.136 Bytes)
Number of Files : 16
Number of Folders : 1
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : No
Disk Number : 1
Partition Number : 2

Unfortunately that doesn't reveal any useful information (as I alluded
to in my other post).

When the Mac burns a "hybrid" disc it includes two separate file
systems. One is Mac OS (HFS) or Mac OS Extended (HFS+), and the other is
ISO-9660 (typically with Joliet extensions for Windows long file names,
and Rock Ridge extensions for long file names on Unix/Linux systems).

HFS and HFS+ are the native Mac file system. They are completely
unrelated to and incompatible with ISO-9660.

It is possible for the HFS/HFS+ and ISO-9660 file systems to contain the
same files, sharing the same physical copy of the files (effectively two
directory strucutres pointing to the same content).

It is also possible to set up a hybrid disc which has completely
different files in the HFS/HFS+ and ISO-9660 file systems, or only a
partial overlap. This is useful for things like software installers that
only apply to one operating system, but which share data files.

When you insert the CD into a Mac, it sees the Mac-native file system
and ignores the ISO-9660 file system.

When you insert the CD into most other operating systems, it sees the
ISO-9660 file system and ignores the Mac file system.

Unfortunately this means that Disk Utility is also ignoring the ISO-9660
file system, so when you do a Get Info it only tells you about the Mac
file system. It doesn't even hint at whether the ISO-9660 file system is
present on the disc.

That should be ISO9660 compliant, should it?

No.

The files on the disk have only got very basic names like "BLACK_01.JPG".
That should not need any Joliet or whatever filenaming extension.
PCs _just see absolutely nothing on that disk_.

Which almost certainly means the disc was burned as a pure Mac native
CD, with just Mac OS Extended (HFS+) and no ISO-9660 file system.

This is possible with third-party disc burning software (such as Toast),
or by using Disc Utility to burn a disk image in Mac OS Extended format
to a CD.

The standard method of creating a CD with Finder (by dragging files onto
the CD and then initiating the burn) will create a hybrid disc.

This is also the default method used in Toast when you burn files to a
CD. You just have a higher degree of control over the process and can
choose your preferred options.

I inserted a brand new CD in the mac, dragged a file from the finder
onto it and ejected the CD, gave a new name to the CD and burnt it.

That CD was also a "Format Mac OSx Extended" _which was however
perfectly readable_ on PCs.

That was a hybrid disc.

Disk utility gave:
Disk Identifier : disk1s1s2
Mount Point : /Volumes/Wikipedia book on Eyes
File System : Mac OS Extended
Connection Bus : ATA
Device Tree : IODeviceTree:/PCI0@0/PATA@1F,1/PRIM@0
Writable : No
Universal Unique Identifier : 39E61054-77E6-377A-86CE-2C230C4EFA12
Capacity : 36,3 MB (38.017.024 Bytes)
Used : 36,3 MB (38.017.024 Bytes)
Number of Files : 2
Number of Folders : 0
Owners Enabled : No
Can Turn Owners Off : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : No
Disk Number : 1
Partition Number : 2


So where could have been that difference?
I just noticed a difference in the device tree info, which i do not
understand.

Nor do I, but it is unlikely to have anything to do with the file system
on the CD.

--
David Empson
dempson@xxxxxxxxxxxxx
.

Relevant Pages

  • Re: dpkg: serious warning: file list file for package package missing, assuming package has no files
    ... That usually caused by a file system error. ... Often things like that mean your disc is about to die. ... belong to which package. ... But I don't think that the disk is bad. ...
    (Ubuntu)
  • Re: Safari wont open
    ... If the problem persists in the new user account, ... Possibly a corrupted file system. ... from the OS X install disk and run Disk Utility's "Repair Disk". ... There are no viruses for Mac OS X. ...
    (comp.sys.mac.system)
  • Re: Autorun CD
    ... I assume all versions of Windows can still auto-run a CD (I haven't used ... It was available in Mac OS 9, and was a vector for a virus that was ... The Mac file system on the CD can coexist with the ISO-9660 file system ... This is known as a "hybrid" disc and is the ...
    (uk.comp.sys.mac)
  • Re: mac will not reboot
    ... I assume you made sure your disk's file system was in good shape before ... That's how Mac OS X tells you it had a "kernel panic"; ... run Disk Utility's Repair Disk (from the ... else you won't be able to install Mac OS 9. ...
    (comp.sys.mac.system)
  • Re: book recommendation: Mac as Unix
    ... I'm a total newbie to the Mac. ... I've been using Unix and Linux ... If you want to launch Terminal.app from the command line, ... An alias is a Mac OS X file system specific abstraction. ...
    (comp.sys.mac.system)