LIGHTNING UK!

NEC's only really handle DVD+R DL booktype setting when using the standard firmware. If you want it on DVD+R or DVD+RW, you need to be looking around for hacked firmware. The cdfreaks.com forum may be of use to you here.

Verify that disc again using Verify mode... does it error out in the exact same place? (look in the debug log to check the contents again). Also, burn it again and see if the same info gets burnt - again, compare the 'miscompare' logs! It's very odd that 98% of the sector data is ok. I don't work on a level any smaller than that, and for data to be ok before AND after the problem bytes... well.... your guess is as good as mine!

3000, please provide your full log. For the actual burning code, nothing has changed since the DVD Dec days. Like I said before, the program just repeats the 'Write (10)' command over and over again. There is no room for error. Show me a log of 10 discs from the same spindle being burnt - 5 with dvd dec, 5 with imgburn. If DVD Dec's all burn ok and ImgBurn's all fail, then maybe I'll be able to take these comment seriously. Without a lot of testing and proof, I can't. ImgBurn is in use by 'Flash' from dvd-recordable.org who burns LOADS of discs as part of his reviews - in all drives. IF there was a problem I could fix, he'd have found it.

BTYME, If you want help with ImgBurn, fine. If not, go elsewhere for the info. You've been bothering people on this forum since the day you joined and I will not tollerate that type of behaviour.

It's often nice to hear when people have it working in one place but not in others. I find it makes them WANT to get the other one working too, rather than just casting the software aside

You mean it wont tell you there's an update? If so, yeah I know about that. I can't get at the server right now to update the update file, so it still thinks 1.0.0.0 is the latest.

That does say 'in the compilation' though and we're talking about burning image files here. I can't imagine Nero would break down the ISO file and parse it on a file by file basis - which it would have to be doing for that documentation to be correct (in it's current wording). More likely, it does a bit for bit compare over the entire disc area (ignoring the actual filesystem contents) - like how ImgBurn now does it. It's still a very odd problem though. I can't imagine for the life of me where this corruption is getting into the burn process!

lol that is a bit of a freaky verify rate! Probably due to drive caching and stuff though... and even then, it was probably a 1 off. It's calculated from 'real' values so at some point in time, the drive must have accepted a lot of 'reads' in a very short space of time. I have tweaked it now to try and ignore values that are 'wrong'. Only time will tell if it's good enough

Run ImgBurn's verify again, but this time press F6 before you start it to enable debug mode. Then when you get a mismatch, the entire sector's worth of data will be added to the log. Copy + paste all of that log (or save to file + attach it). I noticed you said 'I have A system' - does that mean it's ok on another one you have? I've done lots of verifying since that area was improved to check bit by bit and I've never had a failure yet!

Cheers, someone else reported this earlier today. It has been fixed already and so will be in 1.2.0.0

The process cannot be automated, no. Burning with DVD Decrypter was hardcoded into DVD Shrink. The best you can do is copy / rename ImgBurn.exe and pretend it's DVDDecrypter.exe There is a guide for it here: http://forum.imgburn.com/index.php?showtopic=131

By 'download', I assume you actually mean 'write' or 'burn' ! Load ImgBurn, ensure the correct drive is selected in the list, then click Tools -> Drive -> Check For Firmware Update... You should get a page come up with your drive and all the possible firmware updates. You want the latest one - should have highest revision number / code. If you can provide us with the name of the drive (make / model etc), we could possibly help you a little bit more.

Sorry, didn't see this until just now! I've added those options for the Graph Data stuff. The log will be staying as it is though I'm afraid - too many variables to consider.

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