Very Computer

Hello,

Here is is the question:

How do I copy a CD from one CD-ROM drive to another CD-ROM drive (yes this
is a CD writer HP6020i). Has anyone does this, is doing this and if so
could you please post your thoughts and suggestions to this group.

thx nand

I burnt a 500+Mb data CD at 2x on-the-fly (i.e. in a pipeline with 'mkisofs'
- I didn't have
enough free space for the ISO image to reside on the HD) with a CDD2000 on a
486DX133.

It supports mastering/burning Audio CD's too, so that's me sorted... Now if
I can just get the
time to even think about playing with xcdroast (a Linux app) to get that
working with it...

The drive compatibility list explicitly supports the HP6020i (basically a
Philips CDD2600).

If you just need to copy a data CD, you should be able to use 'dd' to read
the source disk
and pipe the resulting image straight into 'cdrecord'. I think. I would point
out that  I haven't
actually done this on FreeBSD yet...

Hope this helps - let me know if there's any interest in instructions for
creating the drivers,
devices and links to get it running on FreeBSD, and I'll maybe stick up a web
page.

Cheers,

AS

Quote:> Can you give me a clue as to how you made cdrecord 1.5 work with FreeBSD?

For what it's worth, I find that cdrecord 1.5 works very nicely with FreeBSD.

At the moment, I'm happy enough with it not to have to boot Windoze to use
Jeff Arnold's (www.goldenhawk.com) excellent CDRWIN program on Windoze
95 at all...

I just worked out how to make 'cdrecord' duplicate a CD recordable
master, and it does that on-the-fly too...  As it also supports mastering
audio CDs from .WAV files, I think that I'm pretty much all set here.. :=)

Quote:> I've hit a stone wall trying to make cdrecord 1.5 work with FreeBSD 2.2.1
> and a Ricoh 6200.

Probably wouldn't be too hard to add others, but this list (and the presence of
the
CDD2000 on it) is at least one reason I bought this model of CDR (the price of
$220
for a refurb with a years warranty from Philips was hard to turn down, too).

Quote:> The drive reads fine under FreeBSD, and reads/writes
> fine under Windoze NT 4.0 and the supplied software, Easy CD Pro 2.11.

> But, all I get is:

Quote:> which I think suggests that the ioctl isn't getting through.  I've tried
> linking /dev/scgx to /dev/cd0a, /dev/cd0c, and /dev/rcd0.ctl.  I even
> made a /dev/cd0.ctl:

Quote:> but that didn't work either!

> What magic incantation am I missing?  At this point, I'll do anything
> so that I can wipe that stupid Windoze NT off my other disk...

I think the missing piece of the puzzle is that you're trying to write to a
CDROM...

There's a few clues in various places that this isn't the way to go, but no-one
really spells it out anywhere in the various docs I saw.

I cannot say that this recipe is definitively correct, merely that it works fine
for me
on FreeBSD 2.2.2-RELEASE with a Philips CDD2000 and cdrecord 1.5...

What I did was:

i)    Include the 'worm', 'pt' and 'sctarg' drivers in the kernel.

ii)    Include the 'su' (SCSI user) and 'ssc' (Super SCSI) pseudo-devices in the
kernel.

I organised this so that 'worm0' came before 'cd0' - this also put my CD back to
'cd0', which
is nice. I lifted the lines from the LINT file, and moved the declaration of
'scbus0' to the top, like
this:

controller      scbus0

device worm0 at scbus?  # SCSI worm
device pt0 at scbus?    # SCSI processor type
device sctarg0 at scbus? # SCSI target

# These are only for watching for bitrot in old SCSI code.
pseudo-device   su              #scsi user
pseudo-device   ssc             #super scsi

device          sd0

device          od0     #See LINT for possible `od' options.

device          st0

etc. etc. etc.

I see this when booting (or from 'dmesg'):

ahc0 <Adaptec 2940 SCSI host adapter> rev 3 int a irq 11 on pci0:14
ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs
ahc0 waiting for scsi devices to settle
ahc0:A:5: refuses synchronous negotiation. Using asynchronous transfers
(ahc0:5:0): "IMS CDD2000/00 1.26" type 5 removable SCSI 2
worm0(ahc0:5:0): Write-Once
(ahc0:6:0): "PLEXTOR CD-ROM PX-6XCS 1.06" type 5 removable SCSI 2

