Jump to content
Sign in to follow this  
fordman

Device MD5 stopped showing in log

Recommended Posts

I burn with ImgBurn 2.1.0.0 and have the option set to calculate MD5 hash values. I also make a habit of pressing F6 to add debug info to the log.

 

I burn with an immediate verify (after cycling the tray) afterwards, and after the verify the ImgBurn has always shown the device MD5, followed by the device (padded) MD5 (if applicable) and finally followed by the image MD5. The image MD5 also appears further up in the log.

 

Today I was runing several discs and all was working as described above, and for the past few discs (even after closing ImgBurn and restarting), ImgBurn only shows the image MD5 after the verify and neither of the device MD5 values. However, if I perform the verify separately, all values are shown.

 

Any idea why the device MD5 value(s) have stopped showing up for me all of a sudden? Could I perhaps have accidentally pressed a function key that has shut just that off? If so, I cannot locate it.

 

In Summary, this is the type of thing that showed after an separate verify after burning and the immediate verify (part of my log):

 

I 00:19:52 Verifying Sectors...

I 00:38:58 Device MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 00:38:58 Device (Padded) MD5: 0cb1131dd42505be8c9e8adb829ff9e4

I 00:38:58 Image MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 00:39:01 Exporting Graph Data...

 

(Note that this is the format that used to be reported after the immediate verification)

 

Now the follwing shows (part of the same log) what is reported after the immediate verification:

 

I 23:13:16 Verifying Sectors...

I 23:32:12 Image MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 23:32:12 Exporting Graph Data...

 

Any ideas?

Share this post


Link to post
Share on other sites

A full log with F6 debug info should also tell you (me) why the device MD5 could not be calculated - i.e. where a call to the API's failed.

 

That said, there were glitches in the MD5 code that have now been fixed. Maybe you're just hitting one of those.

Share this post


Link to post
Share on other sites
A full log with F6 debug info should also tell you (me) why the device MD5 could not be calculated - i.e. where a call to the API's failed.

 

That said, there were glitches in the MD5 code that have now been fixed. Maybe you're just hitting one of those.

 

OK. It's likely a bug that only comes up on some of these titles. This happened for backups of both discs of season 3 of a particular TV series. Meanwhile the backups of all 3 discs from season 1 acted perfectly normal, providing the device MD5 after the immediate verification. I assumed I had pressed something that turned off the device MD5, because this is the first time in all the months that I've been using ImgBurn 2.1.0.0 that it failed to produce the device MD5 when doing the immediate verification.

 

By the way, note that although the LB flag is taken from the original disc, I always choose to display it from withing ImgBurn, so that the analysis will be included in the log - so that information is there because I chose to display it manually.

 

Also, the "D 00:19:29 Disc Capacity: 4121087" line was there because I believe I pressed the F7 key (looking for a mysterious function key that may have turned off the device MD5) and it put it into verification mode.

 

The log is below. By the way, maybe better in separate thread, but I found that the image md5 that is built directly to disc does not match those that I build to ISO. The individual files and dates (and creation dates, etc) are the same, but the image MD5s themselves do not match. Awhile back I had asked whether it would be the same, and it was suggested that as long as the creation and modified volume dates and times as well as the file dates and times were identical, they should match. In fact, for two different discs, I burned one directly and for a subsequent burn, I built an ISO first. In both cases the direct to disc image MD5 did not match the ISO MD5, and I used the same project for each, only chaning the target.... I suppose there must be something else different in there, and will likely have to do a byte-for-byte compare to find it.

 

Thanks and Happy New Year!

 

FordMan

 

-----------------------------------------------------------------------------------------

 

I 22:53:22 ImgBurn Version 2.1.0.0 started!

I 22:53:22 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 22:53:22 Initialising SPTI...

I 22:53:22 Searching for SCSI / ATAPI devices...

I 22:53:22 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW/RAM!

W 22:53:28 Program 'Debug Mode' has been Enabled!

D 22:53:42 GetIFOLayerBreakPositions - MinL0DataZoneCapacity: 2060544

D 22:53:42 GetIFOLayerBreakPositions - MaxL0DataZoneCapacity: 2086912

D 22:53:42 File System - File: VIDEO_TS\VIDEO_TS.BUP - LBA: 10413 - 10422

