LIGHTNING UK!

If you've already removed the problem/virus/malware... no.

This has nothing to do with the actual burning phase. Direct your question towards the DVD Flick author instead (over at his forum).

Read the linked thread.

Because your drive isn't recognising the disc properly. Can you please copy the disc information from the window on the right when you're in 'Read' mode on your computer. Then repeat that process on someone else's PC so we can see what their drive thinks about the disc and compare it to yours.

What's the error when you try and load an ISO file? Get a screenshot or something for me please. What made the ISO in the first place?

Don't use Patin Couffin unless you really really need to. I've already spoken to the guys at VSO Software about the issue and they've said they'll look into it when they next make updates to their driver.

You didn't update your firmware. Please do that and then read this: http://forum.imgburn.com/index.php?showtopic=8000

You've already had a failed burn on that disc.

This is a little odd... Please go back into Write mode (with that disc in the drive) and copy + paste everything from the disc info window on right.

Does anything interesting happen if you run it inside WinDbg? I still find it odd that even the uncompressed exe won't run... I don't recall ever seeing that before. It's always been the upx compression that some low level app didn't like and was blocking.

Maybe they're trying to burn the torrent file?

If you can't handle adding a reg key, there's a program called 'FrogRights' that puts a pretty GUI around it. If you want to use SPTI as a non-admin user there's just no way around it. ImgBurn is one of the few programs (especially freeware) that actually does all the drive communication itself... most the others use a 3rd party library which basically makes them glorified wrapper GUI's. They'd have to install a special drivers to bypass the OS's block - something I have no interest in doing (nor do I know how to). There was no need to take a dig at my work. Either you want to use it or you don't. It's no skin off my nose either way.

I've tested it on a fully updated XP SP3 install and it works fine. So although it *might* have stopped loading after an update, it's not the update itself that's causing the problem... probably some conflict with other software.

So you have the AV from ZoneAlarm Security Suite *and* BitDefender Antivirus 2008?

You might find uninstalling AV and ZA produces different results to just attempting to disable them.

Put that burnt disc in another drive. It could just be that yours is a bit shite and won't initialise the disc properly, hence why the verify never starts. What does the drive say if you switch to read mode and look in the disc info box on the right? Copy + paste it all please.

All you can do is try. If they still don't work, try cleaning your drive. After that, think about investing in a new one.

If the uncompressed one works, PLEASE help to find out which bit of software on your system is causing this issue. If you don't want to help by uninstalling potential problem makers, at least give me a list of everything in your 'add / remove programs' list so I can install all the apps in a VMWare session and do it myself. It's the only way this will every actually get fixed for everyone. The uncompressed exe is just a workaround and far from being an ideal solution.

I expect something on your system is wiping them out after a reboot then or you have a corrupt profile. Of course it could just be that you're loading ImgBurn via a 3rd party tool (i.e. DVDFlick) and they're not saved (on purpose).

Pressing F5 is enough to clear this problem. I've seen it myself but haven't looked into it.

The disc has just gone bad / started off bad and got worse... to the point where your drive can't initialise it. RW's have never really been all that reliable anyway.

Right so your ImgBurn.exe is still compressed by UPX then. It's down to you to figure out which crappy piece of software installed on your machine is preventing UPX compressed apps from running.

Throw it in the bin then.

Ah, so you've got an old new drive. I say 'old' because the current model is 117. Like you say, if it's new then I very much doubt it needs cleaning. The random failures would either be because the drive is just shit or because the batch of Verbatims aren't the quality they should be. Try some of the other 'supported' write speeds. Maybe it'll do a better job?

Yes.