LIGHTNING UK!

There's a bug in the speed calculation when burning CDs in 2.5.8.0. It's just a cosmetic issue and will result in the speed reading a little low. There should be no such problem for any other type of media though. Drives can sometimes limit their speed and not spin up to the next level if they determine the write quality will suffer. Beyond that, I have no idea why it would be happening. ImgBurn always sends data to the drive as quickly as possible. The drive itself controls the speed.

If it burns and verifies ok, the rest is just a case of making the OS see that the disc's contents have changed.

You're probably including another cue file or playlist file in your selection and it's pulling in all the files just by you having selected that.

It could be copy protection or it could just be a faulty/dirty/scratched disc.

Post the log as the pink box up the top please.

Did you actually try clicking on the 'custom' install option for the products offered to you by the OpenCandy platform? I understand that's what you need to do in order to opt out of them being installed. As for removing it after the fact, doesn't it show up in 'Programs and Features' in Control Panel?

Nothing is bundled, you're offered something from a large pool of other programs are are free to decline said offers if you don't want them.

No idea, I've never seen it. What's in the box if you drop it down?

Yes, untick 'perform opc before write' in the settings. That's normal.

Turn OPC back off and re-enable burnproof. The results you're getting in kprobe aren't normal for a correctly functioning drive with decent discs. Normally you'd get a bad spike at the layerbreak if the FHT/OHT etc settings aren't quite right but yours is just all out rubbish from quite a way before that. Did you let the program adjust the drive settings or did you do it yourself manually? If you did it manually, make sure you clear OPC history on the drive before trying again. I'd get another fresh batch of discs if I were you. If they produce the same results, try another drive.

Good, so it's just AMD's crappy drivers then.

Have you actually let the program make the necessary changes? Once you have, post your full burn+verify log and a screenshot of the kprobe scan.

Oh hang on, I know what's going on here... In XP, the program has a 'hidden' window as the actual main/parent window rather than the main 'ImgBurn' window (as you see it). In Vista+, the main 'ImgBurn' window (as you see it) is the main/parent window (this is a requirement for the fancy new taskbar added in the later OS's). All 'child' windows seem to stay on top of the main/parent window in the z-order. That's why in Windows 7 you can't get the DLE window to drop below the main 'ImgBurn' window in the z-order. So click the big 'Show Disc Layout Editor' button on the main 'ImgBurn' window to open the DLE window, create your disc structure and then just close the DLE window again via the red X in the top right corner and go about your business in the main 'ImgBurn' window. Sorry, I was thinking more about 'modal' windows (where you physically can't click on anything other than the foreground one) rather than a z-order issue (which I guess I'm used to now). There's actually a 'quality control' post about it for my development environment (other people didn't like the z-order issue either) but CodeGear marked it down as 'by design' and did nothing to work around / fix it. http://qc.embarcadero.com/wc/qcmain.aspx?d=45606

Log out, clear the board cookies, clear your browser cookies / temp files and try logging in again?

Maybe, give it a try. You don't need to 'clean' the registry, the uninstaller wipes out the registry keys that ImgBurn reads its settings from.

I don't understand what you're having a problem with. I'm running Windows 7 and don't have either of the problems you mentioned in your first post.

Right click the drive selection box and pick 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the log window please. At the moment it looks like a controller / driver issue.

I have no plans to release another version any time soon and even then I'm not sure I'd make the changes required for your specific problem. It will have always worked the way it does now. I've only checked back to v2.4.0.0 though.

Use some 'write once' discs if your drive can't reliably burn to 'rewritable' ones. If it fails to burn those too, get yourself a new drive.

Glad you got it sorted and thanks for the beer money

Yes, you can open and close the DLE window as much as you want. What's displayed in it will be what gets burnt to the disc - it doesn't need to be open for that to be the case.

Optimisation of duplicate files will remain disabled (by force) for the entire VIDEO_TS folder - sorry. Use an authoring program to get rid of the duplicate 2nd view if you don't want/need it.

Well the first thing to check / change would be the SATA port you've connected it to and the cable you used. Make sure it's plugged into the Intel (assuming it's an Intel board) chipset SATA port and not any 3rd party (Marvell, JMicron etc) chipset SATA port.

The MDS file has no baring on the size of the ISO file... quite the opposite in fact. You'll get an MDS when the ISO is a certain size (well, within a range of certain sizes). DVD+RW are always reported to be a fixed size (the size of the entire disc), no matter how much has been recorded onto them. That's why they'll be coming out to 4.37GB each time. Your recorder must also be making the file system look like it's taking up the entire disc as ImgBurn uses that info when creating an ISO from one. So in short, no, there's nothing you can do to make the ISOs come out smaller. The best you could hope for is to use Build mode to build a new ISO (not Read mode) and point the 'Source' to the drive with your DVD+RW in it.

Generally speaking, they have higher error levels than write once media and would be harder for a drive to read back. If they work for you, use them. It's your call at the end of the day.