Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Mac Applications / May 2007



Tip: Looking for answers? Try searching our database.

"LiquidCD" file-system choices

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
no-spam2@lycos.com - 16 Apr 2007 08:35 GMT
I have a question concerning the freeware CD-burner "LiquidCD"
(http://www.maconnect.ch/index.php?lang=en&page=liquidcd).

I'm aiming to burn a CD-R which is compatible with as many computer
systems as possible, but without changing the filenames. It looks as
if "Joliet" is the way to go based on my burning tests.
But what confuses me now is that LiquidCD allows me to choose several
file-systems all at once. Here's a screenshot:
http://img401.imageshack.us/img401/33/customjj3.png

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
can use?
In other words, by not only choosing Joliet, but also ISO9660-1, even
"ancient" computers could read the CD, but with completely "messed up"
filenames (8.3 length, all UPPER case)?

The files (AIFF audio files) have all been done on a 68K Mac running
MacOS 8.1, but have now been transferred to my G4 Powerbook. As far as
I can remember the file naming limit to MacOS 7/8/9 was 31 characters
(correct me if I'm wrong), so no filenames are longer than that.
I have Toast (3.5.7) installed on the 68K Mac with a SCSI CD-burner
(this is how I transferred the files over to the G4 Powerbook by the
way). It seems my old copy of Toast has more features than LiquidCD,
but I'm not prepared to fork out the 80 bucks or so for a new copy of
Toast if LiquidCD will do.

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
even Linux if it supports icons for removable media) -how do I do
that? Is that what they call "hybrid" CDs?
Gregory Weston - 16 Apr 2007 15:50 GMT
> I have a question concerning the freeware CD-burner "LiquidCD"
> (http://www.maconnect.ch/index.php?lang=en&page=liquidcd).
[quoted text clipped - 9 lines]
> file-systems to choose from, and will then choose the "best" one it
> can use?

Yes. CD's are capable of hosting several file systems whose directory
entries reference common data. Exactly how any given OS presents that is
up to the driver reading the disc on that platform; most will pick the
most capable one they support and present that. Potentially some could
show you multiple logical discs.

> In other words, by not only choosing Joliet, but also ISO9660-1, even
> "ancient" computers could read the CD, but with completely "messed up"
> filenames (8.3 length, all UPPER case)?

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.

> 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
> even Linux if it supports icons for removable media) -how do I do
> that?

You burn the disc. If the OS displays icons for a mounted volumes it
should display an icon for that one.

G
no-spam2@lycos.com - 16 Apr 2007 19:34 GMT
>  "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
David C. - 01 May 2007 05:08 GMT
> I have a question concerning the freeware CD-burner "LiquidCD"
> (http://www.maconnect.ch/index.php?lang=en&page=liquidcd).

I'm not familiar with this program, but your questions are pretty
generic, and the answers should be the same for any CD burning app.

> I'm aiming to burn a CD-R which is compatible with as many computer
> systems as possible, but without changing the filenames. It looks as
> if "Joliet" is the way to go based on my burning tests.  But what
> confuses me now is that LiquidCD allows me to choose several
> file-systems all at once.

That would be correct.  CD file systems allow you to have multiple
directories that point to the same files.  So you can, for instance,
have a disc with HFS and ISO-9660 at the same time.

Joliet is an extension to ISO-9660, adding long filename support in the
way Windows likes.  There's also Rock Ridge, a different ISO-9660
extension that adds long filenames and permissions in the way UNIX
systems like.

It is completely possible to make a disc with all of these in use at
once.  If you do, Macs will use the HFS directory, modern Window systems
will use ISO+Joliet, modern UNIX systems will use ISO+Rock Ridge, and
everybody else will use plain ISO-9660 (with 8.3 filenames.)

> 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
> even Linux if it supports icons for removable media) -how do I do
> that? Is that what they call "hybrid" CDs?

Disk icons are usually produced by putting an icon file in the root
directory of the disk.  Different operating systems/GUI
environments/Window managers will use different format files and
different names, but they all use the same general technique.  If your
disk burning software doesn't have a feature to do this automatically, a
bit of Google searching should tell you what each operating system looks
for.

-- David
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.