On Tuesday 11 November 2003 06:23 pm, Dennis Myers wrote:
> On Tuesday 11 November 2003 11:58 am, Charlie M. wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Tuesday 11 November 2003 10:38 am, HaywireMac wrote:
> > > On Tue, 11 Nov 2003 10:09:00 -0700
> > >
> > > "Charlie M." <[EMAIL PROTECTED]> uttered:
> > > > For the CD-RW problem; is that drive a re-badged LG by any chance? If
> > > > so you likely killed it, which you would know if you had read any of
> > > > the multitude of posts, or the warnings on the Mandrake site, in the
> > > > past three weeks.
> > >
> > > From the Mandrake site:
> > >
> > > "NOTE: Based on information we have received from LG Electronics'
> > > technicians, only CD-ROM models are affected by this bug. DVD-ROM/R/RW
> > > and CD-RW devices are not affected."
> >
> > "Based on information...." etc. That still doesn't mean it isn't
> > possible, and it doesn't mean that every "cut rate spec" proprietary
> > drive will be unaffected, correct? (-;
> >
> > I always go with the worst case scenario Haywire, then I can be
> > pleasantly surprised when I'm proved wrong. Which happens a lot.
> >
> > In other words pessimists are correct more often, even though optimists
> > seem to have more fun. <g>
>
> In this case I think the optimist is correct. I have three LG burners, one
> quite new in three different computers and the burners are what I used to
> install ML9.2 after I fried the cdroms.  The burners worked the roms fried,
> that was why I thought maybe my supplier had received a bad batch of CDROMS
> and did not figure out that it was something in ML9.2 doing the dirty deed.
> I believe you are safe with a CDRW of any brand.
I kinda thought they had traced it down to "FLUSH_CACHE" command, which in a 
burner is a normal thing to do, but in a read only drive would not be a 
normal thing to do, and so LG had  decided to use "FLUSH_CACHE" to prepare 
for a firmware update in the rom. 


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to