locked
Utimate failing to recognize blank CD's RRS feed

  • Question

  • I just upgraded an existing system with working CD/DVD drive to Ulimate.

    It allows me to read CD/DVD's  but just ignores blank media.

    On other Vista systems I have, a pop up appears asking me to format the media.

    I don't get this on this system. 

    If I double click on the drive on My computer, it pops up a dialog which says "Windows cannot read the disc...if the disc is unformatted, you need to format it before using it"

    Unfortunately, there appreas to be no option anywhere to format it, assumming this is need given I want to burn files or media onto it.

    If I go to burn media in Media Play, it just tells me to connect a burner and re-start!  Despite the fact there is one installed and ready with blank media.

    This drive worked fine before the upgrade.  i've tried several different blank media, some from the same batch that worked previously (using Nero)

    Monday, March 19, 2007 12:13 PM

Answers

  • Hello Richard,

    I'm sorry to hear you're having issues with blank media in Vista...I've never heard of an issue quite like this one before.  If you could please send a registry dump of the following registry tree/keys to optissue@microsoft.com, I can take a quick look and see if I can narrow down what is causing this odd behavior of not seeing autoplay for blank media. 

    Please dump the following keys while you have blank media in the burner: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning

    I may need a software trace to ultimately pinpoint the error, but I figure we can start with a simple, quick registry dump to see if I can save you the time of making a software trace :-)

    thanks,

    Garrett Jacobson
    SDE, Optical Platform Group

    Monday, March 19, 2007 3:32 PM
  • Hi Garrett,

     

    Well.....I uninstalled the chipset drivers and found that the DVD becomes completely inaccessable.  It will not even show up as a drive on my system.

     

    The offending driver is a JMicron SATA Driver that provides functionality for the onboard SATA RAID Controller.  According to my MB manual "this driver installation is necessary for the devices connected through connectors eSATA1 or IDE1."

     

    When I un-install the JMicron driver - the DVD disappears as I mentioned above.  My DVD has a  PATA interface connected to the IDE1 channel, so without the driver - no DVD.  I am not running RAID on my hard drives, so I do not need the RAID functionality provided by the driver, but I do use the eSATA for an external HDD (which by the way is woking fine).

     

    So unless I can find a driver for the controller that will allow my eSATA to work while at the same time correcting my DVD problem, I think I'm out of luck. 

     

    Guess I'm going to have to buy a new SATA DVD and see if solves the problem, since I will not have anything on the IDE bus.  The only other option I can see is to do a clean install of Vista and then not install the JMicron driver, perhaps that will turn back the hardware ids on the DVD, but will leave me without me eSATA and I would have to use USB 2.0 for that device.

     

    What do you think?

     

    Thanks for the help.

     

    D

     

    Saturday, December 15, 2007 9:04 PM
  • I'm not sure whether or not this problem has been solved, so I thought I would throw in what I found to be causing the problem for me.

    I (stupidly) disabled the Shell Hardware Detection service in Vista. Opened up services, properties, set start up type to automatic and then started the service. Problem was solved instantly. CDs and DVDs of all types (+/- R/RW) are now recognised and I can burn again.

    Hopefully that helps anyone who likes inflicting problems on themselves, like me.

     

    Kyle.

    Friday, February 15, 2008 5:39 PM

