I am using Mandrake 9 exclusively mounted on my master harddrive. My system is a PIII 866 with 384meg ram.

I have a cdrom mounted as master and an LG burner mounted as slave.

I have successfully installed X-CD-Roast and I can burn to CD-R and CD-RW using data files already stored on the harddrive.

My problem is that X-CD does not recognise my cdrom as being the reader with the result that I cannot copy disk to disk (on the fly)

How do I configure the fstab to recognise the cdrom? I am a complete newcomer to Linux and I am afraid that any hints or suggestions need to be in 'idiot proof' terms.

This is a copy of my fstab:

/dev/hda1 / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
/dev/hda6 /home ext3 defaults 1 2
none /mnt/cdrom supermount dev=/dev/hdc,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0
none /mnt/cdrom2 supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-15,codepage=850,umask=0 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0 0
none /mnt/floppy2 supermount dev=/dev/fd1,fs=auto,--,iocharset=iso8859-15,sync,codepage=850,umask=0 0 0
/dev/hdb1 /mnt/win_c2 vfat iocharset=iso8859-15,codepage=850,umask=0 0 0
/dev/hdb5 /mnt/win_d vfat iocharset=iso8859-15,codepage=850,umask=0 0 0
/dev/hdb6 /mnt/win_e vfat iocharset=iso8859-15,codepage=850,umask=0 0 0
none /proc proc defaults 0 0
/dev/hda5 swap swap defaults 0 0

Any help will be much appreciated.

i'd say use a decent program like eroaster or gtoaster, as xcdroast is horrendous. but you'll need to enable ide-scsi mulatino for your cdrom as well if you want to be able to use it as a source. open your /etc/lilo.conf and copy the existing hdX=ide-scsi ipion and add hdc=ide-scsi in teh same set of qoutes and reboot. then you'll need to change the dev=/dev/hdc to dev=/dev/scd1 or similar

Chris, what the heck is mulatino , is it a new thing that comes with boxer's gloves?
ROFL.

acid_kewpie... thanks for your help but I am afraid your reply needs to be a bit more detailed at this time. This is a steep learning curve for me having used Windows all my life.

I presume my burmer is referred to as cdrom2 in my fstab (scd0).

In your post I am not sure what the typo is: 'ipion'

Actually I am not sure what to do at all. Rather than wreck my system which is behaving superbly I would rather make sure of what I'm doing before I go ahead.

he meant "option"
You're not going to wreck your system.
Linux isn't like windows where you change one little
setting, which sets off a chain reaction, and you lose
everything. With most linux settings, you can change it
back if it doesn't work.

"open your /etc/lilo.conf and copy the existing hdX=ide-scsi ipion and add hdc=ide-scsi in teh same set of qoutes and reboot. then you'll need to change the dev=/dev/hdc to dev=/dev/scd1 or "

Thank you whansard. I would never have guessed 'option' but I did guess that 'mulatino' was 'emulation'.

In acid_kewpies quote above I presume that the second part of the statement refers to a change to be made in the fstab?

Also the line "hdX=ide-scsi" does not appear in my lilo.conf, should it be added and if so where?

I should really have attached a copy of the lilo.conf but i am at work at present and I'll have to do that this evening (if it is needed).

Thank you all for your help, regards

maybe you're using grub instead of lilo. they both perform the
same function. fstab controls which filesystems get loaded
at boot. You can still load and unload filesystems after boot.
the "hdX=ide-scsi" thing is a boot parameter to get the kernel
to ignore the drive for now, because you're going to set it up for
scsi emulation. cdrecord can only write to scsi-emulated drives.
supermount could be messing up xcdroast, I don't know.
he may have meant for you to change your cdrom to ide-scsi also,
so that xcdroast might see that too.
by the way, if your cdrom drive is hdc and your burner is the
only drive setup for scsi emulation, then
cat /dev/hdc | cdrecord -v dev=0,0,0 speed=8 fs=10m -
will copy the disk in hdc to your recorder at speed 8
fifo size 10 megs.
You may be booting with grub. You'll have to get an answer
from somebody else about that.

/me promises to take the oven gloves off next time...

acid_kewpie... thanks for your help, is your signature line an advertisement or a veiled insult?

Just wondering... no offence intended.

Regards

I made adjustments to the documents (lilo and fstab) as I thought was intended and it made no difference whatsoever. I have since restored the originals to avoid confusion down the track. This is a copy of my lilo.conf perhaps you could tell me what goes where?

boot=/dev/hda
map=/boot/map
default=linux
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
ignore-table
image=/boot/vmlinuz
label=linux
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=mount hdd=ide-scsi quiet"
vga=788
read-only
image=/boot/vmlinuz
label=linux-nonfb
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=mount hdd=ide-scsi"
read-only
image=/boot/vmlinuz
label=failsafe
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=nomount hdd=ide-scsi failsafe"
read-only
other=/dev/hdb1
label=windows
table=/dev/hdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
other=/dev/fd0
label=floppy
unsafe

Regards...

like this

image=/boot/vmlinuz
label=linux
root=/dev/hda1
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi hdd=ide-scsi quiet"

assuming your cdrom is on the same cable iwth your
burner and is the master.
You have to run lilo by typing
lilo
after any changes, then reboot to see.

Ok whansard... To make the changes I logged on as 'root' and I used kedit to make the earlier changes, I presume I can do the same with the changes you have suggested. Now problem number two and probably three! The line appears three times in the file, one ends in 'quiet', one ends in 'failsafe' and one is just the line. Does your change appear only once and is it in addition to the line that already appears or does it replace it.

I ask this because the change you have suggested I entered three times but in addition to the line that already exists and with the differing endings. The only thing I never did was to run lilo by typing it. I presume this can be done in konsole after I have made the changes with kedit?

Sorry to be such a nuisance... I guess I'll get there eventually,

Regards

the lilo.conf is a text file containing the settings that will
be used if you install lilo. I said that because changes
to lilo.conf will make no difference unless you run lilo
again.
there are several boot configurations there in your lilo.conf
the word "label" shows the boot config that you are editing.
Don't you see when you boot, lilo asks you which to boot,
and see that the default at top is "Linux", and the text i
pasted contained label=linux
each time you see a new image=something, it
is a different configuration with a different label.
so you really only have to change it on the one you
want to boot.

less confusing version :
add hdc=ide-scsi just before the hdd=ide-scsi,
inside the quotes with it, under label=linux,
like i typed in the other post.
save and exit,
run lilo
reboot

whansard... I do thank you for the time you have spent on this problem. I tried the 'fix' that you suggested without success. I also tried the 'fix' that the author suggested. I logged on to the CD-Roast site and he acknowledges that there is a problem in this respect and he suggested:

In the /etc/modules.conf insert > options ide-cd ignore='hdc hdd'
This tells the ide driver to ignore the two devices I want to use in CD-Roast

In the /etc/lilo.conf insert > append="hdc=ide=scsi hdd=ide=scsi"
This tells the kernel to install scsi emulation for the two drives

I tried this and CD-Roast threw it's hands in the air and simply refused to work. It told me I need a scsi contoller in the kernel. I replaced the original files and all is back to normal.

I suspect that I am not doing something properly and when I have a bit more confidence at this game I'll try again. In the meantime I thank you and acid_kewpie for your help. If another idea surfaces in your knowledge bank I'd be pleased to hear it.

Regards.