Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. The command line stuff is all mentioned in the Readme.txt file that gets installed alongside ImgBurn.exe
  2. This is the ImgBurn support forum, try an xbox related forum.
  3. Nope, you can't use that one. The special firmware was made for version B drives *ONLY*.
  4. If your buffer is all over the place during the burn, that's not a bad idea. If it's rock solid, there's really no need.
  5. If your client just wants a straight copy, I assume the original disc was ok... therefore your copy will be to, even if *you* can't play it. Regions aren't changed by reading and burning the disc. If a certain region is configured in the VIDEO_TS.IFO file on the disc then it'll be exactly the same on both discs. I don't know why it would be though, normally these things are created for 'all regions'. You can configure your DT drive for any region - but that only matters if it's emulating a DVD-ROM disc once you've mounted it (mount the MDS if ImgBurn made one). Get back to me when you actually have the disc or ISO in front of you.
  6. Nope. Success or failure is totally down to the drive/firmware/media combo. If it can't write to a bit of the disc, that's when it will error out - and you downloading / browsing has nothing to do with that.
  7. Windows 7 is an operating system... the one you're using! No, that drive isn't able to burn the oversized images. The default layer break setting is 'Calculate Optimal' and that's what it should be left on at all times.
  8. If you're burning from a drive that another program (the OS, Internet Explorer etc) starts using too, it could interrupt the flow of data to ImgBurn. When that happens, the amount stored in ImgBurn's internal buffer may drop off a bit. It's only when it reaches zero that the drive basically has to 'pause' and wait for more data - even that isn't really a problem these days. Usually these interruption are pretty short and the buffer should recover quickly - after all, you're probably burning at less than 10MB/s and modern desktop drives can usually manage 80-100MB/s+ pretty easily. Mechanical hard drives are much better (quicker) at sequential access than they are at random access so if your drive starts thrashing around, you know the buffer levels are going to be dropping off.
  9. It looks like your usb controller/chipset timed out whilst the drive was trying to burn... and then the drive (or something connected via USB) disconnected itself from the machine. Just try another disc.
  10. Other programs may handle formatting differently. You can't really do a direct comparison between them. If ImgBurn hasn't even got to the 'Zeroing Sectors' phase, the drive is still in complete control of the format. By that I mean ImgBurn has issued the 'format' command and the drive goes off and does its thing. All ImgBurn then does is provide basic feedback on % complete - based on what the drive reports. Copy + paste where you're up to from the log window please.
  11. Do you have anything running in the background that could be caching this information? I don't think your issue is related to ImgBurn at all.
  12. Your attachment didn't seem to work but I found the manual of the LG BD 610 player and looked at the 'playable discs' page (page 6). It does seem to suggest that ISO9660, Joliet and UDF should all work. That doesn't account for bugs in the player's firmware though I assume you've checked yours is up to date?
  13. The firmware on your drive is out of date. http://www.firmwarehq.com/Samsung/SH-S223C/files.html You should also read this... http://forum.imgburn.com/index.php?showtopic=8000
  14. You'd really have to check the player's manual for that. What you've done *should* work but I guess the player just doesn't try and read ISO9660 or Joliet at all when BD media is present.
  15. Try the other supported write speeds. Try cleaning the drive with a cleaning disc. Try some discs from another spindle of Verbatim 8x (MKM-003-00) discs - try and get the ones made in Singapore. Service pack 1 is out for Windows 7 btw, you should install it.
  16. Well there's only a quick or full erase. Quick just writes zeros to the first 1024 sectors. Full erase will tell the drive to perform a 'full format' operation on the disc and will (assuming the 'prefer properly formatted discs' option is left enabled in the settings) then write zeroes to all sectors on the disc. There's no way ImgBurn should *still* be displaying the volume label for the disc (when in Read mode) after that's happened.
  17. You haven't really tried the disc or drive enough times to says it's one or the other. It might just have a problem with the discs your laptop is burning - maybe they aren't great quality burns. Drives are cheap enough to replace them quite easily now. If a new one also has a problem reading the discs then it's probably your laptop drive/the media itself at fault.
  18. Let me refer you back to a previous post of mine in your other thread... http://forum.imgburn.com/index.php?showtopic=20057entry140965
  19. The first error is the real one... so in your case that's: Your drive reported a 'Write Error' whilst trying to burn to the media.
  20. You can't erase a BD-R, it's 'write once' media.
  21. Open the CUE in notepad and copy + paste all the text please. Then just try moving/deleting the CUE and burn the BIN directly.
  22. Try all of the supported write speeds Try cleaning the drive with a cleaning disc Try discs from another spindle
  23. Please post the log - as per the pink box up the top
  24. See if you can get a full (desktop sized) screenshot of *exactly* what's visible/going on when the box pops up and tell me the last thing you clicked on.
  25. It's not a problem if you're aware of the issue... which you now are. Why not update the firmware on one of the drives and leave the other one? At least you could try again with this image (those files) and see if the same thing happens when running SB04.
×
×
  • Create New...

Important Information

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