#2 always creates RockRidge info?

[Anonymous]

I'm trying to burn an mp3 (not cd audio) cd
for a car stereo cd/mp3 player. The
rockridge and joliete file info causes the
cd to be unreadable, the cd must be
completely iso9660 level 2 compliant. I
have tried every variation of options under
eroaster, but always get rockridge info
generated and the reulting long filenames.
The mkisofs output window lists 200 - 300
bytes of rockridge info generated. Is this
a bug, or is there a way to turn off
rockridge attributes, unchecking the
checkbox doesn't work?

As an aside, to create multisession cd's on
my burner, I need to send cdrecord the -data
option. I dont think that option is
implemented in eroaster.

Thanks for your help. Aside fromt these
questions, I think eroaster is the best,
most usable linux cd-burning software.

mike

[Nobody/Anonymous]

Logged In: NO

I downloaded the source, and realized that
whenever you choose multisession, it also
includes the creation of rockridge info. Why?

thanks again

mike

[Martin Preishuber]

Logged In: YES
user_id=29575

I just checked, what I do. When starting eroaster with
--debug you can see, that the -R option is missing when you
uncheck the Rockridge flag, so it has to be something else :(

[Martin Preishuber]

Logged In: YES
user_id=29575

Concerning the -R flag when using multisession, this is
considered a must from the cdrecord author. Here's the part
of the multisession readme:

Create a iso-9660 filesystem image with mkisofs-1.10 or later.
mkisofs is included in the cdrecord release (including
SunOS/Solaris multi-session support)
Use the -R flag to add Rock Ridge extensions (this is
important).

So I really think this is required.

[Nobody/Anonymous]

Logged In: NO

Yeah I did a little research, and the creator of
cdrecord claims that the -R flag is needed to
accurately define the previous leadout if the
previous session has a file size of 0. In actual
use however, you can create every possibilty down
to multisession iso9660 level 1 filesystems (I
mean no joliet, no rockridge, 8.3 filenames).
Perhaps there is a potential problem associated
with leaving out the rockridge attributes, but
I've never run into it. I guess this request for
support is nothing more than a feature request.

Thanks for your quick responce.

mike

[Martin Preishuber]

Logged In: YES
user_id=29575

I'm not sure wether it's really possible to skip the -R for
multisession CDs. I did lots of testing with that
multisession stuff and as far as I can remember is it not
possible to write the first track without this flag. Maybe
you can try wether it works and let me know the result. I
won't be here for a month starting from tomorrow, so I can't
make any immediate changes.

[Mike Wollenberg]

Logged In: YES
user_id=365700

I can tell you with 100% certainty, that I can
burn multisession iso level 2 compliant CD-R's
and CD-RW's, meaning no Rockridge extensions, on
my setup, a Matshita 7585 using the generic mmc
driver and cdrecord 1.10. I used this method to
create a multisession iso9660 level 2 disc for
the mp3 player I initially mentioned in my first
post. It is as simple as creating a filesystem
with mkisofs -T -l, and burning it with cdrecord
-multi -data. The second session just needs the
info from -msinfo to import and update the
previous session, which you already do in
eroaster. At this point I am not totally sure
of what combinations work, but I know iso9660
level 1 and 2 work with or without translation
tables, and I think Joliet extensions work with a
translation table, without I think the previous
sessions will be imported with 8.3 filenames,
which is mentioned in the cdrecord faq. I would
be more than thrilled to check into which
combinations work, and report back.

As far as problems with the lack of rockridge on
multisession cd's, the only thing I have noticed
is that whe you write the final track without the
multi option, and close the cd, all but the
first session are inaccessable. I cannot tell
for sure whether this is due to closing the cd
or the fact that I am using cd-rw's and may be
having interference from previous un-erased
recordings. By the way un-erased previous
recordings have screwed up the initial burning,
causing the cd-rw to record in single session
mode even though -multi was used. Not ejectng
and reloading the cd between sessions also
causes problems with the process on my cd
burner.

I'll look into which combinations work, the cd-r
verse cd-rw limitations, and the cd closing
issues and report back if you like.

mike