IRIX skips dots in CD filenames?
Walther Mathieu
in a recent posting I suspiced it were some DOS-like 8.3 naming scheme that
stymied CDROM filenames when displayed by IRIX. But I was wrong again.
The file names IRIX displays are "only" missing a simple dot.... but for my app
- Pro/E - which heavily relies on version numbers behind a second dot (the one
IRIX left in the name) this is fatal. With the former "extension" beeing no
longer separated from the former "name" these files become invisible to it.
There appears to be *nothing* on that media.
This behaviour appears in 4DWM file boxes as well as with "ls" from the console.
Is this a bug? Or is there some intention behind skipping filename dots?
Anybody an idea?
TIA
Walther
Walter Roberson
Walther Mathieu <kon...@walther-mathieu.de> wrote:
:in a recent posting I suspiced it were some DOS-like 8.3 naming scheme that
ISSO 9660 CDROMs *do* have naming scheme similar to 8.3
(but also followed by a semi-colon and a version number.)
If you want the full name to be visible, you have to use
"Rockridge Extensions". If the CDROM is written with those
extensions in place, then IRIX will automatically recognize them
(provided you have eoe.sw.cdrom installed.)
Rainer Canavan
> Hello again,
> in a recent posting I suspiced it were some DOS-like 8.3 naming scheme that
> stymied CDROM filenames when displayed by IRIX. But I was wrong again.
[...]
> This behaviour appears in 4DWM file boxes as well as with "ls" from the console.
> Is this a bug? Or is there some intention behind skipping filename dots?
probably a feature of iso9660 filesystems (the most strict variant is
8.3 and very restrictive about the characters used).
> Anybody an idea?
Try mkisofs (and maybe cdrecord), both are available for cygwin, which
should run under NT. You should be able to make a iso image with rock-ridge
with mkisofs and either use your "normal" recording program or cdrecord
to burn this to CD.
Rainer
Walther Mathieu
Thanks for your suggestions... but I can´t accept that explanation.
Once again: there ARE all dots in the filenames on the CD!
Only when reading in the directory with IRIX they vanish all but one.
So it´s not the CD format but IRIX that does some unwanted filtering...
Or does that mean I should use rockridge extensions while burning CDs
in order to tell IRIX that I indeed *want* all those dots in filenames
(and it otherwise omits them so I cant retrieve files from Pro/E)?
Wolfgang Szoecs
Walther Mathieu <mat...@in4tec.de> writes:
> Thanks for your suggestions... but I can´t accept that explanation.
>
> Once again: there ARE all dots in the filenames on the CD!
> Only when reading in the directory with IRIX they vanish all but one.
> So it´s not the CD format but IRIX that does some unwanted filtering...
>
> Or does that mean I should use rockridge extensions while burning CDs
> in order to tell IRIX that I indeed *want* all those dots in filenames
> (and it otherwise omits them so I cant retrieve files from Pro/E)?
yes.
ISO9660 is 8+3 - period !
Ontop of this 8+3 there are 'extensions' like RockRidge (TRANS.TBL file),
which the system uses to convert the 8+3 to Unix-like names + perms.
Unfortunately, if you create a CD with long names, and don't enforce
using the RockRidge (for example by using M$ Joliet),
the only thing IRIX can do is to fall back is the ISO 8+3.
Wolfgang
<<>>
Level 1 (8+3) and Level 2 (32), which is more commonly called 'Rockridge
Extensions.' You want to choose Level 2 or 'Rockridge Extensions,' I've
had no trouble reading/copying Pro/E files from CD to my Indy. While
burning with Nero, file names that are too long or contain illegal
characters will appear in italics, you must fix them or that filename
will be burned incorrectly.
Chris
Walther Mathieu
> If you are using Nero I believe it makes a distinction between ISO 9660
> Level 1 (8+3) and Level 2 (32), which is more commonly called 'Rockridge
> Extensions.' You want to choose Level 2 or 'Rockridge Extensions,' I've
> had no trouble reading/copying Pro/E files from CD to my Indy. While
> burning with Nero, file names that are too long or contain illegal
> characters will appear in italics, you must fix them or that filename
> will be burned incorrectly.
>
> Chris
Now we´re getting closer to it... ISO9660 Level 2 is identical with those
fabulous
Rockridge Extensions (I didn´t know that). That´s what I used to toast my CDs.
Btw, there were no exotic characters in my proe file names, even *both* dots...
But somewhat IRIX swallows them! I´m still confused - and got no workaround.
You say there was no problem importing proe files - do you use version numbers?
If so, there must be a trick to keep IRIX from skipping the dot.
Regards
Walther
Andreas Backhaus
> "<<>>" wrote:
>
>
>>If you are using Nero I believe it makes a distinction between ISO 9660
>>Level 1 (8+3) and Level 2 (32), which is more commonly called 'Rockridge
>>Extensions.' You want to choose Level 2 or 'Rockridge Extensions,' I've
>>had no trouble reading/copying Pro/E files from CD to my Indy. While
>>burning with Nero, file names that are too long or contain illegal
>>characters will appear in italics, you must fix them or that filename
>>will be burned incorrectly.
>>
>>Chris
>
>
> Now we´re getting closer to it... ISO9660 Level 2 is identical with those
> fabulous
> Rockridge Extensions (I didn´t know that).
Two different animals.
> That´s what I used to toast my CDs.
> Btw, there were no exotic characters in my proe file names, even *both* dots...
>
> But somewhat IRIX swallows them! I´m still confused - and got no workaround.
> You say there was no problem importing proe files - do you use version numbers?
> If so, there must be a trick to keep IRIX from skipping the dot.
Use mkhybrid (or mkiofs - for both apps working Win32 executables are
easy to find) to make an ISO file (which you can burn with whatever you
want), for that ISO file turn on Rockridge Extensions, let it generate a
TRANS.TBL and also turn on Joliet. The result is a CD that'll work
perfectly on Windows, UNIX, VMS, whatever. No more PITA, no more suffering.
Andreas
Olaf Weber
> In article <3CF21BCC...@in4tec.de>,
> Walther Mathieu <mat...@in4tec.de> writes:
>> Thanks for your suggestions... but I can愒 accept that explanation.
>>
>> Once again: there ARE all dots in the filenames on the CD!
>> Only when reading in the directory with IRIX they vanish all but one.
>> So it愀 not the CD format but IRIX that does some unwanted filtering...
>>
>> Or does that mean I should use rockridge extensions while burning CDs
>> in order to tell IRIX that I indeed *want* all those dots in filenames
>> (and it otherwise omits them so I cant retrieve files from Pro/E)?
> yes.
> ISO9660 is 8+3 - period !
> Ontop of this 8+3 there are 'extensions' like RockRidge (TRANS.TBL file),
> which the system uses to convert the 8+3 to Unix-like names + perms.
> Unfortunately, if you create a CD with long names, and don't enforce
> using the RockRidge (for example by using M$ Joliet),
> the only thing IRIX can do is to fall back is the ISO 8+3.
Actually, ISO9660 is more complicated (and weirder) than that.
A filename ("file identifier" in ISO9660 terminology) consists of
three fields: the "file name", the "file name extension", and the
"file version number". The file name and file name extension are
separated by a period '.', the file name extension and file version
number are separated by a semicolon ';'.
The file name and file name extension fields may contain only the
digits 0...9, the uppercase letters A...Z and the underscore '_'.
If the file name is empty, then the file name extension must contain
at least one character.
If the file name extension is empty, the file name must contain at
least one character.
The sum of the lengths of the file name and the file name extension
must be at most 30.
Then there's the level-1, level-2, level-3 distinction, which
introduces additional restrictions, (level-1 implies 8+3, for
example).
For the case under discussion this means you really should use the
Rock Ridge extensions if you need to use filenames containing more
than one period.
--
Olaf Weber SGI Phone: +31(0)30-6696777
Veldzigt 2a Fax: +31(0)30-6696899
Tech Support Engineer 3454 PW de Meern Vnet: 955-6852
Global Product Support The Netherlands Email: ol...@sgi.com
Thomas Jahns
> Ontop of this 8+3 there are 'extensions' like RockRidge (TRANS.TBL file),
> which the system uses to convert the 8+3 to Unix-like names + perms.
I'm not sure why people confuse Rock Ridge with the TRANS.TBL
files. The Information for RR-filename and other stuff is only
duplicated in those TRANS.TBL files, they serve purely informational
purposes and are optional. I would advise anyone who wants to know enough
about RR to write useful ISO-images to read the mkisofs(8) manual page.
Thomas Jahns
--
"Computers are good at following instructions,
but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley1984, 1986, 1996, p. 9