I think the implication is that any CDRs not recognised by the worm driver
probably won't be usable...

Now make the 'worm' device, you can use the MAKEDEV script for this.

Also, you need to make the 'su' devices. Use the script at the bottom of the
'README.xxxBSD' file in the 'cdrecord'  distribution.

Now create a link to 'scgx' from 'rworm0.ctl'. You're all set.

You can still mount CDs on the CDR, just use 'worm0' instead of 'cd0'.

Hope this helps.

Cheers,

AS

I've used it with Win95 on a 133Mhz Pentium, all SCSI, and have noticed
that I can't copy directly from a cdrom to the philips, the software
can't keep a constant data rate to the CD writer.  I have to first copy to
a hard disk in order to get a sucessful copy.  Have you been able to
copy a CD directly with cdrecord?  When copying a CD, 'dd' should be
sufficient or is mkisofs still required?

thanks
J. Rushford

Quote:> I've used it with Win95 on a 133Mhz Pentium, all SCSI, and have noticed
> that I can't copy directly from a cdrom to the philips, the software
> can't keep a constant data rate to the CD writer.  I have to first copy to
> a hard disk in order to get a sucessful copy.  Have you been able to
> copy a CD directly with cdrecord?  When copying a CD, 'dd' should be
> sufficient or is mkisofs still required?

I'm surprised you're having difficulties under Doze95 with your setup.

My hardware is:

486 DX4/133, 32Mb
AHA 2940
Plextor 6X
CDD2000
Quantum Fireball EIDE in PIO Mode 3 (most the MB supports)

I can copy data or audio CDs happily on-the-fly with no intermediate
disk image. I use CDRWIN on '95, because it gives very good control
over the pregap etc when mastering audio CDs, and permits multiple indexes
on a (huge!) sound file that contains mutiple tracks etc. Good software for
$79. I also found that the "noddy" CD-Copy program that came with
Adaptec's EZ-SCSI 4.0 was fine for copying CDs on the fly. ..

I switch on jitter correction on the Plextor for DAE and take the speed
down to 2x, because this model has buggy firmware for DAE, unlike the
rest of the model  range (but it's flawless for  data, and it cost $49,
what'dya want,  *? :=)

I can't use this drive for DAE under FreeBSD, because the author of
'tosha' (the only DAE program I can find for *BSD) obviously spent
more money that I did on his CDROMs, & finds that they don't need it..
Resultant WAV files are not usable for me - YMMV.

To duplicate a CDR with an ISO9660 image on it with 'cdrecord', use the
'-isosize' flag - this stops it from attempting to read the last two blocks
that all CDRs write to the end of the CDR blank, which cannot be read and
will cause the CDROM to timeout and the CDR to buffer underrun (this is
from the 'cdrecord' man page). I set CDR_SPEED and CDR_DEVICE in
the environment, and specify the CDROM device on the command line, I.e.:

    cdrecord -v -isosize /dev/cd0c

This works  very nicely, thank you. I don't believe that the above flag would
be required when copying  a pressed  CD, although I haven't tried it.

I can also 'master' ISO9660 filesystems from the EIDE drive on-the-fly at
full (writer) speed, although kicking off something disk-intensive like a find
from '/' can definately provoke a buffer underrun (yes, I was trying !!).

"Normal" activity, like reading mail/news/surfing doesn't seem to cause a
problem, although Netscape eating all your memory and causing swapping
to start would probably be a bad thing, despite 'cdrecord' locking itself into
memory to avoid being swapped out and apparently using a 4Mb FIFO
to feed the CDR..

It's a little worrying to see comments like "for watching bit rot in old code"
against the generic SCSI drivers, but they seem to work OK so far...

I was so e*d that this all worked that I threw up a web page with my
experiences, what I did to get it working and gross, unwarranted, speculation
about things I have no way of testing (like other CDRs etc) :=) If you're
interested, check out:

    http://www.veryComputer.com/~spadger/CDR-FreeBSD.html

Pip pip!

AS

Quote:>   When copying a CD, 'dd' should be
> sufficient or is mkisofs still required?

--
cheers, J"org

Never trust an operating system you don't have sources for. ;-)