Note, this is a cross-flashed drive now using a CK version of firmware 9P59.
I have owned this drive two years now I think and the first year it worked fine. I have been using it mostly as a DQ scanner, a reader/ripper, bit-setting DVD+RW, and burning the odd DL disc. A bit loud at times, but I mostly have no major complaints. During the second year of ownership I began having the “sticky tray” on trying to eject using the button on the drive. At first the unresponsive tray was quite seldom. But over time (about 8 months) it has gotten worse. Now there are occasions when at least 5 or 6 presses are necessary to eject the tray. Because this problem has gradually worsened over time I assumed all along that this was purely a mechanical problem–poor manufacturing or assembly or maybe a design flaw. I now think this last assumption may not be completely correct, and the problem is also possibly a code (software) conflict or corruption.
Below are two screen shots of windows displayed when using IsoBuster to eject the tray instead of physically pressing the button on the drive. The “Other Application has locked the drive” window occurs first and the tray remains closed. I then press the button in IsoBuster a second time and the “Unexpected Error and Retry Exhausted” window is displayed and the tray still remains closed. I then press the button in IsoBuster a third time and the tray opens with no error displayed. The weird thing is that after performing this whole operation with IsoBuster, the tray is no longer sticky–whether using software or physically pressing the eject button on the drive. It will open practically every time afterwards during that boot of the OS and often on reboots the drive tray will not stick at all.
(By the way, I have never installed Packet Writing Software on my current install of XP SP3–I haven’t installed Nero, Sony software, or any other app with packet writing features–I don’t believe ImgBurn has this.)
Is it possible that a conflict arising from some software in my system is causing this? I experimented with this idea. After opening ImgBurn and using the “Lock Tray” and “Unlock Tray” options in ImgBurn/Tools/Drive/ , I noticed the sound made by the drive tray once I have locked the tray and then pressed the eject button is exactly the same as when the drive tray is in “sticky” mode.
Is it possible that after using some software installed on my system, the tray is locked and left that way? Causing the tray to be stuck thereafter.
What I would like to do is perform a test whenever the tray goes into sticky mode. Is there any software that can send a command to the drive to query if the tray is locked or not? I have done this with IsoBuster, but would like a second opinion from other software.
Also, if another member with this drive and the same problem could test this and post their findings that would be great.