LIGHTNING UK!

Not everyone knows all of the tools and as you were burning with ImgBurn anyway, you need not have mentioned DVD-RB at all. It has nothing to do with the question you asked. No, getting write retries is not 'normal'. However, if the retry worked, everything should be ok. Of course, you can use 'Verify' to double check that.

And surely to have a window where the user can select which images to burn, it is exactly the same as the 'Queue' window you've already got?! Just delete the ones you dont want from within that window.

I guess so, I've never looked it it myself, I just know it's possible somehow!

There is a 'display name' option in this version of the forum software. You should be able to rename yourself via that.

Another good one can be found at www.sysinternals.com One of the best sites on the internet for small FUNCTIONAL admin/advanced user type tools.

lol read the changelog 'Laughing Man'. Not all changes are 'visible' ones.

Can you use something other than Nero to make the images - if you've not already tried that. Just make sure that program makes REAL ISO images and not it's own format of ISO images. I don't have the Nero specs for NRG images so maybe there is something weird in your files that I'm not accounting for. You're making an MDS file for them which leads me to believe they're multipart images too (The MDS shouldn't be necessary btw) - multipart images are even less likely to work.

TweakUI can be used for AutoPlay stuff. You can download it from Microsoft's site. Just search google for it or something. It's easier to use than regedit - which I doubt you've seen before! ImgBurn can also enable/disable 'Auto insert' as a system wide feature via the settings.

Right click your dvd drive in My Computer / Explorer. Then select 'Properties'. Then look on the 'AutoPlay' tab. Ensure the 'Prompt me each time' radio button is selected for each of the content types.

Make sure you use the DVD+R DL discs, NOT the DVD-R DL ones. The drive will change the booktype to DVDROM automatically when you burn on DVD+R DL and you'll also get a layerbreak in the right place - which you can't do with DVD-R DL. Unless your player really just cannot read the media (and that's nothing to do with it just saying it can't - as is often the case if you don't change the booktype), you should not have any problem.

It would be nice if ONES just kept to using ISO files instead of making up their own extension. I can understand it for CD images where they might want to embed special info, but for a DVD it's kinda pointless.

That's why they invented zeroloss linking

Yeah so you're attempting to overburn. You were lucky any previous versions worked... there are two basic methods of burning DVD+R, with or without the reserve track command. From day 1, I just chose to do it without. Without it, the plextor seems to allow automatic overburn. With it, it errors out - which you're seeing here. The opposite is true for BenQ drives and in 1.1.0.0, I added support for overburning on BenQ (by starting to issue the reserve track command if the program had already noticed the user wanted ot overburn) and hence broke overburn for Plextors. So anyway, I'm already aware that Plextors don't do overburn with 1.1.0.0 and fixed it a few days ago ready for 1.2.0.0. So the simple thing for now is to burn an image that actually fits on the disc.

DVD Dec and ImgBurn are both standalone exe files. There is nothing for them to replace or screw up. Seems your drive is getting stuck burning. I assume you're already running the latest firmware for the drive - if not, update it now. If you only have problems when shrink is open, close it! It might be trying to use the drive too, and that's messing things up. The 'Lock Exclusive Usage' bit in the settings (when enabled) 'should' sort that out though (and it's enabled by default), so I don't really know what to suggest.

Ok so what's the exact reserve track message? Are you not being told about 'overburning'? That would explain your errors.

Yes, new firmware fixes problem. No you wont have any problems if you follow the (very simple) instruction. I do it all the time, it's fun!

So are you saying it's not burning anything at all, or are you switching discs between closing imgburn and opening dvd dec? Looking forward to seeing the log Cheers!

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