Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot detect DVD drive in burning software

Status
Not open for further replies.

msammut

MIS
Jan 6, 2003
43
CA
I have an LG GSA-H54N drive that I have used often in the past to burn CD's and DVD's. I can see it in My computer as CD Drive (D:) and if I insert a CD or DVD I can read just fine from it. Now, regardless of which burning application I use, the CD/DVD drive is not detected at all. It says No device detected, when I choose to search for SCSI or ATAPI drives it comes back and says no devices found. I have used a brand new IDE controller cable and hooked it onto the 2nd IDE controller on its own. I am tempted to reinstall firmware but am not too sure of the implications. Any ideas?

 
Check, double-check, and triple-check your jumper settings. Depending on the MB and device, Cable Select might not work. I always use Master/Slave configurations to avoid conflicts. Set the HDD as Master and the DVD as Slave. Some HDDs have Master with Slave Following jumper settings, so examine the chart (should be attached to the HDD or etched in) carefully to insure it's correctly jumpered.

If the DVD's on its own IDE channel make sure it's set to Master.

Tony

Users helping Users...
 
Hi Tony. Thanks for the help. I did have the jumpers set to master on the secondary controller. I read all over the internet that it is a suspected undetected Malware that causes this. Ended up uprading my Windows XP OS. Sure enough, that solved the problem. All is detected and I'm burning. Thanks for your help.
 
Glad you got it sorted. Any clues as to what that "suspected undetected Malware" is called for future reference?

Tony

Users helping Users...
 
I generally interpret "suspected undetected malware" as a Microsoft patch that broke something.



Ed Fair
Give the wrong symptoms, get the wrong solutions.
 
When it is "all over the internet" it kicks in my paranoia.
I've seen too many unintended glitches in Microsoft's patches to let them escape probable cause.

One machine getting something broken, that can happen. Many machines breaking the same way, something came down the line. Then the machine fixes itself? Doesn't happen that much.

The only way to prove it would be to have an image prior to the break, then allow an upgrade. But if it was something in a patch it would likely have been corrected or outdated.

Ed Fair
Give the wrong symptoms, get the wrong solutions.
 
When it is "all over the internet" it kicks in my paranoia.
Sorry to say, but I've not come across this at all yet, though I must confess, I've not searched for it either...

I've seen too many unintended glitches in Microsoft's patches to let them escape probable cause.
Too true...
One machine getting something broken, that can happen. Many machines breaking the same way, something came down the line. Then the machine fixes itself? Doesn't happen that much.
I've seen many being broken by third party software, e.g. Roxio, iTunes, and few others... but you are right, I've yet to see a machine fix itself like that, and that smells like 'Seattle air' (maybe the AutoRun patch they issued a few months ago, which was flaky, and they rectified it this time around)...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"
 
msammut,

When you say:
Ended up uprading my Windows XP OS.

Could you explain exactly what you mean, just to be sure? You did an in place upgrade of XP over your existing install? Or you Upgraded to Windows Vista? Or you upgraded from 98, ME, or 2000 to XP?

I would just like to know for sure for better clarity.

--

"If to err is human, then I must be some kind of human!" -Me
 
Open the case and unplug the IDE / SATA cable and the power cable, then plug them back in, reseating the cables fixes most problems. In a more drastic approach, uninstall and reinstall your burning software.

Gabriel Blanc-Laine
VP Sales & Marketing
 
GabrielBL,

The original poster (OP) stated their problem is now solved. So disconnecting/reconnecting anything isn't required.

Also, I personally think that for most people, uninstalling and reinstalling an app would be far easier/simpler/less complicated than disconnecting and reconnecting devices.

Lastly, this did not at all sound like a hardware issue, which it did turn out not to be.

The last handful of posts were not in helping correct the issue, but rather general discussion about perhaps what caused the issue in the first place.

--

"If to err is human, then I must be some kind of human!" -Me
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top