D 22:53:42 File System - File: VIDEO_TS\VIDEO_TS.IFO - LBA: 9560 - 9569

D 22:53:42 File System - File: VIDEO_TS\VIDEO_TS.VOB - LBA: 9570 - 10412

D 22:53:42 File System - File: VIDEO_TS\VTS_01_0.BUP - LBA: 10745 - 10753

D 22:53:42 File System - File: VIDEO_TS\VTS_01_0.IFO - LBA: 10423 - 10431

D 22:53:42 File System - File: VIDEO_TS\VTS_01_0.VOB - LBA: 10432 - 10543

D 22:53:42 File System - File: VIDEO_TS\VTS_01_1.VOB - LBA: 10544 - 10744

D 22:53:42 File System - File: VIDEO_TS\VTS_02_0.BUP - LBA: 13855 - 13861

D 22:53:42 File System - File: VIDEO_TS\VTS_02_0.IFO - LBA: 10754 - 10760

D 22:53:42 File System - File: VIDEO_TS\VTS_02_1.VOB - LBA: 10761 - 13854

D 22:53:42 File System - File: VIDEO_TS\VTS_03_0.BUP - LBA: 248113 - 248124

D 22:53:42 File System - File: VIDEO_TS\VTS_03_0.IFO - LBA: 13862 - 13873

D 22:53:42 File System - File: VIDEO_TS\VTS_03_1.VOB - LBA: 13874 - 248112

D 22:53:42 File System - File: VIDEO_TS\VTS_04_0.BUP - LBA: 331434 - 331446

D 22:53:42 File System - File: VIDEO_TS\VTS_04_0.IFO - LBA: 248125 - 248137

D 22:53:42 File System - File: VIDEO_TS\VTS_04_0.VOB - LBA: 248138 - 331285

D 22:53:42 File System - File: VIDEO_TS\VTS_04_1.VOB - LBA: 331286 - 331433

D 22:53:42 File System - File: VIDEO_TS\VTS_05_0.BUP - LBA: 3771869 - 3771921

D 22:53:42 File System - File: VIDEO_TS\VTS_05_0.IFO - LBA: 331447 - 331499

D 22:53:42 File System - File: VIDEO_TS\VTS_05_1.VOB - LBA: 331500 - 855771

D 22:53:42 File System - File: VIDEO_TS\VTS_05_2.VOB - LBA: 855772 - 1380043

D 22:53:42 File System - File: VIDEO_TS\VTS_05_3.VOB - LBA: 1380044 - 1904315

D 22:53:42 File System - File: VIDEO_TS\VTS_05_4.VOB - LBA: 1904316 - 2428587

D 22:53:42 File System - File: VIDEO_TS\VTS_05_5.VOB - LBA: 2428588 - 2952859

D 22:53:42 File System - File: VIDEO_TS\VTS_05_6.VOB - LBA: 2952860 - 3477131

D 22:53:42 File System - File: VIDEO_TS\VTS_05_7.VOB - LBA: 3477132 - 3771868

D 22:53:42 File System - File: VIDEO_TS\VTS_06_0.BUP - LBA: 4117224 - 4117234

D 22:53:42 File System - File: VIDEO_TS\VTS_06_0.IFO - LBA: 3771922 - 3771932

D 22:53:42 File System - File: VIDEO_TS\VTS_06_1.VOB - LBA: 3771933 - 4117223

D 22:53:42 File System - File: VIDEO_TS\VTS_07_0.BUP - LBA: 4121070 - 4121076

D 22:53:42 File System - File: VIDEO_TS\VTS_07_0.IFO - LBA: 4117235 - 4117241

D 22:53:42 File System - File: VIDEO_TS\VTS_07_1.VOB - LBA: 4117242 - 4121069

D 22:53:42 GetIFOLayerBreakPositions - Start/End LBA Match - File: VTS_05_4.VOB

D 22:53:42 Potential Layer Break Position! - LBA: 2060544 (VTS_05, PGC: 4, Cell: 1, SPLIP Flag: No)

I 22:53:47 Operation Started!

I 22:53:47 Source File: D:\Images\AD_S3_D2.MDS

I 22:53:47 Source File Sectors: 4,121,078 (MODE1/2048)

I 22:53:47 Source File Size: 8,439,967,744 bytes

I 22:53:47 Source File Volume Identifier: AD_S3_D2

