Unsolved
This post is more than 5 years old
4 Posts
0
11991
August 26th, 2008 16:00
IDE CD DVD-ROM does not recognize a disk is loaded
My D:\ IDE\CD-ROM drive (HL-DT-ST DVD-ROM GDR8163B) is recognized by my Dimension 9100 desktop and is listed as enabled and working properly in the device manager. When loading a disk containing an AUTORUN.INF file, the appropriate program runs. If the loaded disk does not contain an AUTORUN file, the system does not recognize that a disk has been loaded and the Insert disk dialogue ("Please insert a disk into Drive D:.") appears. Very occasionally, the drive successfully reads a disk without an AUTORUN file (containing backup folders only) upon loading. Is this likely a hardware problem?
0 events found
No Events found!


osprey4
4 Operator
•
34.2K Posts
0
August 27th, 2008 10:00
Hi, Lynn:
This sounds like an autoplay problem. There is a little utility provided by MS called the autoplay repair wizard. Go find that and give it a try.
When you post back, please let me know if you are using a UDF writer, such as Sonic DLA or Roxio Drag-to-disc. This type of program can also create problems.
Lynn Trowbridge
4 Posts
0
August 29th, 2008 15:00
Dear Osprey,
Thanks so much for your response. You are wonderful to be so helpful to us.
I had already run AutoPlay, but had interpreted the results as indicating a hardware problem. Fortunately I saved the AutoPlay module and have rerun it with the following results:
AutoFix [V5.2.3790.67]
Time [2008-08-29 10:35:53]
Microsoft Windows Version [5.1 (Service Pack 2) <2600>]
Test [The Shell Hardware Detection service is running.] - Instance [N/A]:
Result [AutoStart Setting]: OK
Result [The Shell Hardware Detection service is running.]: OK
Test [Policies] - Instance [D:\, Drive Type: 5]:
Result [HKCU\...\Policies!NoDrives]: OK {Absent}
Result [HKCU\...\Policies!NoDriveAutorun]: OK {Absent}
Result [HKCU\...\Policies!NoDriveTypeAutorun]: OK {Present}
Result [HKLM\...\Policies!NoDrives]: OK {Absent}
Result [HKLM\...\Policies!NoDriveAutorun]: OK {Absent}
Result [HKLM\...\Policies!NoDriveTypeAutorun]: OK {Absent}
Result [Driver level policies]: OK {
HKLM\...\Services\cdrom!Autorun (Present)
HKLM\...\Services\cdrom\Parameters!Autorun (Absent)
HKLM\System\CCS\Enum\...!AlwaysEnable (Absent)
HKLM\System\CCS\Enum\...!AlwaysDisable (Absent) }
Test [Drive Notification] - Instance [D:\, Drive Type: 5]:
Result [Legacy Notification]: Problems
Result [AutoPlay V2 Notification]: Problems {
Service (Silent)
Shell (Deaf) }
>> Repair << [Legacy AutoPlay Event]
Step: No steps to take.
Result: This AutoPlay setting cannot be fixed. Either the device is malfunctioning, or the wizard cannot determine the problem.
>> Repair << [Autoplay V2 Event]
Step: No steps to take.
Result: This AutoPlay setting cannot be fixed. Either the device is malfunctioning, or the wizard cannot determine the problem.
>> Required action: The wizard found problems but cannot fix them -> None
During the test I opened and closed the drive 3 times. The loaded disc was created using the MS WindowsXP CD Writing Wizard for repeated backups of my Quicken Financial Data. Yes, in fact I do usually use Sonic DigitalMedia LT v7 which contains a DLA feature which I have not been able to turn off. However, the disk used for the test was not created by the Sonic software.
On the chance that the DVD drive (D:\) will not read a disk unless it has been finalized, I have also finalized a similarly created disk using the Sonic software (on drive E:\). This finalized disk was not read on D:\ either.
Again, I appreciate any help you can provide.
Lynn
osprey4
4 Operator
•
34.2K Posts
0
August 30th, 2008 11:00
Another option is to disable autoplay. The easiest way to do this is to download and use this MS utility called TweakUI.
Lynn Trowbridge
4 Posts
0
September 3rd, 2008 16:00
Thanks again for your help. I did not understand that the disabling of DLA on drive D: (the failing DVD drive) was accomplished by disabling the DLA Feature in the Properties of drive E: (the CD burner). Having discovered this, I turned DLA off for both drives and re-ran the test using the same disk without an AUTORUN.INF created by the MS WindowsXP CD Burning Wizard. The test failed and drive D: would not recognize the disk.
I then downloaded TweakUI as suggested and turned off the Autoplay feature on drive D:. Again, the test failed and drive D: would not recognize the disk. I tried this test with and without DLA enabled.
It then occured to me that DLA was a feature affecting the recording process rather than the reading process and that the disk created by the MS WindowsXP CD Burning Wizard might have been affected during the recording process by the enabled DLA feature. Thus, re-tested by burning two disks, one with DLA enabled and one with DLA disabled. I did this using the MS WindowsXP CD Burning Wizard. Drive D: failed to read both disks.
Finally, to completely confuse myself, I decided to test the several "junk" CD-R disks laying around which I use to transfer files from one machine to another. These disks have been created at various times and, in some cases by other people at different locations. The only feature they apparently have in common is that they have not been finalized. Thus, files can be added when necessary. Of the 5 such disks "lying around" 3 could be read on drive D: and 2 were not recognized. This, of course, implies a software problem, but, as I could not see anything unique about the two disk group's contents or settings, I am at a loss to explain this anomaly.
osprey4
4 Operator
•
34.2K Posts
0
September 3rd, 2008 23:00
Hi, Lynn:
Wow, impressive persistence.
DLA only runs on your burner. Your ROM drive, obviously, can read but not write to recordable media.
It sounds like your ROM drive is reading on a hit and miss basis. It might be worth considering a replacement, which would only run $20-25.
Lynn Trowbridge
4 Posts
0
September 8th, 2008 17:00
Hi Osprey,
Well, perhaps I have truly reached the end of the line! I still worry that I haven't successfully turned off Autoplay using TweakUI or DLA in the Drive Properties or that I need to modify some key value in the Registry to fix this problem. But, throwing caution (and $26.24) to the wind, I've ordered a new drive.
I used to believe that this problem was "hit or miss" and hardware related. But your suspicion that it was a software problem and the evidence of my tests seeming to prove that the drive is consistent in its recognition of particular disks while consistently failing to recognize others now seems to me to point to the improper setting of some obscure Registry value. But what do I know? I'll gamble the $26.24 on a new drive.
Thanks again for your expertise,
Lynn
osprey4
4 Operator
•
34.2K Posts
0
September 8th, 2008 23:00