On Thu, 27 Dec 2001 11:18:34 +
Declan Moriarty <[EMAIL PROTECTED]> wrote:
> I am always amazed
> how many red faces this advice produces, but clean the $£"! disk - make sure
> you can see no pawprint on it.
Well, it didn't have any pawprints or any burn tracks either. Ahem, I forgot
to un
Chris Kassopulo wrote:
> Greetings,
>
> I bought an HP9100 cdrw a while back cause my cdrom died. Installed it,
> burned a cd in windows and linux - no problems. I've only used it since
> as a reader. I can read the cd I burnt when I installed. I burn a cd
> today, the right things happen (
On Fri, 28 Dec 2001 02:33, Net Llama wrote:
> 1) What's the deal with the wacky chained symlinks? Symlinks are a
> truly horrible idea when it comes to block devices, because most people
> have no clue what they're trying to do with them (the infamous
> /dev/cdrom thing on RedHat boxes comes imm
Two things are jumping out at me here (in addition to Declan's excellent
suggestion to try mounting a known-good CD):
1) What's the deal with the wacky chained symlinks? Symlinks are a
truly horrible idea when it comes to block devices, because most people
have no clue what they're trying to do w
At a guess, (GUESS) your system doesn't know what protocol the cdr is
written, is trying to automount it and going through a few modules before
giving up the ghost
The usual failure mode for a cdr/cdrw is failure to read. I am always amazed
how many red faces this advice produces, but
Greetings,
I bought an HP9100 cdrw a while back cause my cdrom died. Installed it,
burned a cd in windows and linux - no problems. I've only used it since
as a reader. I can read the cd I burnt when I installed. I burn a cd
today, the right things happen (lights and gcombust feedback) but whe
