LIGHTNING UK!

1. I don't know why that would be happening. The program should be saving the current state of the window and restoring it. 2. It doesn't work like that by default so you must have enabled the 'Stay on top' option. Look on page 2 of the 'Build' tab settings and uncheck the 'Disc Layout Editor Window - Stay on top' option. 3. As dbminter said, but I wouldn't recommend using it between OS's. Some options have different default values depending on the OS and general machine specs.

This isn't an ImgBurn issue, it's a system issue. Try Googling to find out why the 'cdrom' service might be failing to start.

You've got it on the Marvell controller... put it on the Intel one and I'm sure it'll be fine.

I meant the log of you burning and verifying that disc in your ihas drive.

What controller have you attached the drive to? Open the program and go into 'Write' mode, then right click the drive selection box and pick 'Family Tree' on the menu. Close the prompt and then copy + paste everything from the log window.

Windows XP is known for dropping drives back to PIO mode.

1. Post the actual log please - as per the pink box up the top. 2. Make sure you're using v2.5.8.0 and just use the settings it recommends. If it still doesn't work, clear the OPC history within the drive and try again.

If your source image does the same, it's nothing to do with burning and therefore nothing to do with ImgBurn. Either you're imagining the pause, it's caused by the player or it's something in the video stream.

DMA issues probably. Try resetting DMA via the feature in the Tools menu. If that doesn't work, follow the entry in the FAQ.

The ADIP info never changes, look at the 'Last Recorded' one.

That drive can't produce a working overburnt disc.

It doesn't look like you're even getting the full window when using 150%... so it's not due to the 'custom' size, it's just that the window can't fit on the screen and so you're losing the bottom of it. I may be able to tweak what happens in such situations for the next version but there's nothing you can do for the current release.

No, I buy Intel stuff. The last AMD CPU board I had was back in the 'DFI LanParty nF4' days. It doesn't work at a level where the other hardware in your PC comes into it. It goes through the Windows API.

What OS is that? What have you done to 'Themes', font sizes, screen DPI settings etc to make it different from how it looks by default? Can you get a screenshot of the entire screen rather than just a cropped window please?

This is the error at the start... Of all the things you've mentioned (drive, media, software), hopefully you understand that the software (ImgBurn) is the one thing that doesn't change. It doesn't wear out with age / usage or get dusty / dirty to the point where its performance is compromised. It'll send exactly the same commands to the drive on its 1,000,000th usage that it did on its 1st.

Try the other supported write speeds. Maybe 2x isn't up to the job. The error at the start of the burn shouldn't be ignored. There are newer versions of ImgBurn available too.

Your drive reported a 'write error' first so it's related to your drive/firmware/media combo. If 'max' speed (4x) isn't working well for those discs, try 2x or buy some with a different MID and hope it does a better job on those.

The drive reports the error values, the programs just display them. As such, they should all show you the same thing. As for acceptable error levels, you can probably find that info by searching google. I'm sure the MyCE forums will have something about it on them.

Opencandy isn't something that installs. It potentially merges an 'offer' screen or two into the regular program installation. If you don't want what it offers, just opt out of installing them.

This is just due to Microsoft's implementation of the 'Mount' context menu entry... it's rubbish. As soon as anything else is added as an option is just seems to disappear. I'm pretty sure that the first time I came across this problem, the 'Mount' option was still on the 'Open With' sub menu.

http://forum.imgburn.com/index.php?showtopic=12200

If it's only just started happening, maybe you're using a dodgy cable / port? Have any driver updates gone on recently?

Have you tried with a speed other than 2x? That might not be a good one for your drive/firmware/media combo... faster speeds might actually produce better quality (and less prone to a complete failure) discs. As for the buffer thing, well that's down to your machine. It took 8 seconds to fill the program's 512MiB buffer so that seems fine but it then took over a minute for activity on your hdd to settle down. Is the machine busy with other stuff? Maybe something like a defrag was kicking in or something.

No BD drive I've ever used has enabled defect management by default on a new BD-R disc. I've never seen a command to disable it, it's enabled automatically when a disc formatted with spare areas enabled is inserted - and like I said before, the bd-r discs should have those disabled by default, you need to issue a format command to enable them. There's no format command to disable them.