Jump to content

giuseppe

Members
  • Content Count

    4
  • Joined

  • Last visited

About giuseppe

  • Rank
    ISF Newbie
  • Birthday 09/11/1959

Profile Information

  • Gender
    Male
  • Location
    ITALY
  1. giuseppe

    Disc Not Empty in Write/Build/Discovery mode

    Hi, I finally found the drivers in the asus site and installing them the behaviour has improved a little but not solved: after one, two burns ok, the next day, without any actual change, again it doesn't recognize a blank cd. Now after having disabled a number of boot processes it works, but I'm not sure that it'll work tomorrow so I plan to try two checks: 1) upgrading BIOS and all other drivers found in Asus site to check if the behaviour became stable and 2) booting ubuntu because if it doesn't work this way then the problem should be in burner hardware or firmware which needs a new Asus intervention. I'll keep you posted on the outcome of my checks and thanks again for you help.
  2. giuseppe

    Disc Not Empty in Write/Build/Discovery mode

    Sorry for the naive question but I have not found a way to download chipset drivers for free but only via tools asking 30€ . Is this the only way to get such drivers? By the way, the chipset driver turns out to be not updated (2006) in scans made ​​by the tools that I've tried. Thanks again for your help.
  3. giuseppe

    Disc Not Empty in Write/Build/Discovery mode

    Hi Lighting UK and first of all thank you for you quick reply. I've just tried in safe mode but I get the same result. Chipset is Intel® Chief River Chipset HM76, Processor is Intel® Core i7-3630QM CPU @ 2.40GHz, 2401 Mhz. Driver: System Information says: c:\windows\system32\drivers\cdrom.sys (6.3.9600.16384, 160,50 KB (164.352 Byte), 22/08/2013 10.46) Property of SlimtipeDVD says: c:\windows\system32\drivers\cdrom.sys, version 6.3.9600.16384 (winblue_rtm.130821-1623), 21/06/2006. In any case if I try to update the driver online, it proves to be updated.
  4. Hi, I'm getting crazy with the burner that does not recognize blank CD / DVD. When I insert a blank CD (Verbatim CD-R or SONY CD-RW)) or DVD (SONY DVD+R DL) in Read/Verify Mode ImgBurn says "Disc Is Empty", but in Write/Build/Discovery mode says "Disc Not Empty", and you can't burn it. The problem is not specific to ImgBurn because it also happens with Windows Media Player but I hope ImgBurn and your community can help me to solve it. I have not found similar problems in support forum, but excuse me if I missed something. My environment is: Notebook ASUS A55VD, burner SlimtypeDVD A D, OS Windows8. The notebook has few months and I've already sent it to ASUS Support and the burner has been replaced, but after a couple of (random) succesfull attempts, the situation is as described before and I'd like to understand the cause before sending it again to ASUS support. Attached you can find read and write mode logs. Here is CD info got in Read Mode -------------------------------------------------- SlimtypeDVD A D (SATA) Current Profile: CD-R Disc Information: Status: Unknown State of Last Session: Unknown Erasable: Unknown Formatted: Unknown Sessions: Unknown Free Sectors: 359.846 Free Space: 736.964.608 bytes Free Time: 79:59:71 (MM:SS:FF) Next Writable Address: 0 MID: 97m34s23f (Mitsubishi Chemical Corp.) Supported Read Speeds: 10x; 16x; 20x; 24x ATIP Information: Disc ID: 97m34s23f Manufacturer: Mitsubishi Chemical Corp. Start Time of LeadIn: 97m34s23f Last Possible Start Time of LeadOut: 79m59s73f ------------------------------------------------ and this is CD info got in Write Mode ------------------------------------------------ SlimtypeDVD A D (SATA) Current Profile: CD-R Disc Information: Status: Unknown State of Last Session: Unknown Erasable: Unknown Formatted: Unknown Sessions: Unknown Free Sectors: 359.846 Free Space: 736.964.608 bytes Free Time: 79:59:71 (MM:SS:FF) Next Writable Address: 0 MID: 97m34s23f (Mitsubishi Chemical Corp.) Supported Write Speeds: 10x; 16x; 20x; 24x ATIP Information: Disc ID: 97m34s23f Manufacturer: Mitsubishi Chemical Corp. Start Time of LeadIn: 97m34s23f Last Possible Start Time of LeadOut: 79m59s73f Performance (Write Speed): Descriptor 1... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 359847 (0x00057DA7) -> RS: 1.765 KB/s (10x) - WS: 1.765 KB/s (10x) Descriptor 2... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 359847 (0x00057DA7) -> RS: 1.765 KB/s (10x) - WS: 2.823 KB/s (16x) Descriptor 3... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 359847 (0x00057DA7) -> RS: 1.765 KB/s (10x) - WS: 3.529 KB/s (20x) Descriptor 4... -> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00 -> EL: 359847 (0x00057DA7) -> RS: 1.765 KB/s (10x) - WS: 4.234 KB/s (24x) ------------------------------------------------------- Any help is really appreciated! ReadLog.txt WriteLog.txt
×

Important Information

By using this site, you agree to our Terms of Use.