Re: [Cooker] [origin found] 9.2 and fried LG cdroms - what's the solution?

2003-10-29 Thread Guillaume Cottenceau
Leon Brooks [EMAIL PROTECTED] writes:

 On Sat, 25 Oct 2003 05:12, Guillaume Cottenceau wrote:
  Ok, here's status: Nicolas Planel found the origin of the
  problem. It's the packet writing support for cd/dvd burners
  that was introduced on 15th of August
 
 I'm astounded that anyone would ship a drive that can be fried in 
 software.

That's also much of a bad luck, the firmware was probably
designed at a time the FLUSH stuff was not even in the ATAPI
specifications - and since every manufacturer more or less needs
to use an extension of specs to do firmware updates..

What surprises me is that they don't rely on a magic at the
beginning and end of the new firmware sequence, or a md5sum-alike
of the firmware sequence. If it's only known to the hardware it
would be an efficient protection against viruses that would
exploit it to destroy the drive.

 What's the solution? Is a fried drive truly fried, or can they be 
 re-flashed or something to resuscitate it?

We're in technical contacts with LG in korea now. They're nice.
They've talked about a way to recover de firmware but they said
it's not easy for typical customer. We'll see what is it exactly.

-- 
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/



Re: [Cooker] [origin found] 9.2 and fried LG cdroms - what's the solution?

2003-10-25 Thread Leon Brooks
On Sat, 25 Oct 2003 05:12, Guillaume Cottenceau wrote:
 Ok, here's status: Nicolas Planel found the origin of the
 problem. It's the packet writing support for cd/dvd burners
 that was introduced on 15th of August

I'm astounded that anyone would ship a drive that can be fried in 
software.

What's the solution? Is a fried drive truly fried, or can they be 
re-flashed or something to resuscitate it?

Cheers; Leon