LIGHTNING UK!

Besides trying the drive in another pc/reinstalling Windows from scratch, nope.

ImgBurn doesn't support multisession at this time.

The very bottom of the website's main page should cover this. (Basically, it's fine!)

You're 1 bit in the byte out every time... it sure looks like a memory issue to me. Failing that, try a linux live cd with Wine installed and ImgBurn running under it.

This is why I said to try with a different type of disc - so you can rule out the crappy DVD+R DL being an issue.

Yeah but don't keep using the DVD+R DL's! I know I hate anything other than Verbatims but that doesn't mean I want you to keep wasting them

and for the speed thing, just look at the speeds your drive says it supports on that media... It's also shown in the disc info panel on the right as 'Supported Write Speeds'.

Looks like your drive just decided to reset itself midway... that's never a good thing! Update ImgBurn when you get a minute.

Oh for the love of God!!!! Look, ImgBurn CAN just write and verify without ejecting the disc in-between but it's better if it does eject it. Seriously, what do you not understand about that? Just because other software doesn't eject it in-between doesn't mean ImgBurn is wrong, I've just made it more thorough.

You can't mount CUE files in Virtual CloneDrive - and mounting the BIN won't work. ISO is not a format/name you should be using for an Audio CD image.

If there's an INI file (called ImgBurn.ini) in the same folder as ImgBurn.exe it'll load the settings from that automatically.

They're currently two separate things and that's not possible I'm afraid. (and it's too much work to change it for so little gain) If you add the files / folder in the correct way then the prompt for it being a DVD Video disc won't even appear. You can also turn off most of the prompts in the settings.

The Build mode interface is being worked on, don't worry.

For Audio, read the Guides. I can't do 64 bit because my development environment doesn't allow for it. Clearly it's not going to make a difference anyway, ImgBurn just isn't the type of application to benefit from it.

Ok so you've got an intel chipset based motherboard. Install the latest chipset INF drivers from here: http://downloadmirror.intel.com/16023/a08/infinst_autol.exe Once you've done that and rebooted, try following the DMA post in the FAQ and uninstall your controllers from the IDE ATA/ATAPI branch.

The errors don't exist, that's my point. During burning the drives often return 'logical unit not ready, long write in progress' when a 'Write' command is submitted. That one is an expected response and the program just issues the same command again after a short period of time. The NVIDIA drivers corrupt that error so it becomes something totally different - i.e. an 'unhandled / unexpected' error.

You should probably give up then. If a full erase and a normal write operation don't make it change, nothing will. It might work with brand spanking new 'unformatted' DVD+RW though.

DVD-ROM is the 'compatible' booktype, DVD+R is the standard disc format.

That means your drive doesn't support booktyping or the drivers are blocking the command.

Did we already have the conversation about write once media working better than rewritable stuff? If not, you can probably guess what it would be about. Burn onto some decent DVD+R or DVD-R from Verbatim / Taiyo Yuden. Burn at 8x or 12x. Update your firmware to YH14. http://h10025.www1.hp.com/ewfrf/wc/softwar...227&os=2093

That's just your average I/O error message. A lot of I/O commands date back to the days when SCSI ruled the world and to us programmers, that's just how we know them. 'Scsi Status' applies to all devices no matter how they're physically connected. It's the naming convention used within the API functions, nothing more. Now, back to the error message (or lack of since switching to use Nero's SPTI wrapper ASPI dll file)... The problem is that the program is built to handle certain errors automatically (ones that are expected) but because the nvidia drivers corrupt the error codes ImgBurn is then not able to do that and you're presented with the I/O error message box. Unexpected errors show up as 'Retries' in the log and once they've been exhausted the program pops up the I/O error box. Now that ImgBurn is once again getting the correct error codes from the drive, it can deal with the expected errors without ever needing to tell you there's a problem.

No, ImgBurn logs what it does all the time - it goes into the 'Log' window which should be kept open at all times really. (Click the 'View' menu -> 'Log'). That window keeps you informed about everything ImgBurn is doing and any problems it's come across. It's opened/visible by default on a clean install and should really stay that way

You normally get that error there when the drive doesn't like the media you're using or you're not using a *BRAND NEW* disc - i.e. maybe you tried to burn to it before and it failed or something. Also please note the following thread: http://forum.imgburn.com/index.php?showtopic=8000 Your drive is getting on a bit now too, you can't really expect it to handle newer media properly.

It's a LOT easier to find the problems you're talking about if you don't enable I/O debug mode!!! I assume this is the one you mean? Ignore it for now, it's because your drive doesn't handle setting the layer break in the same way other drives do - they don't say it's done until it's actually done but yours is saying it's done and then still saying it's in progress when I try and send the next command. I've just implemented a workaround for that so the next version of the program shouldn't bring up that message.

Where's the burn log?