Jump to content

John_Anderson

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by John_Anderson

  1. The one I want is the 57/43, not the 53/47. Is it the same?
  2. Which layer break position should I choose? I know there is a yellow star and that's the one I should use right? But what about if the 57/43 grey star is by far the most aesthetically pleasing of them all? Is there any downside in using the 57/43 grey star instead of the yellow one? Thanks in advance.
  3. Write offset correction would be an amazing addition.
  4. HELL YEAH!!!!!!!!!!!!!!!!! Finally. This was why I've been having those reading/verifying problems for as long as I can remember! After I uninstalled Daemon Tools AND the driver I finally get perfect graphs! Thanks LIGHTNING UK! for the warning in ImgBurn!!!!!
  5. Well here's the deal. I'm trying to backup a concert DVD to a double layer DVDR. The concert is spread across 2 VTSs (don't know why). I ran it through different programs (such as DVDDecrypter, DVDFab Decrypter, DVD Shrink, etc) to get rid of what I'm about to show you, but nothing works. All the layer breaks are still there. Take a look: So then when I try to build the image with ImgBurn, this is what I get. Which layer break position should I choose? What should I do, in general? Thanks in advance.
  6. I was trying to burn a Verbatim DVD+R DL MKM-001-00 and it failed. I created the image with ImgBurn. I correctly selected the MDS file. And around 53% it failed. I use the latest version (2.4.1.0) Does anyone know why? Here's the log. Thanks. (btw, i have successfully burnt several DL discs, this is the first time it fails) I 15:45:40 ImgBurn Version 2.4.1.0 started! I 15:45:40 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 15:45:40 Total Physical Memory: 981.424 KB - Available: 633.604 KB I 15:45:40 Initialising SPTI... I 15:45:40 Searching for SCSI / ATAPI devices... I 15:45:40 Found 1 DVD-ROM and 1 DVD
×
×
  • Create New...

Important Information

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