The name "Mitsumi" at the end of the Nero version number indicates that the software
is locked to only one drive....you need to do a clean install of a later version of
Nero Express from their web site.
The Registry key you cite is a Windows XP key....why are you cross-posting to a
Windows 98 group?
The 3 in the key indicates that the device was detected as a non-recordable
device....it may not affect Roxio's detection, only whether you can record using
Windows XP's native recording ability.....that is, it won't have a 'Recording" tab
in the Properties sheet, and you won't be able to send files to that drive using
Windows native burning software.
CD-R drive or CD-RW drive is not recognized as a recordable device:
http://support.microsoft.com/kb/316529
Roxio's problem is more likely that the version of the software you have does not
recognise that model drive.
--
Glen Ventura, MS MVP W95/98 Systems
Gary Roach said:
thanks for the info. i'll look into using stomp. the unit came with no
software so i'll have to get some. the device manager shows the device but
makes no mention of its recordability. however, my other burner also shows
this way in device manager - no record indication. i checked the registry
key:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD
Burning\Drives
and found that the existing burner showed a "drive type" value of
0x00000003, while the new combo burner showed "drive type" value of
0x00000001. this tells me that at least for the purpose of the built in
roxio burning software, windows doesn't see the drive as recordable. i
checked the roxio site and the device is not listed in their supported
drives. a computer store told me to try updating to the latest version of
nero express which i am currently in the process of doing.
the nero software that i'm attempting to use shows the version as "Nero
Express 5.5.10.5 Mitsumi" and came with another burner so it looks as if
your suspicion that this is specific to the hardware is correct. i'm
currently trying to update it to a newer (and hopefully less hardware
specific) version. this appears to have worked - although the verification
phase failed, the data was recorded. thanks for the help!