All replies

  • Hello Richard,

    I'm sorry to hear you're having issues with blank media in Vista...I've never heard of an issue quite like this one before.  If you could please send a registry dump of the following registry tree/keys to optissue@microsoft.com, I can take a quick look and see if I can narrow down what is causing this odd behavior of not seeing autoplay for blank media. 

    Please dump the following keys while you have blank media in the burner: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning

    I may need a software trace to ultimately pinpoint the error, but I figure we can start with a simple, quick registry dump to see if I can save you the time of making a software trace :-)

    thanks,

    Garrett Jacobson
    SDE, Optical Platform Group

    Monday, March 19, 2007 3:32 PM
  • I get exactly the same problem on Vista Home Premium, with an Asus DRW-1612BL drive. The drive is recognized by specialist burning software such as InfraRecorder, and is recognized by Vista when containing a commercial CD/DVD.

    If there's a solution to this, please post an answer.


    Here is my registry with blank CD inserted


    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning]

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning\Drives]

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning\StagingInfo]

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning\StagingInfo\Volume{cca64d9b-b953-11db-9fc2-0018f3ab71ee}]
    "StagingPath"="C:\\Users\\Julian\\AppData\\Local\\Microsoft\\Windows\\Burn\\Burn"
    "Active"=dword:00000000
    "DriveNumber"=dword:00000004


    Tuesday, April 3, 2007 7:05 PM
  • I am having the exact same issue.  Was it resolved?

     

    Thank you.

     

     

    Thursday, July 5, 2007 5:56 PM
  • Hi Garrett

    I am having the same problem of blank CD's and DVD's not being recognised as being loaded in the drive, so I cannot drag and drop files on to the discs.  However when Nero Burning  is launched the media is recognised and files can be burned to the media.  The disc can then be placed in the drive and files placed on the CD/DVD can be read like any other CD containing files.  I find it rather strange as it is not consistant as three of my Vista machines work fine and one does not.

    Have you found an answer yet.

    Thanks

    Jim A

     

    Sunday, October 7, 2007 12:14 AM
  • I still can't find an answer to this problem.  Somewhat depressing since this thread has been here since March... any ideas Microsoft!!!?
    Tuesday, October 9, 2007 11:20 AM
  • I have the same problem.  I am using a Plextor PX740 A that worked perfectly in my last machine.  I just moved it over to a new computer with Vista Ultimate.  I can read CD/DVDs with pre-recorded data.  But I put in blank CD or DVD media - then nothing.  I get a message to "format" the media with no way to copy data to the drive. Has there been a reply from Microsoft?

     

    Monday, December 10, 2007 6:34 AM
  •  

    Nothing yet... and the internet is just full if irritating posts such as 'your DVD burner must be broken' or 'your DVD drive can't burn DVDs'!

     

    Sad irony is that I actually bought Vista, rather than pirated it.   I'm going to delete it and run a dual boot XP / Linux.  Linux for the speed, XP for the backwards compatability and software range.  I think I might try to get OSX to work as well.

    Tuesday, December 11, 2007 2:26 PM
  • Unfortunately, I have still never seen a repro of this issue in front of me.....or I can guarantee it would be understood by now =)

     

    The best advice I have is to do a few things which might help me help you pinpoint the issue, which likely has to do with the current configuration of your machine:

    1. check the registry for cdrom-class filter drivers by opening the registry and looking at the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}.  Please let me know the values you have in the 'upperfilters' and 'lowerfilters' registry keys...

    2. try downloading the SDK and building the imapi2sample.  See if you can use it to list your drives (imapi2sample -list).

    3. try killing the explorer.exe process from task manager and restarting it with elevated priveleges.  does this fix the issue?

     

    The information from either of these two experiments might allow me to point you in the right direction to find a solution....

     

    Sorry for the frustration and I hope the culprit can be found...

     

    thanks,

     

    Garrett Jacobson

     

    Thursday, December 13, 2007 2:34 AM
  • Hi Garrett.

     

    FYI, In my particular case - my Vista Premium installation is not an upgrade, but a clean install on a brand new HDD

     

    I went to the the registery location you mention and found that I have  no "upperfilters" and "lowerfilters" keys.  Those keys are not even listed.

     

    I'll try the explorer.exe suggestion next.

     

    Thanks,

     

    D

     

    Thursday, December 13, 2007 6:48 AM
  • Come to think of it, there is another case I looked at a while ago that might be related.  Another interesting piece of information is whether you are using a third party port driver due to the chipset on the motherboard.  The easiest way to look for this is to follow these steps:

     

    1. go to device manager

    2. right click on any optical (cd/dvd) device

    3. left click properties

    4. left click on the 'details' tab

    5. select the 'hardware ids' property (usually the second one from the top)

     

    A good indication that a third party driver has been installed for your chipset is if any of the ID's have SCSI in their name.  Feel free to paste the ID's here and I may be able to help....

     

    I've seen some drivers in the past that mishandled a few commands in a way that prevented IMAPIv2 from functioning properly and caused some of the above behavior.  This should probably not apply to clean DVD installs, but if you have installed drivers for your motherboard, chipset, etc or from the OEM, then this is a possible scenario....

     

    let me know if you guys find anything interesting....

     

    thanks,

     

    Garrett Jacobson

    Thursday, December 13, 2007 7:51 AM
  • My motherboard is a new ABIT IP35 Pro.  I installed all the chipset drivers that came with the board.

     

    Here is what device manager says under the hardware ids' property for the CD/DVD:

     

    SCSI\CdRomPLEXTOR_DVDR___PX-740A__1.02
    SCSI\CdRomPLEXTOR_DVDR___PX-740A__
    SCSI\CdRomPLEXTOR_
    SCSI\PLEXTOR_DVDR___PX-740A__1
    PLEXTOR_DVDR___PX-740A__1
    GenCdRom

     

    Also - I tried running windows explorer in "administrator" mode, but it did not solve the problem.

     

    Thanks,

     

    D


    Friday, December 14, 2007 5:14 AM
  • Hey DennisMco36,

     

    Yup, it looks like the chipset drivers have replaced the inbox storage port driver that sits underneath most of the optical functionality.  In the past, I have seen these port drivers modifying commands in a way that breaks optical functionality.  If the port driver is the cause, none of the other suggestions will work....

     

    Please try uninstalling the chipset drivers that came with the board and see if the hardware id's turn back into IDE\CdRom****.  If they do, please reboot and see if that fixes the optical functionality....

     

    thanks,

    Garrett Jacobson

     

    PS. If they stay SCSI\CdRom*****, we may need to try and rollback your chipset driver to the inbox version....but that can be tricky since you have to make sure you're not relying on any of the RAID functionality of the chipset or you could cause your machine to not boot properly.  If the above doesn't work, let me know and we can try to figure out how to get you back to the inbox Microsoft chipset driver.....

    Friday, December 14, 2007 9:17 PM
  • Hi Garrett,

     

    Well.....I uninstalled the chipset drivers and found that the DVD becomes completely inaccessable.  It will not even show up as a drive on my system.

     

    The offending driver is a JMicron SATA Driver that provides functionality for the onboard SATA RAID Controller.  According to my MB manual "this driver installation is necessary for the devices connected through connectors eSATA1 or IDE1."

     

    When I un-install the JMicron driver - the DVD disappears as I mentioned above.  My DVD has a  PATA interface connected to the IDE1 channel, so without the driver - no DVD.  I am not running RAID on my hard drives, so I do not need the RAID functionality provided by the driver, but I do use the eSATA for an external HDD (which by the way is woking fine).

     

    So unless I can find a driver for the controller that will allow my eSATA to work while at the same time correcting my DVD problem, I think I'm out of luck. 

     

    Guess I'm going to have to buy a new SATA DVD and see if solves the problem, since I will not have anything on the IDE bus.  The only other option I can see is to do a clean install of Vista and then not install the JMicron driver, perhaps that will turn back the hardware ids on the DVD, but will leave me without me eSATA and I would have to use USB 2.0 for that device.

     

    What do you think?

     

    Thanks for the help.

     

    D

     

    Saturday, December 15, 2007 9:04 PM
  • Hey Dennis,

     

    Unfortunately, I don't think a clean install will be any different than the state of your machine now.  Unless......did you install Vista from this dvd drive?

     

    See, the way most of these chipsets work is that the BIOS and chipset report a certain ID string to Windows.  When in a raid mode or any mode that the manufacturer only wants to use their driver, they report a very specific ID string and Windows' inbox ata driver will not load for this device.  However, you can often use BIOS to put the chipset into legacy/pata mode, which will cause it to report an ID string that the inbox ataport driver can load with.  You may want to check the settings in the BIOS and see if you can change this and if it allows the inbox driver to load.  According to the above information, you may lose your eSATA drive.....but it would still be worthwhile to test this theory, you can always switch it back afterwards....

     

    Can you move the DVD drive to another IDE port? 

    Otherwise, the inbox ataport driver should be able to load on this controller if it's in pata/legacy mode in the BIOS....

     

    I'd expect the hard drive to work fine with their port driver, as that is the common case and probably recieves the most testing.  Additionally, hard drives rarely use scsi passthrough for communications, which is what the optical (cd/dvd) stack uses for a lot of it's communications and appears to be what many port drivers are not handling properly...

     

    In summary, I really believe this is the root of the problem....and wish I could do more to help.  I'm doing everything I can on my side to raise awareness of this problem with third party port drivers, but in the mean time I'd just try and help you do whatever you can to either find fixed drivers from the manufacturer or work with the inbox Microsoft drivers....

     

    let me know if you have more questions or any more information to report!

     

    thanks,

     

    Garrett Jacobson

     

     

    Sunday, December 16, 2007 12:53 PM
  • Hi Garrett,

     

    My BIOS did not have a setting that would allow me to use a legacy/pata mode, and I do not have another IDE port on the motherboard.

     

    I purchased a new SATA DVD - installed it -  and it works perfectly! I guess the lessen for me is to not try and move older soon to be legacy hardware (such as PATA device) when building a new system based on SATA

     

    I appreciate the help.  This was an interesting problem and I learned a bit more about hardware problem solving that may help me out in the future.

     

    Thanks again,

     

    D

     

    Wednesday, December 19, 2007 8:13 AM
  • I'm not sure whether or not this problem has been solved, so I thought I would throw in what I found to be causing the problem for me.

    I (stupidly) disabled the Shell Hardware Detection service in Vista. Opened up services, properties, set start up type to automatic and then started the service. Problem was solved instantly. CDs and DVDs of all types (+/- R/RW) are now recognised and I can burn again.

    Hopefully that helps anyone who likes inflicting problems on themselves, like me.

     

    Kyle.

    Friday, February 15, 2008 5:39 PM
  •  

    Thank you Kyle for sharing your resolution.
    Saturday, February 16, 2008 12:17 AM

  • This is indeed a JMicron problem/incompatible problem. They expose all devices connected to their controller as SCSI thus Vista will treat these devices as non-burner.

     

    http://www.jmicron.com/Support_FAQ.html

     

     

    I'm having the same fate.

     

     

    Tuesday, February 26, 2008 1:41 AM
  • How do you enable the shell hardware detection service?

    Sunday, May 11, 2008 8:14 PM
  • I have Windows vista home premium when I insert a blank cd it doesnt not recgonize it, and i cant burn some of my data files.

     Below is what my driver hardware ids are

    IDE\CdRomMemorex_52MAXX_3252AJ1__________________4WS2____
    IDE\Memorex_52MAXX_3252AJ1__________________4WS2____
    IDE\CdRomMemorex_52MAXX_3252AJ1__________________
    Memorex_52MAXX_3252AJ1__________________4WS2____
    GenCdRom

    I dont know why it wont read my blank cds because it use to work about a week ago now it wont recgonize and blank cd media. Could you please help me solve this issue.

    Sunday, May 11, 2008 8:58 PM
  •  

    This forum focuses on OS level topics and is primarily intended for application developers. It is not intended for discussion of user-level optical issues observed in concrete applications, such as DVD Maker or Windows Explorer. Please use other support channels for user-level issues (e.g. http://support.microsoft.com for Microsoft products).

     

    In addition, Windows Vista discussion groups (see http://windowshelp.microsoft.com/communities/newsgroups/en-us/default.mspx) are another good place for discussions of issues that are outside the scope of this forum.

     

    This thread is going off-topic and will be locked.

    Tuesday, May 13, 2008 11:12 PM