Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,458
  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. D 00:59:29 Device Sector Dump...

    D 00:59:30 5B 6F B9 A6 60 A6 9A 92 63 0B 5C 18 D5 97 48 0D

    D 00:59:30 69 ED C1 83 9E 6A 48 F7 AD 70 8A CD 15 00 D6 A6

     

    D 00:59:30 Image File Sector Dump...

    D 00:59:30 5B 6F B9 A6 CD 2F AF BF F3 BB CD 9F AB 6B 72 EE

    D 00:59:30 2D 29 AB EE FF 6A B9 F1 9F BD 6B EB 5B A6 F7 85

     

    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!

  6. 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.

  7. 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.

  8. 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!

  9. 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 ;)

  10. 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!

  11. 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.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.