Re: rip vcd / copy vcd

[Uwe Dippel <udippel_(_at_)_uniten_(_dot_)_edu_(_dot_)_my>]

On Tue, 22 Jun 2004 22:13:04 -0700, Jacob Meuser wrote:

> Oh, never mind that, I just woke up from a nap ...

Don't worry !

> As far as cdrdao, (from reading the manage, I've never used cdrdao)
> I think that you need to use the --datafile option in your command.
> 
> $ cdrdao read-cd --device /dev/rcd1c --datafile disc.bin toc

The default is data.bin and written correctly (AFAICanSee)

> $ cdrdao write --device /dev/rcd1c --datafile disc.bin toc

It starts to rumble along, wait, rumble further, BURN-FREE, etc:

# cdrdao write --device /dev/rcd1c --eject videocd.cue  
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas_(_at_)_daneb_(_dot_)_de>
  SCSI interface library - (C) Joerg Schilling
  Paranoia DAE library - (C) Monty

Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.

Using libscg version 'andreas-0.5-UNIXWARE_Patch'

/dev/rcd1c: _NEC NR-7900A       Rev: 1.23
Using driver: Generic SCSI-3/MMC (raw writing) - Version 2.0 (options 0x0000)

Starting write resid: 1
at speed 4...
Pausing 10 seconds - hit CTRL-C to abort.
Process can be aborted with QUIT signal (usually CTRL-\).
resid: 1
Turning BURN-Proof on
?: Input/output error.  : scsi sendcmd: retryable error
CDB:  5A 00 05 00 00 00 00 00 A4 00
status: 0x0 (GOOD STATUS)
resid: 164
cmd finished after 0.011s timeout 20s
ERROR: Cannot retrieve write parameters mode page.
resid: 1
Turning BURN-Proof on
ERROR: Cannot setup disk-at-once writing for this drive.
ERROR: Writing failed.
?: Input/output error.  : scsi sendcmd: retryable error
CDB:  1E 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.010s timeout 20s
ERROR: Cannot prevent/allow medium removal.

# 

This doesn't actually look like a driver problem (I'd use the standard
driver in any case); plus from my experience, when it doesn't find the
driver, it will keep asking.
It *did* ask for the driver for that COMPAQ, though.


> Also note, that cdrdao asked you to specify which driver to use,
> and if you check the website it tells you to, you will see what
> driver option you need.  You will probably need a similar option
> for cdrecord.


It identifies generic-mmc-raw. When used, the result is exactly identical.
(Look at the output further up; it uses this driver automatically.)


Somehow this doesn't seem to want to work; but so far I don't intend to
give up !


Thanks !