Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by LIGHTNING UK!

  1. 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.
  2. 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.
  3. 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.
  4. If you read a disc to an ISO using Read mode and then simply write the ISO to a new disc using Write mode, everything is preserved. The size of the ISO will match the number of used sectors on the disc (multiplied by the sector size). The size of the source disc is mentioned in the log window when the Read operation starts. It's also in the info box on the right of the main window when in Read mode.
  5. Try enabling the ‘perform opc before write’ option in the settings. Once you’ve done that, burn at each of the supported write speeds again.
  6. I'm sure you could work around the issue by using the right sequence of quotes (double / escaped quotes etc). The processor needs to deal with call to ImgBurn.exe and the arguments you're passing to it as a whole, not try and interpret the arguments you're passing to ImgBurn.exe itself. It needs to see the entire command as a single string - unless you're using a function that specifically wants an arguments parameter, whereby it's then 2 strings - 1 to call ImgBurn and another to for the parameters you're passing to ImgBurn. Does passing /s to cmd make a difference? i.e. cmd /c /s "C:\Users\user\Desktop\ImgBurn.exe" /MODE BUILD /SRC "C:\Users\user\Desktop\NI_33750_ZIP\DVD1\Relatorio\|C:\Users\user\Desktop\NI_33750_ZIP\DVD1\Relatorio\hashes.txt" /DEST "C:\Users\user\Desktop\NI_33750_ZIP\DVD1\imagemteste.iso" /FILESYSTEM "UDF" /UDFREVISION "2.60" /VOLUMELABEL_UDF "DVD1_teste_img_burn" /OVERWRITE YES /RECURSESUBDIRECTORIES YES /NOSAVELOG /NOSAVESETTINGS /START /NOIMAGEDETAILS /CLOSE
  7. Try running it directly from the command prompt rather than powershell. It may be messing with the pipe.
  8. It won't detect it as a BD Video disc unless the folder you're adding has a BDMV folder in it (directly in it, not a sub folder of it). So just double check what's in your source folder.
  9. Any command that gets stuck being processed is down to something else going on with your machine. It could be a driver of some sort in the I/O chain that's not behaving as it should do. Commands should either work or fail... not get stuck. Indeed, the AWS stuff you've configured won't be having anything to do with it behaving itself a little better now, it'll be because you've changed to drive letter. That's not to say I recommend using drive letter - 'drive letter' enumeration doesn't support a few features that the others do. (The default options are usually the best)
  10. If you're worried about anything, stick to building the ISO first, do your checks on it and then use Write mode to burn it to the disc. The only file system you need to include when using Build mode is UDF. Enable the option to include system / hidden files. What gets logged as being excluded?
  11. That dates back to the days of CDs. It’s nothing to do with any movie on the disc.
  12. Disconnect the drive Load the program and enable I/o debug mode Connect the drive. Post the log (in so far as it gets). Thanks
  13. It was probably just opening up off the screen - perhaps due to a multimonitor setup/resolution change or something? It remembers its last location - in terms of X,Y on your screen/desktop. Removing the value you claim didn't work will reset the position of the window. It'll only do that if ImgBurn isn't already open because the settings are loaded when the program is first opened and then saved when it's closed. Removing the value you mentioned (or setting to 1, which is the default anyway) only shows the top 'Explorer' part of the DLE window (so the bottom part doesn't then take up the entire thing). It has nothing to do with the actual DLE window being visible or its location.
  14. What sort of bootable image do you have? What is the purpose of the image, where did you get it from etc. You can extract the bootable image from a drive/disc using ImgBurn, but not from within an image. You could mount the image in a virtual drive program (or Explorer) and extract via that though. We'd need to know more about the image and its contents before being able to offer any real help.
  15. I don't understand the purpose of this topic? The disc layout editor window is only shown when you're in Build, with 'Advanced' input mode selected and you actually click on the 'Show Disc Layout Editor' window button. The setting you've commented on is to do with the Explorer style section of that window, and it's toggled on/off via the left most button on the DLE window's toolbar.
  16. Was the burn log free from warnings / errors? Assuming it was, I'd probably start by running memtest or similar on your machine, just to rule that out.
  17. The value reported in the disc info panel on the right comes from the drive / disc. It is accurate.
  18. If you're trying to burn a DVD, I'm afraid you won't be able to with that drive. It can read DVDs burn it can't burn them. It can only burn CDs.
  19. The day will come and words/hats will be eaten. I messed around with the code basically as soon as I read the 'bug' report, but it then became 12:30AM and I had to call it night. I'm not currently in a position to be able to test anything (I need such an image for a start), but once I have, the change will make it onto the changelog ready for the next release.
  20. Are you using some sort of autoloader for doing all those discs? If not, just close the program occasionally and take a copy of the log file (give it a unique name each time). There's nothing you can do to change the log cut off point as it's all hardcoded.
  • Create New...

Important Information

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