I'm still trying to figure it out. :)
I removed my apt-getable version of cdrecord and downloaded the latest
version, compiled, installed. This one came with mkisofs, which
debian/testing doesn't have yet (not sure why. Just like why does
debian/testing have pan-0.7.6). I burned a new CD-RW and it wouldn't
mount. I mounted an older burned CD, and it read just fine.
Next, I'll take it apart and dust it out a bit. If that doesn't work,
it will be considered a CDR -- maybe I'll even scratch off the W on
the front. ;)
(All of this when I could just copy those files to the samba share,
and burn them from my windows box on an 8x burner. But that's not the
point! :)
-Rob
> On 20010725.2001, rccole said ...
>
> Rob,
>
> If you solve your CDRW problem, please post it to the list. I have a
> similar problem with my yamaha 6416, that I have not taken the time to
> solve. The drive worked for a couple years but has now stopped reading
> its own CDR's. Strange, but CDRW's come out fine. Even weirder, if
> I burn a CDR, my machine won't mount it, but my Windows machine at work
> can read the directory and I have spot checked some of the files.
>
> I wonder if somehow it is a reading problem, rather than a writing
> problem.
>
> It is my understanding, that burning a CD without error means nothing.
> If you read Schilly's site for cdrecord, you will find his rant about
> the inadequate SCSI interface that disallows a complete set of return
> feedback codes. Supposedly, this has been mostly fixed for kernel 2.4.
> I don't know how this affects SCSI over IDE.
>
> Still, it may be some kind of hardware problem. At work they installed
> HP CD writers on 6 Windows machines in our department. After a year or
> so, three of them now fail to read, but still write OK. Our PC expert
> was unable to figure it out, so he just installed a CD-ROM as a second
> CD drive on my machine to read from. (Incidentally, when my machine at
> work tries to read its own CD, it locks up the machine, so that it has
> to be rebooted ;)
>
> I haven't tried this "solution" at home.
>
> Has anyone else encountered similar problems?
>
> ---- Carl
>
>
