aarste Posted February 27, 2008 Share Posted February 27, 2008 (edited) I believe this has started happening since 2.4.0.0, although I'm still new to ImgBurn and only did 2 burns on the previous version which went fine. What happened is I burned an ISO and when data verification started it just threw out read errors until I cancelled it. It wasn't until I closed and restarted ImgBurn and cycled the tray again and retrying image verification comparing to the ISO on the hard drive it passed fine. Same thing happened again when I used Build mode and made a data disc of xvid movies, verification failed until I restarted ImgBurn or cycled the tray myself. I couldn't run a verification for file comparision so I just used the standard verification to check for bad sectors, which passed fine. The log of this burn is attached to the post, can't find the log of my ISO burn though. To summarise, ImgBurn wants to be restarted (or the tray cycled a 2nd time) before it can actually do data verification of my burned disc otherwise it will spit out data errors from sectors 1 to 30 (at which point I decided to cancel). Ignore the Discovery errors, that was just me thinking it was a verification check ImgBurn.log Edited February 27, 2008 by aarste Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 27, 2008 Share Posted February 27, 2008 Seems you forgot to attach the log Link to comment Share on other sites More sharing options...
aarste Posted February 27, 2008 Author Share Posted February 27, 2008 Seems you forgot to attach the log here we go, did attach last time but probably got lost since the post had to be moderated Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 27, 2008 Share Posted February 27, 2008 This is a drive/firmware/media issue. At the moment the drive is doing an awful job of initialising the media after the burn. For example, this is before the burn: I 02:08:39 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x) this is after: I 02:16:07 Source Media Type: DVD+RW (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 4x) DVD+R -> DVD+RW ? Ummm ok! Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x -> Speeds: 4x ? Ummm ok! There is nothing I can do in ImgBurn to fix that, software doesn't even come into it. Link to comment Share on other sites More sharing options...
aarste Posted February 27, 2008 Author Share Posted February 27, 2008 (edited) Seems ok now, burned another disc at 12x instead (Verbatim DVD+R MCC 16x) and from files on the local hard disk rather than from a network drive. 16x was probably too fast as its more than 14mb/sec on a 10/100 network, the 40mb buffer did drop a lot but didn't show any errors otherwise when I did network burn. But whatever different choice I did to burn at 12x or do a local burn made ImgBurn read it as a "I 14:50:55 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 2.4x, 4x, 6x, 8x, 12x, 16x)" for verification after cycle. ImgBurn.log Edited February 27, 2008 by aarste Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 27, 2008 Share Posted February 27, 2008 So long as it initialises it properly, you should have no problems in reading/verifying the disc. If it keeps coming up with DVD+RW for a DVD+R disc and erroring out in the same way with every 'Read' command it's sent, you might like to contact LiteOn and see if they can fix it. Link to comment Share on other sites More sharing options...
aarste Posted January 22, 2009 Author Share Posted January 22, 2009 So long as it initialises it properly, you should have no problems in reading/verifying the disc. If it keeps coming up with DVD+RW for a DVD+R disc and erroring out in the same way with every 'Read' command it's sent, you might like to contact LiteOn and see if they can fix it. Sorry for resurrecting an old topic, but my LiteOn drive finally failed, as it started to read almost every DVD I had in the collection as a DVD-RW disc and being unreadable in Windows Explorer. I suspect it must have come from a bad batch as it was up to date with firmware. Prior to that failure I had to burn DVDs slightly differently, making an ISO image of the files I wanted to burn, then burn the ISO, and if the burnt disc became unreadable I cycled the tray a few times until it could be read then did a verification against the ISO image on my Hard disk, which passed all the time. But anyway, ordered a Pioneer DVR-216DBK last week and started doing some burning on that now, fingers crossed as the issue hasn't come up yet Link to comment Share on other sites More sharing options...
Recommended Posts