To me gttoaster does not make any good. It only creates problems instead of solving them.

The reason is somewhere deeper. Frontends do not work, because they cannot work. That is why reading gttoaster manual does not help. The instructions do not work, because something is wrong with cdrecord. I do have tested them. thats for sure.

But hey I am newbie...Code 18 can allways be there.

BTW, Schilling replied to me like this:

"If you use code broken by readhat, you need to ask redhat!"

So he feels that my flags MUST BE O.K. There may be a bug, you never know.

But I do have recompiled all the possible updates from his own pages...and it still does not work. You cannot blaim Redhat then! And they are *SO EASY* to compile...I think I installed them properly.


-Tommi

wow, you've actually talked to schilling. you must have
really made him mad. he may have answered your
question though. that error may be specific to your
version of redhat. that error message you get isn't
an error from cdrecord, it's an error from from the
kernel or some redhat library.
Did you tell him the error message, and he said
something about redhat without you telling him it's
redhat?

Yo,

No, Schilling didn't guess it was Redhat, I told him very accurately. He replied to me again:

"Did you try with an OS that supports multi-session?"

But surely Linux redhat 9.0 supports multi-session? Please tell me if it otherwise?

I need to reply to him something wise now. :-)

-Tommi

hey guys, gotta nothin to do with versions or distros,
just stop magicdev before burning the cds so automounting does not get in way.
do a rpm -e magicdev
i prefer error free cd writing than automounting.

Frank Jennings

really, it sort of does have something to do with distro's. it must
be the way redhat had automount set up that was causing problems
with your hardware. there's lots of people out there running automount
of some kind, and burning cd's ok.
thanks for posting your solution. it will give people things to try when they
get the same error.

Maybe u r right....mine is redhat 9
and with the automounting removed,
i can blank and burn cdrw without errors,
which i could not do earlier.

fermatjen is correct it has nothing todo with distro or version.

I have RedHat 9 and have no problems with my burner.
I start the program I am going to use before I ever load the cd into the drive, so the program already has control of the device. If it does not have the cd in the drive before hand all the programs I have run will tell you to load a cd or wait untill one is loaded.

It sounds more like you do not have the proper driver for the burners make and model.
Whichh can cause the system to the system to not recognize the burner properly.

If you have not done this already, I would suggest pulling the burner out of the computer and run kudzu to remove the configuration. Then while the burner is out of the sysystem, search and find the exact drivers for the burner. Then reinstall the burner and run kudzu again to configure the burner.

sorry, but that's utter nonsense. it's just automount not working right
with his hardware.

Straight to the point. If the automounter is having issues with his hardware then drivers are probably wrong in some asspect. Thus the drivers are what allow software to use the hardware properly.

i shouldn't have said that.
what i should have said was that there aren't any other drivers to try.
linux uses a generic interface to cdrom drives. it's the same driver
for them all. cdrdao support specific functions of a few drives, but
uses generic-mmc on almost everything. the only way to really change
the driver is change your kernel version to one where the cdrom code
is different.

With redhat 8s kernel I had to recompile my kernal with a differant driver for my DVD +RW to work properly. But when I updated my stystem with 9.0 and the lastest kernal I did not have the problem.

One interesting observation.
i do not need by cdr/cdrw disk mounted to write or rewrite it.
coz, software like cdrecord directly communicate with the scsi bus.
so befor rewriting a cd just umount /mnt/cdrom and do the cd cutting routine. works fine.

thats normal. you're creating a filesystem on the disk.
the same way you mke2fs or mkreiserfs. you don't have the filesystem
mounted to do that.

I read this fix here: http://club.myce.com/f48/fix-multise.../#.UBaK4COSHQQ by mathf NeroLinux Moderator.

[FIX] Multisession issue with Nero Linux 4
Dear all,

Many of you experiences issues with Nero Linux 4 when continuing a multisession disc. Apparently, Nero Linux 4 is looking for some shared libs in the wrong folder, so, of course it is _NEVER_ possible to continue a multisession disc.

This issue will of course be fixed in the next release (don't ask for a date ), but you can use the following trick to make it work for now. As root,

- Go in /usr/lib/nero (/usr/lib64/nero for the 64-bit version)
- Once you are there, copy the files libISOFS.so and libUDFImporter.so to the /usr/lib (/usr/lib64 for the 64-bit version).

This should let you use the multisession features of Nero Linux 4.
Also remember to manually delete these 2 files before you uninstall or upgrade the nero linux package.

After 9 years, I believe this is not a problem anymore.
And wtf is Nero Linux?

1 members found this post helpful.