Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,457
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. Thank you. Can you now go into Read mode and copy + paste all of the info from the box on the right when that disc is in the drive please.
  2. It errors out like that because it predates UAC and used to be able to write to HKLM in the registry. Now it can’t. Run as admin and you won’t get the errors.... or ignore them as you have been doing. iFO RC is IFO file region code. It’s just a byte in the file where you can set which region the disc is for. That’s in addition to the regional code the disc itself might have.
  3. That doesn’t sound right. Lba out of range means it’s beyond the end of the disc. Can you provide a log showing that stuff at all please?
  4. I don’t know what you’ve downloaded there, but it certainly isn’t the ImgBurn setup program (installer). What exactly did you click on when over at the digital digest website? Screenshot that site for me please and show me what you clicked on.
  5. I wonder when the discs were manufactured? Maybe they’ve deteriorated and the drive can’t reliably burn them now. You could try enabling the ‘perform opc before write’ option in the settings and see if that makes a difference.
  6. That info is beyond the 2048 bytes of user data in a CD sector and therefore not included in an ISO. As for making the drive burn as-is (errors and all), that's where RAW mode burning would come in - which ImgBurn doesn't support.
  7. Yes, a properly connected ssd would be fine.
  8. The success one was too loud (it used to scare people), so I’m pretty sure I adjusted it down slightly.
  9. They could be important if the game checks for bits that are intentionally wrong. If your drive corrects them, it’s actually made them ‘wrong’ - and then the game may not play correctly. It could also just mean your image isn’t great in the first place.
  10. Well... there’s only ever 1 active drive in the program at any time, so you can only burn to 1 drive at a time. Different instances can burn to different drives simultaneously, but your storage device(s) would need to be fast enough to support it.
  11. The other two could still be modifying the contents of the disc as it’s being read. ImgBurn won’t be. You’d have to do a file comparison and see what's different between the two (three).
  12. The file system on that disc was made by Toast on an Apple machine. It has nothing to do with the machines you’re using and that info doesn’t change if you ‘copy’ the disc. From best to worst, udf->Joliet->iso9660
  13. Some memory is probably being overwritten - bad! Go for restart rather than continue.
  14. BIN and CUE works fine with DAEMON Tools. I do not really think of 'IMG' as a format. To me, it's just a raw dump of the disc... equivalent to the BIN file (which is pretty useless without the CUE).
  15. It might be getting the 'CubaseSX3Level1' name from an autorun file. It's correctly showing 'My Disc' when you look at the properties (matching what ImgBurn shows). ImgBurn displays the volume label from the (best) file system. It doesn't look at the autorun file. You can hover your mouse over where it says the volume label and it'll show you info from some other fields in the file system descriptors too.
  16. I figured you’d be using the same versions on both machines, so anything that may or may not feature in the changelog for 2.5.8.0 wouldn’t come into it. Obviously I do not remember what I did when, it was years ago!
  17. LRA is last recorded address. If you’ve got the track size, it isn’t overly required. Some drives don’t bother returning that info. The addition of ADIP info might be down to the date of the firmware in the LG drive. The adip info doesn’t change, even once you’ve burnt the disc. So the book type field will show the real type of disc. The last recorded info can be changed as a result of burning, and that’s where you’d then see a disc have its book type changed to dvdrom for compatibility reasons. As for the commas, that’s down to your regional settings. The program uses what your OS is configured for.
  18. Are you able to try your Samsung drive in that other machine? It's quite a specific error and seems weird a drive would return it when reading a normal DVD-RW disc. Maybe you've some software on your PC that's messing with the error codes? There's nothing that can be done software wise to work around this issue. If that's really what the drive thinks the problem is, you just have to live with it. The firmware update might fix it, but you'd have to try and find a changelog for SB01 somewhere. FirmwareHQ is fine, we helped collect all the firmware and build it.
  19. As it’s quite rare these days, are you doing this for someone with no internet connectivity? If they do have the internet, just email them the 3 urls to the YouTube videos.
  20. First things first, have you actually downloaded them as files from YouTube? I'm pretty sure they come down as MP4 or AVI files... but I believe 3rd party tools are required for that job. If that's still the case, you'll need to find out how to download from YouTube before you can begin to do anything with ImgBurn.
  21. It sounds like your I/O is getting hung up. That's why ImgBurn can't be closed and you're having to reboot. When it gets stuck, try just unplugging the drive and see if anything returns to normal - and 'normal' in this situation would mean you get an error message. As to why it's running into issues... who knows. It could be a bad usb cable, outdated drivers, bad usb chipset/drive enclosure chipset combo etc.
  22. Hmmm... weird! Can you try the disc in another drive and see how it gets on with it?
×
×
  • Create New...

Important Information

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