[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Big problems w/ writing any type of cdrom



Hello,

Pigeon and Carl Fink, thank you  for your replies!

See below...

--- Pigeon <jah.pigeon@ukonline.co.uk> wrote:
> On Tue, May 13, 2003 at 01:46:39PM -0700, Joris
> Huizer wrote:
> > Hello everybody,
> > 
> > Sorry about all the confusion the past few days -
> but
> > I really suspect things are terrible wrong when I
> burn
> > CDs: both data CDs and debian installation cds
> seem to
> > be malfunctioning !!
> > 
> > I should have tested data CDs more before - but
> today
> > I found those can't be mounted - just like the
> debian
> > installation cds which can't be read completely
> > 
> > I using this shell script to burn:
> > 
> > 
> > #!/bin/sh
> > 
> > mkisofs  -r   -o cd_image   "$1/"
> > cdrecord -v speed=24 blank=all dev=0,1,0  -data 
> > cd_image
> > cdrecord -v -eject speed=24 dev=0,1,0 cd_image
> 
> I'd try only the one invocation of cdrecord. Delete
> the line with
> blank=all in it. Iff you are using CD-RWs do the
> blanking as a
> separate, preceding step, by hand.
> 

As I didn't know exactly how to do blanking by hand, I
tried xcdroast - however, that program uses cdrecord
too so it doesn't solve anything - what's the program
to use for blanking ?

> > When copying the contents off the cd, I get the
> > following error output:
> > 
> > hdc: cdrom_decode_status: status=0x51 { DriveReady
> > SeekCompleteError } 
> > hdc: cdrom_decode_status: error=0x30
> > 
> > during the hole damn cd writing process, not a
> single
> > other (custom) proces was running; One thing which
> > feels wrong is, at first the fifo was 100% or 98%
> -
> > but after some time it rapidly dropped to very low
> > values ( < 10% ) - however, I don't know wether
> this
> > has something to do with the incorrect burning
> 
> I should say it probably does. I don't think
> "burnproof" drives are
> guaranteed 100% "burnproof" under all conditions.
> 
> What is the minimum fifo fill reported by cdrecord
> when it finishes?
> 

I'm not sure, but I think it was extremely low (only a
few %)

> What sort of HD/MB/CPU have you got?
> 

Sorry I don't know the exact numbers - my dad has the
info *somewhere* here but I can't find it;

> Try setting speed=2 or something similarly slow and
> see if your fifo
> fill levels improve. Use the -dummy option to
> experiment without
> wasting CD-Rs.
> 

I tried the following commend: 
 cdrecord -v -eject -dummy -force speed=2 dev=0,1,0
cd_image 

The speed seemed to be 98%/100% the hole time - and
the minimum fifo fill was 81% - do you think this is a
reasonable number (say, enough to assume this will
work correctly) or should I try speed=1 ?


I was using the high value of speed=24 because that's
what the cd writer reports (48x24x48) - well any way
that's too much I see now.


> -- 
> Pigeon
> 
> Be kind to pigeons
> Get my GPG key here:
>
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F
> 

> ATTACHMENT part 2 application/pgp-signature 



__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com



Reply to: