LIGHTNING UK!

The Windows API (DeviceIoControl) is just returning that error there, nothing I can do about it I'm afraid. As you can see, it's just repeating 1 command over and over again - nothing changes - and yet eventually something messes up. If the enclosure is of your own choosing, perhaps try looking for a firmware update for it. I've got a couple using the Prolific chipset and there has been several updates for it. Also check no other programs could be attempting to the use drive at the same time (not even just polling it - as ImgBurn is doing with the 'test unit ready' command). I've found USB to be particularly sensitive to buffer alignment etc and some programs/drivers can cause usb drives to hang.

None of those, it's where you select the 'Target Device' having clicked the 'Backup!' button

It won't shrink the actual input file(s), it makes new output files (BUP/IFO/VOB) or a new ISO image. It all depends on how you have DVD Shrink configured.

I'd probably go for the one that says VTS_03_0.IFO in the 'File/VTS' column. Any of them would do though!

When you think it's gotten stuck (i.e. been doing it for a while), press F8 and see if the program is still actually communicating with the drive (and the drive responding). If the log fills up with stuff, you know it is and it's then just a case of your drive thinking it's still busy. Nothing I can do about that I'm afraid. Try this firmware update, it may fix the issue your drive is having with the media. http://h10025.www1.hp.com/ewfrf/wc/generic...=en&lang=en Direct Link: ftp://ftp.hp.com/pub/softlib/software7/CO...2-1/sp26639.exe It's version E223 where yours is only E152

It's not that they don't work with the program, they just don't work with your drive. ImgBurn has no control over if your drive can / cannot burn to certain media.

Discs aside, you really must update your drives firmware. Running v1.01 is like still running Windows 3.1 ! New versions fix problems, improve burn quality / speed and add support for more media.

That does seem to depend on the drive. Some appear to test more thoroughly in 'test mode' ! Test mode is still having to focus the laser on the sectors etc and your drive is just seeing something it doesn't like - hence why it's erroring out. Ritekf1 are not good discs so that would make sense.

I think you were just unlucky with that disc. The drive returned a 'write error' so basically it had the problem, not ImgBurn.

Only if you do it at the same time as burning. After that, you can verify the readability of the disc using Verify mode - having unchecked the 'Verify against image file' option. To compare the individual files you'll need to use another tool.

JasonFriday13, If it was a real (and obvious) glitch in my code, SOMEONE else would be able to reproduce it too! I, nor any of the beta team, can do that. I've got every debug option possible enable and I'm running codeguard which hooks into all the memory allocation calls and keeps track of memory accesses etc. I'm not getting a single problem come back from it.

You're fine to install all the windows updates, I do and I know I'm not getting shutdown errors! I really can't reproduce this issue you're having and I've tried it on every OS Microsoft has released, starting with Windows 95. Sorry but I'm at a total loss as to why it's dying on your PC. You can go back a version, sure, but it might mean you're stuck with it forever!

The settings are pretty much all saved anyway. You can however use project files (*.ibb) to configure the program in any way you want to - with respect to 'Build' mode of course.

I agree with Shamus, your 'DVD' discs actually appear to be 'CD' discs! So either you made a mistake when you purchased them or they're not labelled up properly. From the screenshot I can also see you're on the original version of the firmware for that Plextor PX-708A drive, v1.01. http://www.plextor.be/technicalservices/do...e=DVD-Recorders Go and download + install the latest one, v1.12.

There's a version of shrink available that calls upon ImgBurn rather than DVD Dec, just go hunt that down. Google is your friend.

Yeah your drive is just failing to write to the disc, hence the 'Write Error - Recovery Failed' message. So basically it doesn't like those discs at the moment. If you can't find a firmware update (and one that DOES then like them!), you're stuck and will need to buy different discs. As LFC said, Verbatim / Taiyo Yudens are the ones to go for.

he was only messing around palman, just ignore him!

If it's failing during the verify stage, the drive cant read back what it just wrote. A firmware update may fix that - if there is one for that drive?! After that, if no discs work, maybe your drive has just had it?

Ignore the names the program gives the info, those names are taken from the MMC specs. The manufacturer id (on minus format media) and disc id (on plus format media) ARE the dye manufacturer/type.

Sorry to be a pain but can I just double check that the logs you're posting a from when you've opened AND THEN closed imgburn whilst it's running in windbg? WinDbg mentions the address 0040180a in the log, but your screenshot shows a very different address.

lol I only ever discard non existent things! I can see with my own eyes that *something* isn't working properly on your PC and I actually quite like the challenge of finding out what that is I've not even given the beta team a beta version since the final v2.1 release..... far too much testing for me to do first! Maybe once I give them a beta I'll PM you or something.

I'm amazed that even 'Test Mode' is failing! Are you sure there are no visible flaws on the outer edge of those discs?!

There seems to be far too many people making multiple backups these days! Sorry, no, ImgBurn cannot burn to 2 drives at the same time. The best alternative is to queue the image a couple of times, one to each burner.

Ok that says it's a first time exception, so what if you click 'debug' -> 'go' again? When it shows that stuff in the windbg window, has the error popped up properly in the messagebox like it did in the original screenshot?

Just to be clear... The created and modified date fields use the current time/date if not specified. The effective and expiration date fields are zeroed out if not specified.