LIGHTNING UK!

Hmm most odd. The 'Close Track' command doesn't appear to be failing but it's taking almost no time at all to complete. I guess it's just reporting that's it's finished way before it actually has. Next time you burn (or just before it comes to the end of the burn - i.e. at 97% or something), press F8 to enable I/O debug mode. Then when it's finished (after erroring out etc), press F8 to disable it again. Save the log and upload it (might be too long for copy + paste). Ta.

It's the drive that's erroring out here, just remember that. Drives have bugs too, ImgBurn might just be doing something that causes it to rise to the surface. All the software is doing for the entire burn is sending data, repeating the 'Write (10)' command over and over again. There is no reason for it to fail, it just is and it's out of my hands. Also, Roxio might not be using DAO for burning, it might be using the Packet / Incremental write type. Try switching to use that instead. Again, there's no reason for that to work either really but firmware bugs could mean that it does.

Could you post the log from that failure too, just so I can compare things. Thanks.

There are known problems with the 112 / 212's burning CD's Shamus mate. The speedlabs.org forum has a guy from Pioneer who's recently started posting on it and one of his thread discusses that very issue! If the 1.21 firmware doesn't fix the issues, I would think the next one will. http://forums.speedlabs.org/index.php?topic=2303.0

None of the Pioneers bitset DVD+R as standard, only DVD+R DL. As you say chewy, you need the Buffalo firmware to get bitsetting on DVD+R SL media. That's the whole reason people crossflash to the Buffalo firmware - otherwise there would be no point!

No need for cross posting.

I've already said this will happen one day. Just got other more important things to implement first.

Remember that it's not the manufacturer you need to look out for, it's the dye the discs use. Verbatim's are MCC / Taiyo Yuden dye and Taiyo Yuden's are of course Taiyo Yuden dye! Even though you have 2 spindles of the same 'brand', they might be using different dyes - hence why one works and the other doesn't.

At the moment it's just basically support for bin/cue files. (which of course can include audio tracks if they're specified in the cue file) No attempt has been made a burning a random bunch of wav/mp3/wma etc as an audio cd via the likes of build mode. I may just do it one step at a time so that I limit the number of bugs introduced! Even the bin/cue support meant a rather large rewrite as previously everything was very basic due to the single session / track limitation.

That error is from the drive so basically it's just decided it doesn't like the media you're using. I assume you've tried others from that spindle? You'll probably just have to buy some different discs - Verbatims DVD+R's or Taiyo Yuden DVD-R's are about the best going.

I fairly sure recode isn't free?! It's part of the nero package - which of course you have to pay for. That said, if your machine has never had nero on it and you can install recode without it asking for a serial number / activation, I guess it must be!

Press F6 the next time you go to burn a disc, then post the log again. Oh and take off the compatibility thing. If you're running Vista the program would want the OS to report that because it has to make slight changes. Please also post the details for your filter drivers (look in the Tools menu).

That drive might be new to you but it's not new in the world of optical drives! There have been 2 firmware releases since the one you're on - HS07. Try updating it to HS0E http://forum.rpc1.org/dl_firmware.php?download_id=2191

No need for a debug log there... a normal one is enough The drive is simply unable to read those sectors and is timing out after 10 seconds - hence the error code being returned to the program - and then displayed by the program "Timeout on Logical Unit". Besides ditching the CMC media, you might like to try the TU03 firmware update. http://www.toshibaer.com/firmware/index.php?path=SD-R5472C/

Slim to none I'm afraid shamus. Too much pissing around with shell extensions and extra dll's.

No, it's a burning program, not a conversion program.

This just looks like a drive / media compatibility issue to me. Try some DVD+R Verbatims instead of the -R ones.

Stick with the ones you've got, I prefer them to the 8x ones anyway. Try burning another one and see if you get the same problem.

Yeah I'm afraid the standard windows dialog boxes just don't allow for selecting multiple folders. Explorer -> Drag + Drop is the only way to do it.

With the one that didn't work, try closing the track manually and then closing the disc. Do that via the 'Tools' -> 'Drive' -> 'Close' options.

The thing you're looking at is not a file - or at least not in the way you think it is. IsoBuster just displays the bootable image using the 'Developer ID' as the name of the file. i.e. if you told ImgBurn to write a disc using 'Hello' as the Developer ID for a bootable image, IsoBuster would show the bootable image 'file' as being called 'Hello.img' or whatever.

'Build' mode -> 'Advanced' tab -> 'Bootable Disc' tab -> 'Create Boot Image'. Just point it at the right drive and click the little blue floppy disk icon.

Only use Verbatim DVD+R DL discs, the rest are useless in comparison.

No, not for a long time, sorry.

Going by my testing, it was. (although it's not actually a DT problem, it's a DuplexSecure (SPTD) problem. DuplexSecure admit the previous versions had problems with ASPI that wraps SPTI) Changing the Nero ASPI version didn't do anything for me - but I didn't try donta's specific one, I already had a collection of them. Since updating to SPTD 1.45 Beta, I've been able to switch ImgBurn to using the VirtualAlloc function and Nero ASPI works fine - even the latest version.