> "no-sp...@lycos.com" <no-sp...@lycos.com> wrote:
> > Does this mean that the computer reading the CD-R will have several
> > file-systems to choose from, and will then choose the "best" one it
[quoted text clipped - 5 lines]
> most capable one they support and present that. Potentially some could
> show you multiple logical discs.
Interesting.
So I guess I could make the CD readable even on "ancient" filesystems
like the old DOS 3.1, sacrificing the original names of course, but
still usable.
But since the filenames have no use if they're changed I suppose
Joliet is the way to go.
I was under the impression that ISO-9660-Rock ridge would be OK since
the filenames are no longer than 31 characters, but I found out that
Rock ridge changes the filenames to all upper-case, so that won't do.
Joliet is the next step up, isn't it?
> Joliet's a special case because it doesn't stand on its own. A Joliet
> disc _is_ a 9660 disc, that also has additional information on it.
I see. Is the correct term for the type of CD I'll be burning:
"ISO-9660-Joliet"?
> > However, if I would like an icon for the CD to pop up on the desktop
> > for the various systems (MacOSX, MacOS 7/8/9, Windows, and perhaps
[quoted text clipped - 3 lines]
> You burn the disc. If the OS displays icons for a mounted volumes it
> should display an icon for that one.
Yes, but I mean a *custom* icon.
I've been able to make a custom icon show up in MacOSX, but not on a
68K Mac running MacOS 8.1, neither on a PC with Windows ME.
To add the MacOSX icon I clicked on the "Properties" button (lower
part of the main window in LiquidCD) and dragged an image to where it
says I should do that). I also found out that I need to burn the CD
with HFS+ in addition to ISO-9660-Joliet.
I suppose custom icons on all operating systems are just regular files
but "hidden" somehow, so if this is correct, could I just burn an
ISO-9660-Joliet/HFS+ CD with the appropriately named (and placed in
the correct part of the CD which I assume is in the root) icon in the
Windows format and another icon in the MacOS format?
Does anyone have the specifics on this?
Gregory Weston - 16 Apr 2007 23:04 GMT
> > "no-sp...@lycos.com" <no-sp...@lycos.com> wrote:
>
[quoted text clipped - 12 lines]
> like the old DOS 3.1, sacrificing the original names of course, but
> still usable.
Right. That'd be your 9660, Level 1 method.
> But since the filenames have no use if they're changed I suppose
> Joliet is the way to go.
> I was under the impression that ISO-9660-Rock ridge would be OK since
> the filenames are no longer than 31 characters, but I found out that
> Rock ridge changes the filenames to all upper-case, so that won't do.
Rock Ridge supports mixed-case filenames through ancillary records in
the catalog. Like Joliet, it's an extension to 9660, not a replacement.
But...
> Joliet is the next step up, isn't it?
Joliet _is_ the next step up in that it's got even more relaxed naming
restrictions.
> > Joliet's a special case because it doesn't stand on its own. A Joliet
> > disc _is_ a 9660 disc, that also has additional information on it.
>
> I see. Is the correct term for the type of CD I'll be burning:
> "ISO-9660-Joliet"?
You could just say Joliet. ISO 9660 is implied in that. But Joliet
support on Macs prior to OS X is spotty (3rd-party, although I think
freeware) so you'd probably also want some Mac-native file system along
with it.
G
David C. - 01 May 2007 05:12 GMT
> Joliet _is_ the next step up in that it's got even more relaxed naming
> restrictions.
But it's not without limits. For instance, it has a 64-character name
limit. This bit me recently when I was burning an MP3 CD. One of my
tracks (a concatenation of four tracks from a Broadway soundtrack) had a
longer name than this. The name was truncated to 64 characters on
Joliet, but was perfectly fine on the HFS+ file system. Because of
this, the ".mp3" extension was lost and the track couldn't be played on
Windows or in my car stereo until I burned a new CD with a shorter name.
> You could just say Joliet. ISO 9660 is implied in that. But Joliet
> support on Macs prior to OS X is spotty (3rd-party, although I think
> freeware) so you'd probably also want some Mac-native file system along
> with it.
Which is why I always make a hybrid HFS/Joliet disc when I burn CDs
(with Toast). This way, even old Macs can see the correct file names.
-- David