LIGHTNING UK!

By 3rd party apps, I was referring to AnyDVD / DVD43. So long as you're sure you don't have those enabled, there is no reason for failure so long as the disc really isn't broken.

I'm 99% sure it works fine. I would have double checked (making 100%), but having just turned on my XP 64-bit machine, my hdd has decided to die on me. Arrrgh!

hahaha, that really did make me....

Notice it says 'find' though, not 'click' Can anyone find me a cliff with a really long drop?

Do you have any 16x discs you can try? It's hard to tell if weird things are going on if you're only burning at the lowest speed. With USB, the higher the throughput, the higher the CPU usage. I can't tell if the program is being greedy (it's not for me), or if is just one of those USB short falls. You may find firewire behaves better - if your PC has such a connection. I do expect dips in the graph though, that's the drive WOPC kicking in at bad bits on the disc - or where it notices the quality isn't quite up to scratch. WOPC also does checks at various points (not quality related), to make sure the burn speed is still ok for that media. These are normally evenly spaced out.

I was just wondering if it's something I need to tweak, that's all. I'll do some tests myself and see if I can reproduce it.

It 'should' have worked fine. The file association reg entries are removed/added when the program is shut down - depending on what you've ticked/unticked in the setting.

Most the options on the Device menu come directly from the MMC specs available at http://www.t10.org ReZero puts the laser back over LBA 0 and basically reinitialises the drive. Sync Cache is used after a failed burn (not needed if you burnt with ImgBurn because it performs that operation regardless). It basically tells the drive the Write operation has finished and that it's to finish writing everything in it's cache to the disc and basically clean up after itself. What exactly were you hoping/expecting them to do? and why are you clicking things when you have no idea about the consequences?!

untick all the 'file association' options in the settings. Depending on how other programs in your system have installed themselves, this may be slightly harder that just doing the above.

Check your PC drives firmware is up to date. Clearly it 'should' be able to read the discs back too. Where you say it 'bombed out', did you get an I/O Error or just a miscompare? 3rd party DVD related apps running in the background will/can cause verify to fail - because they're changing the data read from the drive on the fly. As such, these programs must be disabled.

So, RIGHT NOW, you can burn with 1.0.0.0 and it works fine, then you load 1.1.0.0 and it burns slowly? Clearly it's no good comparing something you did last week to something you're doing today.... things change If you could perform that simple test for me (burn 1 disc straight after the other), it would really help. Use Test Mode if you like, then you won't be wasting any discs. (Will need to be DVD-R/-RW of course!)

No, that kind of logic is too difficult to implement (to be 100% perfect anyway). It's often also a case of what works for 1 person isn't right for another. I have to draw the line somewhere with these things or it complicates the program beyond what's really needed. Clearly it wouldn't cause any harm reinserting that already burnt disc - because it wont be writable. For rewritables, you actually need to click the Ok button before it'll accept them. Oh, that is unless you have 'Eject After Write' enabled, in which case it doesn't expect the user to be stupid enough to put the same disc back in - unless it's done intentionally

That is indeed odd! Not much goes on inside the main thread besides the drawing of stuff and so there should never be anything that takes AAAAAAAges to complete - before then allowing then next paint message to be processed. All the I/O stuff is done in threads (well, most of it).

Erm..... maybe

You want ImgTool Classic, not ImgTool Burn.

lol yeah, that's what's supposed to happen! The program appears to be working just fine. You put your disc in, select your image and then click on the big 'Write' button.

Unless Stomp doesn't check the image against the data, it should fail on both of the burnt discs. There is no reason for a disc burnt with ImgBurn to behave any differently to one burnt with DVD Decrypter. Maybe your image burnt with DVD Dec had already had all the bits removed and so AnyDVD isn't actually doing anything in the way of changing what the drive is reading.

I will probably try to add an option to just have it work like the old version (i.e. just check the sectors are readable, rather than comparing their content to that of the file). That way, if you're not fussed about comparing to the file, you won't need to mess with AnyDVD each time.

This would only be used for DVD-RW and DVD+RW. Clearly you can't format write once media! In such cases, ImgBurn isn't any use to you anyway. It prepares the disc for burning images, it doesn't format it so that it can accept files via programs that do 'drop to disc' type stuff.

The verification is only failing because AnyDVD is changing the contents of the sectors on the fly to remove things like PUO's etc. You don't need to disable it when you burn, just when you verify - but of course verify generally happens straight after burn so it's best to disable it over the entire process

It wouldn't even read back in the PC?! Forget about playing it for now, can't explorer even see the contents of the disc? Booktype stuff will help with standalone players but it shouldn't make any difference to a PC. Also, it might be an idea to enable the 'Verify' option for after the burn. At least then you'll know if the disc contains everything it should do and that it burnt correctly.

Hmm...where on earth did you get the idea you needed Administrative privileges from?!

Are you sure you don't have HDD (DMA) issues then? Your burner is on USB which rules DMA problems out for that one, but if the main buffer is up and down all the time, maybe your hdd isn't running as it should be. Quite simply, if the 'Buffer' goes up and down all the time, the program cannot read data from the HDD quickly enough. It should be on 100% (rock solid) all of the time.

Not useful to you perhaps but not everyone works how you do. You should be thankful it has any sort of queuing system, it is FREE remember! Adding support for multiple drives etc is something I'd already thought about and will probably be added in a future version.

The old version didn't compare against a file, it just checked the disc was readable. Could you please copy + the entire log. You don't need to burn the disc again or anything, just switch to Verify mode, put in your burnt disc and try again. Also note, a 3rd party background app could be changing the disc on the fly without you knowing - and hence what my program thinks it is reading from the drive is not actually what's on the disc.