LIGHTNING UK!

Some people really have no idea do they!

Sort out why your machine can't sustain the write buffer for an 8x burn too.

It's not a bug, it's just your machine / drive doesn't do what it's meant to. As has been pointed out, your drive is old and has problems of its own. Commands should either work or be rejected, hanging really isn't my problem and all I end up doing is implementing workarounds for buggy drives. How about the answer to my question from earlier? Back to the empty disc... once it has finally been initialised (even if it takes a few hours), please copy + paste the disc info text from the panel on the right so I can see what the drive is returning and why it doesn't think the disc is empty.

Generally speaking you just Google 'APE DirectShow' and 'FLAC DirectShow' and then install the one from the first result. However, I have no idea if they work with x64 as I've never tried / used it properly. The madFlac one from the guy on Doom9 might be ok and if it's not you can just post in the thread to ask him to fix it.

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

Check event viewer too, it might show that there are errors on your hdd or something. You can test if it's the hdd by burning a disc in discovery mode - where only memory is used because the data is made up on the fly.

Bring up task manager before you start burning. Is the CPU% usage at 100% all the time during the burn? (which process is using it all up?) If so, it still really seems as though DMA is the problem - regardless of you saying you've checked it or whatever. Did you do your 'fresh install' and then put ImgBurn on BEFORE *anything* else and try it that way?

Do you actually mean 'Getting Disc Recording Management Area Information' ? The text you provided doesn't exist in my code. Can you also please tell me if it does the same thing when you put in a disc you've already burnt?

There are a couple of others about it and they'll say the same thing... No Device drivers are not my area and there are already some excellent freeware utils for this job.

It's not my area and I have no interest in it, sorry.

Being branded by 'Philips' doesn't mean anything, it's the dye that's important and yours are using the 'RITEK-S04-66' one. The best / most compatible one is 'MKM-001-00' and you'll only find that on Verbatim DVD+R DL 2.4x speed discs.

Your drive isn't old at all and I don't know why it's having a problem burning them, it just is. Try burning in safe mode and see if you have the same problem.

You can't cancel it, once the command has been submitted the rest is down to the drive.

The clue is here... Just cancel the verify.

Go through all the other speeds available to you too. These are the ones your drive is supposed to support on that media... If none of them work, you're probably out of luck. Where are those Verbatims made? Look on the box / case / spindle / package. Get some of the 2.4x ones as mentioned in that thread you read earlier.

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

Because some of these things just don't work properly! You can disable them, but on some level they're still running. Keep hunting down the problem app, I'll make a mental note of ones that don't play nicely

Do you have any desktop theme type programs running? Something is obviously getting at the exe before any real code (i.e. my stuff) is run and it's bombing out. Normally that's caused by AV (as mentioned earlier) but it could of course include anti spyware, malware, rootkit type utils. Basically anything that works at a very low level and checks programs when they load. You could give decompressing the exe a go (that's what most of these AV type programs don't like), you just need to download UPX and run it with the switch to decompress the imgburn.exe file.

Damn, I wanted to do that

Maybe run sfc /scannow too.

Normally you go to the website of whoever makes your PC. Don't forget to update ImgBurn. This covers something else volvofl10 mentioned - http://forum.imgburn.com/index.php?showtopic=8000

So you don't even get the splashscreen? That's pretty much the first line in my code so it's probably not something I'm doing. I assume it's worked ok before yeah? In which case, what's changed since it last worked? First things to look at when the program won't load are apps that check up on programs when the load - i.e. antivirus etc. Disable them, uninstall them, do whatever you can to make sure they're not on and then try again.

The unlocker thing might have fudged something so you were able to put the file in place, but now that it's there, the same program that stopped you from copying it there originally is now stopping you from running it. Clean all the suspect programs off your machine until it works and then put them back on one at a time until it doesn't... then you'll know which one to avoid in the future.

Looks like the problem is with Alcohol then. I assume it's up-to-date? Does the same thing happen if you use the latest DAEMON Tools to mount the images?

Overclocking gone wrong then?