Announcement

Collapse
No announcement yet.

Failed to Burn DVD - ARGHHH!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tad_R
    replied
    Before you sweat through a change of drive, I notice you're still using the Sony media...the Media ID isn't the same as what I used to get, and I suspect your drive (or stand-alone player... or both) doesn't like the media - try a change of media first, before you go for a new drive...

    Try the smallest container you can find of Verbatim, SL, either +R or -R... if you get +R, please go back into Imgburn and make sure the Booktype is set to DVD-ROM, and try once more. (Just don't get Memorex...).

    For what it's worth, from someone who has done a lot of back-ups, I wouldn't bother with the verification option... discs that verify clean can still pixelate, freeze, etc... the best verification method is your own two eyes...
    Okay, I got some Verbatim SL DVD +Rs at Best Buy and tried again. I even took off the verification option. I also tried to copy one of my kids Veggie Tales, just to make sure it wasn't some issue with the other disc I was copying. Still no luck. I have attached logs and a picture of an I/O error I received from IMGBurn. As far as setting the booktype, I couldn't figure out what to do. IMGBurn seemed to recognize that I was using DVD +Rs, but when I went into the booktype setting screen, I didn't see an option to change to DVD-ROM without selecting a manufacturer. It wanted me to select by brand name of the drive, which I could not find (even after going into the device manager). Is it normal to not see a manufacturer name on a device?

    I am ready to get a shovel and go bury this burner. Incidentally, I probably should have warned you all that I am the most unlucky person on the planet. If there is a high degree of statistical improbability that something negative will happen with something I purchase, then I will be in the affected group. You should have run for the hills when you saw me coming - LOL!

    Anyway, if you guys are out of ideas, then I think I'm going back to Best Buy and buy a good quality drive. Any recommendations on brand and specs?

    Tad
    Attached Files

    Leave a comment:


  • dvd_gwr
    replied
    "Try the smallest container you can find of Verbatim, SL, either +R or -R... if you get +R, please go back into Imgburn and make sure the Booktype is set to DVD-ROM, and try once more. (Just don't get Memorex...)."

    opps... I have been using Memorex and having issues with reading/playing on my new dvd system (although burning was not a problem).. I just bought Verbatim -R blanks to try............ Thanks for your great advice You guys are great...

    Leave a comment:


  • CBR929
    replied
    Tad_R sorry to hear you are still having trouble. Best Buy had verbatim on sale for $12.99 for 50 but ended yesterday. Could someone tell me what these strange characters are in his dvdfab_internal log files 0m 06.28s: volume label =@~y and 0m 04.57s: volume label „§êy because they are not in his previous logs? Sorry also found this in his post #3 33m 54.00s: volume label Ws€Â´‰XøŒ à
    Last edited by CBR929; 02-07-2010, 04:17 PM.

    Leave a comment:


  • maineman
    replied
    Yup, I agree with DC.
    I suspect your burner is belly up, but you really should pick up some Verbatim media and give this another shot.

    As far as drives causing problems or dying, it's not uncommon.
    On the other hand, I've been doing this a long time and have never had a "bad" drive.
    "Retired" drives...oh yeah!

    It's a very simple process to swap out drive

    Leave a comment:


  • DarthCopier
    replied
    Originally posted by Tad_R View Post
    Okay, the weird stuff just keeps on rollin. I installed IMGBurn and got everything set up per the tutorial and video. I went ahead and selected the option to have the disc verify when done burning. It copied the disc, but it bombed out when verifying. I tried to play the disc in 2 DVD players and Windows media and no luck. I have attached all logs.

    The only thing recommended that I haven't done is delete the patin-couffin driver, but I didn't figure that mattered since I was using IMGBurn now. Incidentally, I did finally find the driver. It wasn't showing up before as either the uninstall or CCleaner had already removed it. Now it is back since I reistalled DVDFAB.

    Anyway, I have my own guess and maybe someone can tell me if they think I'm on the right track. My computer is brand new and a pretty decent Gateway system. But right after I bought it, I remember that I had a problem burning some files to a disc just using the Windows software. Is there a good chance that all of these problems are due to a bad drive? Is that common?

    Now, if it turns out that I do need a new drive, what is a good and hopefully economical burning drive to buy? Are they hard to install? Funny thing is I bought an extended warranty for the computer, but since it is so new I would have to send the entire computer to Hoboken or somewhere just to have them test are replace the drive. I figure it might just be cheaper, and quicker, to get a new drive and install it myself. Of course, that is if the drive is the issue.

    Any ideas?

    Tad


    Before you sweat through a change of drive, I notice you're still using the Sony media...the Media ID isn't the same as what I used to get, and I suspect your drive (or stand-alone player... or both) doesn't like the media - try a change of media first, before you go for a new drive...

    Try the smallest container you can find of Verbatim, SL, either +R or -R... if you get +R, please go back into Imgburn and make sure the Booktype is set to DVD-ROM, and try once more. (Just don't get Memorex...).

    For what it's worth, from someone who has done a lot of back-ups, I wouldn't bother with the verification option... discs that verify clean can still pixelate, freeze, etc... the best verification method is your own two eyes...

    Please let us know.

    DC

    Leave a comment:


  • Tad_R
    replied
    I believe the simplest way out of this is to switch to Img.
    Most of the old timers here and all the mods (I think anyway) prefer Img.
    It is much more reliable, configurable and it's the best darn burn engine on the planet.
    It's also freeware and has great support from the author, LIGHTNING UK!
    Most users leave their problems behind when they switch.
    Okay, the weird stuff just keeps on rollin. I installed IMGBurn and got everything set up per the tutorial and video. I went ahead and selected the option to have the disc verify when done burning. It copied the disc, but it bombed out when verifying. I tried to play the disc in 2 DVD players and Windows media and no luck. I have attached all logs.

    The only thing recommended that I haven't done is delete the patin-couffin driver, but I didn't figure that mattered since I was using IMGBurn now. Incidentally, I did finally find the driver. It wasn't showing up before as either the uninstall or CCleaner had already removed it. Now it is back since I reistalled DVDFAB.

    Anyway, I have my own guess and maybe someone can tell me if they think I'm on the right track. My computer is brand new and a pretty decent Gateway system. But right after I bought it, I remember that I had a problem burning some files to a disc just using the Windows software. Is there a good chance that all of these problems are due to a bad drive? Is that common?

    Now, if it turns out that I do need a new drive, what is a good and hopefully economical burning drive to buy? Are they hard to install? Funny thing is I bought an extended warranty for the computer, but since it is so new I would have to send the entire computer to Hoboken or somewhere just to have them test are replace the drive. I figure it might just be cheaper, and quicker, to get a new drive and install it myself. Of course, that is if the drive is the issue.

    Any ideas?

    Tad
    Attached Files

    Leave a comment:


  • Bob78634
    replied
    You may try imgburn, a free program but you can make a donation.

    Leave a comment:


  • maineman
    replied
    Originally posted by StormJumper View Post
    Not sure what you disagree on
    I only suggested the member to make sure no other program uses the patin-couffin driver because it would cause un-wanted issues with any other program that may be on the system if the member decides to not to re-install it
    I disagree with your advice on the basis of the following:

    Telling the OP to make certain no other software uses the patin-couffin driver prior to uninstalling doesn't help him in any way.
    It needlessly creates a conflict as to how to proceed.

    VSO support states it can be safely removed and is not needed as SPTI is now the preferred access driver for VSO.
    As a matter of fact, if suspected of causing problems, they recommend removing it.

    No software other than VSO uses it anyway.
    Regardless, Patin-couffin driver is reinstalled as soon as Fab is installed unless the user manually opts out.

    Originally posted by StormJumper View Post
    I didn't say not to go with your recommendation, anyway like I said was only my .02 cents
    I never said that you advised the OP not to follow my advice.

    I suggest we return to helping to OP

    Leave a comment:


  • StormJumper
    replied
    Originally posted by maineman View Post
    I disagree.
    There's no way to determine if the patin-couffin driver is part of the problem without deleting it.
    Regardless, the patin-couffin driver is reinstalled with the next install of Fab without harm to other VSO programs.

    You would have to opt out manually and not install VSO at all in order to prevent it from installing.
    BTW, Fab will still work without it as it now uses SPTI as its access driver.
    Not sure what you disagree on
    I only suggested the member to make sure no other program uses the patin-couffin driver because it would cause un-wanted issues with any other program that may be on the system if the member decides to not to re-install it
    I didn't say not to go with your recommendation, anyway like I said was only my .02 cents

    Leave a comment:


  • maineman
    replied
    Oh yeah...
    Patin-couffin should show up in device manager right where I said.
    I'm running Win7 Pro 64-bit.
    I outlined in red where to click to expand.
    Here's a screenshot:
    Attached Files

    Leave a comment:


  • maineman
    replied
    Hi again Tad.
    I believe the simplest way out of this is to switch to Img.
    Most of the old timers here and all the mods (I think anyway) prefer Img.
    It is much more reliable, configurable and it's the best darn burn engine on the planet.
    It's also freeware and has great support from the author, LIGHTNING UK!
    Most users leave their problems behind when they switch.

    Here is an excellent video tutorial and the thread also has a download link:

    Leave a comment:


  • Tad_R
    replied
    Okay, I have some wierd stuff to report. I followed the instructions and deleted the old version and went and searched out all files I could find that were associated with DVDFAB. Then, I ran CCleaner and rebooted and reinstalled. The only thing I didn't do was delete the patin-couffin driver because I couldn't find it. In Windows 7, it isn't in the device manager, or at least I didn't see it - and I ran many searches trying to find it with no luck.

    Anyway, guess what - It worked . . . or so I thought. I was able to finally get one of the discs to burn. It created a good working copy.

    So, I thought I would try again to test my luck and make sure that this wasn't just a fluke. I tried another disc in the same kid's series (to make the test as similar as possible) and it went back to giving me the "Failed to Burn DVD. Do you want to burn again?" message. Oddly, each time I tried to burn, it never did much after I entered the disc. The progress indicator stays at 0.00% or barely over that. When I did get it to work, it burned very quickly, although the finalizing seemed to take quite a while (made me very nervous).

    Anyway, I have attached the new logs. Please take a look and see if any news ideas pop up. This is very odd.

    Tad
    Attached Files
    Last edited by Tad_R; 02-05-2010, 04:55 AM.

    Leave a comment:


  • maineman
    replied
    I disagree.
    There's no way to determine if the patin-couffin driver is part of the problem without deleting it.
    Regardless, the patin-couffin driver is reinstalled with the next install of Fab without harm to other VSO programs.

    You would have to opt out manually and not install VSO at all in order to prevent it from installing.
    BTW, Fab will still work without it as it now uses SPTI as its access driver.

    Originally posted by StormJumper View Post
    Suggestion...
    Before removing or deleting the patin-couffin driver you should check to make sure you have no other program on your system that uses the patin-couffin driver because if you do those program will no longer work properly.

    Just my .02 cents

    Leave a comment:


  • StormJumper
    replied
    Suggestion...
    Before removing or deleting the patin-couffin driver you should check to make sure you have no other program on your system that uses the patin-couffin driver because if you do those program will no longer work properly.

    Just my .02 cents

    Leave a comment:


  • maineman
    replied
    In addition to the excellent advice so far...

    Uninstall everything with respect to Fab.
    Use the uninstaller and then manually delete anything you find.

    In Windoz device manager > scroll down to VSO (at or near the bottom) >
    click on + to expand >
    Uninstall all instances of patin-couffin driver

    If you don't already have it, download and run CCleaner.
    Be certain to tick Old Prefetch Data under the Advanced heading.

    As DC suggested, Sony discs are good quality. However, they tend to be a bit finicky.
    By this, I mean they are less universally compatible than Verbs or Taiyo Yuden, but when they work, they work very well.

    I didn't have a chance to research your burner and firmware, but we can do that if it becomes necessary.

    I also believe you will be better off with Img as your default burn engine...
    but one step at a time.

    Good luck

    Leave a comment:

Working...
X