LIGHTNING UK!

That's more down to their driver than ImgBurn. It must be reporting itself as a CDROM drive but then isn't processing the commands properly. If you want one that works properly, try Virtual CloneDrive. http://www.slysoft.com/en/virtual-clonedrive.html

Is it a disc image file? If not, burn it in 'Build' mode, that accepts any type of file. So basically, you were probably just 'doing it wrong'.

Yes, you need to buy the decent Verbatim MKM-003-00 8x discs.

Your drive is probably 10 years old... you'll need 'old' discs that its firmware supports. Better still, buy a new drive.

Not 'silently', it's mentioned in the Log window. I will consider adding an optional prompt.

You did a quick erase there, you need to do a full one. Have you tried another disc? It's nothing you're doing wrong, your drive just isn't working properly with that media.

Your drive is reporting a 'write error' as it attempts to burn the media. The first thing I suggest doing is using the correct Verbatim discs. It doesn't matter if you think those TDK (CMC MID) discs are/were ok, obviously they aren't now I haven't tried that drive with oversized images, but I've yet to see any that work properly if they don't support the hypertuning stuff that the liteon drives do. Burnermax enabling ok and a seemingly successful write operation doesn't mean the disc is 100% readable and will actually work.

Ah I have heard of shorten, I just wasn't aware of its file extension. ImgBurn will support anything that has a directshow filter as that's what it uses for the conversion process - it's all automatic.

I can't explain that, so I'd go for memory corruption. Run memtest for a few passes, just to check it's ok.

There isn't a way, you'd need to pass the correctly formatted volume label to the program. You can't start it minimized either.

It looks like your drive is producing an unreadable disc. Try updating the firmware on the drive. http://www.firmwarehq.com/Samsung/SH-S202N/files.html Try burning the disc at all of the 'Supported' write speeds. 1x isn't one of them so it's using 4x instead. As such, try 6x, 8x and 10x. If the drive still fails to produce a working disc, try cleaning it with a cleaning disc or replace it for one that works properly.

Your drive is getting on a bit now and probably can't handle the 'MID' of the discs you're using. Try and get some 2.4x speed Verbatim discs ('MKM-001-00' MID) or invest in a new drive if you'd like to have more chance of burning the ones you've purchased ('CMC MAG-D03-64'). btw, the image you're burning there would easily fit on a single layer disc, you didn't need to buy double layer ones.

I've never come across SHN files, what are they and what creates them?

No, the drive settings (or eeprom settings) are the hypertuning stuff... they're nothing to do with ImgBurn (but it can manipulate them). You have the latest firmware on your drive, but maybe it's just no good at burning 'VERBAT-IM1-000' - or you have a duff disc.

It's something to do with your drive/media/firmware combo. Reset the drive settings back to default and try again. Only the 'SmartBurn' option should be on. Enable Burn-proof again too. If it still fails, do a full erase on the disc, try burning again and post a new log please.

Sorry, I was wrong earlier... The thing you're talking about is a debugging feature. It tells you (or rather the developer) which OS the disc was made on. ImgBurn actually leaves the fields blank (zeroed) which should translate to 'undefined' and not DOS/Windows 3.1 as IsoBuster is displaying. Look up 'IdentifierSuffix' and 'OS Class' / 'OS Identifier' in the UDF specs. There's no benefit to setting it to Windows 95, it has nothing to do with compatibility etc.

No because that's not 'Burning' and an SD card isn't an Optical disc - which is all ImgBurn works with.

That's the earliest OS it works with... and DOS / Win 3.x predates Windows 95, so Windows 95 is already supported. So if you want to use UDF 1.50, just select it in the list and build your image.

Yes, try some Verbatim or Taiyo Yuden (JVC) discs.

If you believe something OpenCandy is offering you is malicious, you can contact them about it. The ImgBurn installer just uses their ad serving plugin. There's nothing bundled with it or distributed by it.

I don't know why making that component 'read only' also stops it from being used as a drag source, I guess the code could be modified so that doesn't happen (it's open source), but there must be a reason why it behaves the way it does.

It burns exactly what you give it. If you have an ISO of a 3D video and burn it to disc, you'll end up with a 3D disc. It can't 'Build' the file system for a 3D disc from files/folders though.

Your drive doesn't appear to like the discs you're trying to use. Return the settings to their default values and buy some different discs.

It's not my component so I'm afraid I can't do that.

It has to be a cold boot I think... I've haven't had the issue myself, so don't quote me on that!