[vox-tech] CDR annoyance

[Rod Roark]

CD burners frequently go bad.  I did have one that would not=20
recognize that a disc was in the drive, which looks similar=20
to your problem here.

You might try seeing if it will _read_ a CD.

-- Rod
   http://www.sunsetsystems.com/

On Sunday 24 November 2002 08:12 pm, Bill Kendrick wrote:
> Well, I'm trying to test CD-R writing under Melissa's Linux box
> (it's a Mitsumi CR-2801TE), and with some "audio CD-R's" I had,
> I was getting "cannot write - application code mismatch" from cdrecord,
> although it looked like it was sucessfully doing _something_.
>
> The discs were unmountable, though.
>
>
> So, I went out and bought a set of TDK 74min, 650MB discs,
> "for computer burning" (vs. just audio CD-Rs - I specifically AVOIDED
> getting the 80min discs I saw at the store, in case this drive didn't
> like them; I figured lowest common denominator).
>
>
> When I even try to use "cdrecord" with the "-dummy" option, it immediat=
ely
> quits out and yells:
>
>   cdrecord: No disk / Wrong disk!
>
>
> Specifically, the command is:
>
>   # nice --10 cdrecord -v  -dummy speed=3D4 dev=3D1,0,0 tuxpaint.raw
>
> and the full output is:
>
>   Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J=F6rg Schi=
lling
>   TOC Type: 1 =3D CD-ROM
>   scsidev: '1,0,0'
>   scsibus: 1 target: 0 lun: 0
>   Linux sg driver version: 3.1.22
>   Using libscg version 'schily-0.5'
>   atapi: 1
>   Device type    : Removable CD-ROM
>   Version        : 0
>   Response Format: 1
>   Vendor_info    : 'MITSUMI '
>   Identifikation : 'CR-2801TE       '
>   Revision       : '1.10'
>   Device seems to be: Philips CDD-522.
>   Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
>   Driver flags   : SWABAUDIO
>   FIFO size      : 4194304 =3D 4096 KB
>   Track 01: data    8 MB
>   Total size:       9 MB (00:58.69) =3D 4402 sectors
>   Lout start:      10 MB (01:00/52) =3D 4402 sectors
>   cdrecord: Input/output error. test unit ready: scsi sendcmd: no error
>   CDB:  00 00 00 00 00 00
>   status: 0x2 (CHECK CONDITION)
>   Sense Bytes: 70 00 02 00 00 00 00 06 00 00 00 00 3A 01
>   Sense Key: 0x2 Not Ready, Segment 0
>   Sense Code: 0x3A Qual 0x01 (medium not present - tray closed) Fru 0x0
>   Sense flags: Blk 0 (not valid)
>   cmd finished after 0.001s timeout 40s
>   cdrecord: No disk / Wrong disk!
>
>
> Any ideas?  Did I just pick up discs that won't work?
>
> Doing some Googling, for the "No disk / Wrong disk" message, I noticed
> one person who said their drive burns just fine, unless the machine's
> been on for a while.  Then it complains.  If they reboot, it becomes ha=
ppy
> again.  (I didn't notice if they mentioned what particular brand of dri=
ve
> it was.)
>
>
> Of course, most often people's suggestions are "try a different brand o=
f
> disc."
>
> Goddamn.  CD burning is irritating, isn't it!? >:^(
>
>
> -bill!
> i've got some nice, shiny gold coasters for sale :^)  never used!