> I'm thinking it's the shoddy linux 2.4 VM. I don't think my
> system is being overloaded (cdrecord only uses 40% of my RAM and
> I used to run SETI@home on this machine while burning). I will
> soon try 2.2.20 (I have to re-format because 2.2.X doesn't
> support 3.5.X format reiserfs part
Yes, I am. I am going to try a 2.2.X kernel and then I'm going
to test my RAM. Check, eventually, I'll change my SCSI cable.
It's weird though, because, everything to do with the CDRW drive
is fine in Windows 95. No problems ever.
On 11 Nov 2001, David Lerner wrote:
> Karol,
>
> You are
Karol,
You are using software that is working well for others. This seems like
a hardware problem. Check the cable and the terminations.
Dave
Karol Pietrzak wrote:
> Hello.
> As some of you may remember, I posted this problem a while back.
>
> I've been burning CD's in Linux ever since 2.2.1
>From: "Karol Pietrzak" <[EMAIL PROTECTED]>
>I've been burning CD's in Linux ever since 2.2.14. Back then I
>was using Slackware 7.1 and cdrecord ~1.10a09 to burn CD's on my
>Yamaha 8424SZ. Everything worked beautifully. I even ran
>SETI@home while ripping and burning.
>I then got a Plext
Hello.
As some of you may remember, I posted this problem a while back.
I've been burning CD's in Linux ever since 2.2.14. Back then I
was using Slackware 7.1 and cdrecord ~1.10a09 to burn CD's on my
Yamaha 8424SZ. Everything worked beautifully. I even ran
SETI@home while ripping and burnin
5 matches
Mail list logo
