🚀 go-pugleaf

What you see in the registry was put there by the burner software install.
The drive recognition routine in the software compares that to the string in
the EEPROM in the drive itself, which Creative has changed. Changing the
string in the registry to match the ID string in the EEPROM *might* get the
software to work, but it's not as simple as it may appear.
None of this helps at all for drive firmware updates, however. If the drive
OEM offers a firmware update, the patch program must find the original drive
ID in the EEPROM for the patch to work. Since Creative has changed the ID in
the EEPROM and won't provide firmware updates that recognize the Creative ID
string, owners unwilling to attempt drastic measures to rewrite the original
OEM ID string to the drive EEPROM are SOL.

"Jason Chong" <cvw@pc.jaring.my> wrote in message
news:3B79C22E.5487@pc.jaring.my...
> Hey, if the drives we get from creative are
> rebadged panasonic/matsushita/samsung/sanyo/plextor...
>
> So what if they changed the ID string ? Why not change it
> to the original manufacturer's ID at the registry ?
> I saw entries for them in the localmachine/enum/scsi
>
> Just change for example, 'Creative 8439e' to
> 'Matsushita cw-7586' etc and now those burners
> that support cw-7586 should be able to use it.
>
> Why the heck is there a need to specially support a particular
> drive? All drives are ATAPI compliant and should read/write
> data CDs and others without problems!
>
> That's what ATAPI and SCSI interfaces are for, why does
> cd-writer software need to know the cdrw manufacturer
> string even ?!