Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,514
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. It sounds to me like you don't need a bootable disc at all, you just need a disc that has an autorun file on it. Have a go at googling that and maybe you'll figure it out.
  2. Your drive will either do it automatically or it won't. There's no way of asking it to do it.
  3. There do seem to be a good few people having issues with them. You should be reporting this to Verbatim though. If enough people tell them about problems with their discs, maybe they'll do something about it. It's a shame really because they were the go-to discs for anything DVD+R DL related. Theirs would work when all others would fail.
  4. http://forum.imgburn.com/index.php?showtopic=14632
  5. You've uploaded the graph data file and not the log.
  6. Technically, yes, the write and Verify operations might complete successfully and without error, but it certainly won't be 'fine'. At least not if you're doing it for testing before replication. Layer 0 on OTP media can only ever be greater than or equal to the size of L1. So the layout you're attempting to burn is incompatible with OTP discs and it's physically impossible to burn it with the layer break in the correct place. That's why you're getting the warnings from ImgBurn. So it's not about me recommending you don't do it, you flat out can't... it's impossible. The disc you're ending up with is nothing like the one you've actually created in scenarist. The physical layer break will have been moved to a location compliant with what's actually possible on OTP media. It may or may not be able to also adjust the ifo files on the disc accordingly. You can just copy and paste the correct ImgBurn session's worth of entries from the big log file - or zip the entire thing and upload that.
  7. The TOC isn't part of the ISO and it's just something the drive handles itself. As for exactly where on the disc it goes, that's probably covered in the MMC specs... or the disc format specs. I'd have to look it up as I don't know it off hand.... or you could?
  8. All LiteOn drives look basically the same, so you can't go on looks alone. As for quality... you can't afford to be picky with this. There aren't many options!
  9. Can you post the log of you burning it please? As I said in my previous reply, unless you have some special hardware and media allowing you to burn an ISO created for PTP (and not compliant with OTP limitations), it's never going to burn 'properly'.
  10. There's a LiteOn listed but it doesn't mention the model number. https://www.bigbang.si/bralniki-in-zapisovalniki/24x-dvd-rw-zapisovalnik-sata-liteon-585235
  11. You don't have the required hardware. Buy a new LiteOn ihas124 / ihas324 drive (or one of the special Optiarc 5280S-CB-PLUS / 5290S ones).
  12. Yes
  13. That message looks like one your drive is returning - so it doesn't support those discs. It's impossible to say what'll work / not work without knowing more about the discs. Generally speaking though, you should just need a drive that can burn DL discs... which you've already got... so you're just unlucky. A firmware update for the drive may fix the issue.
  14. Post the whole log please.
  15. I'm not sure I follow you. You can't burn PTP with normal drives/media and it's not possible to have more on layer 1 than layer 0 with OTP media. Your image shows layer 1 is bigger than layer 0.
  16. It's 1 cue file per disc and you don't 'convert' to cue files, that's not what it does. The cue pulls in the MP3 files you've created it for.... however many that might be. Glad you eventually figured it out.
  17. This isn't the DVD Decrypter forum... that program is dead and unsupported. Luckily, your errors are pretty generic and (for the most part) would apply to ImgBurn too. Yes, your disc is unreadable. That could be due to the scratches or it could be part of any copy protection the disc happens to be using. If the program is able to get the drive to read any problem sectors by simply asking it to attempt to read them again and again, fingers crossed, the data it returns should be fine. That's all down to the drive though. The error messages when you close it down are indeed down to permissions. The program needed to be run as an administrator and what you've done will work just fine.
  18. Disc information box? Something along those lines!
  19. Visit the website, download the pfctoc zip, extract it to the ImgBurn program files folder and try again.
  20. They lied. They'll probably be east and west discs. Just burn them to SL discs.
  21. Masters of business administration? Assuming you're talking about the way I've worded various prompts and not the status bar messages that Cynthia has covered in her reply, I'm sorry to hear you don't like them. I can only suggest you don't make as many mistakes whereby the program feels the need to prompt in the first place.
  22. Do you have the ability to verify the disc in another drive... just to triple check things?! Unfortunately, Sony Optiarc have stopped making drives.
  23. Do you have an efisys.bin on the usb stick? That's probably the boot file if you're using a pure EFI booting recovery stick/image. I assume the only option for creating the recovery media was to use a USB stick? It would obviously be easier if it allowed for creating a DVD version.
  24. Usually, when a drive is returning empty sectors, it'll do so in ECC sized chunks. So I'd expect the number of miscompares to be a multiple of 16 - unless of course the image file also has empty sectors in it for some of those sectors within said ECC blocks. Take that failed disc and verify it again. Double check that you have the same issue at the exact same sectors. Can I ask you to please right click the drive selection box and pick the 'Family Tree' option. Close the box that pops up and then copy + paste everything from the log window into your next reply.
  25. Yup, coincidence. AWS is the feature whereby you configure different speeds for different discs based on disc type and MID. The value shown in brackets is the speed at which the program will be using based on how you've configured the AWS feature (or in your case, not configured it). So both times, you've burnt at 'MAX' speed.
×
×
  • Create New...

Important Information

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