LIGHTNING UK!

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?

lol there's obviously a language gap here so don't be too mean Currently, your ImgBurn is set to Burn the disc and then Verify it. i.e. it has a Write process followed by a Read process. Obviously the 'Write' process is the only one that's strictly needed for the disc to be playable, the 'Read' (Verify) process is just there to check the drive did a good job at burning the media you're using and that the disc is 100% readable (in that drive at least). Before ImgBurn starts the 'Read' (Verify) phase it ejects the disc so the drives ability to reinitialise it is put to the test... this is where your drive is failing. Once the drive has ejected the disc, it simply won't read it again - this is NOT normal! The exact same thing would happen if you disabled the Verify phase (whereby ImgBurn wouldn't cycle the tray and the Read (verify) phase would never take place), ejected the disc yourself and then tried to read it back a day later. (* unless the failure to reinitialise the disc is cause by the heat produced during burning). What you have to understand is that there's a whole verification type check missed out (can the drive reinitialise the disc?) when you just do... Write -> Verify. compared to... Write -> Cycle Tray -> Verify. If 'Cycle Tray' is missed out then the drive already knows all the info about the disc from its initial discovery (when it was blank) combined with what's been updated as a result of burning the disc. It's finding all that info out in one go (i.e. from scratch, on the burnt discs) that your drive has a problem with. I don't know how else to explain / dumb this down, sorry.

Nope, I would think you're out of luck there. You'll need the 2.4x MKM-001-00 dye Verbatims instead.

Really? That log entry suggests to me that something isn't right. I guess I'll have to dig out an old NEC drive and see exactly what's what.

The Nero ASPI driver is just an SPTI wrapper really but it limits/overrides my 24 byte sense area and calls the commands with an 18 byte one - hence the sense data isn't corrupted by the drivers and ImgBurn gets the proper error codes back from the drive where it is then able to handle them correctly. A lot of drivers emulate SCSI controllers, I wouldn't worry about it too much. I think it's just because they can provide additional functionality that way - RAID etc.

The problem is that the NVIDIA drivers corrupt the 'sense area' that contains the error code from the drive when a command fails if the program allocates more than 18 bytes for sense area data - ImgBurn allocates 24. Some commands are supposed to fail but the errors can only be dealt with if the error codes are correct. A way around this (for now) will be to put the wnaspi32 file from Nero's app dir into the ImgBurn one and change the I/O interface within ImgBurn to 'ASPI'. I can/have worked around the problem ready for the next release but really it would be better if NVIDIA just fix their drivers.

Test mode only works on DVD-R or DVD-RW media. Obviously rewritable discs would be your best bet here... do you have any DVD+RW, DVD-RW or DVD-RAM discs? Any luck with the device manager screenshot?

The nvidia drivers are rubbish, you won't be able to fix this unless you can find a set (or revert to a set) that actually works.

It can't 'cancel' because ImgBurn isn't in control. The 'DeviceIoControl' windows API function has been called and ImgBurn is stuck until it returns (success or failure, I don't care which!). 'AUTO' write speed doesn't mean anything if you've not configured the 'Automatic Write Speed' feature. Please take a look in the Guides forum for info on how to do that.

http://forum.imgburn.com/index.php?showtop...amp;hl=magiciso http://forum.imgburn.com/index.php?showtop...amp;hl=magiciso

If SCSI/RAID isn't visible then you probably don't have anything under that branch - and hence it's not shown Device manager is nothing to do with ImgBurn (obviously!) so it doesn't matter if ImgBurn is running or not when you open it. I just want to see which controllers are present in your machine incase there are any drivers updates etc. Are both the buffers full when it just stops burning?

I've made a few tweaks here and there so when I eventually send you a beta I'm quietly confident it'll pass

Do you have access to any other PC's at all? I be interest to see if it's just your machine that's stopping it from working or the enclosure the drive is in. I have a 20A3P in my machine you see and I never have a problem with mine getting stuck like this.

Tools -> Settings -> Write -> Cycle tray before verify I just hope you understand that turning this option off isn't going to solve anything if your drive is constantly burning discs that it can't read back once they've been ejected.

Ignore all that rubbish, just run the update.

Re-read my previous post.

I hope you ordered Verbatim 2.4x DVD+R DL discs! If your drive supports the booktype commands, ImgBurn will automatically booktype DVD+R DL media to DVD-ROM.

So it's actually a DX-20A3P? If so, try flashing with the XY13 firmware I mentioned earlier. http://www.liteonit.eu/optical-storage-dvd...p/download.html

Repeat that few more times and see if you always end up with 'CDB Interpretation: Read Disc Structure - Physical Information' as the last line in the log. It's weird because it's already processed that command just fine earlier on. What machine did that drive come in? XY13 is the latest official liteon firmware so I don't know where your XP5V stands. Can you please post your filter driver list too - the option is in the Tools menu.