LIGHTNING UK!

That may well be something I haven't considered. The event that gets called when the field is changed manually probably isn't firing and thus the values / bar aren't being updated. I'll check it and fix it. Thanks

I added each one individually.

The CCD references the IMG file and you only have to select the CCD, ImgBurn does the rest automatically. ImgBurn doesn't make use of the SUB file though, you'll need to burn the CCD with CloneCD (which is what made the image in the first place) if you need accurate subchannel info (and you may well do).

Just click ignore twice as you appear to have been doing anyway. Tracks recorded in TAO mode often have 2 unreadable sectors at the end of them.... I'm not sure why the software isn't dealing with that automatically, I'm pretty sure it does normally! Have you tried reading the disc in your other drive?

It isn't a stopwatch you can just 'pause', it simply compares the start time to the end time and the duration is whatever the difference is.

1. Please post a log where I can see the actual error. It's saved automatically when you close the program. Access it via the 'Help' menu. I can't help without the proper / full error details. 2. Where are the files stored that you're burning? Is it a slow / external drive? It's taking quite a while to read 500MiB from it. So that's 22 seconds to read 500MiB = 22MiB/s Then during the burn when you run into buffering issues... So that's 48 seconds to read 500MiB = 10MiB/s It's then taking over a minute for the seemingly excessive drive activity to subside. Either your source drive is busy with other stuff or it's just plain slow.

Update ImgBurn and try again.

It was actually added at the request of the 'Ask Jeeves' team, back when I first started to bundle their toolbar. Now it's just there because I've had no reason to remove it.

I wouldn't expect a drive to do that. Once you eject the tray, it should stay ejected.

I have nothing to do with the offer screens.

Try with decent Verbatim MKM-003-00 media.

If you haven't done so already, try another cable / port. Buy a new 10 pack of MKM-003-00 discs to try too.

An iHAS A, B, C, D or E will do the job. Use the media everyone tells you to use (MKM-003-00) with the correct drive settings and you should be fine.

It's probably just a case of changing the file extension. I don't know how you created your img files in the first place but I'd be surprised if they're any different to the normal mode 1 sector dump saved as an ISO.

I've tried that drive myself, it doesn't work. See for yourself in the 'Drives' section. http://forum.imgburn.com/index.php?act=findpost&pid=150084

Maybe these will help? https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=861&DwnldID=23061&keyword=%22chipset+device+software%22&lang=eng https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=23496&keyword=%22rapid%22&lang=eng

What speeds does your drive support that media at? Burn a disc at each speed and see which one works the best. If you have a drive that can perform disc quality tests on BD media, even better. You may find a post or 2 where someone has already burnt a disc with the same MID of your on that drive over at the MyCE forums.

Normally the players just query an online database and get the disc info.

That drive can't overburn DVD+R DL discs. The payload tool might appear to work, but that doesn't mean the actual burning bit will.

Do you have the same problem if you burn at the other supported write speeds? i.e. 4x, 6x and 8x. Can you try with different discs? If you can and they have the same problem, try cleaning the drive with a cleaning disc.

No, everything has swapped to the KiB / MiB / GiB naming scheme.

Does it play other DVDs ok? Once upon a time, windows media player couldn't play DVD video discs without some 3rd party software being installed.

Sorry, I don't know what you mean. If you read a disc to an image and then burn that image back to disc, you end up with a copy that'll behave exactly as the original disc did.

You'd have to install the latest Intel chipset INF driver and probably the Intel Rapid Storage Tech ones too. Checking Windows Update for newer drivers won't find the absolute latest ones.

The values haven't changed, it now just shows the units as KiB rather than KB... as KiB is technically more correct (I've always used 1024 rather than 1000).