Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Well, you could post your filter driver list. Use the feature in the Tools menu. Did you not have the option of getting an internal drive? If you have the ability to add an internal normal size (non slimline) drive to your PC, you should always do that rather than buying an external. It'll be far more reliable.
  2. 1 makes a new file system, 2 doesn't. You can't really compare them. The content of both images should be the same (assuming there's no clever stuff going on with having multiple files use the same sectors - 1 would then make a much larger ISO)
  3. It's a drive/firmware/media combo thing and nothing to do with ImgBurn.
  4. Have you tried resetting the DMA settings in Windows? Try the option in the Tools menu first. Then, if that doesn't work, refer to the post in the FAQ.
  5. http://lmgtfy.com/?q=Duplex+Secure%27s+SPTD+driver+can+have+a+detrimental+effect+on+drive+performance For the 'image too large for disc' issue, refer to this. http://forum.imgburn.com/index.php?showtopic=12200
  6. Freezing (where something stops processing the I/O) is usually due to drivers (including 'filter' drivers - check the 'Tools' menu) or the way the drive is connected - in your case, USB.
  7. Always post the log please, regardless of what you think it shows / doesn't show.
  8. It should be valid, yes. If using a 64 bit machine (with a 64 bit app), the path would be slightly different - 'HKEY_LOCAL_MACHINE\Software\Wow6432Node\ImgBurn'.
  9. How about using a Silicon Image PCI card? Do you have any spare PCI slots? If the machine just won't process the command (and hangs/freezes), there isn't much I can do I'm afraid.
  10. Do you not have any real SATA ports you can connect it to?
  11. You've formatted that BD-RE with spare areas enabled. That means the drive will verify as it writes (slowing it down to 0.8x) - and it appears to have failed (hence the 'Write Error – Auto-Reallocation Failed' message). Optical drives don't like being on RAID controllers, that's probably why you have '9999' as the firmware version. Get it off that controller if possible and then see if there's a firmware update available for the drive. Maybe then you'll have more luck burning those new Verbatim BD-RE DL discs.
  12. Try making an ISO first (so you aren't burning 'on the fly') and then burn that in Write mode. If Verify fails again, repear the Verify process again but put the disc in one of your other drives.
  13. Post the log showing you burning+verifying the disc please.
  14. Post the log please. It sounds like a DMA issue.
  15. Yes. It's actually mentioned on the dvdisaster page too. http://dvdisaster.net/en/howtos91.html Look under 'Possible error causes and remedy:' -> 'Typical problem: wrong image size.'
  16. The drive just reported a write error. You can but try again and hope it doesn't happen a 2nd time.
  17. You're better off asking this over at the Doom9 forums where fellow multiavchd users can see it. They'll know what works and what doesn't work where PS3 playback is concerned... I do not.
  18. You can expect anything up to an additional 31 sectors of data (well, padding) on a BD-R disc as the ECC block size is 32 on BD media (it's 16 on DVD media). This data (padding) is added by the drive. So if you only burn 1 sector, the drive will write 32. If you burn 33, the drive will write 64.
  19. The right commands will be being sent, it's down to your drive as to what it does with them.
  20. What I'm saying is that if 'C:\Documents\steam-BU\12-23-11.ISO' is the augmented ISO and its size really is 24,125,872,128 bytes (check its properties in Explorer), all the data is present on the disc. Without watching what you do every step of the way, I can't possibly know if you've done everything correctly. If the ISO you've read back from that burnt disc (your log didn't include that step) isn't also 24,125,872,128 bytes in size, something is going wrong.
  21. It has burnt and verified whatever you gave it... so if something is missing, it must be in the ISO itself.
  22. ImgBurn burns files as-is. If you want to convert your wmv into a proper set of DVD Video files you'll need to use something like DVD Flick or ConvertXtoDVD. Once you've got/done that, burn the VIDEO_TS folder with ImgBurn.
  23. The ratings given to layer break positions are nothing to do with how readable the disc will be at that point. They're based on technical stuff (flags in the IFO/VOB files mainly). There's nothing wrong with an 'average' one. The % value shows how much will be put on each layer. Discs are most readable when equal amounts are written to both layers... so 50/50 may perform a little better than 70/30 etc. I'd be interested to see the burn + verify log from your most recent burn. Don't also forget you can run something like 'Opti Drive Control' (Google it) on that drive/disc and get a 'Disc Quality' graph of how well the burn went. (set it to scan at 4x) - maybe that's what you meant by 'test result' ? If so, post the screenshot of that too please. You've picked the layer break position via that window that pops up. The software translates it to a sector/lba address and then tells the drive to use it. No, you don't need OPC on. You can check the iHAS624 B/iHAS124 B drive tests (in the 'Drives' section of the forum) to see which speed produced the best quality burns on MKM-003-00 media (which I assume is what you're still using).
  24. Please post the log of you reading the source disc and burning the new one.
×
×
  • Create New...

Important Information

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