Walden wrote:
> Greetings to all,
>
> Running XP Pro, Service Pack 3
>
> I have two DVD drives manufactured by LITE-ON (LH-20A1P and LH-20A1H)
> that have worked properly, then suddenly decided not to open their
> drawers. (Okay ... no jokes about that!)
>
> Both of them show up in Device Manager without asterisks and whose
> Properties tell me they're "working properly."
>
> Neither the button on the front, nor selecting "Eject" on their
> context menus produce the same result ... a round of clicking and
> brief moments of trying to open ... then stop.
>
> I've disconnected the cables from both, then restarted XP, after which
> they disappear from Device Manager ... then reconnected them ... let
> Plug and Play find them as new hardware ... after which they
> re-display in Device Manager as "working properly," but still have the
> same problem.
>
> I applied the most recent firmware from LITE-ON to one of them ... the
> other one (the LightScribe model) has no firmware updates available.
>
> Since both of them behave in the same way, I don't think it's a
> mechanical problem. I have a feeing it's a corrupted driver problem,
> but don't know how to fix it. I'm totally puzzled. Can anyone help?
>
> Thanks,
>
> Walden
>
Windows allows programs you install, to add "shims" to the protocol stack.
A term for this is "upperfilter / lowerfilter". And that term refers to
a "filter driver", which is a driver that jams itself between two
regular parts of the driver stack, and filters the commands it sees,
or adds commands of its own.
Examples of interfering third party software would be CD/DVD burner
programs, virtual CDs (mount an ISO9660 image), ripping programs and
so on. In some cases, you may not be aware the program has potentially
interfering components (iTunes).
With regard to feature set, here is a section from a copy of the ATA/ATAPI
spec I have on disk here.
******* d1532v1r1a-ATA-ATAPI-7 *******
4.11.2 Removable Media feature set
The Removable Media feature set is intended only for devices not implementing
the PACKET Command feature set. This feature set operates with Media Status
Notification disabled. The MEDIA LOCK and MEDIA UNLOCK commands are used to
secure the media and the MEDIA EJECT command is used to remove the media.
While the media is locked, the eject button does not eject the media. Media status
is determined by checking the media status bits returned by the MEDIA LOCK and
MEDIA UNLOCK commands. Power-on reset, hardware reset, and the
EXECUTE DEVICE DIAGNOSTIC command clear the Media Lock (LOCK) state and the
Media Change Request (MCR) state. Software reset clears the Media Lock (LOCK)
state, clears the Media Change Request (MCR) state, and preserves the
Media Change (MC) state. The following commands are defined to implement
the Removable Media feature set.
- MEDIA EJECT
- MEDIA LOCK
- MEDIA UNLOCK
*******
If some software is issuing MEDIA LOCK commands, that could account for a
lack of user control of the situation.
A more far-fetched cause, would be a bug in a root kit, such as TDSS/Alureon,
impacting the function of the ATAPI interface. Kaspersky hosts a tool
called TDSSKiller for that, but I would only run that if there was evidence
you needed it. A root kit can prevent a user from fixing things, such as
running System File Checker and attempting to repair files that make the
protocol stack for a storage device. TDSS interferes in such a way, as to
hide its presence, and uses an unused part of the disk, to store any
information it might need for re-infection or starting itself at
boot time. A tool that might detect TDSS is MalwareBytes MBAM.
TDSS would be a giant, pain in the ass kind of filter driver.
TDSSKiller
http://support.kaspersky.com/viruses...?qid=208280684
(The free version is suitable for scanning and curing problems)
http://en.wikipedia.org/wiki/Malwarebytes
If you have any trouble running tools like that, that's generally
a sign you're infected.
What you've done recently to the computer, whether the computer
has acted "weird" recently, may give you some hint as to what
the problem is. It's possible for the tray mechanism to fail,
but as you observe, the odds of two drives failing in exactly
the same way, is far fetched.
If you can
1) Turn off the computer power.
2) Turn it on again (necessary, because the design of SATA doesn't
guarantee sanity unless you turn off the power).
3) Start the computer.
4) Enter the BIOS setup screen. The BIOS setup screen should be
a relatively benign environment for testing.
5) Practice inserting and removing a CD or DVD via the button,
and it works...
then that would tell you the tray mechanism isn't broken.
The tray mechanism has a form of overcurrent detection. If the
tray "meets resistance" while it is opening, it can reverse
direction. This occasionally accounts for the symptoms, and
might give a bit of noises as well. But it isn't likely that
two drives die at the same time. If you press the button,
and there is no state change at all evident (drive still
spinning, no new noises), that's "MEDIA LOCK".
If the media inserted in the drive is virtually unreadable,
has a high error rate, flaky etc., that can also cause
the drive to freeze. The drive may be attempting to read the
media tag, and do its discovery thing, and then, ignoring
all other user or computer input. Test the tray with
"known good" media.
Paul