I 22:53:47 Source File Implementation Identifier: MEI

I 22:53:47 Source File File System(s): ISO9660, UDF (1.02)

I 22:53:47 Destination Device: [1:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)

I 22:53:47 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)

I 22:53:47 Destination Media Sectors: 4,173,824

I 22:53:47 Write Mode: DVD

I 22:53:47 Write Type: DAO

I 22:53:47 Write Speed: 6x

I 22:53:47 Link Size: Auto

I 22:53:47 Test Mode: No

I 22:53:47 BURN-Proof: Enabled

I 22:53:47 Optimal L0 Data Zone Capacity: 2,060,544

I 22:53:47 Optimal L0 Data Zone Method: Copied From Original Disc

D 22:54:04 Device Buffer Size: 1,605,632 bytes.

D 22:54:04 Device Buffer Available: 1,605,632 bytes.

I 22:54:04 Filling Buffer...

I 22:54:09 Writing LeadIn...

I 22:54:20 Writing Image...

I 22:54:20 Writing Layer 0... (LBA: 0 - 2060543)

I 23:03:03 Writing Layer 1... (LBA: 2060544 - 4121077)

I 23:12:06 Synchronising Cache...

I 23:12:07 Closing Track...

I 23:12:14 Finalising Disc...

I 23:12:49 Image MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 23:12:49 Exporting Graph Data...

I 23:12:49 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_12-31-2006_10-53_PM_MKM-001-00_6x_AD_S3_D2.ibg

I 23:12:49 Export Successfully Completed!

I 23:12:49 Operation Successfully Completed! - Duration: 00:19:02

I 23:12:49 Average Write Rate: 7,739 KB/s (5.6x) - Maximum Write Rate: 8,375 KB/s (6.0x)

I 23:12:49 Cycling Tray before Verify...

I 23:13:15 Device Ready!

I 23:13:15 Operation Started!

I 23:13:15 Source Device: [1:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)

I 23:13:15 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)

I 23:13:15 Image File: D:\Images\AD_S3_D2.MDS

I 23:13:15 Image File Sectors: 4,121,078 (MODE1/2048)

I 23:13:15 Image File Size: 8,439,967,744 bytes

I 23:13:15 Image File Volume Identifier: AD_S3_D2

I 23:13:15 Image File Implementation Identifier: MEI

I 23:13:15 Image File File System(s): ISO9660, UDF (1.02)

I 23:13:16 Verifying Sectors...

I 23:32:12 Image MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 23:32:12 Exporting Graph Data...

I 23:32:12 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_12-31-2006_10-53_PM_MKM-001-00_6x_AD_S3_D2.ibg

I 23:32:12 Export Successfully Completed!

I 23:32:12 Operation Successfully Completed! - Duration: 00:18:56

I 23:32:12 Average Verify Rate: 7,261 KB/s (5.2x) - Maximum Verify Rate: 10,528 KB/s (7.6x)

D 00:19:29 Disc Capacity: 4121087

I 00:19:52 Operation Started!

I 00:19:52 Source Device: [1:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)

I 00:19:52 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x, 8x)

I 00:19:52 Image File: D:\Images\AD_S3_D2.MDS

I 00:19:52 Image File Sectors: 4,121,078 (MODE1/2048)

I 00:19:52 Image File Size: 8,439,967,744 bytes

I 00:19:52 Image File Volume Identifier: AD_S3_D2

I 00:19:52 Image File Implementation Identifier: MEI

I 00:19:52 Image File File System(s): ISO9660, UDF (1.02)

I 00:19:52 Verifying Sectors...

I 00:38:58 Device MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 00:38:58 Device (Padded) MD5: 0cb1131dd42505be8c9e8adb829ff9e4

I 00:38:58 Image MD5: 582a7a08c07de71b9e54ae2b7390ae1f

I 00:39:01 Exporting Graph Data...

I 00:39:02 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_1-1-2007_12-19_AM_MKM-001-00_AD_S3_D2.ibg

I 00:39:02 Export Successfully Completed!

I 00:39:02 Operation Successfully Completed! - Duration: 00:19:06

I 00:39:02 Average Verify Rate: 7,204 KB/s (5.2x) - Maximum Verify Rate: 10,528 KB/s (7.6x)

D 00:39:28 Disc Capacity: 4121087

