View Full Version : Problem with DVD Burner...
My DVD Burner thinks it's a CD drive... I don't get it. I haven't done anything to change the settings - how do I make my DVD burner work again? It's a dual layer Lite On.
Thanks in advance!
09-03-05, 08:44 PM
Why do you think your DVD burner thinks that?
In other words, more details please. And name your OS.
When I open Explorer, it labels my drive E: as CD Drive (E:)
Also, Im trying to burn a disk with Nero and it won't recognize a DVD - it will only recognize CD media.
Im using Win XP with SP2.
Maybe try to flash the firmware and see what happens?
This is drive specific
get the correct model (even if you have to open your computer and read the label to find out what model yoy have)
see what happens, pay attention if you get an error message and write it down exactly
My DVD burners are labeled "Compact Disk (E:)", "Compact Disk (F:)", in Explorer too. (Different OS)
I would look for Nero upgrades too. Did Nero ever burn DVDs with the burner? What version of Nero?
I did the firmware upgrade and it was successful - but getting my DVD to be recognized was not successful. It's weird because I have two DVD players - one to play and one to burn. The one to play is labeled DVD Drive (D) and the one to burn is still CD Drive (E)... I don't get it, this thing worked just 3 days ago.
Also - I have already tried to "uninstall" all of my drives and let windows find them and reinstall them - no luck there either.
Thanks for everyone's replies - I've narrowed down the culprit to Nero... not sure why yet, but everytime I run Nero, my DVD defaults to a CD Drive. Somehow my drive showed up as a DVD Drive - so I went to run Nero and BAM- right back to a CD Drive. I'm going to check on Nero compatibility problems and versions now. Again, thanks for all your guys' help!
That's why I said to update Nero. I've had burners not be recognized as DVD burners, just as CD burners. Updating Nero updated the drive definitions and fixed the problem.
CD Creator was notorious for this and had particular problems with some Lite-On drives. You had to futz around in the registry to fix it.