Win7 T61p CDRW/DVDRW Not Recognized

[cps]

Maybe folks here can help.

Upgraded my T61p (6460-DVU) from XP to 7 some time ago. Recently, when trying to write to my UJ862 DVDRW, I discovered it won't! Up until then, reads worked fine (data/music/video).

Checking devices, I noticed the drive is recognized as "CD-ROM", obviously wrong, but explains why Win7 has problems.

No obvious driver upgrades either via MSFT or Lenovo. XP/Vista solutions don't seem to apply to Win7.

Any suggestions?

Apologies if this issue has already been dealt with in this forum, but a quick search didn't reveal any relevant thread.

cps

[RealBlackStuff]

Try this: http://social.technet.microsoft.com/For ... 88c718ef2/

[cps]

Try this: http://social.technet.microsoft.com/For ... 88c718ef2/

Alas, I had already tried that possible "fix", but it seems only applicable to WinXP and Vista.

Windows 7 doesn't have those parameters for the identified hotkey (at least, on my system).

Thanks, anyway.

[zemlin]

The DVD drive in my my 6460-67U works fine under W7x64. I don't remember having to jump through any hoops for that when installing the OS. It is listed as MATSHITA DVD-RAM UJ-862 ATA Device. Under Driver:
Provider Microsoft
Driver Date 6/21/2006
Driver Version 6.1.7601.17514
C:\Windows\system32\DRIVERS\cdrom.sys

Let me know if I can provide any more info for you.

[cps]

It is listed as MATSHITA DVD-RAM UJ-862 ATA Device. Under Driver:
Provider Microsoft
Driver Date 6/21/2006
Driver Version 6.1.7601.17514
C:\Windows\system32\DRIVERS\cdrom.sys

I checked my device/driver and have the same settings.

That got me thinking perhaps the problem was associated the DVD-RW I had inserted being blank (i.e. unformatted). I had presumed Autoplay would prompt me if formatting was required.

I forced a format (UDF 2.01 - Default) via Control Panel>Administrative Tools and was successful in getting it to play nice with Windows Explorer. So, that was good.

But, I wondered, why didn't Win7 prompt me to format the drive when I inserted the blank disk? That led me to suspect something was amiss with Autoplay, which turned out to be the problem all along. Following the steps specified in:

http://www.mydigitallife.info/fix-windo ... nd-pop-up/

particularly resetting Shell Hardware Detection service to "automatic", got things working nicely once the system was rebooted.

I provide this information in case others have a similar problem.