Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,457
  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. That’s the /noimagedetails command if I remember correctly. Take a look in the readme txt file.
  2. That’s not bytes, it’s sectors - and that’s all the disc has on it. The issue would be with burnplot, it was made before TL discs existed.
  3. So the IMG was 0 bytes in size? That goes along with what's displayed in your screenshot. I don't suppose it'll work unless you have a file that's the size of what's to actually be burnt.
  4. It could just be a CCD that it doesn't like very much. CCD is CloneCD's native file format. My implementation is just a 'best guess' at it. What does the accompanying IMG file look like? Size in bytes etc. Feel free to upload the CCD so I can take a look at it.
  5. You may need RAW mode writing for that... which ImgBurn doesn't support. The image is / was meant for Padus DiscJuggler, but they've shut down, so you probably can't get it now - not legitimately anyway.
  6. ImgBurn won't be shifting anything, so the issue lies elsewhere. Stick to using the special software.
  7. How are you even telling it to start the verify process? I don’t recall giving the user an option to speed things up. It cycles the tray and then proceeds once the drive thinks it’s ready again. If you have to push the tray in manually, it would just wait longer.
  8. I'm pretty sure it's just based on the name of the disc. You might be able to force a name and the program will then try to make it unique (add a '(1)', '(2)' etc to it), but don't quote me on that! There's definitely no support for grabbing names from a CSV or whatever.
  9. The first error is the one you need to focus on. So, your drive is reporting a 'Write Error'. Which other drives have you tested?
  10. If the inserted media doesn't appear to be rewritable (or cannot be determined), you're given the option to override. So the user probably just selected DVD+RW. I've never seen rewritable DVD+R DL media... have you?
  11. You'll have to use a new blank one, you've wasted that one I'm afraid. Your discs are 'Write Once, Read Many' (WORM) discs and cannot be erased / overwritten.
  12. There is no absolute end of life like that. It works until it doesn’t. At that point, you’ll get write errors or it won’t be readable (verify will fail).
  13. Did you use Read mode to make the image of the disc? It should have created a CUE file to go with that BIN file, you shouldn’t be doing it manually. To actually use the BIN/CUE, you then need to mount the CUE in a virtual drive program.
  14. There's nothing obviously wrong with what you've done. As 'invalid parameter' is often to do with memory alignment, I'd guess you just need to tweak things a little so everything is happy. I have a 'DWORD filler' between your 's' and 'sense' to realign on dword boundaries - going by the comment next to it anyway
  15. The plus/robot drives just basically have burnermax built in. As you know, the XGD3 images are too big to burn to a DVD+R DL under normal circumstances. Burnermax allowed for a bit of overburning on specific drives and these vinpower ones support overburning by default and that’s all that matters (not the burnermax bit) You will not get good results trying to overburn anything other than the verbatim discs. Alternative manufacturers weren’t even that reliable for regular sized images, let alone oversized ones.
  16. Yes, the optiarc, piodata and plextor ‘plus’ / ‘robot’ models all support dvd+r dl over burning out of the box.
  17. You can still buy brand new drives from vinpower that’ll do the job. No need for a B drive, most versions after B worked just fine.
  18. Modifying the image using your hex editor is the quickest way right now, but ultimately you want ImgBurn to be able to insert the padding by itself.
  19. Yes, you could modify the image to insert 358272 empty sectors at sector 1913760.
  20. You can’t compare different images in different programs. It must be the same image in different programs. Please can you do the verify bit I mentioned? Put an mRDL burnt disc in the drive, load ImgBurn and go into Verify mode. Select the image you burnt it from and then click the start button. Once it has finished, copy and paste everything from the log window please.
  21. Thanks for all of the posts but you don’t appear to have done anything I asked you to do. Can you re-read my post please and provide the required info. If you’re unsure on how to do anything I’ve asked, please ask for more help.
  22. I don't recall even having heard of mRDL before... but it's old and very niche, so I've probably forgotten about it anyway! Please put one of the discs you've burnt with it into your drive and go into ImgBurn's Read mode. Copy and paste everything from the box on the right of the main window for me please. Can you also then use Verify mode to compare the disc against the image file and post the log file please? I'd like to see if they're changing anything being written to the disc.
  23. Have you actually tried just burning one and seeing what happens? If the firmware in the xbox drive supports it, maybe it'll just work.
×
×
  • Create New...

Important Information

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