Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Lost ability to burn (write) in Windows 2008 using Dell Latitude D830 and TSSTCorp DVD+-RW drive

Posted on 2009-04-03
5
Medium Priority
?
443 Views
Last Modified: 2013-11-06
I'm an advanced user.

This seems to be a third-party software conflict or Windows registry issue, I'm not exactly sure.  It isn't a drive issue, but it could be how Windows detects drives.  I can use the same modular drive in another notebook and it works fine.  I insert a different CD+-RW modular drive and get the same problem.

Windows recognizes it, can read from it, no errors in Device Manager.  Nero InfoTool reports the drive and characteristics properly.  Both ImgBurn and WMP11 both display "no burner detected" and "insert burner and restart WMP", respectively.  This was working before, but for how long am I uncertain.

I've tried several things.  Uninstalling and reinstalling in Device Manager, uninstalling Daemon Tools Lite (which I thought was a strong candidate for 3rd party conflict).  I've combed through MSCONFIG looking for "unusual" suspects.

I also did some googling for the product, and found that there is a firmware upgrade.  I illogically tried to upgrade the firmware even though it doesn't seem to be a device specific problem, but the application can't find the drive.  I don't know if it's because the app is written poorly or that it's running into the same issue the other programs are.

I've assigned this the highest point value because if this doesn't get resolved in a week I'll need to reformat/reinstall.  Thanks in advance for your help.
4-3-2009-9-10-41-AM.jpg
0
Comment
Question by:z0ner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 70

Accepted Solution

by:
Merete earned 1500 total points
ID: 24075085
Hi z0ner, a couple of ideas,
first is Nero bundled with this drive? OEM !!
This problem may start with the burning software you have, which version?
 in XP I had to update Nero, Patch it to run with xpsp2 maybe you have to patch it for windows 2008.
What is windows 2008 ??
Next have you tried deleting the upper lower filters? Seems to fix this type of issues
covers XP as well Vista sroll down
http://support.microsoft.com/kb/314060#letmefixit
I agree with your sentiments on daemon tools did you disable any virtual drives first?
uninstalling Daemon Tools Lite (which I thought was a strong candidate for 3rd party conflict).  
Don't like the lite versions stick with the old known working versions
http://www.videohelp.com/tools/Daemon_Tools/old-versions#download

have you actually removed the rom drive rebooted with it.
Then  uninstalled Nero fully even delete folders regestry keys
Then put the rom drive back re-install Nero clean
The rom drive is MASTER slave
0
 

Author Closing Comment

by:z0ner
ID: 31566328
Thanks for the reply.  It turned out that all I needed to do was simply reinstall both burning applications.  Sometimes the most difficult problem is solved with an easy solution.
0
 
LVL 70

Expert Comment

by:Merete
ID: 24267208
Very good, glad to hear it resolved z0ner, may I ask why the B rating since I did suggest you uninstall Nero fully. My suggestion was spot on.
B ratings make us feel we didn't help much.
0
 

Author Comment

by:z0ner
ID: 24271290
Merete,

Sorry, I didn't mean to offend with the B rating, it's just that there were several suggestions you made that didn't make sense or seemed to be redundant, as if you didn't understand the question fully.  

For example, why would you suggest I patch Nero when I explained I was able to use it with my workstation initially?

Also, WMP11 and the Windows 2008 OS still don't detect my burner.  So the solution was partial at best.  

Again, I'm not condeming your answer but I was hoping to get a solution that would fix Windows' native ability to detect and write.  I'm confident the problem was caused by installing Daemon Tools, but there is obviously some other damage left behind.
0
 
LVL 70

Expert Comment

by:Merete
ID: 24277104
Thank you.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question