LIGHTNING UK!

lol it fails an awful lot for something that's not completely broken! How 'broken' does it have to be exactly?! lol You NEED to test it in another machine with a nice clean / fully working OS (that's known to be able to burn). If it works, fix/reinstall your PC. If it doesn't, you'll know for sure it's the drive. Oh and you're not bothering, I just don't like to see people wasting their time by repeating things that just keep failing without actually having changed anything significant.

That write error doesn't really match up with the IBG you're displaying in DVDInfoPro - well, not unless a manual 'retry' worked? The error says it died at LBA 1131168 and the graph shows it burnt far beyond that. Seriously, don't waste any more time and money on that drive as it is. Try it in another PC (or don't). Then just buy a new drive. They're less than £20 here in the UK now and you've probably done that in coasters!

If you take the external case apart, can you locate the main chip on the little circuit board? Try and read the number off it. Is there a web link to the product you purchased? (even that might help a little!)

What drive do you have exactly? It sounds as though it has the problem, ImgBurn always tries to terminate the burn nicely and leave everything in a fully working state. If all it keeps doing is erroring out with 'command sequence error' then it can't be behaving itself.

It's not possible with 2.3.2.0, but it is with 2.4.0.0 (when released).

I consider it more a 'fix' than a suggestion

The error is a USB problem, the firmware just makes the burns better Did you buy the drive as a retail external model? Maybe you can update the bios on the enclosure... that could fix it.

Well if it keeps failing on another PC that can currently burn without any problems then you'll know is your drive rather than some other software/hardware configuration issue. What you're burning and how you're doing it is nothing to do with the error. The drive doesn't know or care about that type of thing. You could be burning all 0's for all it cares.

I'd say now is a good time to get testing the drive in another PC before then investing in a new one.

It can't hurt to try it again. The I/O interface used shouldn't make any difference to what works and what doesn't. It's just a road going from the software to the drive. By using ASPI, all you're doing is taking an alternative route. Success / failure is determined by the drive/firmware/media combo, nothing else should come into it. (Besides buggy filter drivers, which hopefully we've cut down on)

Ctrl+C when the box is on the screen But really the log provides us with all the info we need. As ASPI clearly fails too, go back to SPTI as it has other benefits.

Don't worry, what you did was correct, you just have a very clean list!

Fair enough, can't do much fine tuning with that!

Ok I made a little change for you Jason. When loading an IBB it will process the CLI options (and apply them to the GUI) after it's processed the IBB (which in turn occurs after the device scan). At all other times the order of processing remains unchanged.

Disable autoplay in windows, this is nothing to do with ImgBurn.

Saying you've always used Memorex media doesn't mean anything, it's the dye that's important. Maybe your other discs used a different dye. The current ones seem to be using RITEK-D03-01. You should also try burning at all the different speeds supported by the drive (in your case and with those discs - 4x, 6x, 8x). Some work better than others. Post your filter drivers list if you get a minute, it's in the Tools menu. (just press the clipboard button and then paste into your reply)

Well it's 5 less drivers that the I/O calls have to go through! 5 less drivers to introduce errors.

If you've just inserted the disc and then you click browse, it's normal. It's a single API call and windows blocks it until the drive is ready - it's nothing to do with ImgBurn itself.

Ok well personally I'd remove: NTIDrvr ASAPI pfc PxHelp20 Afc and then reboot.

If that works all the time now, you must have another driver in your machine that's screwing up the I/O subsystem. You really don't want to use ASPI - there's a reason they stopped making it and MS told people not to use it. What do you have in your Filter Drivers list? (check it out in the Tools menu)

Is ImgBurn still using SPTI?

If it's at all possible, get that drive off usb and make it internal. You might also like to try updating to the 1.18 firmware. http://www.pioneer.eu/files/support/DVR/DVR115D_FW118EU.zip

The size of the ISO built by ImgBurn doesn't have to be the same as the one made by another program. So if when you say 'original' you're talking about a disc that wasn't created and burnt by ImgBurn, that's why.

Yup if the line isn't there then the control isn't changed.

That doesn't make a lot of sense to me I'm afraid. Build mode should tell you exactly how big the image is that it'll create. That size should then be the same when you open it in Write mode. Can you provide a test case when that's not true?