LIGHTNING UK!

Post the log of that burn please.

It burnt and verified ok, so I can't see there being a problem with it really. Maybe the OS just hasn't noticed the contents of the disc have changed. Eject it, reboot and insert it again.

Does the disc verify ok after the burn or have you disabled that step? It would be nice to see the log.

I'd say it's just having trouble reading the disc.

All you need to do and should be doing is feeding the video_ts folder into ImgBurn's Build mode. If you're burning direct to disc and click the calculate button, it should prompt you to select a layer break position - assuming your video_ts folder is large enough to spam both layers of the disc. If you run into a problem when doing that, post the log so we can see what's happening.

It finds the opencandy plugin used by the installer. You can read about opencandy on their website. It's an advertising plugin for installation programs. If you don't want what it offers you, opt out of installing said 3rd party apps.

That's something external to ImgBurn then.

Right click the drive selection drop down box and click 'family tree'. Close the prompt that comes up and then copy and paste everything from the log window please.

Read the pinned topic about burning double layer discs.

That doesn't look blank to me and that's why it won't look blank to the program.

You're probably looking at the disc usage bar. This is not a progress bar.

Your drive can't do it I'm afraid. You'll need a different one.

The field within that descriptor probably doesn't distinguish between the two.

Just copy your ImgBurn folder from home and put it on a read only share somewhere people can access or add those files to an msi package and roll it out via group policy. OpenCandy is not a wrapper, you can't do what db said above. That just gets you access to the ImgBurn files that end up in the ImgBurn program folder.

No, not a clue. The command takes a single value as to the size (in sectors) of the track to be reserved.

This isn't a bug, it's just your system / drive isn't processing the 'reserve track' command and is getting stuck. You'd have to talk to LG and see why that would be the case given the firmware version you're on and discs you're using. Perhaps they'll release an update that fixes the problem.

No, the I/O options are just for ImgBurn and are not system wide.

You should copy and paste the disc info from the box on the right when that happens so we can see what your drive is reporting.

Verifying just checks every sector is readable by the drive. If the drive reports an error, ImgBurn tells you about it. If it doesn't, it doesn't. So basically, your drive thinks it can read the disc just fine. I do not know what discspeed is doing in order to show orange sections in its map. CDDA discs are unlike any others in that the full 2352 bytes of the sector are used for CDDA data. Normally some is used for error correction and synchronisation etc, making it easier for a drive to know a problem exists when it's asked to return (read) data from a given sector. The verify function normally compares the data the drive returns during a verify (read) operation to what it knows it should be, but that can't happen on CDDA discs because drives write that type of data with an offset and so the data isn't exactly where it should be.

You just need to select the lines of text in the log window and copy and paste via the usual Edit menu or Ctrl+C, Ctrl+V.

Read my previous message. If you want to compare a file against another one, use a file comparison tool. You can use 'comp' via the command line or any number of hex editor tools.

Where are you expecting to see it? ImgBurn is for reading and burning optical discs in an optical drive. Don't expect to see a USB sick listed in the source or destination drop down boxes.

It doesn't look like the program made any attempt to change the booktype to dvdrom. That isn't default behaviour, so have you switched off the option to automatically set the booktype?

The % complete comes from the drive itself and aren't always accurate. Something in the log just doesn't add up, hence why I asked if there was more. It's highly unlikely you enabled I/o debug mode at the exact second the drive stops processing more i/o commands. (At 21:28:48) Anyway, I'm glad it's working for you one way or another now.

Was there nothing after that? Oh and 4 minutes isn't long enough to format a disc. Give it longer. It'll take at least as long as it would take to burn the full disc at the max speed your drive supports it at.