SEO

The md5sum checks out ok for FC3-i386-disc1.iso, on the hard drive,
using <http://www.md5summer.org/>. as I haven't found a way to test
the
actual burned cd, thought I might post the output of cdrecord, using
<http://demosten.com/cdrfe/>.

does the burn look ok?
how would I check with md5sum from windows 2000?



Command line: cdrecord dev=1,0,0 -v -dao "C:\Documents and
Settings\Administrator\Desktop\New Folder (4)\FC3-i386-disc1.iso"

Everything is ready
To begin press 'Start' button

scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
SCSI buffer size: 64512
Cdrecord-Clone 2.01a32 (i686-pc-cygwin) Copyright (C) 1995-2004 Jörg
Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.8'.
atapi: -1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'CD-RW '
Identifikation : 'CDR-6S52 '
Revision : '6SR2'
Device seems to be: Generic mmc CD-RW.
Current: 0x000A
Profile: 0x000A (current)
Profile: 0x0009
Profile: 0x0008
Profile: 0x0002
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P
RAW/R96R
Drive buf size : 1422080 = 1388 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 617 MB
Total size: 708 MB (70:12.16) = 315912 sectors
Lout start: 708 MB (70:14/12) = 315912 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Reference speed: 2
Is not unrestricted
Is erasable
ATIP start of lead in: -11239 (97:32/11)
ATIP start of lead out: 359849 (79:59/74)
1T speed low: 0 (reserved val 0) 1T speed high: 4
2T speed low: 0 (reserved val 5) 2T speed high: 0 (reserved val
10)
power mult factor: 4 5
recommended erase/write power: 3
A1 values: 02 4A B0
A2 values: 5A C8 06
Disk type: Phase change
Manuf. index: 27
Manufacturer: Prodisc Technology Inc.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 43937
Forcespeed is OFF.
Starting to write CD/DVD at speed 4 in real SAO mode for single
session.
Last chance to quit, starting real write in 9 seconds. 8
seconds. 7 seconds. 6 seconds.
5 seconds. 4 seconds. 3 seconds.
2 seconds. 1 seconds. 0
seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is OFF.
Performing OPC...
Sending CUE sheet...
Writing pregap for track 1 at -150
Track 01: 617 of 617 MB written (fifo 100%) [buf 99%] 4.0x.
Track 01: Total bytes read/written: 646987776/646987776 (315912
sectors).
Writing time: 1099.375s
Average write speed 3.9x.
Min drive buffer fill was 98%
Fixating...
Fixating time: 24.253s
cdrecord: fifo had 10191 puts and 10191 gets.
cdrecord: fifo was 0 times empty and 10118 times full, min fill was
92%.

----- [10.01.2005 - 01:27:28], Finished in 0:18:55.773, Process exit
code is 0 -----

Command line: cdrecord dev=1,0,0 -v -dao "C:\Documents and
Settings\Administrator\Desktop\New Folder (4)\FC3-i386-disc1.iso"

Everything is ready
To repeat process press 'Start' button again



thanks,

Thufir Hawat

heh, forgot to say why I even posted: the disc failed the "verify"
when actually installing. Does that failure indicate a problem with
the disc or the data, pls?

thanks,

Thufir Hawat

thufir.hawat@mail.com wrote:

> The md5sum checks out ok for FC3-i386-disc1.iso, on the hard drive,
> using <http://www.md5summer.org/>. as I haven't found a way to test
> the
> actual burned cd, thought I might post the output of cdrecord, using
> <http://demosten.com/cdrfe/>.
>
> does the burn look ok?
> how would I check with md5sum from windows 2000?

if you burned on Linux side, why would you worry
about the md5sum on the win side? you can run
md5sum on the CD.

> Command line: cdrecord dev=1,0,0 -v -dao "C:\Documents and
> Settings\Administrator\Desktop\New Folder (4)\FC3-i386-disc1.iso"

.... you might want to move the ISO to a local native
Linux filesystem to alleviate any issues. and dont
use -dao
--
<< http://michaeljtobler.homelinux.com/ >>
A New York City ordinance prohibits the shooting of rabbits from the
rear of a Third Avenue street car -- if the car is in motion.

mjt wrote:
[..]
> if you burned on Linux side, why would you worry
> about the md5sum on the win side? you can run
> md5sum on the CD.

it's all from win2k, using <http://demosten.com/cdrfe/>.
still haven't figured how to check the cd

> > Command line: cdrecord dev=1,0,0 -v -dao "C:\Documents and
> > Settings\Administrator\Desktop\New Folder (4)\FC3-i386-disc1.iso"
>
> ... you might want to move the ISO to a local native
> Linux filesystem to alleviate any issues. and dont
> use -dao

I'll try it like:
cdrecord dev=1,0,0 -v FC3.iso
do I erase the cd-r/w first? if so, full or fast?

--
Thufir

"thufir.hawat@mail.com" <thufir.hawat@mail.com> writes:

>The md5sum checks out ok for FC3-i386-disc1.iso, on the hard drive,
>using <http://www.md5summer.org/>. as I haven't found a way to test
>the
>actual burned cd, thought I might post the output of cdrecord, using
><http://demosten.com/cdrfe/>.

What makes you think that the burn might be bad? Are you worrying too much?


>does the burn look ok?
>how would I check with md5sum from windows 2000?

In article <1105352741.888401.61730@c13g2000cwb.googlegroups. com>,
"thufir.hawat@mail.com" <thufir.hawat@mail.com> wrote:

>The md5sum checks out ok for FC3-i386-disc1.iso, on the hard drive,
>using <http://www.md5summer.org/>. as I haven't found a way to test
>the actual burned cd...

What I do is mount it and do a diff -r against the original files. In
your case the originals are on a CD image, but you can mount that via
loopback.

from my googling, mount loopback appears to be linux/BSD. for now, I'm
on win2k. however, I'll look into doing that from knoppix, thanks
--
Thufir Hawat

On Tue, 11 Jan 2005 01:58:54 -0800, thufir.hawat@mail.com wrote:

> from my googling, mount loopback appears to be linux/BSD.
> For now, I'm on win2k. however, I'll look into doing that
> from knoppix, thanks

You could also try the CD "rawread" script to get an md5sum for the
contents of the disk. Google for "coasterless CD burning".

--
Mark South: World Citizen, Net Denizen