LIGHTNING UK!

Post the log of the burn+verify operation. ImgBurn tries to cycle the drive tray between the burn operation and verify one. If you have a slimline drive, you will have to push the tray back in manually. ImgBurn should then continue to verify the disc. If the drive fails to initialise the disc properly (common when using bad media or the drive is faulty), the program will cycle the tray again. It does this 3 times before giving up.

I've noticed mine spin up a fair bit too. I think it's just something they do when something asks the drive for certain info. Don't leave a disc in it

This is an xbox issue really, not an ImgBurn one. Read some sites that specialise in the latest xbox related info.

It's something the drive does, not the program... well, not for DVD-RW media anyway. Not many people burn

The WDTV boxes don't support BD Video images properly, only DVD Video ones. It's probably just picking out the largest stream/playlist/whatever and playing it. Whilst that might work for some discs, it won't work for others. You'd be better off converting to a single MKV and playing that.

It's impossible to say if it's the drive or the discs until you actually try some others. It's got to be one of the two though. Do you know anyone with the same drive (and firmware) that wouldn't mind testing your discs? Failing that, even if you can't find Singapore Verbatims, just try whatever you *can* find. (Only buy a small amount, not 50!)

It's some combination of your drive/firmware/media. Changing any one of the three could potentially fix the issue. You might have more luck with some decent Verbatim / Taiyo Yuden discs - and I'd actually recommend you start using those even if you do get a new / better drive.

Of course. If it wasn't 'normal', it certainly wouldn't be telling you that it was doing it (and obviously it is/does)! Like I said before, cycling the tray so the drive is forced to reinitialise the disc is part of the verification process.

That's caused by a bug in your drive's firmware. It should not be returning that error code. In any case, just click ignore/continue. That's all your own fault because you're forcing the layer break position to something (and it just happens to be invalid for this burn). It should always be set to 'Calculate Optimal'. The correct LB is read from the .DVD file. These are low quality discs. http://forum.imgburn.com/index.php?showtopic=8000

You're using an old version of ImgBurn there. It won't fix the problem you're having (because it's nothing to do with it), but it'll fix a lot of others. Verify your burns to ensure everything is as it should be and readable. If the mounted ISO works, there's no reason a fully readable burnt DVD+R DL wouldn't. Look for player updates (software updates and firmware for your standalone). Look for updates to the adobe software too.

Don't cancel it, the drive will be burning 1GB of *something* (I don't know what exactly) to the disc regardless of how much/little you think you're burning. It'll eventually finish and your disc will be fine.

Were you creating ISO files by reading a disc or building ISO files from random files/folders on your hdd? You can right click the destination 'browse' button in both modes (Read and Build) and get a list of recent files. Failing that, look in the Help menu and you'll see an option to look at the log file. Inside the log file you should be able to locate the session where you did one of those two things and then find what you set as the destination folder for the ISO image.

Try burning at 8x if 4x isn't working for you (2.4x doesn't exist as an option for your drive/firmware/media combo). If that still doesn't work, buy some better discs.

I have no idea what you mean when you say that. Cycling the tray does nothing to the disc itself. It ejects *after* the burn has totally finished and before the verify starts. It's the only way to really test things properly. If you don't eject and reinsert the disc, the drive never has to reinitialise it - and that's often a point of failure.

If the extension is ISO, it's an ISO file and you burn it as such. (i.e. you burn it normally!) The fact it has an icon you'd usually see being used for RAR files just means WinRAR has been associated with ISO files. You can turn that off in its settings.

You should pay attention to what ImgBurn tells you. It will have warned you right from the start that it wouldn't fit on the disc.

If the one you're about to burn (and yes, it'll be useless) is ok, you can at least use them for 'normal' size burns. By the sounds of it you've already tried various settings in an attempt to make them burn properly. There's only so much changing the settings can actually do. If the media is bad, you're probably going to be out of luck.

No, the discs should be perfectly clean. It just looks like yours have a bad outer edge - but possibly only effecting the area you're trying to overburn into. Burn one in discovery mode with a custom number of sectors. Set it to 4,173,824. Then scan that one and see how it turns out.

The risk is that the software hasn't been fully tested with it. Obviously you want to stick with it on Incremental so just do that. If you run into problems with other things, you'll know to switch back.

With those same settings, if you get the same bad bit around the LB after clearing OPC history (and power cycling the drive), get another spindle of discs. Get them in 25's rather than 50's... then you don't have to write so many off if the spindle is bad! I assume the 50's were from Singapore too?

I never do any real testing with non-default settings. The defaults are what I use day in, day out - and have done so for about 5 years. Do you really burn enough undersized images to DVD-RW disc to make it worth the risk? Are you really sat there tapping your fingers for the extra 2 minutes that DAO/SAO could take? It's totally your call, I'm just saying I wouldn't do it.

I'm pretty sure LabelTag doesn't work on double layer discs.

Try using multiAVCHD instead.

You're trying to overburn in build mode and that hits a known issue in 2.5.6.0. Just check the size of your compilation BEFORE trying to burn it to disc.

Turn off OHT. Does it still do the same thing? I saw better results from my drive by turning Overspeed on and setting the speed to 4x. Can you also please post the family tree info. Just right click the drive selection box and you should see the option on the context menu. Close the prompt and copy + paste from the log window.