Jump to content

fordman

Members
  • Posts

    184
  • Joined

  • Last visited

Posts posted by fordman

  1. Buffers emptying are usually a sign that the machine is doing something and requires memory/CPU etc. I know it is restrictive, but it might pay for you to turn off emails and the like while burning. Not sure of your rig - a dual core should lessen fluctuating buffer issues. In any event, this does not address your issue of the device MD5.

     

    Regards

     

    Yep, I always kill most (antivirus stays) background processes and then only burn without running anything else. Yet for some reason her computer really seemed to bog down when reading from the same space as the OS, and it is in UltraDMA-5 mode. It seemed that it could always recover before the 256MB cache completely emptied and would allow a constant 6X burn. Now that I use a secondary hard drive, I can lower the buffer to the default 20MB and leave everything open without issue. Her computer is a Celeron 2.0 Ghz with 1GB RAM. My home burning machine is a 2.66 Ghz P4 (no hyperthreading) with 2 GB RAM...

  2. Looking forward to the feedback. BTW: Even with 2Gb, I reckon a 256Mb buffer is a trifle high - that's more than 10% of your memory. I have 1Gb and run at 40Mb. In discussions with LUK while testing, his view was little if any benefit would be gained over 40Mb (which is what I run with consistent success) and that is the default for all 1Gb+ rigs. I am sure he'll correct me if I have misunderstood him.

     

    Regards

     

    OK, I reset back to the defaults (which apparently is still 20 MB buffer on my GF's machine - I'll reset the home later tonight). I then exited ImgBurn after resetting to default settings, reopened ImgBurn and burned the same single layer image three times without closing ImgBurn. My results were as follows:

     

    success -> success -> failure

     

    after which I stopped... So, the issue seems independent of the buffer size, and will need LUKs changes on the machines I burn with.

     

    As for the best buffer size, I added a secondary hard drive to my GF's machine back in January, and 20 MB buffer seems to suffice without having the writing stop to refill the buffer, etc. However before that when she only had one hard drive and the image was on the same (only) drive as the OS, then the buffer would empty all the time, writing would suspend, etc. dropping my average write rate well below the 6X I had set! I found that 256 MB seemed to take care of that issue with that single drive.

     

    LUK: I suppose when I said ImgBurn installation was the only thing I had done to my GF's machine, I was referring to software, which is what I thought you were referring to. I did add a hard drive recently, and a Pioneer DVD writer months before that.

  3. Wonder how things would go with the read buffer at default? Just musing, but could this have anything at all to do with it?

     

    Regards

     

    While the best fix will be what LUK has decided to incorporate, I will lower my buffer back to 20 MB until he releases that version and will let you know.

     

    I burned my 4th DL burn at home and it (like the previous 3) failed to show the device MD5, so perhaps it DOES think it's done buring when it gets 256MB from the end and calls for the device MD5, even though it's not finished yet? Just hazarding a guess based on what LUK said it was doing to cause this.

     

    Stay tuned over the next few days, and I'll see if a lower buffer helps...

  4. In response to a question posted in your previous reply, no, the MD5 isn't used to determine if it was a success verify or not.

     

    The seemingly random nature of this problem made is very difficult to pinpoint the actual cause. Unlike most bugs, this one wasn't something you could reproduce 100% of the time given a certain image file etc. Those kinds of bugs are easy to locate and fix, this one was not.

     

    I'd like to take this opportunity to apologise for being human and thank you for the time you've spent reporting the issue (for a 2nd time!), even though I was being quite rude and you could quite easily have just told me to F off!

     

    Ok, then a sector by sector comparison is used, I suppose.

     

    Perhaps your machine is fast enough that the MD5 string was always available by the time it was queried.

     

    No need to apologize - I admit I was surprised by your response because you have always been so open to constructive comments I've made in the past, but I also understand wanting to defend "your baby." You've spent a lot of time on your programs and I certainly don't have the programming expertise you do, so I only hope to help troubleshoot usability issues.

     

    Thanks again for taking another look "outside the box!" :thumbup:

     

    FordMan

  5. Sorry fordman, I know that what I put earlier was pretty harsh!

     

    It's just that from my point of view - i.e. looking at the code, line by line - I simply cannot fault it!

     

    After the initial problems you were having in 2.1.0.0, I went through it and quickly found the issue and fixed it.

     

    OK, but I know you've made similar statements about not being able to fault the code before, and later came back to state that you did find an issue. Unless it is the API itself, perhaps that will happen again.

     

    Also, this and your prior post in this thread make it sound like I was the only one encountering this issue. However in thread http://forum.imgburn.com/index.php?s=&...ost&p=35232 you stated that my log showed I was experiencing the same issue as the other person that reported it, so at best I'm the second person to have had the issue. You also mentioned glitches in the MD5 code in that thread, so the changes were presumably being made for more than just me. Also dirio49 in this thread appears to have the same issue with 2.2.0.0, so statistically, I'm sure there are others out there.

     

    Perhaps it has something to do with timing, or other changes I've made in ImgBurn - for instance I increased the read buffer in both places to 256MB from the default 20MB, since I have 2GB RAM on my machine, and my girlfriend has 1GB RAM on hers. It seems to give burns that never dip below the max burn speed, except for recalibration.

     

    After my previous post in this thread, I continued burning 6 more single layer images on my GF's PC. This time, I chose to leave ImgBurn open between burns. The status of the device MD5 displaying in the log were as follows:

     

    success -> fail -> success -> success -> fail -> success

     

    so one-third failure rate for that batch. I won't bother to provide the log, unless you want it. It basically follows the others I've posted, device MD5 doesn't show, but no other information is shown to give a clue why.

     

    I then later returned home and burned two dual layer images (had only burned the one dual layer image with 2.2.0.0 up to that point and that failed to show the device MD5), and both new images failed to show the device MD5 after verification - so I'm 0 for 3 at home. I will try some dual layer images on the GF's machine, and some single layer ones at home, but it appears that whatever code change was made to work around this issue has actually made things worse for me. Again, the logs are the same - no additional info to show why the device MD5 isn't shown.

     

    I'll let this issue go for now, and will experiment with lowering my read buffer back to settings that others are likely using to see what happens.

     

    However, here's is a question of great interest to me:

     

    How does ImgBurn determine whether a verification was successful? Is it calculating both the device and image MD5 values and them comparing them? If so, when the device MD5 fails to show, yet the verify operation says is completed successfully, what does that mean? Is the device actually being calculated (even if not shown) and compared to the image MD5 successfully? I'm curious, because I would like to have confidence at least in the determination that the verification was successful. Otherwise I suppose I can always go back to doing separate file based verification after the burn.

     

    Not only did I fix it, but there's not a single error that could slip past without something being logged - and you've no such log entries!

     

    So the only thing that can be failing is the API itself - even though it's still returning that it completed successfully.

     

    Hopefully you see / agree that those sorts of problems are totally out of my control. I don't write the cryptography DLLs in windows!

     

    As I said in my last post, I've now included logging for times when the API's complete successfully but when the data they return could be invalid or not quite what I'm expecting.

     

    I will email you a beta in due course and hopefully we'll get to the bottom of this problem.

     

    Thanks, I do appreciate your product and welcome the opportunity to help nail down the issue. Given the fact that it occurs both on my home PC and my GF's PC (with ImgBurn being my only addition), then my guess is that it is due to some combination of settings I have changed from the defaults, i.e. read buffer, since I have configured both ImgBurn installations the same...

     

    Regards,

    FordMan

  6. OK, I reproduced the error on my girfriend's PC also!

     

    After one successful burn earlier today, I burned 3 DVDs this evening, closing ImgBurn after each burn and and reopening to do the next burn.

     

    To reitereate, I open ImgBurn, press F6 for debug info and burn with verification. On the 3rd burn, the device MD5 failed to show! So that makes two PCs I've experienced it on, and of course dirio49 has verified it also. Again, the only addition I've made to my girlfriend's PC is ImgBurn.

     

    If anyone else finds this behavior, please post your experience here. If there are enough that experience it, like there apparently was in 2.1.0.0, perhaps it will again be officially recognized as an outstanding issue.

     

    FordMan

     

    My log follows:

     

    I 20:50:41 ImgBurn Version 2.2.0.0 started!

    I 20:50:41 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

    I 20:50:41 Total Physical Memory: 1,047,024 KB - Available: 558,996 KB

    I 20:50:41 Initialising SPTI...

    I 20:50:41 Searching for SCSI / ATAPI devices...

    I 20:50:42 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW/RAM!

    W 20:50:45 Program 'Debug Mode' has been Enabled!

    I 20:51:02 Operation Started!

    I 20:51:02 Source File: D:\Images\OS_DVD5.ISO

    I 20:51:02 Source File Sectors: 2,290,416 (MODE1/2048)

    I 20:51:02 Source File Size: 4,690,771,968 bytes

    I 20:51:02 Source File Volume Identifier: OS

    I 20:51:02 Source File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER!

    I 20:51:02 Source File Implementation Identifier: ImgBurn

    I 20:51:02 Source File File System(s): ISO9660, UDF (1.02)

    I 20:51:02 Destination Device: [1:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)

    I 20:51:02 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x)

    I 20:51:02 Destination Media Sectors: 2,295,104

    I 20:51:02 Write Mode: DVD

    I 20:51:02 Write Type: DAO

    I 20:51:02 Write Speed: 6x

    I 20:51:02 Link Size: Auto

    I 20:51:02 Test Mode: No

    I 20:51:02 BURN-Proof: Enabled

    D 20:51:03 Device Buffer Size: 1,605,632 bytes.

    D 20:51:03 Device Buffer Available: 1,605,632 bytes.

    I 20:51:03 Filling Buffer... (256 MB)

    I 20:51:09 Writing LeadIn...

    I 20:51:24 Writing Image...

    I 21:00:52 Synchronising Cache...

    I 21:00:53 Closing Track...

    I 21:00:58 Finalising Disc...

    I 21:01:20 Image MD5: b7ef64bfea21fa624b7c12e23558281b

    I 21:01:20 Exporting Graph Data...

    I 21:01:20 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_2-18-2007_8-51_PM_MCC-004-00_6x_OS.ibg

    I 21:01:20 Export Successfully Completed!

    I 21:01:20 Operation Successfully Completed! - Duration: 00:10:18

    I 21:01:20 Average Write Rate: 8,064 KB/s (5.8x) - Maximum Write Rate: 8,403 KB/s (6.1x)

    I 21:01:20 Cycling Tray before Verify...

    I 21:01:40 Device Ready!

    D 21:01:40 File System - File: ._Mac Clickme - LBA: 2285704 - 2286336 - Size: 1,296,321 bytes

    D 21:01:40 File System - File: AUTORUN.INF - LBA: 2286337 - 2286337 - Size: 34 bytes

    D 21:01:40 File System - File: Mac Clickme - LBA: 2286338 - 2286356 - Size: 37,598 bytes

    D 21:01:40 File System - File: PC_Clickme.exe - LBA: 2286357 - 2286945 - Size: 1,205,666 bytes

    D 21:01:40 File System - File: main.jpg - LBA: 2286946 - 2287046 - Size: 205,176 bytes

    D 21:01:40 File System - File: weblink.dxr - LBA: 2287047 - 2287610 - Size: 1,153,258 bytes

    D 21:01:40 File System - File: Files\go.exe - LBA: 2287611 - 2287638 - Size: 57,344 bytes

    D 21:01:40 File System - File: Files\weblink.dxr - LBA: 2287639 - 2288202 - Size: 1,153,322 bytes

    D 21:01:40 File System - File: JACKET_P\J00___5L.MP2 - LBA: 591 - 635 - Size: 92,160 bytes

    D 21:01:40 File System - File: JACKET_P\J00___5M.MP2 - LBA: 636 - 640 - Size: 10,240 bytes

    D 21:01:40 File System - File: JACKET_P\J00___5S.MP2 - LBA: 641 - 642 - Size: 4,096 bytes

    D 21:01:40 File System - File: VIDEO_TS\VIDEO_TS.BUP - LBA: 7751 - 7792 - Size: 86,016 bytes

    D 21:01:40 File System - File: VIDEO_TS\VIDEO_TS.IFO - LBA: 643 - 684 - Size: 86,016 bytes

    D 21:01:40 File System - File: VIDEO_TS\VIDEO_TS.VOB - LBA: 685 - 7750 - Size: 14,471,168 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_0.BUP - LBA: 1455069 - 1455110 - Size: 86,016 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_0.IFO - LBA: 7793 - 7834 - Size: 86,016 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_0.VOB - LBA: 7835 - 78891 - Size: 145,524,736 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_1.VOB - LBA: 78892 - 603178 - Size: 1,073,739,776 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_2.VOB - LBA: 603179 - 1127465 - Size: 1,073,739,776 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_01_3.VOB - LBA: 1127466 - 1455068 - Size: 670,930,944 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_02_0.BUP - LBA: 1871988 - 1872003 - Size: 32,768 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_02_0.IFO - LBA: 1455111 - 1455126 - Size: 32,768 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_02_1.VOB - LBA: 1455127 - 1871987 - Size: 853,731,328 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_03_0.BUP - LBA: 1931332 - 1931339 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_03_0.IFO - LBA: 1872004 - 1872011 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_03_1.VOB - LBA: 1872012 - 1931331 - Size: 121,487,360 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_04_0.BUP - LBA: 1995914 - 1995921 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_04_0.IFO - LBA: 1931340 - 1931347 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_04_1.VOB - LBA: 1931348 - 1995913 - Size: 132,231,168 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_05_0.BUP - LBA: 2008688 - 2008694 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_05_0.IFO - LBA: 1995922 - 1995928 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_05_1.VOB - LBA: 1995929 - 2008687 - Size: 26,130,432 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_06_0.BUP - LBA: 2020389 - 2020396 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_06_0.IFO - LBA: 2008695 - 2008702 - Size: 16,384 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_06_1.VOB - LBA: 2008703 - 2020388 - Size: 23,932,928 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_07_0.BUP - LBA: 2020558 - 2020581 - Size: 49,152 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_07_0.IFO - LBA: 2020397 - 2020420 - Size: 49,152 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_07_1.VOB - LBA: 2020421 - 2020557 - Size: 280,576 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_08_0.BUP - LBA: 2214791 - 2214804 - Size: 28,672 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_08_0.IFO - LBA: 2020582 - 2020595 - Size: 28,672 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_08_1.VOB - LBA: 2020596 - 2214790 - Size: 397,711,360 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_09_0.BUP - LBA: 2217034 - 2217040 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_09_0.IFO - LBA: 2214805 - 2214811 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_09_1.VOB - LBA: 2214812 - 2217033 - Size: 4,550,656 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_10_0.BUP - LBA: 2230660 - 2230666 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_10_0.IFO - LBA: 2217041 - 2217047 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_10_1.VOB - LBA: 2217048 - 2230659 - Size: 27,877,376 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_11_0.BUP - LBA: 2230690 - 2230696 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_11_0.IFO - LBA: 2230667 - 2230673 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_11_1.VOB - LBA: 2230674 - 2230677 - Size: 8,192 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_12_0.BUP - LBA: 2230720 - 2230726 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_12_0.IFO - LBA: 2230697 - 2230703 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_12_1.VOB - LBA: 2230704 - 2230707 - Size: 8,192 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_13_0.BUP - LBA: 2230750 - 2230756 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_13_0.IFO - LBA: 2230727 - 2230733 - Size: 14,336 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_13_1.VOB - LBA: 2230734 - 2230737 - Size: 8,192 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_14_0.BUP - LBA: 2262342 - 2262350 - Size: 18,432 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_14_0.IFO - LBA: 2230757 - 2230765 - Size: 18,432 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_14_0.VOB - LBA: 2230766 - 2231411 - Size: 1,323,008 bytes

    D 21:01:40 File System - File: VIDEO_TS\VTS_14_1.VOB - LBA: 2231412 - 2262341 - Size: 63,344,640 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_15_0.BUP - LBA: 2276681 - 2276686 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_15_0.IFO - LBA: 2262351 - 2262356 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_15_1.VOB - LBA: 2262357 - 2276680 - Size: 29,335,552 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_16_0.BUP - LBA: 2283757 - 2283763 - Size: 14,336 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_16_0.IFO - LBA: 2276687 - 2276693 - Size: 14,336 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_16_1.VOB - LBA: 2276694 - 2283756 - Size: 14,465,024 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_17_0.BUP - LBA: 2283792 - 2283803 - Size: 24,576 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_17_0.IFO - LBA: 2283764 - 2283775 - Size: 24,576 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_17_1.VOB - LBA: 2283776 - 2283779 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_18_0.BUP - LBA: 2283826 - 2283831 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_18_0.IFO - LBA: 2283804 - 2283809 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_18_1.VOB - LBA: 2283810 - 2283813 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_19_0.BUP - LBA: 2283854 - 2283859 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_19_0.IFO - LBA: 2283832 - 2283837 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_19_1.VOB - LBA: 2283838 - 2283841 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_20_0.BUP - LBA: 2283882 - 2283887 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_20_0.IFO - LBA: 2283860 - 2283865 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_20_1.VOB - LBA: 2283866 - 2283869 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_21_0.BUP - LBA: 2283910 - 2283915 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_21_0.IFO - LBA: 2283888 - 2283893 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_21_1.VOB - LBA: 2283894 - 2283897 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_22_0.BUP - LBA: 2283938 - 2283943 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_22_0.IFO - LBA: 2283916 - 2283921 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_22_1.VOB - LBA: 2283922 - 2283925 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_23_0.BUP - LBA: 2283966 - 2283971 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_23_0.IFO - LBA: 2283944 - 2283949 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_23_1.VOB - LBA: 2283950 - 2283953 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_24_0.BUP - LBA: 2283994 - 2283999 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_24_0.IFO - LBA: 2283972 - 2283977 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_24_1.VOB - LBA: 2283978 - 2283981 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_25_0.BUP - LBA: 2284022 - 2284027 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_25_0.IFO - LBA: 2284000 - 2284005 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_25_1.VOB - LBA: 2284006 - 2284009 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_26_0.BUP - LBA: 2284050 - 2284055 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_26_0.IFO - LBA: 2284028 - 2284033 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_26_1.VOB - LBA: 2284034 - 2284037 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_27_0.BUP - LBA: 2284078 - 2284083 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_27_0.IFO - LBA: 2284056 - 2284061 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_27_1.VOB - LBA: 2284062 - 2284065 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_28_0.BUP - LBA: 2284106 - 2284111 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_28_0.IFO - LBA: 2284084 - 2284089 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_28_1.VOB - LBA: 2284090 - 2284093 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_29_0.BUP - LBA: 2284134 - 2284139 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_29_0.IFO - LBA: 2284112 - 2284117 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_29_1.VOB - LBA: 2284118 - 2284121 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_30_0.BUP - LBA: 2284162 - 2284167 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_30_0.IFO - LBA: 2284140 - 2284145 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_30_1.VOB - LBA: 2284146 - 2284149 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_31_0.BUP - LBA: 2284190 - 2284195 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_31_0.IFO - LBA: 2284168 - 2284173 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_31_1.VOB - LBA: 2284174 - 2284177 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_32_0.BUP - LBA: 2284218 - 2284223 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_32_0.IFO - LBA: 2284196 - 2284201 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_32_1.VOB - LBA: 2284202 - 2284205 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_33_0.BUP - LBA: 2284246 - 2284251 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_33_0.IFO - LBA: 2284224 - 2284229 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_33_1.VOB - LBA: 2284230 - 2284233 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_34_0.BUP - LBA: 2284274 - 2284279 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_34_0.IFO - LBA: 2284252 - 2284257 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_34_1.VOB - LBA: 2284258 - 2284261 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_35_0.BUP - LBA: 2284302 - 2284307 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_35_0.IFO - LBA: 2284280 - 2284285 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_35_1.VOB - LBA: 2284286 - 2284289 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_36_0.BUP - LBA: 2284330 - 2284335 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_36_0.IFO - LBA: 2284308 - 2284313 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_36_1.VOB - LBA: 2284314 - 2284317 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_37_0.BUP - LBA: 2284358 - 2284363 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_37_0.IFO - LBA: 2284336 - 2284341 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_37_1.VOB - LBA: 2284342 - 2284345 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_38_0.BUP - LBA: 2284386 - 2284391 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_38_0.IFO - LBA: 2284364 - 2284369 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_38_1.VOB - LBA: 2284370 - 2284373 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_39_0.BUP - LBA: 2284414 - 2284419 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_39_0.IFO - LBA: 2284392 - 2284397 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_39_1.VOB - LBA: 2284398 - 2284401 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_40_0.BUP - LBA: 2284442 - 2284447 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_40_0.IFO - LBA: 2284420 - 2284425 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_40_1.VOB - LBA: 2284426 - 2284429 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_41_0.BUP - LBA: 2284470 - 2284475 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_41_0.IFO - LBA: 2284448 - 2284453 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_41_1.VOB - LBA: 2284454 - 2284457 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_42_0.BUP - LBA: 2284498 - 2284503 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_42_0.IFO - LBA: 2284476 - 2284481 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_42_1.VOB - LBA: 2284482 - 2284485 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_43_0.BUP - LBA: 2284526 - 2284531 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_43_0.IFO - LBA: 2284504 - 2284509 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_43_1.VOB - LBA: 2284510 - 2284513 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_44_0.BUP - LBA: 2284554 - 2284559 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_44_0.IFO - LBA: 2284532 - 2284537 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_44_1.VOB - LBA: 2284538 - 2284541 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_45_0.BUP - LBA: 2284582 - 2284587 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_45_0.IFO - LBA: 2284560 - 2284565 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_45_1.VOB - LBA: 2284566 - 2284569 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_46_0.BUP - LBA: 2284610 - 2284615 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_46_0.IFO - LBA: 2284588 - 2284593 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_46_1.VOB - LBA: 2284594 - 2284597 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_47_0.BUP - LBA: 2284638 - 2284643 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_47_0.IFO - LBA: 2284616 - 2284621 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_47_1.VOB - LBA: 2284622 - 2284625 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_48_0.BUP - LBA: 2284666 - 2284671 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_48_0.IFO - LBA: 2284644 - 2284649 - Size: 12,288 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_48_1.VOB - LBA: 2284650 - 2284653 - Size: 8,192 bytes

    D 21:01:41 File System - File: VIDEO_TS\VTS_49_0.BUP - LBA: 2284694 - 2284699 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_49_0.IFO - LBA: 2284672 - 2284677 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_49_1.VOB - LBA: 2284678 - 2284681 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_50_0.BUP - LBA: 2284722 - 2284727 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_50_0.IFO - LBA: 2284700 - 2284705 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_50_1.VOB - LBA: 2284706 - 2284709 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_51_0.BUP - LBA: 2284756 - 2284767 - Size: 24,576 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_51_0.IFO - LBA: 2284728 - 2284739 - Size: 24,576 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_51_1.VOB - LBA: 2284740 - 2284743 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_52_0.BUP - LBA: 2284790 - 2284795 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_52_0.IFO - LBA: 2284768 - 2284773 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_52_1.VOB - LBA: 2284774 - 2284777 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_53_0.BUP - LBA: 2284818 - 2284823 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_53_0.IFO - LBA: 2284796 - 2284801 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_53_1.VOB - LBA: 2284802 - 2284805 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_54_0.BUP - LBA: 2284846 - 2284851 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_54_0.IFO - LBA: 2284824 - 2284829 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_54_1.VOB - LBA: 2284830 - 2284833 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_55_0.BUP - LBA: 2284874 - 2284879 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_55_0.IFO - LBA: 2284852 - 2284857 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_55_1.VOB - LBA: 2284858 - 2284861 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_56_0.BUP - LBA: 2284902 - 2284907 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_56_0.IFO - LBA: 2284880 - 2284885 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_56_1.VOB - LBA: 2284886 - 2284889 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_57_0.BUP - LBA: 2284930 - 2284935 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_57_0.IFO - LBA: 2284908 - 2284913 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_57_1.VOB - LBA: 2284914 - 2284917 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_58_0.BUP - LBA: 2284958 - 2284963 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_58_0.IFO - LBA: 2284936 - 2284941 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_58_1.VOB - LBA: 2284942 - 2284945 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_59_0.BUP - LBA: 2284986 - 2284991 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_59_0.IFO - LBA: 2284964 - 2284969 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_59_1.VOB - LBA: 2284970 - 2284973 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_60_0.BUP - LBA: 2285014 - 2285019 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_60_0.IFO - LBA: 2284992 - 2284997 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_60_1.VOB - LBA: 2284998 - 2285001 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_61_0.BUP - LBA: 2285042 - 2285047 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_61_0.IFO - LBA: 2285020 - 2285025 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_61_1.VOB - LBA: 2285026 - 2285029 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_62_0.BUP - LBA: 2285070 - 2285075 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_62_0.IFO - LBA: 2285048 - 2285053 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_62_1.VOB - LBA: 2285054 - 2285057 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_63_0.BUP - LBA: 2285098 - 2285103 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_63_0.IFO - LBA: 2285076 - 2285081 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_63_1.VOB - LBA: 2285082 - 2285085 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_64_0.BUP - LBA: 2285126 - 2285131 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_64_0.IFO - LBA: 2285104 - 2285109 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_64_1.VOB - LBA: 2285110 - 2285113 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_65_0.BUP - LBA: 2285154 - 2285159 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_65_0.IFO - LBA: 2285132 - 2285137 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_65_1.VOB - LBA: 2285138 - 2285141 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_66_0.BUP - LBA: 2285182 - 2285187 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_66_0.IFO - LBA: 2285160 - 2285165 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_66_1.VOB - LBA: 2285166 - 2285169 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_67_0.BUP - LBA: 2285210 - 2285215 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_67_0.IFO - LBA: 2285188 - 2285193 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_67_1.VOB - LBA: 2285194 - 2285197 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_68_0.BUP - LBA: 2285238 - 2285243 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_68_0.IFO - LBA: 2285216 - 2285221 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_68_1.VOB - LBA: 2285222 - 2285225 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_69_0.BUP - LBA: 2285266 - 2285271 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_69_0.IFO - LBA: 2285244 - 2285249 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_69_1.VOB - LBA: 2285250 - 2285253 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_70_0.BUP - LBA: 2285294 - 2285299 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_70_0.IFO - LBA: 2285272 - 2285277 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_70_1.VOB - LBA: 2285278 - 2285281 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_71_0.BUP - LBA: 2285322 - 2285327 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_71_0.IFO - LBA: 2285300 - 2285305 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_71_1.VOB - LBA: 2285306 - 2285309 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_72_0.BUP - LBA: 2285350 - 2285355 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_72_0.IFO - LBA: 2285328 - 2285333 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_72_1.VOB - LBA: 2285334 - 2285337 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_73_0.BUP - LBA: 2285378 - 2285383 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_73_0.IFO - LBA: 2285356 - 2285361 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_73_1.VOB - LBA: 2285362 - 2285365 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_74_0.BUP - LBA: 2285406 - 2285411 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_74_0.IFO - LBA: 2285384 - 2285389 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_74_1.VOB - LBA: 2285390 - 2285393 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_75_0.BUP - LBA: 2285434 - 2285439 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_75_0.IFO - LBA: 2285412 - 2285417 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_75_1.VOB - LBA: 2285418 - 2285421 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_76_0.BUP - LBA: 2285462 - 2285467 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_76_0.IFO - LBA: 2285440 - 2285445 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_76_1.VOB - LBA: 2285446 - 2285449 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_77_0.BUP - LBA: 2285490 - 2285495 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_77_0.IFO - LBA: 2285468 - 2285473 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_77_1.VOB - LBA: 2285474 - 2285477 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_78_0.BUP - LBA: 2285518 - 2285523 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_78_0.IFO - LBA: 2285496 - 2285501 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_78_1.VOB - LBA: 2285502 - 2285505 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_79_0.BUP - LBA: 2285546 - 2285551 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_79_0.IFO - LBA: 2285524 - 2285529 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_79_1.VOB - LBA: 2285530 - 2285533 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_80_0.BUP - LBA: 2285574 - 2285579 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_80_0.IFO - LBA: 2285552 - 2285557 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_80_1.VOB - LBA: 2285558 - 2285561 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_81_0.BUP - LBA: 2285602 - 2285607 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_81_0.IFO - LBA: 2285580 - 2285585 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_81_1.VOB - LBA: 2285586 - 2285589 - Size: 8,192 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_82_0.BUP - LBA: 2285630 - 2285635 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_82_0.IFO - LBA: 2285608 - 2285613 - Size: 12,288 bytes

    D 21:01:42 File System - File: VIDEO_TS\VTS_82_1.VOB - LBA: 2285614 - 2285617 - Size: 8,192 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_83_0.BUP - LBA: 2285658 - 2285663 - Size: 12,288 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_83_0.IFO - LBA: 2285636 - 2285641 - Size: 12,288 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_83_1.VOB - LBA: 2285642 - 2285645 - Size: 8,192 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_84_0.BUP - LBA: 2285692 - 2285703 - Size: 24,576 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_84_0.IFO - LBA: 2285664 - 2285675 - Size: 24,576 bytes

    D 21:01:43 File System - File: VIDEO_TS\VTS_84_1.VOB - LBA: 2285676 - 2285679 - Size: 8,192 bytes

    D 21:01:43 File System - File: Xtras\._Font Xtra PPC - LBA: 2288203 - 2288203 - Size: 1,991 bytes

    D 21:01:43 File System - File: Xtras\._InetUrl PPC Xtra - LBA: 2288204 - 2288204 - Size: 670 bytes

    D 21:01:43 File System - File: Xtras\._NetFile PPC Xtra - LBA: 2288205 - 2288205 - Size: 670 bytes

    D 21:01:43 File System - File: Xtras\._NetLingo PPC Xtra - LBA: 2288206 - 2288206 - Size: 670 bytes

    D 21:01:43 File System - File: Xtras\._SWA Decompression PPC Xtra - LBA: 2288207 - 2288207 - Size: 682 bytes

    D 21:01:43 File System - File: Xtras\._Sound Control - LBA: 2288208 - 2288208 - Size: 666 bytes

    D 21:01:43 File System - File: Xtras\._TextAsset PPC - LBA: 2288209 - 2288210 - Size: 2,602 bytes

    D 21:01:43 File System - File: Xtras\._TextXtra PPC - LBA: 2288211 - 2288211 - Size: 666 bytes

    D 21:01:43 File System - File: Xtras\Dirapi.dll - LBA: 2288212 - 2288747 - Size: 1,097,728 bytes

    D 21:01:43 File System - File: Xtras\DirectSound.x32 - LBA: 2288748 - 2288763 - Size: 32,768 bytes

    D 21:01:43 File System - File: Xtras\Font Xtra PPC - LBA: 2288764 - 2288959 - Size: 399,517 bytes

    D 21:01:43 File System - File: Xtras\Font Xtra.x32 - LBA: 2288960 - 2289097 - Size: 282,624 bytes

    D 21:01:43 File System - File: Xtras\INetURL.x32 - LBA: 2289098 - 2289121 - Size: 49,152 bytes

    D 21:01:43 File System - File: Xtras\Iml32.dll - LBA: 2289122 - 2289395 - Size: 561,152 bytes

    D 21:01:43 File System - File: Xtras\InetUrl PPC Xtra - LBA: 2289396 - 2289416 - Size: 42,903 bytes

    D 21:01:43 File System - File: Xtras\MacroMix.x32 - LBA: 2289417 - 2289442 - Size: 53,248 bytes

    D 21:01:43 File System - File: Xtras\NetFile PPC Xtra - LBA: 2289443 - 2289475 - Size: 67,213 bytes

    D 21:01:43 File System - File: Xtras\NetFile.x32 - LBA: 2289476 - 2289501 - Size: 53,248 bytes

    D 21:01:43 File System - File: Xtras\NetLingo PPC Xtra - LBA: 2289502 - 2289526 - Size: 50,974 bytes

    D 21:01:43 File System - File: Xtras\NetLingo.x32 - LBA: 2289527 - 2289550 - Size: 49,152 bytes

    D 21:01:43 File System - File: Xtras\Proj.dll - LBA: 2289551 - 2289628 - Size: 159,744 bytes

    D 21:01:43 File System - File: Xtras\SWA Decompression PPC Xtra - LBA: 2289629 - 2289661 - Size: 66,090 bytes

    D 21:01:43 File System - File: Xtras\SWADCmpr.x32 - LBA: 2289662 - 2289695 - Size: 69,632 bytes

    D 21:01:43 File System - File: Xtras\Sound Control - LBA: 2289696 - 2289723 - Size: 55,559 bytes

    D 21:01:43 File System - File: Xtras\Sound Control.x32 - LBA: 2289724 - 2289749 - Size: 53,248 bytes

    D 21:01:43 File System - File: Xtras\Text Asset.x32 - LBA: 2289750 - 2289797 - Size: 98,304 bytes

    D 21:01:43 File System - File: Xtras\TextAsset PPC - LBA: 2289798 - 2289858 - Size: 124,301 bytes

    D 21:01:43 File System - File: Xtras\TextXtra PPC - LBA: 2289859 - 2290109 - Size: 512,532 bytes

    D 21:01:43 File System - File: Xtras\TextXtra.x32 - LBA: 2290110 - 2290279 - Size: 348,160 bytes

    D 21:01:43 File System - File: Xtras\msvcrt.dll - LBA: 2290280 - 2290410 - Size: 266,293 bytes

    D 21:01:43 __ParseFS - Found 300 Files

    I 21:01:43 Operation Started!

    I 21:01:43 Source Device: [1:0:0] PIONEER DVD-RW DVR-111L 8.29 (E:) (ATA)

    I 21:01:43 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x)

    I 21:01:43 Image File: D:\Images\OS_DVD5.ISO

    I 21:01:43 Image File Sectors: 2,290,416 (MODE1/2048)

    I 21:01:43 Image File Size: 4,690,771,968 bytes

    I 21:01:43 Image File Volume Identifier: OS

    I 21:01:43 Image File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER!

    I 21:01:43 Image File Implementation Identifier: ImgBurn

    I 21:01:43 Image File File System(s): ISO9660, UDF (1.02)

    I 21:01:44 Verifying Sectors... (LBA: 0 - 2290415)

    I 21:08:06 Image MD5: b7ef64bfea21fa624b7c12e23558281b

    I 21:08:06 Exporting Graph Data...

    I 21:08:06 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_2-18-2007_8-51_PM_MCC-004-00_6x_OS.ibg

    I 21:08:06 Export Successfully Completed!

    I 21:08:06 Operation Successfully Completed! - Duration: 00:06:23

    I 21:08:06 Average Verify Rate: 11,991 KB/s (8.7x) - Maximum Verify Rate: 17,394 KB/s (12.6x)

  7. but then Once i got both and then the other time I got only one. the image.

    it keep on happening on the verify

     

    fordman, i didn't burn, i just verified and i got different result. There was no image burning. Check the log. ;)

     

    dirio49,

     

    Sorry! I was looking at dontasciime's log file, thinking he was quoting yours, so my mistake. You are RIGHT - you have verified my assertion that there is still a bug in the verification code! However, unless LUK and/or the official beta testers encounter it, it looks like your machine and mine (and my girlfriend's) are considered "messed up."

     

    However, on your follow up example, you show something different: the device MD5 (which is usually what is missing) is shown, but no image MD5. However in this case I see that line that states:

     

    "Verify Against Image File: No"

     

    That makes me believe that the image MD5 is not shown because you are not verifying against the image file, only doing a read test on the device burned DVD. I assume you changed the verification setting before the second burn to not verify against the image file (which is the default)?

     

    Anyway, your first example supports my results, so I'm satisified that I'm not alone. Now if we can convince LUK that this is the case...

     

    I wonder if it could have something to do with burning several discs while ImgBurn is open versus closing it between burns? I have a batch of discs to burn on my girlfriends's PC, so if I encounter it again, I'll report back.

     

    Thanks,

    FordMan

     

    Here is another one, just verifying a disk and once I get MD5 and the other time I don't get it.

    I 12:11:10 Operation Started!

    I 12:11:10 Source Device: [2:1:0]MW3612P OUN711I 1.0 (J:) (SCSI)

    I 12:11:10 Source Media Type: DVD-ROM (Book Type: DVD-ROM)

    I 12:11:10 Source Media Sectors: 202,816

    I 12:11:10 Source Media Size: 415,367,168 bytes

    I 12:11:10 Verify Against Image File: No

    I 12:11:10 Read Speed: MAX

    I 12:11:10 Verifying Sectors... (LBA: 0 - 202815)

    I 12:11:32 Device MD5: a62fbce2f66753f44e56bcb3aef0e439

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

    I 12:11:32 Graph Data File: C:\Documents and Settings\MW3612P_OUN711I_1.0_SUNDAY-FEBRUARY-18-2007_12-11_PM_N-A.ibg

    I 12:11:32 Export Successfully Completed!

    I 12:11:32 Operation Successfully Completed! - Duration: 00:00:21

    I 12:11:32 Average Verify Rate: 19,315 KB/s (13.9x) - Maximum Verify Rate: 26,017 KB/s (18.8x)

    I 12:11:38 Operation Started!

    I 12:11:38 Source Device: [2:1:0] MW3612P OUN711I 1.0 (J:) (SCSI)

    I 12:11:38 Source Media Type: DVD-ROM (Book Type: DVD-ROM)

    I 12:11:38 Source Media Sectors: 202,816

    I 12:11:38 Source Media Size: 415,367,168 bytes

    I 12:11:39 Verify Against Image File: No

    I 12:11:39 Read Speed: MAX

    I 12:11:39 Verifying Sectors... (LBA: 0 - 202815)

    I 12:11:56 Exporting Graph Data...

    I 12:11:56 Graph Data File: C:\Documents and Settings\MW3612P_OUN711I_1.0_SUNDAY-FEBRUARY-18-2007_12-11_PM_N-A(1).ibg

    I 12:11:56 Export Successfully Completed!

    I 12:11:56 Operation Successfully Completed! - Duration: 00:00:17

    I 12:11:56 Average Verify Rate: 23,860 KB/s (17.2x) - Maximum Verify Rate: 33,816 KB/s (24.4x)

  8. I did test to see what would happens and if you see,

    i verified the same iso twice and got it one to get only only the device MD5 and the other time both.

    no idea why this happened.

     

    No, what you got is normal. It shows only the image MD5 when writing, because it has not yet read the device image yet, as it does when it verifies. So, your worked properly on this particular burning session...

     

    I wrote a single layer image on my girlfriend's PC, and the device MD5 showed with the image MD5 on verify, so that worked for this particular image, and set of conditions. I'll keep an eye on it with future burns.

     

    When I brought this issue up with 2.1.0.0, LUK told me that others experienced it also, so the changes in 2.2.0.0 weren't made specifically for me and my experience with the bug. I expect that others will encounter it also with 2.2.0.0, if they bother to verify and calculate MD5s every time they write...

  9. Well I actually never had an issue with 2.1.0.0 either.

     

    I found what I thought could be causing the issue on your PC - because the code wasn't quite 'by the book'. I changed it in 2.2.0.0 so that it is and put in error messages EVERYWHERE to do with the MD5 stuff when any API call failed.

     

    The fact that you're not getting any messages means it's not actually failing!

     

    You're getting 'Good' status return codes but must be getting odd numbers (i.e. zero (0) ) for the length of the returned data. Just for you, I've added more logging in to tell us about that too.

     

    So, that extra logging "just for me" is in a revised 2.2.0.0 that is in beta status? Unless I have a copy of that version, I'll not be able to report back anything from the extra logging...

     

     

    There really is nothing I can do about it now. I'm perfectly happy with my current implementation and if it's just not working for you then I will live with that.

     

    I've looked though all the logs of the beta team and none of those have shown any issues reporting the device md5, so no, I don't agree there's an issue.

    Wow! I'm surprised by this response! Look, I am very grateful for your program, and certainly hope I didn't come off sounding otherwise. However, you only just recently released this program, so I think time will tell whether others are having issues. Please recall the other issues I found for you that were never experienced (or more likely, never NOTICED) by your beta team. If you recall I found that your code to update the .bup/.ifo files with a new non-seamless/LB flag was buggering up VOB files, and after I reported it you found that you were using 32-bit data structures versus 64-bit (or something like that) data structures to calculate the position of the .BUP file after the VOBs, and were instead making the change as a result in the middle of a VOB... I also discovered that your code to remove old LB flags inside of an ISO was buggered and it left the old LB when it was adding the new one the person selected. All that was apparently not noticed by the beta team, so they are not infallible! I found those bugs because I do extensive data verification with outside utilities, like .SFV file makers to verify what was written matches my source. Apparently your beta team didn't bother to do any of that. Also, don't forget that Microsoft products go through extensive beta testing and get unleashed upon the world with many bugs and flaws. I think the "more beta testers are better" approach is what has lead many authors, like the author of PGCEdit, to have all the betas available for open testing - more testers means more possibility to find bugs...

     

    So, no, I don't agree that the problem is only on my machine(s). You are the one that told me that it was being experienced by others with 2.1.0.0 and that you thought you had tracked down the issue. I expect that you will find other normal users like me that will have the issue, and hopefully will report it. Unless you are sure that your beta testers create the MD5 signatures all the time and bother to look, then I don't even think you can say it is not an issue with the beta team.

     

    If your goal is only to have all ImgBurn's features work on your machine, and maybe your beta tester's machines with their combination of hardware and software, then I can see why you are happy with the current implementation.

     

    Seeing as how both PC's are yours, there's every chance that whatever messed up one machine has also been put onto the other machine and messed that up too. I don't know the inner workings of the Crypt API's but I do know none of them are failing and so it's out of my hands.

     

    Ahhh, they are NOT both my machines. The second one that 2.1.0.0 failed on is my girlfriend's machine, and the ONLY change I made to her machine is that I installed ImgBurn on it. She does not have the same mix of other burning software, etc., so her lowerfilter/upperfilter settings are even different. So, no that premise is incorrect. These are two indpendent platforms that experienced the same issue (along with the others that reported it) with 2.1.0.0, so I know that all these machines weren't "messed up." Perhaps there is something additional that you have that allows yours to work all the time? That doesn't mean those that don't have whatever that may be have messed up machines. Seeing as 2.2.0.0 hasn't been out that long, I'm sure it will be a matter of time when others will report it, assuming they use the function and bother to check.

     

    I was surprised to see the lack of the device MD5 on my very first burn with 2.2.0.0, so thought I should report it. I am only trying to help, and as all know a bug in one area due to code that isn't "by the book" (your characterization of your code in 2.1.0.0) can lead to unpredictable behavior elsewhere...

  10. I've had it on every single one of my burns so I'm still totally clueless as to why it doesn't work on your pc.

     

    I suppose you mean every one of your burns so far? How often did it occur with 2.1.0.0? That's the first and only DVD I burned with 2.2.0.0 so far, but 2.1.0.0 failed sometimes both on that same PC as well as a separate PC with XP pro versus XP home, celeron vs. P4, etc. I'll let you know, but I expect that I will encounter it on that PC also. Like I mentioned in a previous thread about this subect with 2.1.0.0, that version worked great from it's release up until January when I started encountering the missing device MD5, and it happened about the same time on both PCs I burn DVDs on, and since the beginning of February, I had stopped seeing it. Without knowing the specifics of what you thought the bug was that you thought you found to fix the issue, I cannot even guess what could be causing it. However, since the burn is OK in every other way, I suspect there are other possible causes that perhaps were not fixed by the change you made in 2.2.0.0. Let me burn some more with 2.2.0.0 on the other PC and I'll let you know if I get a failure. If I do, then I imagine you'd agree that there is still an issue and it is unrelated to the PC...

  11. The MD5 hash value calculated from the device failed in the very first (and only to date) image I burned with Imgburn 2.2.0.0, so the bug is apparently still there. Meanwhile it had been awhile since it happened with 2.1.0.0. I sprang up right after the new year and seemed to subside when February came along.

     

    My log to support this is below. Note that I always choose to used debug mode and "Display IFO Layer Break Information" whenever I am about to burn an image, even when it is stored in the MDS, so that I will have a record of which file it occurs during in the log file...

     

    FordMan

     

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

     

    I 22:04:10 ImgBurn Version 2.2.0.0 started!

    I 22:04:10 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

    I 22:04:10 Total Physical Memory: 2,096,620 KB - Available: 1,495,376 KB

    W 22:04:10 Drive E:\ (FAT32) does not support single files > 4 GB in size.

    I 22:04:10 Initialising SPTI...

    I 22:04:10 Searching for SCSI / ATAPI devices...

    I 22:04:10 Found 2 DVD-ROMs, 2 DVD?RWs and 1 DVD?RW/RAM!

    W 22:06:16 Program 'Debug Mode' has been Enabled!

    D 22:06:33 GetIFOLayerBreakPositions - MinL0DataZoneCapacity: 1593248

    D 22:06:33 GetIFOLayerBreakPositions - MaxL0DataZoneCapacity: 2086912

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.IFO - LBA: 307 - 315 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.VOB - LBA: 316 - 372 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.BUP - LBA: 373 - 381 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.IFO - LBA: 382 - 430 - Size: 100,352 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.VOB - LBA: 431 - 315657 - Size: 645,584,896 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_1.VOB - LBA: 315658 - 839859 - Size: 1,073,565,696 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_2.VOB - LBA: 839860 - 1364061 - Size: 1,073,565,696 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_3.VOB - LBA: 1364062 - 1888263 - Size: 1,073,565,696 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_4.VOB - LBA: 1888264 - 2412465 - Size: 1,073,565,696 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_5.VOB - LBA: 2412466 - 2687469 - Size: 563,208,192 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.BUP - LBA: 2687470 - 2687518 - Size: 100,352 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.IFO - LBA: 2687519 - 2687527 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.VOB - LBA: 2687528 - 2687584 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_1.VOB - LBA: 2687585 - 2735231 - Size: 97,581,056 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.BUP - LBA: 2735232 - 2735240 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.IFO - LBA: 2735241 - 2735249 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.VOB - LBA: 2735250 - 2735306 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_1.VOB - LBA: 2735307 - 2754478 - Size: 39,264,256 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.BUP - LBA: 2754479 - 2754487 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.IFO - LBA: 2754488 - 2754496 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.VOB - LBA: 2754497 - 2754553 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_1.VOB - LBA: 2754554 - 2774642 - Size: 41,142,272 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.BUP - LBA: 2774643 - 2774651 - Size: 18,432 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.IFO - LBA: 2774652 - 2774665 - Size: 28,672 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.VOB - LBA: 2774666 - 2774722 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_1.VOB - LBA: 2774723 - 2996848 - Size: 454,914,048 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.BUP - LBA: 2996849 - 2996862 - Size: 28,672 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.IFO - LBA: 2996863 - 2996872 - Size: 20,480 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.VOB - LBA: 2996873 - 2996929 - Size: 116,736 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_1.VOB - LBA: 2996930 - 3186462 - Size: 388,163,584 bytes

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.BUP - LBA: 3186463 - 3186472 - Size: 20,480 bytes

    D 22:06:33 __ParseFS - Found 31 Files

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.IFO - LBA: 307 - 315

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.VOB - LBA: 316 - 372

    D 22:06:33 File System - File: VIDEO_TS\VIDEO_TS.BUP - LBA: 373 - 381

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.IFO - LBA: 382 - 430

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.VOB - LBA: 431 - 315657

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_1.VOB - LBA: 315658 - 839859

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_2.VOB - LBA: 839860 - 1364061

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_3.VOB - LBA: 1364062 - 1888263

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_4.VOB - LBA: 1888264 - 2412465

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_5.VOB - LBA: 2412466 - 2687469

    D 22:06:33 File System - File: VIDEO_TS\VTS_01_0.BUP - LBA: 2687470 - 2687518

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.IFO - LBA: 2687519 - 2687527

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.VOB - LBA: 2687528 - 2687584

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_1.VOB - LBA: 2687585 - 2735231

    D 22:06:33 File System - File: VIDEO_TS\VTS_02_0.BUP - LBA: 2735232 - 2735240

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.IFO - LBA: 2735241 - 2735249

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.VOB - LBA: 2735250 - 2735306

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_1.VOB - LBA: 2735307 - 2754478

    D 22:06:33 File System - File: VIDEO_TS\VTS_03_0.BUP - LBA: 2754479 - 2754487

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.IFO - LBA: 2754488 - 2754496

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.VOB - LBA: 2754497 - 2754553

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_1.VOB - LBA: 2754554 - 2774642

    D 22:06:33 File System - File: VIDEO_TS\VTS_04_0.BUP - LBA: 2774643 - 2774651

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.IFO - LBA: 2774652 - 2774665

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.VOB - LBA: 2774666 - 2774722

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_1.VOB - LBA: 2774723 - 2996848

    D 22:06:33 File System - File: VIDEO_TS\VTS_05_0.BUP - LBA: 2996849 - 2996862

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.IFO - LBA: 2996863 - 2996872

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.VOB - LBA: 2996873 - 2996929

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_1.VOB - LBA: 2996930 - 3186462

    D 22:06:33 File System - File: VIDEO_TS\VTS_06_0.BUP - LBA: 3186463 - 3186472

    D 22:06:33 GetIFOLayerBreakPositions - Start/End LBA Match - File: VTS_01_3.VOB

    D 22:06:33 GetIFOLayerBreakPositions - Start/End LBA Match - File: VTS_01_4.VOB

    D 22:06:33 Potential Layer Break Position! - LBA: 1855344 (VTS_01, PGC: 1, Cell: 23, Vob/Cell ID: 1/23, Time: 00:53:36, SPLIP Flag: No)

    I 22:06:43 Operation Started!

    I 22:06:43 Source File: U:\BOM - Image\BOM.MDS

    I 22:06:43 Source File Sectors: 3,186,496 (MODE1/2048)

    I 22:06:43 Source File Size: 6,525,943,808 bytes

    I 22:06:43 Source File Volume Identifier: BOM

    I 22:06:43 Source File Application Identifier: DVD Studio Pro:4.0.2, DSPInterface:371, DVDAuthoring:350, DVDBase:371(Encoder: 483), Oxygene:409

    I 22:06:43 Source File Implementation Identifier: Apple Computer, Inc.

    I 22:06:43 Source File File System(s): ISO9660, UDF (1.02)

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

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

    I 22:06:43 Destination Media Sectors: 4,173,824

    I 22:06:43 Write Mode: DVD

    I 22:06:43 Write Type: DAO

    I 22:06:43 Write Speed: 6x

    I 22:06:43 Link Size: Auto

    I 22:06:43 Test Mode: No

    I 22:06:43 BURN-Proof: Enabled

    I 22:06:43 Optimal L0 Data Zone Capacity: 1,855,344

    I 22:06:43 Optimal L0 Data Zone Method: Copied From Original Disc

    D 22:07:03 Device Buffer Size: 1,605,632 bytes.

    D 22:07:03 Device Buffer Available: 1,605,632 bytes.

    I 22:07:03 Filling Buffer... (256 MB)

    I 22:07:09 Writing LeadIn...

    I 22:07:22 Writing Image...

    I 22:07:22 Writing Layer 0... (LBA: 0 - 1855343)

    I 22:15:18 Writing Layer 1... (LBA: 1855344 - 3186495)

    I 22:21:15 Synchronising Cache...

    I 22:21:16 Closing Track...

    I 22:21:24 Finalising Disc...

    I 22:25:28 Image MD5: 9cfc873e93673baa89a9436b73505d8a

    I 22:25:28 Exporting Graph Data...

    I 22:25:29 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_2-15-2007_10-06_PM_MKM-001-00_6x_BOM.ibg

    I 22:25:29 Export Successfully Completed!

    I 22:25:29 Operation Successfully Completed! - Duration: 00:18:45

    I 22:25:29 Average Write Rate: 7,659 KB/s (5.5x) - Maximum Write Rate: 8,503 KB/s (6.1x)

    I 22:25:29 Cycling Tray before Verify...

    I 22:25:54 Device Ready!

    D 22:25:54 File System - File: VIDEO_TS\VIDEO_TS.IFO - LBA: 307 - 315 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VIDEO_TS.VOB - LBA: 316 - 372 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VIDEO_TS.BUP - LBA: 373 - 381 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_0.IFO - LBA: 382 - 430 - Size: 100,352 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_0.VOB - LBA: 431 - 315657 - Size: 645,584,896 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_1.VOB - LBA: 315658 - 839859 - Size: 1,073,565,696 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_2.VOB - LBA: 839860 - 1364061 - Size: 1,073,565,696 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_3.VOB - LBA: 1364062 - 1888263 - Size: 1,073,565,696 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_4.VOB - LBA: 1888264 - 2412465 - Size: 1,073,565,696 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_5.VOB - LBA: 2412466 - 2687469 - Size: 563,208,192 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_01_0.BUP - LBA: 2687470 - 2687518 - Size: 100,352 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_02_0.IFO - LBA: 2687519 - 2687527 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_02_0.VOB - LBA: 2687528 - 2687584 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_02_1.VOB - LBA: 2687585 - 2735231 - Size: 97,581,056 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_02_0.BUP - LBA: 2735232 - 2735240 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_03_0.IFO - LBA: 2735241 - 2735249 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_03_0.VOB - LBA: 2735250 - 2735306 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_03_1.VOB - LBA: 2735307 - 2754478 - Size: 39,264,256 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_03_0.BUP - LBA: 2754479 - 2754487 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_04_0.IFO - LBA: 2754488 - 2754496 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_04_0.VOB - LBA: 2754497 - 2754553 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_04_1.VOB - LBA: 2754554 - 2774642 - Size: 41,142,272 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_04_0.BUP - LBA: 2774643 - 2774651 - Size: 18,432 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_05_0.IFO - LBA: 2774652 - 2774665 - Size: 28,672 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_05_0.VOB - LBA: 2774666 - 2774722 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_05_1.VOB - LBA: 2774723 - 2996848 - Size: 454,914,048 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_05_0.BUP - LBA: 2996849 - 2996862 - Size: 28,672 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_06_0.IFO - LBA: 2996863 - 2996872 - Size: 20,480 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_06_0.VOB - LBA: 2996873 - 2996929 - Size: 116,736 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_06_1.VOB - LBA: 2996930 - 3186462 - Size: 388,163,584 bytes

    D 22:25:54 File System - File: VIDEO_TS\VTS_06_0.BUP - LBA: 3186463 - 3186472 - Size: 20,480 bytes

    D 22:25:54 __ParseFS - Found 31 Files

    I 22:25:54 Operation Started!

    I 22:25:54 Source Device: [1:1:0] PIONEER DVD-RW DVR-111L 8.29 (I:) (ATA)

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

    I 22:25:54 Image File: U:\BOM - Image\BOM.MDS

    I 22:25:54 Image File Sectors: 3,186,496 (MODE1/2048)

    I 22:25:54 Image File Size: 6,525,943,808 bytes

    I 22:25:54 Image File Volume Identifier: BOM

    I 22:25:54 Image File Application Identifier: DVD Studio Pro:4.0.2, DSPInterface:371, DVDAuthoring:350, DVDBase:371(Encoder: 483), Oxygene:409

    I 22:25:54 Image File Implementation Identifier: Apple Computer, Inc.

    I 22:25:54 Image File File System(s): ISO9660, UDF (1.02)

    I 22:25:54 Verifying Sectors... (LBA: 0 - 3186495)

    I 22:40:16 Image MD5: 9cfc873e93673baa89a9436b73505d8a

    I 22:40:16 Exporting Graph Data...

    I 22:40:16 Graph Data File: C:\Program Files\ImgBurn\PIONEER_DVD-RW_DVR-111L_8.29_2-15-2007_10-06_PM_MKM-001-00_6x_BOM.ibg

    I 22:40:16 Export Successfully Completed!

    I 22:40:16 Operation Successfully Completed! - Duration: 00:14:21

    I 22:40:16 Average Verify Rate: 7,401 KB/s (5.3x) - Maximum Verify Rate: 10,052 KB/s (7.3x)

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

  13. =)) 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...

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

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

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

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

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

  19. Does anyone really know for sure that the mux rate is important?!

     

    No, I think I was going from what I read in the PGCEdit screen or in a related discussion group. Now that I think more about it, I think the only instance where the MUX rate may change is when there is a change from one VOB ID to another VOB ID, e.g. from VOB 1, cell 26 to VOB 2, cell 1. So that would indicate that it has to do with the STC discontinuity, which for some (most) DVDs also coincides with a non-seamless flag.

     

    I have to admit that I'm not even sure why the an author would use one mux rate for part of the movie and then finish with a different mux rate, but it somehow seems sensible that some kind of interruption may be necessary to give the player a chance to adjust to the change.

     

    No, I don't have access to the DVD-VIDEO specs, so I cannot be certain that this is in fact needed. However, I am certain that every pressed DVD-VIDEO that I've looked at with PGCEdit that had mixed mux rates in fact does have a non-seamless and STC discontinuity flag where that occurs. Perhaps only the STC discontinuity flag is needed, but it also provides a convenient place for a non-seamless flag?

     

    I have seen some pressed DVDs that have a change in VOB ID that happened to have the same mux rate for each VOB ID. However, it seems the STC/non-seamless flags are there also at the transition.

     

    It strikes me that programs have been setting layer breaks without any regard for mux rate for ages and it's never really been an issue!

     

    As stated above, all pressed DVD-VIDEO discs that I've come across did have STC/non-seamless flags at the transition between mux rates, so how can you be certain that they were authored without regard to the mux rate?

  20. I understand that it is necessary to have a LB flag (or is it STC discontinuity flag) between cells that have different MUX rates. PGCEdit shows the mux rate when making a layer break selection.

     

    Is there any easy way, i.e., through IFOEdit or something to examine the mux rates without going through a mock burn process with PGCEdit? Are there any other utilities that allow one to examine the mux rate?

     

    I would suggest that at a minimum, IMGBurn should include this info in the LB selection window, so one does not end up removing a LB flag where there is a mux rate change to another cell which has the same mux rate before and after it.

     

    fordman

  21. Any work arounds? What can I do to delete the folder?

     

    Thanks,

    Kizer

     

    Yes, download Process Explorer from Sysinternals:

     

    http://www.sysinternals.com/Utilities/ProcessExplorer.html

     

    It's free and is great. Search for a file handle (binoculars) - suggest just entering video as the search term. In the results window, double-click the term that looks like the one that is relevant and then when you get to the file handle listing, right click on the highlighted one and choose to "close handle." Works for me every time, and saves you from having to reboot!

     

    I have one program, QuickSFV, which I use for making .SFV files that sometimes crashes Windows Explorer and it leaves the file handle open to the .SFV that it was making. Closing the handle allows me to delete the incomplete .SFV file and start over...

  22. Just to be clear...

     

    The created and modified date fields use the current time/date if not specified.

     

    The effective and expiration date fields are zeroed out if not specified.

     

    You anticipated my next curiosity, but I wasn't going to bother to ask! I saw all the zeros in sector 16 after the created and modified dates, and wondered why the modified date wasn't also defaulted to zeros.

     

    Thanks.

  23. It's probably the creation (first date) and then modified (second date) that you're seeing in the ISO9660 filesystem. Both of which are configurable on that same 'Dates' tab.

     

    Aaah, OK. So, I'll set 3 date fields and then the images should match. I was hesitant to change other fields since I wasn unsure of the implications behind the effective and expiration dates.

     

    No fix needed then, I just wasn't using the options you already have built in.

     

    Thanks for the pointer.

  24. In theory yes, if the files hadn't changed and you set all the dates etc the MD5 should be the same.

     

    Ok, I've verified that an .ISO image ripped from a disc made directly from build mode does not match an ISO made from build mode.

     

    You made an adjustment to the UDF recording time as referenced in the following thread:

     

    http://forum.imgburn.com/index.php?showtopic=2037

     

    and in this thread we discussed that as long as the files stayed the same and the date settings were the same the disc made directly in build mode should compare exactly to one made from an ISO file first made in build mode and then burned.

     

    I set the "Volume Dates/Creation" and "Folder/File Dates - Use Custom Date & Time" options to the same date and time for the direct to disc build and the build to ISO.

     

    I can verify that the DVDInfoPro UDF recording time is now shown the same for both, however there is a difference in sector 16 of the ISO file system (as viewed with the sector view in ISOBuster). At offset 032D of sector 16, the date string I used for volume creation is shown, but immediately following that the actual date I recorded to disc (or to ISO image) is shown. Therefore the two will never match.

     

    I had assumed that this would be where you modified the UDF recording time, and only ever verified your adjustment in DVDInfoPro. I've been since building direct to disc, bypassing the ISO file altogether (a big time saver!) and just happened to be looking at sectors in ISOBuster when I noticed this. Now I'm realizing that the UDF recording time likely isn't stored in the ISO file system structure, but I cannot find a similar string in the UDF file system sectors. So, where is the UDF recording time stored, i.e. where did you make that adjustment?

     

    Is it possible to also change the second date in the ISO file system? I've noticed that in pressed DVDs these either seem to match, or the second date is not there at all (all zeros).

     

    Thanks,

    fordman

×
×
  • Create New...

Important Information

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