LIGHTNING UK!

In DVDInfoPro, click the 'Scan' button.

dabull69, Don't hijack other peoples threads, post your own. That said, try searching first next time please. http://forum.imgburn.com/index.php?showtopic=10354

Does that drive work in cdspeed / dvdinfopro for doing PIPO scans? If so, give that a go too.

Verify your burns. The drive could just be creating coasters - without actually telling you there was a problem.

Your drive should have burnt at whatever it supported that was close to 2.4x. If you burn another disc, press F8 (to enable Debug mode) before clicking the Write button and then save the log to a file and upload it. I'll then tell you what speed the drive thought it was burning at - or why it rejected the commands used to set the speed.

You mean 'Queue', not 'Query'. No, you can't loop it.

loop what?

And what's the message in the statusbar?

2.4x is not a valid speed on that drive. The media you're using is rated for 8x, so try burning at that speed... your drive might do a better job.

Find out who really makes the drive and use that OEM.

ImgBurn detects a bootable image by the presence of the El Torito descriptor, nothing more. If there is an error with it, that would be cause for your machine not to boot it.

That drive is a virtual one from DAEMON Tools / Alcohol 120%

Burn a disc of the same content with each program and examine the result (using your eyes and Explorer) to check the exact same folders / files are present on both.

The Swedish one is normally done before ImgBurn is ever released to the public. The person in charge of the translation (Cynthia) is on the beta team! So basically, I have no need for you. Thanks anyway though.

That's awesome but it's nothing to do with it. The drive doesn't know / care what you're burning... it's all the same thing. You've just got an unreliable drive/firmware/media combo.

http://forum.imgburn.com/index.php?showtopic=8000

Ok so at least the LB was moved eventually, even if the drive didn't report it as such the first time around. You'd be helping me out if the next time you burn a DL disc you press F8 before clicking the big 'Write' button. That'll put more info into the log and it might just enable me to tweak my code incase I need to wait a bit for the drive to set the LB position and it's not returning the error codes that make the current version of ImgBurn wait.

If it's got to the stage of writing leadin, all it's doing is sending the 'write' command over and over again.

I really wouldn't bother with the recovery, something is obviously messed up.

Put that disc back in the drive and copy + paste the disc info from the panel on the right.

Once you've killed that, all the rubbish will be exposed and you can then use normal programs (all of them if I were you!) to remove what's left.

That one will probably just crash but give it a go if you want. Yes, scan everything and see what it finds. You might have more luck with gmer and mbam though. Feel free to upload any screenshots to do with what each tool finds etc.

Try this one: RootRepeal - http://rootrepeal.googlepages.com/ or gmer - http://www.gmer.net/ We talk about it in this thread... http://forum.imgburn.com/index.php?showtopic=10038 try mbam too. http://www.malwarebytes.org/mbam.php Are you really really sure DrWeb CureIt didn't find anything though?! Did you run a complete scan ok?

So you ran drweb cureit and the problem wasn't fixed? How about avg anti-rootkit? You obviously have a much bigger problem here than just ImgBurn not working... your entire machine is screwed until you fix this.

What problem do you have exactly? 'No Writers Detected' or 'The maximum number of secrets that may be stored in a single system has been exceeded.' The 2nd causes the 1st but the 1st can happen for several reasons.