Share this post


Link to post
Share on other sites
A full log with F6 debug info should also tell you (me) why the device MD5 could not be calculated - i.e. where a call to the API's failed.

 

That said, there were glitches in the MD5 code that have now been fixed. Maybe you're just hitting one of those.

 

So, any further info on this issue? I now have had it happen on a different computer which (of course) has a completely separate installation of ImgBurn 2.1.0.0. However, in this case, a verification afterward won't reveal the device .MD5 value....

 

Strange, but this seems to have become an issue after the new year. Never one instance from when 2.1.0.0 was released in September until this January....seems improbable that it is date related....but.

 

I'd be happy to beta test any release that may have a fix against these images.

 

Thanks,

Ford Man

Share this post


Link to post
Share on other sites

Well your log show you have the same issue as the person who originally reported the issue to me.

 

It's failing, but not in a big way - and only the 'big way' stuff has extra logging behind it - hence why you don't get any.

 

I'm sure the work I've already done in this area is enough to get it working again on your PC's. Maybe I will just slip you a beta the day before I plan to release it though so you can double check it's ok now.

Share this post


Link to post
Share on other sites
Maybe I will just slip you a beta the day before

:o !!! He tricked me like that too fordman

Share this post


Link to post
Share on other sites
Well your log show you have the same issue as the person who originally reported the issue to me.

 

It's failing, but not in a big way - and only the 'big way' stuff has extra logging behind it - hence why you don't get any.

 

I'm sure the work I've already done in this area is enough to get it working again on your PC's. Maybe I will just slip you a beta the day before I plan to release it though so you can double check it's ok now.

 

OK, at least glad to know that others are experiencing it also. I'm somewhat fanatical about ensuring that the data matches before I delete an image, so this MD5 feature is highly desirable. I had even tried an uninstall and reinstallation, but no improvement was noted. The fact that the behavior can be repeated seems to point that it is related to the image content itself...

 

By the way, on the second machine where I was able to reproduce the behavior, but it also failed on the separate verification, I have more to report.

 

The first part still holds - the device MD5 is not calculated directly after burning on my internal (IDE) Pioneer DVR-111L. I originally reported that a separate verification also fails, and that is true when I decided to verify the disc in my external (IEEE1394) Plextor PX-740A. However, I re-did the verification in yet another internal drive, my Plextor PX-716A, and that time the device MD5 showed in the separate verification. So, perhaps the IEEE1394 to IDE interface is responsible for the omission of the device MD5 in that case? I know that DVDInfoPro does not show all media info detail when using that external drive, compared to when I use either internal drive... However, all previous observations of the missing device MD5 behavior were observed using internal IDE drives only.

Edited by fordman

Share this post


Link to post
Share on other sites
Maybe I will just slip you a beta the day before

:o !!! He tricked me like that too fordman

 

:D

 

I think I read it the way you did at first, but I THINK LUK may mean that he'll pass the beta to me the day before he releases the beta, not the day before the final release????

Edited by fordman

Share this post


Link to post
Share on other sites

=)) Seriously for a sec I think LUK means he will let you test a beta the day before he intends to release the next update !!

 

Altho maybe :poof: !! :D

Share this post


Link to post
Share on other sites

The MD5 issue is nothing to do with where the data is coming from / going to. Those functions only work with ImgBurn's internal buffer so the original location of the data doesn't even come into it.

 

It was simply an implementation bug. Sometimes it works, sometimes it doesn't. It the luck of the draw, depending on how your OS feels that day and what's in the memory.

Share this post


Link to post
Share on other sites
=)) Seriously for a sec I think LUK means he will let you test a beta the day before he intends to release the next update !!

 

Altho maybe :poof: !! :D

 

OK - yes that makes more sense. I did some limited testing on a prior beta, but that was after you beta testers already had it. It makes sense that he wants to make sure it was stamped out before the final release...

Share this post


Link to post
Share on other sites
It was simply an implementation bug. Sometimes it works, sometimes it doesn't. It the luck of the draw, depending on how your OS feels that day and what's in the memory.

 

Hmmm, I have to admit that since I didn't record the same images again (dual layer, so still don't want to waste media), I can't verify whether it would happen a second time during an immediate verify after recording. It has still not happened on verification of a single layer image, otherwise I'd be willing to re-test that...

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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