> And for most of the drives, you have to send special commands to do the
> writing (it is a 'write track at once' command, instead of the normal
> 'write').
> In any case, you will need the scsi specs of the cd-writer, and write
> a special program for it (there is no need of a special driver, you can use
> the 'cd' driver, and send raw scsi commands).

What SCSI-spec exactly. I have a list of (numeric) commands the writer
supports, and short verbal descriptions what they do, is this sufficient?


> I've written such a program for a Ricoh CD-R, but I switched back to GEAR
> under winlooze, because it has much more powerfull error recovery than my
> program :)

Hm, i'm not too deeply into programming, but just for curiosity, could you send
me that program, please? :)


> And, as a unix machine need to be single user while writing a cd (to be sure
> there won't be any speed problems), it does't make a big difference for it to
> be under ms-windows.

Hm, i wonder if i have to take the machine single-user. Of course if that
swap-lag occurs that 1.2 has (and which stalls the machine for seconds with the
SCSI-led on), the CD to burn is hosed, but this would also appear in single
user mode, i guess.

On the other side, i see what a friend of me does under Linux with his burner,
and get more envious every thime he tells me about making his own CDROMS,
audio-CDs, even sampling audio-tapes and burning the tracks to audio-CDs.
He's using Xcd-roast... any chance to get this to work when we can transfer
images to CDs safely? I haven't looked into it yet...


Hubert

-- 
Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>