Shooter Posted January 13, 2009 Share Posted January 13, 2009 Hi: User of ImgBurn since 1.2.0.0.... Just started to use with dual layer. Got in the enclosed log report errors upon verify, not sure what I'm possibly doing wrong (succeeded 2 out of 6 disks). //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Friday, 02 January 2009, 23:00:44 ; \\****************************************// ; ; I 21:55:59 ImgBurn Version 2.4.2.0 started! I 21:55:59 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 21:55:59 Total Physical Memory: 2,095,180 KB - Available: 1,424,704 KB I 21:55:59 Initialising SPTI... I 21:55:59 Searching for SCSI / ATAPI devices... I 21:55:59 Found 1 DVD-ROM and 1 DVD Link to comment Share on other sites More sharing options...
cornholio7 Posted January 13, 2009 Share Posted January 13, 2009 where are those discs made, it should say on the package Link to comment Share on other sites More sharing options...
Shooter Posted January 13, 2009 Author Share Posted January 13, 2009 where are those discs made, it should say on the package Thanks for checking in From what I've read here, not the one's to have ......India :& I have a friend who has used these same verbatim dl made in India disks, without issue One thing he doesn't use is imgburn for his burning (his loss) . I have viewed these disks without any visible errors. Steve Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 13, 2009 Share Posted January 13, 2009 It could just be an issue with your drive (or controller drivers / filter drivers) Typically the first 4 bytes for a sector within a vob file would be 00 00 01 BA. According to the log, the drive is returning data that doesn't match that... and is probably just filled with zeroes. (The 'Offset' value (which starts from 0) is always 2 and we can see that it's correctly reading the value '01' from the image file so that's not the problem here) Have you tried making an ISO rather than burning on the fly, burning+verifying the ISO and then if it fails, leaving it an hour before then repeating the verify manually in Verify mode? Link to comment Share on other sites More sharing options...
Shooter Posted January 14, 2009 Author Share Posted January 14, 2009 It could just be an issue with your drive (or controller drivers / filter drivers) Typically the first 4 bytes for a sector within a vob file would be 00 00 01 BA. According to the log, the drive is returning data that doesn't match that... and is probably just filled with zeroes. (The 'Offset' value (which starts from 0) is always 2 and we can see that it's correctly reading the value '01' from the image file so that's not the problem here) Have you tried making an ISO rather than burning on the fly, burning+verifying the ISO and then if it fails, leaving it an hour before then repeating the verify manually in Verify mode? No I have not.... I have burned ISO's before I usually just Build-Write-Verify. But I think its worth a try It seems to burning the disk fine , but coughing on verify. I did put the disk in my DVD Player, everything seems OK, but haven't watch from beginning to end to see. Didn't try Nero's CD-DVD Speed to see if the burn was good. I have without any coasters burned many DVD-5 disks. In fact I shrinked and burned to a single layer that same file without issue. Just starting to try dual-layers to preserve PQ. But I realize dual-layers can be tricky. Not familiar with "filter drivers", but I will look into that also Thanks for helping, Love you efforts Steve Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 14, 2009 Share Posted January 14, 2009 You can find out about filter drives on your machine via the Tools menu. Link to comment Share on other sites More sharing options...
Shooter Posted January 14, 2009 Author Share Posted January 14, 2009 You can find out about filter drives on your machine via the Tools menu. Not sure if this info helps There is some much information at your disposal, it can get hard to sift through all the different settings Thanks to Cynthia, cornholio7, and of course you, for all the guides to help me understand the capabilities. =============================================== Filter Driver Load Order - ImgBurn v2.4.2.0 =============================================== Upper Device Filter: redbook Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: DLACDBHM Lower Class Filter: DRVMCDB Lower Class Filter: AFS2K Lower Class Filter: PxHelp20 Lower Device Filter: imapi Filter Name: redbook File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) File Description: Redbook Audio Filter Driver Product Name: Microsoft Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 14, 2009 Share Posted January 14, 2009 Delete these: Lower Class Filter: DLACDBHM Lower Class Filter: DRVMCDB Lower Class Filter: AFS2K Link to comment Share on other sites More sharing options...
Shooter Posted January 14, 2009 Author Share Posted January 14, 2009 Have you tried making an ISO rather than burning on the fly, burning+verifying the ISO and then if it fails, leaving it an hour before then repeating the verify manually in Verify mode? Its seems everything went well As far I can tell . Including Log of burn & verify. ; //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Wednesday, 14 January 2009, 11:13:12 ; \\****************************************// ; ; I 10:25:41 ImgBurn Version 2.4.2.0 started! I 10:25:41 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 10:25:41 Total Physical Memory: 2,095,180 KB - Available: 1,457,772 KB I 10:25:41 Initialising SPTI... I 10:25:41 Searching for SCSI / ATAPI devices... I 10:25:42 Found 1 DVD-ROM and 1 DVD Link to comment Share on other sites More sharing options...
Shooter Posted January 14, 2009 Author Share Posted January 14, 2009 Delete these: Lower Class Filter: DLACDBHM Lower Class Filter: DRVMCDB Lower Class Filter: AFS2K Filter Name: DLACDBHM File Name: C:\WINDOWS\System32\Drivers\DLACDBHM.SYS File Version: 5.20.01a [5.20.1.0] File Description: Shared Driver Component Product Name: Product Version: [1.0.0.1] Company Name: Sonic Solutions Copyright: Copyright Link to comment Share on other sites More sharing options...
mmalves Posted January 14, 2009 Share Posted January 14, 2009 The only way to know is removing those filters and burning again. If some program stops working because it used one of those filters (unlikely situation) you can always re-install that program, right? Link to comment Share on other sites More sharing options...
Shooter Posted January 14, 2009 Author Share Posted January 14, 2009 The only way to know is removing those filters and burning again. If some program stops working because it used one of those filters (unlikely situation) you can always re-install that program, right? Sonic came with the computer, so its OEM not to concerned about reinstalling Steve Thanks for helping Link to comment Share on other sites More sharing options...
Recommended Posts