I apologize in advance if this has been covered already in the forums, but I haven't found any threads that include my problem specifically.
I have had an LG GSA-H10N "Super Multi DVD Rewriter" for about a year with no problems (link to model here: http://www.lge.com/products/model/detail/gsa-h10n_1_6.jhtml), updated to the latest firmware (JL12). I am using WinXP Home, fully updated. Media I'm using is Maxell DVD+R and DVD-R, though other brands show the same problem.
As of last night, when I put a disc in the drive, Windows Explorer recognizes the disc title, but not the files. Using the autoplay, if I try to browse the files, nothing happens (the Win Explorer window doesn't even pop up). If I try to explore the drive, it defaults back to desktop.
That being said, if I use autoplay and ask a specific program to read the disc (for example, Windows Media Player to play video files), it will do so without flaw.
The disc spins fine and explorer recognizes the specific disc is in the drive by it's name, but it won't let me look at the file list or access the files. I have done absolutely nothing to the computer (no installs, etc) for over a month, with the exception of the latest XP updates, which I installed very soon before this problem occurred.
Is anyone else experiencing this problem? I'm assuming the problem is software related since the drive is technically working fine...just not explorable in windows explorer. I was thinking about buying a new drive, but that seems like it might be a waste of time. If anyone can offer any help, I'd be most appreciative. Thank you.
For quirky behaviour with XP and DVD drives, I have turned 'Recording' off on the drive properties, rebooted then turned it back on.
Remember to set the maximum speed when turning Recording back on.
Also uninstalled the IDE controller that the drive is connected to, rebooted.
Thanks a million for your suggestion. I had disc recording turned off. Turned it on and my problem was remedied. I then rebooted, and turned it off again. No problems!
Still no idea what caused the issue (probably a new update for XP). Hopefully if anyone else is having the problem, the quick fix will work for them as well.
