Optical Drives Not Responding

NeoFXNeoFX Utah, US of A
edited September 2004 in Hardware
Well this has happened once before about 2-3 weeks ago and I don't remember how I fixed it. I was burning a CD last night and it finished... but the cd never ejected automatically like it usually does. I pressed the button and nothing... I tried my DVD drive and nothing either. I turned off the computer, removed the CD by using the little key to manually open the drive and then I rebooted. Still no response. I then restarted and tried to redetect the drives in the bios and it said it found them ok. I rebooted and STILL nothing!

Anyone have any thoughts about this?

I'm using a LiteOn 52x32x52x CD-R/W drive and a Pioneer DVR-A05 DVD-R/W drive. (latest firmware as far as I know is installed)

Comments

  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited September 2004
    On same IDE cable???? The Liteon often likes to be MASTER, so if on same cable make the Liteon jumpered to Master and the DVD to SLAVE. Then if still problems, take the DVD and disconnect from cable and power, then jumper the Liteon to cable select and see what it does, and if it ends up as slave or master. Might run a Cleaning CD through it if you then get access sometimes.

    Then add the DVD back into the mix, see what happens. Ever seen two devices of optical kind from different mfrs not like each other??? I have.... Took one IDE device ouit of a box once, stuck in another, and the one left and the one in the new box were both "happy as clams in mud" as long as they were not in the same box. These two drives had to be divorced from each other physically.

    Turned out both mfrs each had problems with each OTHERs shortcuts and coding of firmware. Pioneers and Plextors work together usually. Liteon and Pioneer do not always work together and it can happen with two drives of just the wrong firmware to get along.

    Scientific??? Yes, there is a reason set , and part of it is what the drives WANTED to be (were CODED to prefer most). BOTH liked MASTER when on same cable as another optical, one in fact would run as slave with a HD on other connector, but then HD ran slow as molasses. Part of it was also the drive's abilities to recognize and adjust for each other were lacking. The average IDE controller on a motherboard was not meant to handle device versus device (when both are on same cable) firmware bickering. BUT, in two different boxes (which was in which did NOT matter at all) BOTH drives worked fine. OH, same Model Brand and BIOS version burn for motherboard in both boxes also..... Go Figure.
  • NeoFXNeoFX Utah, US of A
    edited September 2004
    Alright... thanks :D I shut down my computer, turned off the power and reset everything and it worked again... we'll see what happens next time it tries to die on me. I'll have to try the IDE master/slave stuff...
Sign In or Register to comment.