cdrecord/mkisofs and dd, what is the difference?
Michael Wang
using cdrecord on Windows.
I googled around, and find that the way to make
exact CD copy using cdrecord is the two step process:
1) dd if=/dev/cdrom0 of=cd_copy.iso
2) cdrecord <options> cd_copy.iso
While I have no problem with this on Unixes, I have
difficulty doing step 1) on Windows.
I can, however, make an image of the source CD with the command:
mkisofs -J -r -o cd_copy.iso /directory
but I am afraid "cd_copy.iso" is NOT exact copy of the original CD.
Is it possible to make _exact_ copy of a CD using cdrecord on windows?
PS:
I can use dd under uwin on Windows 2000, but "cdrecord -scanbus"
binary coredumped. While cdrecord binary works on NT, uwin does
not recognize the /dev/cdrom*.
--
Michael Wang * http://www.unixlabplus.com/ * mw...@unixlabplus.com
Why pay $35 for a domain only if you can get domain and hosting at
www.name2host.com? my name2host username = "mw...@unixlabplus.com"
--
Michael Wang * http://www.unixlabplus.com/ * mw...@unixlabplus.com
Why pay $35 for a domain only if you can get domain and hosting at
www.name2host.com? my name2host username = "mw...@unixlabplus.com"
Joerg Schilling
Michael Wang <mw...@unixlabplus.com> wrote:
>I would like to make an _exact_ copy of a CD
>using cdrecord on Windows.
>
>I googled around, and find that the way to make
>exact CD copy using cdrecord is the two step process:
>
>1) dd if=/dev/cdrom0 of=cd_copy.iso
>2) cdrecord <options> cd_copy.iso
>
>While I have no problem with this on Unixes, I have
>difficulty doing step 1) on Windows.
It will not work to copy a Solaris boot CD on Solaris this way.
Why don't you read the man pages for cdrecord? There is a way to
create a correct copy that works on any sopported OS and it is mentioned in
the man pages...
>PS:
>I can use dd under uwin on Windows 2000, but "cdrecord -scanbus"
>binary coredumped. While cdrecord binary works on NT, uwin does
So you did install a broken ASPI on your NT.
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schi...@fokus.fhg.de (work) chars I am J"org Schilling
URL: http://www.fokus.fhd.de/usr/schilling ftp://ftp.berlios.de/pub/schily
Michael Wang
Joerg Schilling <j...@cs.tu-berlin.de> wrote:
>>1) dd if=/dev/cdrom0 of=cd_copy.iso
>>2) cdrecord <options> cd_copy.iso
>
>Why don't you read the man pages for cdrecord? There is a way to
>create a correct copy that works on any sopported OS and it is mentioned in
>the man pages...
I have read the man pages 10+ times, but I could not figure out
how to do this common task (To make an exact CD copy). Then I googled
around and found that I am not the only one confused. Please
see the summary in the URL below:
http://www.linuxmanagers.org/pipermail/linuxmanagers/2002-August/000666.html
People came up all sorts of answers. Most people suggested "dd" method,
so I assumed that it is the correct method. Now you said that it ain't
correct, can you spelled out what is the correct method, for my benefit
and people who read this thread?
I used cdrecord binary distribution for windows, but "cdrecord -scanbus"
core-dumped on two of my windows 2000 computers. I do not have CD-RW drive
hardware installed on these two computers, could that be a problem? Or other
people have the same problem? I run the command to find if cdrecord.exe
works before I purchase a CD-RW drive.
Thanks.
Joerg Schilling
Michael Wang <mw...@unixlabplus.com> wrote:
>>>1) dd if=/dev/cdrom0 of=cd_copy.iso
>>>2) cdrecord <options> cd_copy.iso
>>
>>It will not work to copy a Solaris boot CD on Solaris this way.
>>Why don't you read the man pages for cdrecord? There is a way to
>>create a correct copy that works on any sopported OS and it is mentioned in
>>the man pages...
>
>I have read the man pages 10+ times, but I could not figure out
>how to do this common task (To make an exact CD copy). Then I googled
Please note: telling other people that you did read the man page does
not result in getting the required knowledge. You need to _read_ the man page.
It seems that you lack basic OS knowledge....
from man cdrecord:
...
SEE ALSO
cdda2wav(1), readcd(1), scg(7), fbk(7), mkisofs(8), rcmd(3),
ssh(1).
Why don't you do what other people do and read the referenced man pages?
This part did not change for nearly 2 years.
>around and found that I am not the only one confused. Please
>see the summary in the URL below:
>
>http://www.linuxmanagers.org/pipermail/linuxmanagers/2002-August/000666.html
>
>People came up all sorts of answers. Most people suggested "dd" method,
>so I assumed that it is the correct method. Now you said that it ain't
>correct, can you spelled out what is the correct method, for my benefit
>and people who read this thread?
It does not help to find other people who did not read the man page :-(
>
>I used cdrecord binary distribution for windows, but "cdrecord -scanbus"
>core-dumped on two of my windows 2000 computers. I do not have CD-RW drive
>hardware installed on these two computers, could that be a problem? Or other
>people have the same problem? I run the command to find if cdrecord.exe
>works before I purchase a CD-RW drive.
Well you did proove that did not even read my last posting:
You installed a broken ASPI. This broken ASPI is dynamically loaded and causes
cdrecord to dump core!
If you had a broken dynamic libc on your system many programs would dump
core....
Michael Wang
Joerg Schilling <j...@cs.tu-berlin.de> wrote:
>Please note: telling other people that you did read the man page does
>not result in getting the required knowledge. You need to _read_ the man page.
get the required knowledge from you or the other people.
Telling other people that I have read the man page, and have googled
around is to get an specific answer for an specific question, as the
answer is not easily available from the man page, or from the internet.
>It seems that you lack basic OS knowledge....
Interesting conclusion.
>from man cdrecord:
>...
>SEE ALSO
> cdda2wav(1), readcd(1), scg(7), fbk(7), mkisofs(8), rcmd(3),
> ssh(1).
>
>Why don't you do what other people do and read the referenced man pages?
>This part did not change for nearly 2 years.
I have read these man pages. That is why I meantioned "mkisofs"
in my previous post, but I do not think it is the right tool to
make a CD *copy*. As I gets all sorts of errors complaining about
non-standard filenames. I need a tool to make raw copy, not at
filesystem level.
Read between your lines, I think the correct way to
make a CD copy (exact copy) might be:
readcd dev=a,b,c f=cd.iso
cdrecord dev=x,y,z cd.iso
Unfortunately, I could not try it. It seems readcd binary needs
drand48() but could not located in ctgwin1.dll. The exact error
message is:
The procedure entry point drand48 could not be located in the
dynamic link library ctgwin1.dll.
I get the cdrtools binary distribution from an URL referenced on
your website.
I would appreciate that you can confirm this is the right way, and
I will try to compile a working copy of the binary myself.
I would also appreciate that you can tell me why you think "dd" method
isn't correct. "dd" is supposed to make an exact copy of floppies
and cdrom's. And what is the main difference among readcd, dd, and mkisofs?
>>around and found that I am not the only one confused. Please
>>see the summary in the URL below:
>>
>>http://www.linuxmanagers.org/pipermail/linuxmanagers/2002-August/000666.html
>>
>>People came up all sorts of answers. Most people suggested "dd" method,
>>so I assumed that it is the correct method. Now you said that it ain't
>>correct, can you spelled out what is the correct method, for my benefit
>>and people who read this thread?
>
>It does not help to find other people who did not read the man page :-(
It does not help to get me an answer, but if 15 people in the
linuxmanagers' list did not come up with correct answers, then
I think the problem is not they do not read the man pages.
As a curiosity, the readcd man page says:
"readcd - read or write data Compact Discs"
How can readcd be used to write data Compact Discs? I did not find it
in the man page. Isn't it the job of cdrecord?
>Well you did proove that did not even read my last posting:
>
>You installed a broken ASPI. This broken ASPI is dynamically loaded and causes
>cdrecord to dump core!
>
>If you had a broken dynamic libc on your system many programs would dump
>core....
I did read your last posting, and with care. The issue is that just like
your man pages, I have hard time comprehending.
I have an working windows 2000. I even did a fresh install on a spare
machine just to make sure the windows 2000 is ok. I downloaded cdrtools
binary for windows, but "cdrecord -scanbus" dumped core. Where did
"broken ASPI" come in? And how do I fix it?
It appears everything else runs fine except cdrecord.exe. I do not
think I have libc library in my windows 2000 box.
I would appreciate your reply. Thanks.
Joerg Schilling
Michael Wang <mw...@unixlabplus.com> wrote:
>>from man cdrecord:
>>...
>>SEE ALSO
>> cdda2wav(1), readcd(1), scg(7), fbk(7), mkisofs(8), rcmd(3),
>> ssh(1).
>>
>>Why don't you do what other people do and read the referenced man pages?
>>This part did not change for nearly 2 years.
>
>I have read these man pages. That is why I meantioned "mkisofs"
>in my previous post, but I do not think it is the right tool to
>make a CD *copy*. As I gets all sorts of errors complaining about
>non-standard filenames. I need a tool to make raw copy, not at
>filesystem level.
>
>Read between your lines, I think the correct way to
>make a CD copy (exact copy) might be:
>
>readcd dev=a,b,c f=cd.iso
>cdrecord dev=x,y,z cd.iso
This is correct. It is also mentioned in various README's in the cdrtools
package.......
>Unfortunately, I could not try it. It seems readcd binary needs
>drand48() but could not located in ctgwin1.dll. The exact error
>message is:
>
> The procedure entry point drand48 could not be located in the
> dynamic link library ctgwin1.dll.
This is caused by the fact that you use a too old cygwin installation.
Cdrtools is source ware, the best idea is to compile it yourself.
If you do not like to compile it yourself, you may check google to
find places with recent binaries.
>I would appreciate that you can confirm this is the right way, and
>I will try to compile a working copy of the binary myself.
Some time ago, I gave up to create win32 binaries for cdrtools because
it takes a lot of time for me (I have no win32 up and running but must reboot
a UNIX system...) and because the Cygwin people would not alloe me to
publish win32 binaries thay include cygwin1.dll but do not include the needed
sources to compile exactly this cygwin1.dll. Before I used to point to
the official Cygwin server for sources....
>I would also appreciate that you can tell me why you think "dd" method
>isn't correct. "dd" is supposed to make an exact copy of floppies
>and cdrom's. And what is the main difference among readcd, dd, and mkisofs?
dd will not work on OS without 'devices', dd will not work as expected if there
is a a partition record on the CD and the OS you run "understands" and
honors the partition record....
>>>http://www.linuxmanagers.org/pipermail/linuxmanagers/2002-August/000666.html
>>>
>>>People came up all sorts of answers. Most people suggested "dd" method,
>>>so I assumed that it is the correct method. Now you said that it ain't
>>>correct, can you spelled out what is the correct method, for my benefit
>>>and people who read this thread?
>>
>>It does not help to find other people who did not read the man page :-(
>
>It does not help to get me an answer, but if 15 people in the
>linuxmanagers' list did not come up with correct answers, then
>I think the problem is not they do not read the man pages.
Well 'Linux Managers' behave similar to 'Linux kernel people (Linus included)'
then just believe me that many of these people do not like to learn from other
people who know better.
>As a curiosity, the readcd man page says:
>
> "readcd - read or write data Compact Discs"
>
>How can readcd be used to write data Compact Discs? I did not find it
>in the man page. Isn't it the job of cdrecord?
Depends.... If the CD-RW has been for formatted for random read/write or if you
are refering a DVD-RAM, then readcd is the right tool.
On most OS, you cannot write to a drive that identifies as CD-ROM - with readcd
you can.
>>You installed a broken ASPI. This broken ASPI is dynamically loaded and causes
>>cdrecord to dump core!
>>
>>If you had a broken dynamic libc on your system many programs would dump
>>core....
>
>I did read your last posting, and with care. The issue is that just like
>your man pages, I have hard time comprehending.
>
>I have an working windows 2000. I even did a fresh install on a spare
>machine just to make sure the windows 2000 is ok. I downloaded cdrtools
>binary for windows, but "cdrecord -scanbus" dumped core. Where did
>"broken ASPI" come in? And how do I fix it?
It may be part of the 'fresh 2000 installation' :-(
M$ is junkware....
>It appears everything else runs fine except cdrecord.exe. I do not
cdrecord does need ASPI on win32 and it assumes that the installed ASPI
works as it is documented by Adaptec....
Try to look for ForceASPI to install a non-broken ASPI. But note that
this is an answer you should rather try to get from a M$ related group.
Michael Wang
Joerg Schilling <j...@cs.tu-berlin.de> wrote:
>>
>> The procedure entry point drand48 could not be located in the
>> dynamic link library ctgwin1.dll.
>
>This is caused by the fact that you use a too old cygwin installation.
>Cdrtools is source ware, the best idea is to compile it yourself.
>Try to look for ForceASPI to install a non-broken ASPI. But note that
>this is an answer you should rather try to get from a M$ related group.
(1)
I did two things:
(a) Compiled a new version of cdrtools-2.0 binaries under cygwin/win2k
(b) Installed aspi_v470.exe and rebooted the box
These two things allow "cdrecord.exe -scanbus" and "readcd.exe" to run.
However I get stuck in "readcd". At the begining of "readcd" session,
"readcd" reports an error, and at the very end, it reports a same (to me)
error.
I googled, and found the problem description in the URL below matches mine:
http://lists.suse.com/archive/suse-multimedia-e/2002-Mar/0038.html
My error messages are included at the end of this post.
My computer is "Dell PowerEdge 4350" with scsi CDROM (no CD-RW drive)
and scsi hard drive, all Dell original hardware.
(2)
Can I use cdrtools to read and write from/to hard drives reported on
"cdrecord.exe -scanbus"? I would like to use cdrtools as dump/restore/dd
as on Unix boxes, to backup and clone a disk, basically what "ghost.exe" does.
Is it possible?
(3)
By the way, there is a bit of problem with "make install". It expects
to find filenames like "#12345#", while the actual filenames are like
"#12345#.exe".
Thanks.
$ /opt/schily/bin/cdrecord.exe -scanbus
Cdrecord 2.0 (i686-pc-cygwin) Copyright (C) 1995-2002 Jörg Schilling
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) 'NEC ' 'CD-ROM DRIVE:466' '1.06' Removable CD-ROM
0,6,0 6) *
0,7,0 7) HOST ADAPTOR
scsibus1:
1,0,0 100) *
1,1,0 101) 'IBM ' 'DRVS09D ' '0140' Disk
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) 'DELL ' '1x3 U2W SCSI BP ' '5.12' Processor
1,7,0 107) HOST ADAPTOR
Administrator@ULWIN2K ~
$ /opt/schily/bin/readcd.exe dev=0,5,0 f=/tmp/cd.iso
/opt/schily/bin/readcd: I/O error. set cd speed: scsi sendcmd: retryable error
CDB: BB 00 FF FF FF FF 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.001s timeout 40s
Read speed: 2999 kB/s (CD 17x, DVD 2x).
Write speed: 0 kB/s (CD 0x, DVD 0x).
Capacity: 352123 Blocks = 704246 kBytes = 687 MBytes = 721 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (0,5,0) disk to file '/tmp/cd.iso'
end: 352123
/opt/schily/bin/readcd: I/O error. read_g1: scsi sendcmd: retryable error
CDB: 28 00 00 05 5F 62 00 00 19 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 00 05 5F 79 0A 00 00 00 00 64 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0
Sense flags: Blk 352121 (valid)
cmd finished after 0.035s timeout 40s
/opt/schily/bin/readcd: I/O error. Cannot read source disk
/opt/schily/bin/readcd: Retrying from sector 352098.
........................~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~+~~~-~~~
/opt/schily/bin/readcd: I/O error. Error on sector 352121 not corrected. Total of 1 errors.
Time total: 371.251sec
Read 704196.00 kB at 1896.8 kB/sec.
Joerg Schilling
Michael Wang <mw...@unixlabplus.com> wrote:
>However I get stuck in "readcd". At the begining of "readcd" session,
>"readcd" reports an error, and at the very end, it reports a same (to me)
>error.
>
>I googled, and found the problem description in the URL below matches mine:
>
>http://lists.suse.com/archive/suse-multimedia-e/2002-Mar/0038.html
>
>My error messages are included at the end of this post.
>
>My computer is "Dell PowerEdge 4350" with scsi CDROM (no CD-RW drive)
>and scsi hard drive, all Dell original hardware.
You did not mention what type of media you try to copy....
Read README.copy & README.verify
>(2)
>
>Can I use cdrtools to read and write from/to hard drives reported on
>"cdrecord.exe -scanbus"? I would like to use cdrtools as dump/restore/dd
>as on Unix boxes, to backup and clone a disk, basically what "ghost.exe" does.
>Is it possible?
???? If you do not write what ypou like to do, nonody may help you.
>(3)
>
>By the way, there is a bit of problem with "make install". It expects
>to find filenames like "#12345#", while the actual filenames are like
>"#12345#.exe".
This is a problem with the non-standard behaviour of Win32 systems.
Only "make install" is affected by the problem. Adding support for .exe to
the makefile system would be not trivial. Use find . -name '*.exe' -exec ....
to copy the files.
Your drive at 0,5,0 does not implement the SCSI/mmc command set correctly.