LIGHTNING UK!

Sorry, it's not something I've ever had to deal with or look into. If it's doable at all, you'd need to be using the RAW write type... and ImgBurn only supports Incremental, TAO and SAO. Maybe you could do it in CloneCD by messing with the CCD file?

Same difference there I'm afraid. The error from your drive (if there even was a real one in the first place) seems to be getting lost and you're getting a Windows error rather than a drive error. Try burning in safemode and see if you have the same problem.

Was that your first failure? Maybe it was a fluke, try again. If not... http://forum.imgburn.com/index.php?showtopic=8000 You can read about your options in that thread.

Install the rapid storage tech drivers from here - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3409&DwnldID=20768&keyword=%22rapid%22&lang=eng You want the 'STOR_allOS_10.8.0.1003.exe' file.

Ok so I seem to have received a bug report email from you since my previous reply. It was missing the actual attachment but the text in the email was enough to go on. That's the exact message I'd expect to see if you were doing what I mentioned in my first reply... burning too much to a disc. Instead of clicking the 'Write' button, hit the 'Calculate' one and see what the size comes out to.

It still looks like you have a driver issue there. What controller is the drive attached to? Right click the drive selection drop down box and pick 'Family Tree'. Close the prompt and then copy + paste the lines that were added to the log window so we can take a look.

Are you just playing it in windows media player? Try using some real playback software such as PowerDVD. A free alternative would be something like 'Media Player Classic - Home Cinema'.

Your drive reported a 'Write Error' at the start of the burn. You may have more luck with your particular drive/firmware/media combo if you slow the write speed down to 8x rather than burning at 'Max'. Failing that, try cleaning the drive with a cleaning disc. If that still doesn't work, you're probably best off buying a new drive. It shouldn't be having problems burning to Verbatim discs.

I updated my post with the info from Microsoft. You must have read it before I had

If you ever installed it and ticked the option, it'll stay enabled. It's not an ImgBurn thing so uninstalling doesn't change it. You'd have to dig into the registry or group policy stuff to turn it off again. http://support.microsoft.com/kb/330135 Method 3 is the one you need to look at.

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

You're going to have to post a log then so we can see what's what. Did you actually send the bug report when it prompted you to? I can't fix them if I never receive them... obviously

http://forum.imgburn.com/index.php?showtopic=8000 btw, I've combined your threads - you didn't need to make a new one, you just needed to reply to the old one!

Were you trying to burn files to a disc in Build mode and those files were too big for the disc? It's a known problem and was fixed ages ago ready for the next public release. Burn the correct amount of data for the disc you're using and you won't have a problem.

1. ISO files should all be the same. They're meant to be very basic - single session, single track, just user data (not 'raw'). 2. They're normally created when reading a double layer disc (but a bug in the code means they're created all the time). They contain info about the layer break position. If you have no intention of burning the image to another disc and have a single large ISO file (so file splitting isn't being used), you don't need them and they can be deleted. ImgBurn understands MDS (v1) and DVD (they're just plain text) files, but you have the option of which (if any) it creates alongside the ISO depending on which other tools you use. The MDS is meant for mounting the image in DAEMON Tools. The DVD is meant for mounting the image in Virtual CloneDrive.

Ok well I guess you can try an image that isn't a multiple of 16 sectors and see if your drive also pads DVD-R to that level. If it doesn't then you're ok. If it does then you're stuck! You'd have to record the original ISO length in a document and manually trim it after reading the disc back to a new ISO.

It doesn't matter which file systems are present when you're using Windows for playback/browsing, it supports all 3 of the ones ImgBurn can create. The only time it becomes something to think about is when you want to put the disc in a standalone player - where you then need to read the manual to see what it supports. Windows will pick the best supported file system available on the disc. If you have a disc with UDF + Joliet + ISO9660, that'll be UDF. The other file systems are just ignored (but do no harm by being there). Some standalone players will only attempt to read DVD/BD video structures from a UDF file system, after that they fall back to Joliet for regular data discs (Again, check the user manual). If you don't have Joliet on the disc then it'll read ISO9660 and that's rubbish! UDF is required for the DVD / BD Video discs - or at least that's what all commericial discs use. For data discs you can use whatever meets your requirements. If Windows isn't popping up the autoplay box, it's probably because it hasn't detected that the media changed (been written to). Just reboot and try it again.

Press F2 and type it in? Media Player will be trying to look up its info in the online database... and of course it's not going to exist if it's homemade.

Everything up until the end of the original ISO will be exactly the same... so you haven't really 'lost' anything. When burning to DVD+ format discs the drive just pads the end (with zeros) so it's a multiple of 16 sectors (1 ECC block). So at most it will have added 15 sectors worth of zeros (15 * 2048 bytes). Even if you went back to the original ISO, it would still end up the same the next time you burnt it (to a DVD+ disc). I don't know what kind of ISO it is that you're burning (what it contains), but is it really a deal breaker if it's larger? When ImgBurn 'builds' ISO files it always makes their size a multiple of 16 sectors for this very reason.

The button is right there in the 'Source' box. It's located in the bottom right corner and has got a picture of a disc+question mark on it. Don't rule out SP1 because it failed once on what was probably a bad install to start with. It's used by millions of people around the world... if there was a major problem with it, you'd know about it and it would have been pulled/fixed already. Just take an image of your hdd onto an external drive if you're worried. Then in the unlikely event of it messing up again, you can just restore the old image. All you'd have wasted was 30 mins or so of your time.

Regardless of the 'burn proof' setting, it's always on. If it wasn't, you wouldn't be able to pause the burn and start it up again (and you can). That's just how the LiteOn drives work (and possibly burning DVD+ format discs in general). OPC made no difference in my tests. I did quite a few if you look at the iHAS124 thread in the drives section. All the other program settings people mention (buffer size on 71 - 73 etc) are rubbish. I've read and laughed (to myself anyway) at most, if not all of them.

Did you just make that CUE file up? It certainly isn't one ImgBurn created so why does it have all of those 'REM FILE-DECODED-SIZE' entries in it? Click the 'View Image Information' button on the main window (once you've loaded the CUE), you might spot something in there (times going backwards or something). Track 14's title needs fixing btw. Service Pack 1 is out for Windows 7 btw.

It's the top link in Google when I search for 'Windows 7 Service Pack 1'. http://windows.microsoft.com/installwindows7sp1

So you can add more data to the disc I guess. ImgBurn doesn't do multisession (unless you're burning a CD BIN/CUE image) so it's pointless for me to do that.

Did you burn it to a DVD+ format disc? If the image size wasn't already a multiple of 16 sectors, it will be now - and that's where the MD5 / SHA-1 will go wrong.