Jump to content

fordman

Members
  • Posts

    184
  • Joined

  • Last visited

Posts posted by fordman

  1. Have you tried with OPC disabled? Some burners go banana with that option enabled.

     

    Yes, tried disabling that, though it works on all other images (single or dual layer) on my Pioneer BDR-206 drive. The reserve track for DVD+R is also disabled. Something seems to be triggering an unneeded reserve track operation in ImgBurn. Even LUK states that BD-R DL discs are "treated like a big single layer," so I don't understand why reserving a track on these discs would even be necessary. I wish there was an override switch for it. At least the blanks were not ruined, and I do have backup options, but not with all the options I'm used to in ImgBurn, i.e. immediate verification after writing, MD5 calculation, etc....

  2. Sorry to activate an older thread, but I've run into the exact same issue - ImgBurn 2.5.7.0 hangs on the "reserving track" operation on a BD-R DL, but ONLY on one image I built with ImgBurn that requires a 50GB blank. Others I've burned for months before and the two days since on 3 different brands of discs have worked fine (Verbatim VERBAT-IMf-000, Ritek RITEK-DR2-000, and CMC Magnetics CMCMAG-DI6-000 labeled as Optical Quantum) with my Pioneer BDR-206 recorder.

     

    It gets more interesting: Immediately after encountering the issue with this particular image file, I rolled back a set of windows updates I had made the day before, but it still didn't work, so then I did a system restore to no avail. I then tried different blanks to no avail. Then I moved on to new BD50 images and they burned just fine on the very same blanks that hung in the reserving track operation on the problem image. They had only gone through the OPC operation so the blanks were not wasted... I didn't notice the status bar of ImgBurn stating that it was reserving the track on these working image, and it is not stated in the log. Finally, I decided to use another tool on my computer to burn the problem ISO image, AND IT WORKED! I could then use ImgBurn to verify the image to the disc written with the other utility, and the MD5 hash value is exact! The finished disc plays fine in all my set-top bluray players...

     

    Since this follows most of the guidelines of experimental design, my conclusion is that ImgBurn is the problem or otherwise is doing some more rigorous checks ONLY with certain images than other burning tools do. The image size is close to the one the "Cars 2" image that the OP had the issue with. Could it be that ImgBurn is doing some type of calculation for sector layouts before burning, and it "gets confused" and issues an unneeded "reserve track" command?

     

    Here's my attempted writing log (had to abort and power down the system), and the verify log of the successful disc burned with the other image burning program:

     

    Unsuccessful ImgBurn Write Log:

     

    ; //****************************************\\

    ; ImgBurn Version 2.5.7.0 - Log

    ; Saturday, 21 July 2012, 14:02:07

    ; \\****************************************//

    ;

    ;

    I 14:00:25 ImgBurn Version 2.5.7.0 started!

    I 14:00:25 Microsoft Windows Vista Home Premium Edition (6.0, Build 6002 : Service Pack 2)

    I 14:00:25 Total Physical Memory: 3,405,920 KB - Available: 1,920,544 KB

    W 14:00:25 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.

    I 14:00:25 Initialising SPTI...

    I 14:00:25 Searching for SCSI / ATAPI devices...

    I 14:00:25 -> Drive 1 - Info: PIONEER DVD-RW DVR-116L 1.10 (F:) (ATA)

    I 14:00:26 -> Drive 2 - Info: HL-DT-ST BD-RE WH10LS30 1.00-06 (G:) (ATA)

    I 14:00:26 -> Drive 3 - Info: PIONEER BD-RW BDR-206 1.06 (H:) (ATA)

    I 14:00:26 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

    I 14:00:26 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 2 BD-REs!

    W 14:00:34 Program 'Debug Mode' has been Enabled!

    I 14:00:47 Operation Started!

    I 14:00:47 Source File: T:\Images\TNTD - 1920x1080 ImgBurn BluRay Image\TNTD.ISO

    I 14:00:47 Source File Sectors: 23,099,296 (MODE1/2048)

    I 14:00:47 Source File Size: 47,307,358,208 bytes

    I 14:00:47 Source File Volume Identifier: TNTD

    I 14:00:47 Source File Volume Set Identifier: 3D73080001607609

    I 14:00:47 Source File Application Identifier: ImgBurn v2.5.7.0

    I 14:00:47 Source File Implementation Identifier: ImgBurn

    I 14:00:47 Source File File System(s): UDF (2.50)

    I 14:00:47 Destination Device: [7:0:0] PIONEER BD-RW BDR-206 1.06 (H:) (ATA)

    I 14:00:47 Destination Media Type: BD-R (Disc ID: RITEK-DR2-000)

    I 14:00:47 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x

    I 14:00:47 Destination Media Sectors: 24,438,784

    I 14:00:47 Write Mode: BD

    I 14:00:47 Write Type: DAO

    I 14:00:47 Write Speed: 4x

    I 14:00:47 Hardware Defect Management Active: No

    I 14:00:47 BD-R Verify Not Required: Yes

    I 14:00:47 Link Size: Auto

    I 14:00:47 Lock Volume: Yes

    I 14:00:47 Test Mode: No

    I 14:00:47 OPC: Yes

    I 14:00:47 BURN-Proof: Enabled

    D 14:00:47 DeviceIoControl(FSCTL_UNLOCK_VOLUME) Failed! - Reason: The segment is already unlocked.

    D 14:00:47 DeviceIoControl(FSCTL_LOCK_VOLUME) Succeeded!

    I 14:00:47 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x)

    I 14:00:47 Advanced Settings - Optimal Writing Speed: No

    D 14:00:47 Logical Unit Most Desirable Link Size: 0

    I 14:01:56 Abort Request Acknowledged

     

     

    ImgBurn Verify Log after burning with other recording tool:

     

    ; //****************************************\\

    ; ImgBurn Version 2.5.7.0 - Log

    ; Sunday, 22 July 2012, 14:26:07

    ; \\****************************************//

    ;

    ;

    I 12:58:54 ImgBurn Version 2.5.7.0 started!

    I 12:58:54 Microsoft Windows Vista Home Premium Edition (6.0, Build 6002 : Service Pack 2)

    I 12:58:54 Total Physical Memory: 3,405,920 KB - Available: 1,625,380 KB

    W 12:58:54 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.

    I 12:58:54 Initialising SPTI...

    I 12:58:54 Searching for SCSI / ATAPI devices...

    I 12:58:54 -> Drive 1 - Info: PIONEER DVD-RW DVR-116L 1.10 (F:) (ATA)

    I 12:58:55 -> Drive 2 - Info: HL-DT-ST BD-RE WH10LS30 1.00-06 (G:) (ATA)

    I 12:58:55 -> Drive 3 - Info: PIONEER BD-RW BDR-206 1.06 (H:) (ATA)

    I 12:58:55 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

    I 12:58:55 Found 1 DVD±RW/RAM, 1 BD-ROM/HD DVD-ROM and 2 BD-REs!

    W 12:58:56 Program 'Debug Mode' has been Enabled!

    D 12:59:53 File System - File: \BDMV\index.bdmv - LBA: 672 - 672 - Size: 1,188 bytes

    D 12:59:53 File System - File: \BDMV\MovieObject.bdmv - LBA: 673 - 695 - Size: 46,366 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\index.bdmv - LBA: 696 - 696 - Size: 1,188 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\MovieObject.bdmv - LBA: 697 - 719 - Size: 46,366 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00000.bdjo - LBA: 720 - 720 - Size: 262 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00011.bdjo - LBA: 721 - 721 - Size: 262 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00012.bdjo - LBA: 722 - 722 - Size: 262 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00013.bdjo - LBA: 723 - 723 - Size: 90 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00086.bdjo - LBA: 724 - 724 - Size: 262 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\00087.bdjo - LBA: 725 - 725 - Size: 262 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\12345.bdjo - LBA: 726 - 726 - Size: 90 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\65535.bdjo - LBA: 727 - 727 - Size: 268 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\BDJO\88888.bdjo - LBA: 728 - 728 - Size: 342 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00153.clpi - LBA: 729 - 729 - Size: 468 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00239.clpi - LBA: 730 - 730 - Size: 336 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00240.clpi - LBA: 731 - 731 - Size: 348 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00241.clpi - LBA: 732 - 732 - Size: 496 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00242.clpi - LBA: 733 - 733 - Size: 324 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00243.clpi - LBA: 734 - 734 - Size: 324 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00251.clpi - LBA: 735 - 735 - Size: 536 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00282.clpi - LBA: 736 - 736 - Size: 336 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00283.clpi - LBA: 737 - 737 - Size: 336 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00312.clpi - LBA: 738 - 765 - Size: 56,736 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00385.clpi - LBA: 766 - 766 - Size: 912 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00387.clpi - LBA: 767 - 767 - Size: 572 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00413.clpi - LBA: 768 - 768 - Size: 336 bytes

    D 12:59:53 File System - File: \BDMV\BACKUP\CLIPINF\00522.clpi - LBA: 769 - 769 - Size: 412 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00523.clpi - LBA: 770 - 773 - Size: 7,732 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00524.clpi - LBA: 774 - 775 - Size: 3,024 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00525.clpi - LBA: 776 - 777 - Size: 3,832 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00526.clpi - LBA: 778 - 778 - Size: 1,368 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00527.clpi - LBA: 779 - 779 - Size: 452 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00528.clpi - LBA: 780 - 780 - Size: 524 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00529.clpi - LBA: 781 - 781 - Size: 444 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00530.clpi - LBA: 782 - 782 - Size: 648 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00531.clpi - LBA: 783 - 783 - Size: 552 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00532.clpi - LBA: 784 - 784 - Size: 584 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00533.clpi - LBA: 785 - 785 - Size: 624 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00534.clpi - LBA: 786 - 786 - Size: 744 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00535.clpi - LBA: 787 - 787 - Size: 708 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00536.clpi - LBA: 788 - 788 - Size: 812 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00537.clpi - LBA: 789 - 789 - Size: 1,412 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00538.clpi - LBA: 790 - 790 - Size: 1,008 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00539.clpi - LBA: 791 - 791 - Size: 520 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00540.clpi - LBA: 792 - 792 - Size: 1,944 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00541.clpi - LBA: 793 - 793 - Size: 1,184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00542.clpi - LBA: 794 - 794 - Size: 664 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00543.clpi - LBA: 795 - 795 - Size: 816 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00544.clpi - LBA: 796 - 796 - Size: 1,444 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00545.clpi - LBA: 797 - 797 - Size: 1,416 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00546.clpi - LBA: 798 - 798 - Size: 1,224 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00547.clpi - LBA: 799 - 799 - Size: 1,456 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\CLIPINF\00548.clpi - LBA: 800 - 800 - Size: 996 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\JAR\03001.jar - LBA: 801 - 1648 - Size: 1,735,707 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\JAR\88888.jar - LBA: 1649 - 2022 - Size: 763,947 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00002.mpls - LBA: 2023 - 2023 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00003.mpls - LBA: 2024 - 2051 - Size: 56,186 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00011.mpls - LBA: 2052 - 2052 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00017.mpls - LBA: 2053 - 2053 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00018.mpls - LBA: 2054 - 2054 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00020.mpls - LBA: 2055 - 2055 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00021.mpls - LBA: 2056 - 2056 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00051.mpls - LBA: 2057 - 2057 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00052.mpls - LBA: 2058 - 2058 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00115.mpls - LBA: 2059 - 2059 - Size: 186 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00502.mpls - LBA: 2060 - 2060 - Size: 154 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00503.mpls - LBA: 2061 - 2061 - Size: 154 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00504.mpls - LBA: 2062 - 2062 - Size: 362 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00505.mpls - LBA: 2063 - 2063 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00506.mpls - LBA: 2064 - 2064 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00602.mpls - LBA: 2065 - 2065 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00603.mpls - LBA: 2066 - 2066 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00611.mpls - LBA: 2067 - 2067 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00636.mpls - LBA: 2068 - 2068 - Size: 472 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00637.mpls - LBA: 2069 - 2069 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00638.mpls - LBA: 2070 - 2070 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00800.mpls - LBA: 2071 - 2071 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00801.mpls - LBA: 2072 - 2072 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00802.mpls - LBA: 2073 - 2073 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00805.mpls - LBA: 2074 - 2074 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00856.mpls - LBA: 2075 - 2075 - Size: 472 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00857.mpls - LBA: 2076 - 2076 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00858.mpls - LBA: 2077 - 2077 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00859.mpls - LBA: 2078 - 2078 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00860.mpls - LBA: 2079 - 2079 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00861.mpls - LBA: 2080 - 2080 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00862.mpls - LBA: 2081 - 2081 - Size: 280 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00863.mpls - LBA: 2082 - 2082 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00864.mpls - LBA: 2083 - 2083 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00865.mpls - LBA: 2084 - 2084 - Size: 376 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00866.mpls - LBA: 2085 - 2085 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00867.mpls - LBA: 2086 - 2086 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00868.mpls - LBA: 2087 - 2087 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00869.mpls - LBA: 2088 - 2088 - Size: 376 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00870.mpls - LBA: 2089 - 2089 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00871.mpls - LBA: 2090 - 2090 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00872.mpls - LBA: 2091 - 2091 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00873.mpls - LBA: 2092 - 2092 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00874.mpls - LBA: 2093 - 2093 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00875.mpls - LBA: 2094 - 2094 - Size: 280 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00876.mpls - LBA: 2095 - 2095 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00877.mpls - LBA: 2096 - 2096 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00878.mpls - LBA: 2097 - 2097 - Size: 474 bytes

    D 12:59:54 File System - File: \BDMV\BACKUP\PLAYLIST\00879.mpls - LBA: 2098 - 2098 - Size: 186 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00000.bdjo - LBA: 2099 - 2099 - Size: 262 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00011.bdjo - LBA: 2100 - 2100 - Size: 262 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00012.bdjo - LBA: 2101 - 2101 - Size: 262 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00013.bdjo - LBA: 2102 - 2102 - Size: 90 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00086.bdjo - LBA: 2103 - 2103 - Size: 262 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\00087.bdjo - LBA: 2104 - 2104 - Size: 262 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\12345.bdjo - LBA: 2105 - 2105 - Size: 90 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\65535.bdjo - LBA: 2106 - 2106 - Size: 268 bytes

    D 12:59:54 File System - File: \BDMV\BDJO\88888.bdjo - LBA: 2107 - 2107 - Size: 342 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00153.clpi - LBA: 2108 - 2108 - Size: 468 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00239.clpi - LBA: 2109 - 2109 - Size: 336 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00240.clpi - LBA: 2110 - 2110 - Size: 348 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00241.clpi - LBA: 2111 - 2111 - Size: 496 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00242.clpi - LBA: 2112 - 2112 - Size: 324 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00243.clpi - LBA: 2113 - 2113 - Size: 324 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00251.clpi - LBA: 2114 - 2114 - Size: 536 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00282.clpi - LBA: 2115 - 2115 - Size: 336 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00283.clpi - LBA: 2116 - 2116 - Size: 336 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00312.clpi - LBA: 2117 - 2144 - Size: 56,736 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00385.clpi - LBA: 2145 - 2145 - Size: 912 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00387.clpi - LBA: 2146 - 2146 - Size: 572 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00413.clpi - LBA: 2147 - 2147 - Size: 336 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00522.clpi - LBA: 2148 - 2148 - Size: 412 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00523.clpi - LBA: 2149 - 2152 - Size: 7,732 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00524.clpi - LBA: 2153 - 2154 - Size: 3,024 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00525.clpi - LBA: 2155 - 2156 - Size: 3,832 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00526.clpi - LBA: 2157 - 2157 - Size: 1,368 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00527.clpi - LBA: 2158 - 2158 - Size: 452 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00528.clpi - LBA: 2159 - 2159 - Size: 524 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00529.clpi - LBA: 2160 - 2160 - Size: 444 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00530.clpi - LBA: 2161 - 2161 - Size: 648 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00531.clpi - LBA: 2162 - 2162 - Size: 552 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00532.clpi - LBA: 2163 - 2163 - Size: 584 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00533.clpi - LBA: 2164 - 2164 - Size: 624 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00534.clpi - LBA: 2165 - 2165 - Size: 744 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00535.clpi - LBA: 2166 - 2166 - Size: 708 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00536.clpi - LBA: 2167 - 2167 - Size: 812 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00537.clpi - LBA: 2168 - 2168 - Size: 1,412 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00538.clpi - LBA: 2169 - 2169 - Size: 1,008 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00539.clpi - LBA: 2170 - 2170 - Size: 520 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00540.clpi - LBA: 2171 - 2171 - Size: 1,944 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00541.clpi - LBA: 2172 - 2172 - Size: 1,184 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00542.clpi - LBA: 2173 - 2173 - Size: 664 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00543.clpi - LBA: 2174 - 2174 - Size: 816 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00544.clpi - LBA: 2175 - 2175 - Size: 1,444 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00545.clpi - LBA: 2176 - 2176 - Size: 1,416 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00546.clpi - LBA: 2177 - 2177 - Size: 1,224 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00547.clpi - LBA: 2178 - 2178 - Size: 1,456 bytes

    D 12:59:54 File System - File: \BDMV\CLIPINF\00548.clpi - LBA: 2179 - 2179 - Size: 996 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03001.jar - LBA: 2180 - 3027 - Size: 1,735,707 bytes

    D 12:59:54 File System - File: \BDMV\JAR\88888.jar - LBA: 3028 - 3401 - Size: 763,947 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\composite1.png - LBA: 3402 - 3432 - Size: 63,128 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\config.xml - LBA: 3433 - 3435 - Size: 4,290 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\editor.xml - LBA: 3436 - 3437 - Size: 2,709 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\FontSet1.krn - LBA: 3438 - 3482 - Size: 90,930 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\license_agreement.txt - LBA: 3483 - 3493 - Size: 21,331 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\resources.xml - LBA: 3494 - 3499 - Size: 11,643 bytes

    D 12:59:54 File System - File: \BDMV\JAR\00005\titlejump.xml - LBA: 3500 - 3500 - Size: 135 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\activate.bdmv - LBA: 3501 - 3517 - Size: 32,828 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\background.jpg - LBA: 3518 - 3643 - Size: 257,173 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite1.png - LBA: 3644 - 3728 - Size: 172,181 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite1_description.txt - LBA: 3729 - 3734 - Size: 11,000 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite2.png - LBA: 3735 - 5457 - Size: 3,527,371 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite2_description.txt - LBA: 5458 - 5463 - Size: 10,871 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite3.png - LBA: 5464 - 5491 - Size: 56,531 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\composite3_description.txt - LBA: 5492 - 5496 - Size: 9,623 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\counterresource.txt - LBA: 5497 - 5497 - Size: 363 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\fontlarge_aresource.txt - LBA: 5498 - 5545 - Size: 96,805 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\fontlarge_sresource.txt - LBA: 5546 - 5593 - Size: 96,805 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\fontsmall_aresource.txt - LBA: 5594 - 5641 - Size: 98,159 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\fontsmall_sresource.txt - LBA: 5642 - 5689 - Size: 98,159 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\fp_config.txt - LBA: 5690 - 5690 - Size: 177 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\header1resource.txt - LBA: 5691 - 5748 - Size: 118,782 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\large_text_aresource.txt - LBA: 5749 - 5806 - Size: 118,346 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\large_text_sresource.txt - LBA: 5807 - 5864 - Size: 118,346 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\loader.png - LBA: 5865 - 5866 - Size: 3,286 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\loader_description.txt - LBA: 5867 - 5867 - Size: 81 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\perf_test.png - LBA: 5868 - 5869 - Size: 3,007 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\playbackconfig.xml - LBA: 5870 - 5881 - Size: 23,105 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\PlayerSettingRegisters.xml - LBA: 5882 - 5882 - Size: 1,190 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\projectsettings.xml - LBA: 5883 - 5885 - Size: 4,962 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\projectsettingsfilename.xml - LBA: 5886 - 5886 - Size: 151 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\select.bdmv - LBA: 5887 - 5933 - Size: 94,268 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\slider_comp.png - LBA: 5934 - 5978 - Size: 91,568 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\slider_comp_description.txt - LBA: 5979 - 5980 - Size: 3,411 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\sliderfontresource.txt - LBA: 5981 - 5990 - Size: 20,289 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\small_text_aresource.txt - LBA: 5991 - 6048 - Size: 117,591 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\small_text_sresource.txt - LBA: 6049 - 6106 - Size: 117,591 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\ss_slideon.bdmv - LBA: 6107 - 6366 - Size: 531,560 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\streamproperties.xml - LBA: 6367 - 6368 - Size: 2,486 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\stringtable.txt - LBA: 6369 - 6370 - Size: 2,482 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\tier1resource.txt - LBA: 6371 - 6428 - Size: 118,646 bytes

    D 12:59:54 File System - File: \BDMV\JAR\03000\tier2resource.txt - LBA: 6429 - 6486 - Size: 118,699 bytes

    D 12:59:54 File System - File: \BDMV\META\DL\bdmt_eng.xml - LBA: 6487 - 6487 - Size: 405 bytes

    D 12:59:54 File System - File: \BDMV\META\DL\large2.jpg - LBA: 6488 - 6514 - Size: 54,712 bytes

    D 12:59:54 File System - File: \BDMV\META\DL\small2.jpg - LBA: 6515 - 6528 - Size: 27,220 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00002.mpls - LBA: 6529 - 6529 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00003.mpls - LBA: 6530 - 6557 - Size: 56,186 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00011.mpls - LBA: 6558 - 6558 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00017.mpls - LBA: 6559 - 6559 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00018.mpls - LBA: 6560 - 6560 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00020.mpls - LBA: 6561 - 6561 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00021.mpls - LBA: 6562 - 6562 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00051.mpls - LBA: 6563 - 6563 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00052.mpls - LBA: 6564 - 6564 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00115.mpls - LBA: 6565 - 6565 - Size: 186 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00502.mpls - LBA: 6566 - 6566 - Size: 154 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00503.mpls - LBA: 6567 - 6567 - Size: 154 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00504.mpls - LBA: 6568 - 6568 - Size: 362 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00505.mpls - LBA: 6569 - 6569 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00506.mpls - LBA: 6570 - 6570 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00602.mpls - LBA: 6571 - 6571 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00603.mpls - LBA: 6572 - 6572 - Size: 168 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00611.mpls - LBA: 6573 - 6573 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00636.mpls - LBA: 6574 - 6574 - Size: 472 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00637.mpls - LBA: 6575 - 6575 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00638.mpls - LBA: 6576 - 6576 - Size: 170 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00800.mpls - LBA: 6577 - 6577 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00801.mpls - LBA: 6578 - 6578 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00802.mpls - LBA: 6579 - 6579 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00805.mpls - LBA: 6580 - 6580 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00856.mpls - LBA: 6581 - 6581 - Size: 472 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00857.mpls - LBA: 6582 - 6582 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00858.mpls - LBA: 6583 - 6583 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00859.mpls - LBA: 6584 - 6584 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00860.mpls - LBA: 6585 - 6585 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00861.mpls - LBA: 6586 - 6586 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00862.mpls - LBA: 6587 - 6587 - Size: 280 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00863.mpls - LBA: 6588 - 6588 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00864.mpls - LBA: 6589 - 6589 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00865.mpls - LBA: 6590 - 6590 - Size: 376 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00866.mpls - LBA: 6591 - 6591 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00867.mpls - LBA: 6592 - 6592 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00868.mpls - LBA: 6593 - 6593 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00869.mpls - LBA: 6594 - 6594 - Size: 376 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00870.mpls - LBA: 6595 - 6595 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00871.mpls - LBA: 6596 - 6596 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00872.mpls - LBA: 6597 - 6597 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00873.mpls - LBA: 6598 - 6598 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00874.mpls - LBA: 6599 - 6599 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00875.mpls - LBA: 6600 - 6600 - Size: 280 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00876.mpls - LBA: 6601 - 6601 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00877.mpls - LBA: 6602 - 6602 - Size: 184 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00878.mpls - LBA: 6603 - 6603 - Size: 474 bytes

    D 12:59:54 File System - File: \BDMV\PLAYLIST\00879.mpls - LBA: 6604 - 6604 - Size: 186 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00153.m2ts - LBA: 6605 - 31471 - Size: 50,927,616 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00239.m2ts - LBA: 31472 - 31864 - Size: 804,864 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00240.m2ts - LBA: 31865 - 32038 - Size: 356,352 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00241.m2ts - LBA: 32039 - 46459 - Size: 29,534,208 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00242.m2ts - LBA: 46460 - 46621 - Size: 331,776 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00243.m2ts - LBA: 46622 - 46822 - Size: 411,648 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00251.m2ts - LBA: 46823 - 80923 - Size: 69,838,848 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00282.m2ts - LBA: 80924 - 81520 - Size: 1,222,656 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00283.m2ts - LBA: 81521 - 81850 - Size: 675,840 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00312.m2ts - LBA: 81851 - 17350693 - Size: 35,366,590,464 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00385.m2ts - LBA: 17350694 - 17413879 - Size: 129,404,928 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00387.m2ts - LBA: 17413880 - 17449486 - Size: 72,923,136 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00413.m2ts - LBA: 17449487 - 17449933 - Size: 915,456 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00522.m2ts - LBA: 17449934 - 17453041 - Size: 6,365,184 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00523.m2ts - LBA: 17453042 - 19101622 - Size: 3,376,293,888 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00524.m2ts - LBA: 19101623 - 19706236 - Size: 1,238,249,472 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00525.m2ts - LBA: 19706237 - 20386351 - Size: 1,392,875,520 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00526.m2ts - LBA: 20386352 - 20602840 - Size: 443,369,472 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00527.m2ts - LBA: 20602841 - 20626663 - Size: 48,789,504 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00528.m2ts - LBA: 20626664 - 20668867 - Size: 86,433,792 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00529.m2ts - LBA: 20668868 - 20690263 - Size: 43,819,008 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00530.m2ts - LBA: 20690264 - 20758789 - Size: 140,341,248 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00531.m2ts - LBA: 20758790 - 20805694 - Size: 96,061,440 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00532.m2ts - LBA: 20805695 - 20859904 - Size: 111,022,080 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00533.m2ts - LBA: 20859905 - 20921554 - Size: 126,259,200 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00534.m2ts - LBA: 20921555 - 21014251 - Size: 189,843,456 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00535.m2ts - LBA: 21014252 - 21096910 - Size: 169,285,632 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00536.m2ts - LBA: 21096911 - 21197521 - Size: 206,051,328 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00537.m2ts - LBA: 21197522 - 21430477 - Size: 477,093,888 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00538.m2ts - LBA: 21430478 - 21577036 - Size: 300,152,832 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00539.m2ts - LBA: 21577037 - 21618442 - Size: 84,799,488 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00540.m2ts - LBA: 21618443 - 21974113 - Size: 728,414,208 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00541.m2ts - LBA: 21974114 - 22163314 - Size: 387,483,648 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00542.m2ts - LBA: 22163315 - 22236346 - Size: 149,569,536 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00543.m2ts - LBA: 22236347 - 22343062 - Size: 218,554,368 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00544.m2ts - LBA: 22343063 - 22521178 - Size: 364,781,568 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00545.m2ts - LBA: 22521179 - 22702981 - Size: 372,332,544 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00546.m2ts - LBA: 22702982 - 22847653 - Size: 296,288,256 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00547.m2ts - LBA: 22847654 - 23028277 - Size: 369,917,952 bytes

    D 12:59:54 File System - File: \BDMV\STREAM\00548.m2ts - LBA: 23028278 - 23098876 - Size: 144,586,752 bytes

    D 12:59:54 File System - File: \CERTIFICATE\app.discroot.crt - LBA: 23098877 - 23098877 - Size: 876 bytes

    D 12:59:54 File System - File: \CERTIFICATE\bu.discroot.crt - LBA: 23098878 - 23098878 - Size: 814 bytes

    D 12:59:54 File System - File: \CERTIFICATE\id.bdmv - LBA: 23098879 - 23098879 - Size: 104 bytes

    D 12:59:54 File System - File: \CERTIFICATE\online.crl - LBA: 23098880 - 23098880 - Size: 2,048 bytes

    D 12:59:54 File System - File: \CERTIFICATE\online.crt - LBA: 23098881 - 23098881 - Size: 848 bytes

    D 12:59:54 File System - File: \CERTIFICATE\online.sig - LBA: 23098882 - 23098882 - Size: 296 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\app.discroot.crt - LBA: 23098883 - 23098883 - Size: 876 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\bu.discroot.crt - LBA: 23098884 - 23098884 - Size: 814 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\id.bdmv - LBA: 23098885 - 23098885 - Size: 104 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\online.crl - LBA: 23098886 - 23098886 - Size: 2,048 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\online.crt - LBA: 23098887 - 23098887 - Size: 848 bytes

    D 12:59:54 File System - File: \CERTIFICATE\BACKUP\online.sig - LBA: 23098888 - 23098888 - Size: 296 bytes

    D 12:59:54 __ParseFS - Found 301 Files

    I 12:59:54 Operation Started!

    I 12:59:54 Source Device: [7:0:0] PIONEER BD-RW BDR-206 1.06 (H:) (ATA)

    I 12:59:54 Source Media Type: BD-R (Disc ID: CMCMAG-DI6-000)

    I 12:59:54 Source Media Supported Write Speeds: 2x, 4x, 6x

    I 12:59:54 Image File: T:\Images\TNTD - 1920x1080 ImgBurn BluRay Image\TNTD.ISO

    I 12:59:54 Image File Sectors: 23,099,296 (MODE1/2048)

    I 12:59:54 Image File Size: 47,307,358,208 bytes

    I 12:59:54 Image File Volume Identifier: TNTD

    I 12:59:54 Image File Volume Set Identifier: 3D73080001607609

    I 12:59:54 Image File Application Identifier: ImgBurn v2.5.7.0

    I 12:59:54 Image File Implementation Identifier: ImgBurn

    I 12:59:54 Image File File System(s): UDF (2.50)

    I 12:59:54 Read Speed (Data/Audio): MAX / MAX

    D 12:59:55 Calling PdhOpenQuery...

    D 12:59:55 Calling PdhAddCounter(\Processor(_Total)\% Processor Time)...

    D 12:59:55 Calling PdhCollectQueryData...

    D 12:59:55 Calling PdhGetFormattedCounterValue...

    I 12:59:56 Verifying Session 1 of 1... (1 Track, LBA: 0 - 23099295)

    I 12:59:56 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 23099295)

    I 12:59:56 Verifying Layer 0... (LBA: 0 - 12219391)

    I 13:19:51 Verifying Layer 1... (LBA: 12219392 - 23099295)

    D 13:36:29 CryptGetHashParam(File, HP_HASHSIZE) - Size: 16 - Length: 4

    D 13:36:29 CryptGetHashParam(File, HP_HASHVAL) - Length: 16

    D 13:36:44 CryptGetHashParam(Device, HP_HASHSIZE) - Size: 16 - Length: 4

    D 13:36:44 CryptGetHashParam(Device, HP_HASHVAL) - Length: 16

    I 13:36:44 Device MD5: d447c674d7eb18cdaf3d2cc373524d4e

    I 13:36:44 Image MD5: d447c674d7eb18cdaf3d2cc373524d4e

    D 13:36:44 Calling PdhRemoveCounter...

    D 13:36:44 Calling PdhCloseQuery...

    I 13:36:45 Exporting Graph Data...

    I 13:36:45 Graph Data File: C:\Users\Kevin\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-206_1.06_7-22-2012_12-59_PM_CMCMAG-DI6-000_TNTD.ibg

    I 13:36:45 Export Successfully Completed!

    I 13:36:45 Operation Successfully Completed! - Duration: 00:36:49

    I 13:36:45 Average Verify Rate: 20,923 KB/s (4.7x) - Maximum Verify Rate: 28,304 KB/s (6.3x)

    I 14:26:07 Close Request Acknowledged

    I 14:26:07 Closing Down...

    I 14:26:07 Shutting down SPTI...

    I 14:26:07 ImgBurn closed!

     

     

    Any ideas why ImgBurn fails on just certain images? Is it a coincidence that my image and that of the OP are withing 27 MB of each other?

     

    I love ImgBurn, but would like to be able to rely on it to burn ALL my images.

     

    Regards,

    FordMan

  3. It's the reading of the TOC that drives normally fail on.

     

    If you don't cycle the tray then the drive just uses what it has in memory and you'll never know if it can actually read it until the next time you put the disc in the drive - only to find it doesn't work!

     

    So, even if ImgBurn is set to do a sector-by-sector copy, the TOC itself is outside the actual data area, or is within it but read from memory instead of the sector in which it is contained?

     

    Sounds like I need to reconsider if that is the case. It's really not that much of a problem with standard try type drives, but it is a bit of a hassle on laptop drives where the tray needs to be pushed back in, as the OP stated. Hmmm, I've never had a slot loading writer, but it makes me wonder how that would work...

  4. I've found the workaround, but perhaps it would be useful to add an option to "always insert LB flag in images without one" for new users?

     

    If the MDS is present and loaded (with a valid LB value), the correct thing is to assume is that the ISO should not be modified. I'm sorry but I won't be changing that.

     

    By moving the ISO's LB via the use of a custom MDS file, you're technically 'doing it all wrong'. You should recreate the ISO and have ImgBurn fixup the SPLIP flags etc to match the the new MDS file it'll then create.

     

    By recreating the ISO in Build mode you'll also potentially open up a whole load more LB positions that simply weren't available when looking at the ISO as a whole (and where no padding could be applied).

     

    I see you've put the cut/paste option in the newest version, though I've not had a chance to try it yet - thanks!

     

    As far as "doing it all wrong," I have to disagree. If I can make a simple change and move the physical layer break point from somewhere in the midst of a video titleset to before an .IFO file, for instance, and all the while maintain the original file dates/times, original authoring program info, etc, that is contained in the original image, that is doing it all RIGHT per my way of thinking. Those details were the true beauty of your previous, decomissioned program. Anyway, I thought when you first added this capability, it was supposed to fix up the SLIP flags directly in the .IFO and .BUP files of the image, including resetting an existing one in favor of the new one that the user selects? Since I always compare the individual files of my burned discs to the image before erasing the image, I am sure the .IFOs and .BUPs are changed, but I haven't had an existing one for awhile in a titleset that I wanted to relocate to another cell within the same titleset. However, I do recall an old forum message where you replied that ImgBurn should do that, and I provided an example of where it failed. I think it may have been related to the old bug where I pointed out that ImgBurn was corrupting VOBs and NOT adjusting the .BUP when it adjusted the .IFO. I think you found that it was related to the wrong number of bits used in calculating the position within the image file, and it was changing bits in a VOB instead of the .BUP which was further into the image.

     

    In the specific instance I brought up, i.e. Sony discs, I am using this feature to move the physical LB sector from within a titleset where Sony doesn't bother to set the SPLIP flag at all to before an .IFO file of another titleset, and the new position is actually CLOSER to the optimal 50/50 split of the image. Yep, that is definitely doing it all right! Thankfully you forsaw the value of doing this and added the ability to select LB positions from existing images...

     

    fordman

  5. I think it's important - otherwise I wouldn't make the program do it by default!

     

    You probably want the 'cycle tray before verify' checkbox in the Settings on the Write tab.

     

    Thanks LUK.

     

    Edit/Update: I was going to ask why it was necessary, but I have now found out why, with a search.

     

    Mea culpa: I should have searched before.

     

    Thanks for your time.

    Regards,

    M.

     

    It's been awhile since I researched it, but it was something about "clearing buffers" if I remember correctly. Anyway, I disabled the tray cycling for my external USB pioneer drives and have never had a problem with the disc verifying correctly against the image....unless of course not clearing buffers can lead to a false good verification report!....

  6. We'll have to agree to disagree on this one then!

     

    In my mind, the thing representing the other thing has to be the same. In your example, I don't think they are.

     

    A folder representing a folder is ok.

    Folder content representing folder content is ok.

    Folder content representing a folder is not ok.

     

    So basically that leaves us with these following options (to name but a few):

     

    1. Leave it as it is.

    2. Change it to - 'Does the 'X' folder represent the image's root directory?

    3. Change it to - 'Does the 'X' folder represent what should be the root directory for the image?

    4. Change it to - 'Does the 'X' folder represent what should be the image's root directory?

    7. Change it to - 'Does the 'X' folder content represent the root directory content for the image?'

    8. Change it to - 'Does the 'X' folder content represent the image's root directory content?

    9. Change it to - 'Does the 'X' folder content represent the content of the image's root directory?

    10. Change it to - 'Does the 'X' folder content represent the content of the root directory for the image?

    11. Change it to - 'Does the 'X' folder content represent what should be the root directory content?

    12. Change it to - 'Does the 'X' folder content represent what should be the root directory content for the image?

    13. Change it to - 'Does the 'X' folder content represent what should be the image's root directory content?

     

     

    I personally like options 5 and 6 - I love a little mystery in my dialog boxes! :wink:

  7. It's always nice to hear about how different people use different bits of the program :)

     

    btw, when you make a new MDS to overwrite an old one, do you load/add the MDS into the 'Create DVD MDS File' window or do you add the actual image file(s)?

     

    No doubt about it - I LOVE your ImgBurn program, which is one reason I decided to donate awhile back. Since it started handling audio CDs, I've found that I can completely ignore all other CD/DVD burning software on my system. (Side note, I've found that I can reproduce the original CRCs of all audio tracks burned with ImgBurn, while EAC will only allow reproduction of about one-third of the CRCs on the copy!)

     

    I don't actually overwrite the original MDS file. After using ImgBurn to check the original position, I close ImgBurn, move or delete the original MDS and then add the ISO file in the make MDS dialog, manually enter the LB sector number and OTP. It then correctly makes a new MDS with the position I chose. Because of the possible conflict, I never thought of opening the original MDS file. Would the LB sector stored in the original possibly override the sector number I'm putting into the dialog if I used it instead?

     

    By the way, when burning an .ISO/.MSD image set that I've made from a DVD that didn't have a LB flag set, e.g. most Sony titles and SuperBit titles, the burned copy will be the same (no LB), and the log does not show that the flag was reset. I assume this is because the MDS overrides the flag reset logic in ImgBurn to ensure the structure is the same as the original. However, since I want the LB flag set, I've deleted or moved the original MDS in this instance and load the .ISO instead. Then ImgBurn will insert a LB flag (actually modify the ISO image) as desired. I suppose if I made a replacement .MDS, it would burn it as if there was a flag at that sector, but not actually insert it into the relevant .IFO/.BUP in the ISO image? I think I tried it once and that was the case - I found I HAD to burn the .ISO directly to get it to insert the LB flag. I've found the workaround, but perhaps it would be useful to add an option to "always insert LB flag in images without one" for new users?

     

    Thanks again,

     

    fordman

  8. Adding the option to copy the value is a possiblity, I wouldn't bother with the other one.

     

    OK, thanks. When I first used the tool to make the MDS, I somewhat expected that it would use the LB algorithm. The ability to copy and paste the sector number will suffice.

     

    Might I ask why you're having to make the MDS anyway? The program automatically makes the MDS file when Reading or Building an image so (assuming you're using ImgBurn in the first place) there shouldn't be any need.

     

    Certainly, though I'm surprised you would ask why I'm using one of ImgBurn's features. I use it for the same reason you included it in the program! :-)

     

    Seriously though, I imagine you designed it as part of ImgBurn because you could foresee circumstances where a user might need it. In my case there are different instances where I have used it. In one such instance I've used one of your previous programs to make a .ISO/.MDS image set. When burning with ImgBurn, I routinely check for the optimal layer break position even when I have a .MDS with the original location. On several occasions ImgBurn has found more than one possible LB position - the original and alternates. Sometimes I find the alternate to be preferable to the original location, e.g. between titlesets instead of in the middle of a titleset. I've found that as long as the original .MDS is in the directory with the .ISO, ImgBurn will always use that instead of any different position I've chosen in the dialog. Therefore, I make a replacement .MDS with the position I desire. There are of course other instances where I've encountered a .ISO (with compliant LB possibilities), but it had no .MDS with it. The ability to make a .MDS with the desired LB position is valuable in this case also.

     

    Thanks again for your consideration of my suggestion!

  9. Would it be possible to have the MDS file creation tool call up the LB analysis tool to enter the LB sector number chosen automatically?

     

    My current method is to run the LB analysis tool, look at the sector number where I want to create the LB point, and then run the MDS file creation tool and then manually enter the number from memory or by looking at the log. Even the ability to cut the sector number from the LB tool and paste into the MDS file creation tool would be a big improvement....

     

    Regards,

    fordman

  10. You've got debug mode enabled, don't turn it on (as it's not supposed to be on) and you won't get them.

     

    Debug mode is for my usage really, not yours.

     

    The files being output are what directshow outputs + my own wav header. The files aren't used at all, they're simply there for debugging purposes.

     

    Yep, I do indeed like to use debugging mode for all my burns, expecially the extra info recorded when choosing layer break points (I save my logs along with the .IBB files in case I ever want to go back and burn differently).

     

    OK, it's good to know that the original files ARE the ones being burned. I was surprised to see all these new wave files in the directory left behind, and assumed they were being used.

     

    fordman

  11. I've started using ImgBurn for my audio recordings, and noticed that regardless of how my *.wav files are made, i.e. ripped from CD, ImgBurn doesn't simply use those files, and instead makes a copy of them with "ImgBurn" in the filename. Meanwhile, the LOGs show that they are being rendered through "NULL" (the NULL renderer), so I would expect that means ImgBurn recognizes that no filters are needed to make this burn to an audio CD.

     

    Normally this would seem minor, but I've computed CRCs for the copies and they never match the original files, and when one goes ot the trouble of accurate ripping with Exact Audio Copy, it would be better if the WAVEs were recorded "unmolested." What is ImgBurn changing in the WAVE files to prepare them for burning?

     

    fordman

  12. Indeed, there's nothing stopping the program from working under a non-admin user.

     

    In fact, more of it would work on Vista as a standard user (UAC turned on) because you're still allowed SPTI access.

     

    Even if some things don't work (maybe the 'computer information' stuff?), it should still load up and work just fine but with reduced functionality.

     

    I should have been clearer about the SPTI access - I was referring specifically to the installation check under Windows XP on my workplace computer, where I have only user access. There I had to hack the registry to switch DVDInfo Pro to use the SPTI interface (which I had access to because of the allocate cdroms reg hack) instead of ASPI, which DVDInfo Pro suggested should be available to me (if installed) under a normal user account (it was installed for my scanner but didn't work for DVDInfo Pro). For my Vista machine, where I do indeed run most of the type as a user with UAC turned on for security, I did in fact install DVDInfo Pro under my admin account, and it is accessible under my normal user account, albeit with the app crash when I close the drive info window. Under version 5.100, the author has put in a check to see if you are running as an admin, and it displays a dialog informing you that you MUST run as admin and only allows you to close the dialog. It seems purposeful on his part, but perhaps there are some new features that make it a necessity....I will inquire.

     

    In the meantime, thanks again for the command line method of adding performance monitor permissions to my normal user accounts. I've found it far less bothersome to close the crashed DVDInfo Pro dialog when I'm done with my graphing than to log in every time I use ImgBurn.

     

    Ford Man

  13. Have you mentioned this to the DVDInfoPro author?

     

    Not yet, I just discovered it the day before I reported it here. I immediately went back to 4.79 and will stick with it since I don't have any HD drives attached to my computers, so I don't need that HD features in the newest DVDInfo Pro.

     

    Also, it appears to be a purposeful change on his part based on how later versions of 4.xx made assumptions about not having access to SPTI when running under user mode. However, perhaps it would be worthwhile to mention it to the DVDInfo Pro author.

  14. NOTE: For all that are used to using DVDInfo Pro to display burn data directly after an ImgBurn job, the new DVDInfoPro HD version 5.100 totally breaks the ability to use it when logged in as a non-admin user.

     

    The previous version I was using, 4.79, would successfully launch from ImgBurn and display the data, but had an annoying crash when trying to close the drive info screen. This new version 5.100 totally breaks the ability for ImgBurn to launch it from an ImgBurn session run under a non-admin account in addition to refusing to run as a standalone app unless the user has admin permissions.

     

    A big step backward for DVDInfo Pro, in my opinion....

     

    Ford Man

  15. Bring up a command prompt window (running as admin user) and try typing in:

     

    net localgroup "Performance Monitor Users" "%USERNAME%" /add

     

    It basically does the same thing only involves using the keyboard rather than the mouse ;)

     

    GREAT - I cannot wait to try this out when I get home! Thanks!

     

    I was wondering if there was a registry hack or something similar (like I used to give myself access to SPTI on my work XP machine where I have only a user account) that would do this.

     

    I suppose Microsoft eliminates the easy visual tool from Vista Basic to push the user toward Premium or Ultimate. No suprise there.

     

    The only remaining issue that I may have if this does indeed work is with DVDInfo Pro itself. I've found that if I launch DVDInfo Pro separately under a regular user account (Vista or XP), it crashes on exit. Running Imgburn as an admin apparently passes on admin rights to DVDInfo Pro when it launches it, because the DVDInfo Pro crash never happened when running ImgBurn as an admin. I suppose I may now get my full graphs as a regular user, but will start getting the crashes when I close the DVDInfo Pro windows. I'm guessing that DVDInfo Pro is attempting to write to an area of the registry no writeable by regular accounts, e.g. HKEY_LOCAL_MACHINE entries, and crashes when it is unsuccessful. There is apparently some preference for admin accounts by DVDInfo Pro. I've found that it CAN be installed in a non-protected directory like many programs (ImgBurn included) on a non-admin account, but the installation routine warns about not having access to SPTI (on my non-admin XP machine), and that the communications interface needs to be switched to ASPI. DVDInfo Pro's installation doesn't allow for the possibility that the user may have done the "allocate CDROMs" registry hack to gain access to SPTI, and I found that even though it is installed for my old SCSI HP scanner, ASPI wouldn't work anyway. To get around the issue, I ended up copying the relevant communications registry keys from my laptop where I was able to install it as an administrator. I've been meaning to let the DVDInfo Pro author know about these issues...

     

    Thanks again. I'll report back if the commandline method of adding performance monitor permissions doesn't work...

     

    [UPDATE: The command line worked great - I had to use the literal username instead of the variable. As expected, DVDInfo Pro crashes when I close the summary screen (the graph screen closes first without crashing)] - I can live with this. Thanks.

     

    Ford Man

  16. What exactly is missing in Vista basic that the guide doesn't work?

     

    Is the group not in the list or can you not even get so far as seeing the list?

     

    Yes, the "Local Users and Groups" snap-in (I believe that is what Windows calls them) is missing under Windows Vista Basic, even when running completely under an admin account. I've attached a PNG file to illustrate this.

     

    You may want to update the guide at http://forum.imgburn.com/index.php?showtopic=5319 to note that it does not work for Windows Vista Basic.

     

    There was a thread somewhere here (can't find it right now) where another ImgBurn user noted this issue with Vista Basic and recommended changing the properties for ImgBurn.exe to always force it to run as admin so the performance monitors would always be available to DVDInfo Pro... Of course that then kills drag and drop under a regular user account.

     

    Thanks,

    Ford Man

    post-2506-1219841180_thumb.png

  17. Can't you use the bit mentioned in the Guides to get performance counters working?

     

    It seems Vista won't allow D+D between utils running under different security levels. It would probably work ok if ImgBurn was the source app of the D+D, but not the other way around. (i.e. must go highest to lowest)

     

    Thank you all for your replies.

     

    Yes, I followed the guide only to find out that Vista Basic doesn't have the necessary policy control to allow performance counters for non-admin users. Another ImgBurn user noted that in a thread here and I've been using his solution ever since - set ImgBurn to run as administrator by default for all users. That works for the performance counter but not with using drag and drop from windows explorer launched under a non-admin account.

     

    I'll just deal with doing this manually...

  18. You can activate the Drop Zone by going to View->Drop Zone ~ http://forum.imgburn.com/index.php?showtop...ost&p=66435

     

    OK, thanks to both you and blutach! I didn't realize that was a feature!

     

    I tried it, and it has the same limitation when running ImgBurn as administrator while logged in as a regular user. I need to find a way to create two shortcuts, one which points to ImgBurn as an administrator, and one that runs it without logging in as Admin. I tried to create a different shortcut, but apparently when you change the "compatibility settings for all users under the shortcut properties, it is really performing the function on the actual imgburn.exe file, so any shortcut ends up running as admin....

     

    Just a limitation of Vista Basic not being able to provide access to performance monitors for regular users....not an ImgBurn issue.

     

    I will be using the drop zone from now on when I have files from several directories!

  19. Are you using the Drop Zone or trying to drop into Imgburn's queue?

     

    I suppose you would call it the drop zone. It's the large box below "source" in the "Write files/folders to disc" mode. It works if ImgBurn and Windows Explorer are running under the same user, but not if I use it as described earlier.

     

    I'm guessing this is just a windows issue and other programs would behave the same. Perhaps if I open windows explorer as admin also....

  20. There were some topics a while back about how drag and drop doesn't work when dragging folders and files to ImgBurn. Because I was always burning VIDEO DVDs and was used to copying the path and pasting it into "add" entry box, I never experienced that issue. However, I've begun burning more and more file collections, and the drag and drop doesn't work for me, but I realize why.

     

    I am running this on Vista Basic, and as was pointed out in a previous topic, I run ImgBurn as an administrator so I have access to all the performance monitor measures that are then passed on to DVDInfo Pro. I'm sure that the inability to drag and drop is because ImgBurn is opened under Administrator, while the explorer windows that I'm dragging from is opened in my regular user account. I don't have permission to drag to the application opened by the admin account.

     

    So, is there a way to make this scenario work - use drag and drop while keeping my performance measures in Vista basic and running windows under a regular account?

  21. This is an xbox360 image by the looks of it.

     

    Number 1 shouldn't apply (uninstalling said software would confirm, combined with testing in different drives/machines) and it's definitely not anything to do with number 2 (it's was removed in 2.4.1.0).

     

    I'm curious: why did you remove the "fix" in the latest version? I'm glad it's gone, but you seemed to feel pretty strongly about it. Was it causing unintended effects?

  22. Note that this has been observed on a Dell Windows XP machine with both ImgBurn 2.4.0.0 and 2.4.1.0,

     

    That'll be why, you can't go between the two without messing up this setting.

     

    The installer corrects it (sets it back to default) but if that's not being used then it'll get messed up.

     

    Stick to the one version.

     

    Actually, that's not what I meant by that statement. I meant it has happened when using 2.4.0.0 (before the release of 2.4.1.0), and then again once I replaced 2.4.0.0 with 2.4.1.0. These two versions are not being used side by side.

     

    So, the mystery remains...

     

    UPDATE: I've verified that the ImgBurn write type is reset to "Incremental" after powering down the affected computer and booting booting back up. I shut down this computer every night and the next morning when I come in, ImgBurn shows the write type re-set to Incremental even though I had it set to DAO/SAO. As long as I leave the computer running, as I normally do during the course of a day, it will remain set at DAO/SAO, even if I close and re-open ImgBurn. Again, this is on a User account in Windows XP SP2 on which I have access to SPTI. All other options remain on the settings I chose. Any ideas?

  23. Is ImgBurn set to check whether it would be better for a particular drive to record with Incremental versus DAO/SAO? I'm copying .ISO or .ISO/.MDS images, and though I have ImgBurn set to the DAO/SAO writing mode, I'll notice that sometimes it has inexplicably switched to Incremental mode, with no overt change from me! I set it back to DAO/SAO, and the log shows it burns with DAO mode, and I can even shut down ImgBurn, re-start it and the DAO/SAO option is retained. Then days later I'll start ImgBurn and notice in the log that it is burning in Incremental mode!

     

    I understand that Incremental is essentially packet-writing mode and that means the laser may be turned on and off many times when recording, while DAO is theoretically a continuous burn with the laser on, though most recorders recalibrate during the burn, and this may cycle the laser.

     

    Does ImgBurn detect if a particular device or image would be better with Incremental recording and make the switch automatically? If not, has anybody else observed this?

     

    Note that this has been observed on a Dell Windows XP machine with both ImgBurn 2.4.0.0 and 2.4.1.0, and I'm recording to a Pioneer DVR-212 SATA drive. I'm using ImgBurn on a User level account, though I have access to SPTI, and I'm using that as my communications protocol.

     

    This just happened again today, and after switching it back to DAO/SAO that has stuck for subsequent recordings.

     

    Are their any real differences in the recording method on the burned DVD?

     

    Thanks

    fordman

  24. Description of problem:

     

    I put in the ritek/memorex DL disc and Nero tells me it is already written to.

     

    Do you happen to have any packet-writing software like InCD or DirectCD enabled and set to automatically format inserted blank media in the background? A friend of mine that encountered this issue had DirectCD doing this. After I disabled it on his computer, it never happened again.

  25. I did have DVD43 installed, but I tried verifying with it off and I get the same miscompares. I have a pioneer dvr-115d drive and am using Ritek DVD +R disks. This error only happens occasionally, but as I said its is repeatable with those particular images. Also, the images have a set layerbreak. Any thoughts on what might be the problem?

     

    1. Do you have any utilities installed that are similar to DVD43, e.g. AnyDVD? That can sometimes be a cause.

     

    2. Did you copy the image to your hard drive with ImgBurn? I had a similar issue when I copied a non-protected DVD (a wedding video mastered on a MAC) to my hard drive and then burned it with ImgBurn. I copied to the hard drive two ways, one with ISOBuster and one with ImgBurn's Read mode. Before burning, I compared each image with the original DVD, and the one read with ISOBuster compared exactly using ImgBurn's verify mode, while the one read with ImgBurn did NOT! I verified that the MD5 values that ImgBurn was returning for the image files were accurate. I posted this as a suspected bug only to learn that while I was away from the forums for awhile, LUK had implemented code to modify some images (presumably in the structure areas and not data areas) that would make the recorded DVD read more reliably on some standalone DVD players. Apparently there are a limited number of players out there that will refuse to play some discs, and LUK was patching the read image to make it more compatible. In this case, any copy made from the image read by ImgBurn would never compare with the original DVD. I don't have any of those DVD players that have an issue, apparently, so I burned the image read by ISOBuster instead...

     

    Anyway, number 2 is a possibility if you used ImgBurn to read the original DVD.

×
×
  • Create New...

Important Information

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