shadowcaster

As always, thank you !!

Thanks for the firmware tip! Chkdsk and Hard Drive Sentinel report no weak/bad sectors. I'l try a surface scan later tonight. So, are you saying the burn is good? Also, what are those 2 spikes in the export graph and are they significant?

About 50% point, burning a BD25, when a dialog box pops up with the topic message CRC Cyclic redundancy check error re 00000.m2ts. Options are to cancel or retry and I press "retry" and the burn finishes normally. Then during the "verify" process the same message appears again. I press "retry" and the verify finishes successfully. Nowhere in the log files is there an indication that this happenned. ; ; //****************************************\\ ; ImgBurn Version 2.5.6.0 - Log ; Monday, 20 February 2012, 14:47:55 ; \\****************************************// ; ; I 13:45:19 ImgBurn Version 2.5.6.0 started! I 13:45:19 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 13:45:19 Total Physical Memory: 3,652,912 KB - Available: 1,755,240 KB I 13:45:19 Initialising SPTI... I 13:45:19 Searching for SCSI / ATAPI devices... I 13:45:19 -> Drive 1 - Info: HL-DT-ST BD-RE GGW-H20L YL05 (F:) (ATA) I 13:45:20 -> Drive 2 - Info: hp DVD-RAM GH40L RB0E (G:) (ATA) I 13:45:20 -> Drive 3 - Info: Generic DVD-ROM 1.0 (H:) (SCSI) I 13:45:20 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 HD DVD-ROM/BD-RE! I 13:45:25 Operation Started! I 13:45:25 Building Image Tree... I 13:45:25 Calculating Totals... I 13:45:25 Preparing Image... I 13:45:25 Contents: 16 Files, 15 Folders I 13:45:25 Content Type: BD Video I 13:45:25 Data Type: MODE1/2048 I 13:45:25 File System(s): UDF (2.50) I 13:45:25 Volume Label: [Not Configured] I 13:45:25 Size: 24,883,917,500 bytes I 13:45:25 Sectors: 12,150,361 I 13:45:25 Image Size: 24,884,936,704 bytes I 13:45:25 Image Sectors: 12,150,848 I 13:45:25 Operation Successfully Completed! - Duration: 00:00:00 I 13:47:13 Operation Started! I 13:47:13 Building Image Tree... I 13:47:13 Calculating Totals... I 13:47:13 Preparing Image... I 13:47:13 Contents: 16 Files, 15 Folders I 13:47:13 Content Type: BD Video I 13:47:13 Data Type: MODE1/2048 I 13:47:13 File System(s): UDF (2.50) I 13:47:13 Volume Label: The_Phantom_Of_The_Opera I 13:47:13 Size: 24,883,917,500 bytes I 13:47:13 Sectors: 12,150,361 I 13:47:13 Image Size: 24,884,936,704 bytes I 13:47:13 Image Sectors: 12,150,848 I 13:47:16 Operation Successfully Completed! - Duration: 00:00:02 I 13:47:16 Operation Started! I 13:47:16 Source File: -==/\/[bUILD IMAGE]\/\==- I 13:47:16 Source File Sectors: 12,150,848 (MODE1/2048) I 13:47:16 Source File Size: 24,884,936,704 bytes I 13:47:16 Source File Volume Identifier: The_Phantom_Of_The_Opera I 13:47:16 Source File Volume Set Identifier: 40546DE600B967D9 I 13:47:16 Source File Application Identifier: ImgBurn v2.5.6.0 I 13:47:16 Source File Implementation Identifier: ImgBurn I 13:47:16 Source File File System(s): UDF (2.50) I 13:47:16 Destination Device: [3:1:0] HL-DT-ST BD-RE GGW-H20L YL05 (F:) (ATA) I 13:47:16 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 13:47:16 Destination Media Supported Write Speeds: 2x, 4x, 6x I 13:47:16 Destination Media Sectors: 12,219,392 I 13:47:16 Write Mode: BD I 13:47:16 Write Type: DAO I 13:47:16 Write Speed: 4x I 13:47:16 BD-R Verify Not Required: Yes I 13:47:16 Link Size: Auto I 13:47:16 Lock Volume: Yes I 13:47:16 Test Mode: No I 13:47:16 OPC: No I 13:47:16 BURN-Proof: Enabled I 13:47:16 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 13:47:27 Filling Buffer... (60 MB) I 13:47:28 Writing LeadIn... I 13:47:28 Writing Session 1 of 1... (1 Track, LBA: 0 - 12150847) I 13:47:28 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12150847) I 14:14:59 Synchronising Cache... I 14:15:02 Closing Track... I 14:15:03 Finalising Disc... I 14:15:12 Exporting Graph Data... I 14:15:12 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_MONDAY-FEBRUARY-20-2012_1-47_PM_VERBAT-IMe-000_4x.ibg I 14:15:12 Export Successfully Completed! I 14:15:12 Operation Successfully Completed! - Duration: 00:27:56 I 14:15:12 Average Write Rate: 14,728 KB/s (3.3x) - Maximum Write Rate: 18,326 KB/s (4.1x) I 14:15:12 Cycling Tray before Verify... W 14:15:21 Waiting for device to become ready... I 14:15:36 Device Ready! I 14:15:37 Operation Started! I 14:15:37 Source Device: [3:1:0] HL-DT-ST BD-RE GGW-H20L YL05 (F:) (ATA) I 14:15:37 Source Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 14:15:37 Source Media Supported Write Speeds: 2x, 4x, 6x I 14:15:37 Image File: -==/\/[bUILD IMAGE]\/\==- I 14:15:37 Image File Sectors: 12,150,848 (MODE1/2048) I 14:15:37 Image File Size: 24,884,936,704 bytes I 14:15:37 Image File Volume Identifier: The_Phantom_Of_The_Opera I 14:15:37 Image File Volume Set Identifier: 40546DE600B967D9 I 14:15:37 Image File Application Identifier: ImgBurn v2.5.6.0 I 14:15:37 Image File Implementation Identifier: ImgBurn I 14:15:37 Image File File System(s): UDF (2.50) I 14:15:37 Read Speed (Data/Audio): MAX / MAX I 14:15:38 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12150847) I 14:15:38 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12150847) I 14:47:17 Exporting Graph Data... I 14:47:17 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_MONDAY-FEBRUARY-20-2012_1-47_PM_VERBAT-IMe-000_4x.ibg I 14:47:17 Export Successfully Completed! I 14:47:17 Operation Successfully Completed! - Duration: 00:31:39 I 14:47:17 Average Verify Rate: 12,810 KB/s (2.8x) - Maximum Verify Rate: 33,086 KB/s (7.4x) I 14:47:55 Close Request Acknowledged I 14:47:55 Closing Down... I 14:47:55 Shutting down SPTI... I 14:47:55 ImgBurn closed! Export graph : I also ran a read test in DVDinfoPro and there were no errors. The disc appears to play properly at the time point of the message so is this a problem or not ? Thanks

Same result, 1x. Edit: BTW, they play fine in a SA BD player, so I assume that the media has no problem with the 1x burn speed ?

Here's one of a BD-25 that I tried the other day, and the write rate was correct @ 2X : I 13:30:31 ImgBurn Version 2.5.5.0 started! I 13:30:31 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 13:30:31 Total Physical Memory: 3,128,624 KB - Available: 2,364,996 KB I 13:30:31 Initialising SPTI... I 13:30:31 Searching for SCSI / ATAPI devices... I 13:30:31 -> Drive 1 - Info: ATAPI DVD A DH16A1L KH3B (F:) (ATA) I 13:30:31 -> Drive 2 - Info: HL-DT-ST BD-RE GGW-H20L YL05 (E:) (ATA) I 13:30:31 -> Drive 3 - Info: Generic DVD-ROM 1.0 (G:) (SCSI) I 13:30:31 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 HD DVD-ROM/BD-RE! I 13:31:46 Operation Started! I 13:31:46 Building Image Tree... I 13:31:46 Calculating Totals... I 13:31:46 Preparing Image... I 13:31:46 Contents: 9 Files, 14 Folders I 13:31:46 Content Type: BD Video I 13:31:46 Data Type: MODE1/2048 I 13:31:46 File System(s): UDF (2.50) I 13:31:46 Volume Label: [Not Configured] I 13:31:46 Size: 24,463,801,506 bytes I 13:31:46 Sectors: 11,945,222 I 13:31:46 Image Size: 24,464,850,944 bytes I 13:31:46 Image Sectors: 11,945,728 I 13:31:46 Operation Successfully Completed! - Duration: 00:00:00 I 13:32:46 Operation Started! I 13:32:46 Building Image Tree... I 13:32:46 Calculating Totals... I 13:32:46 Preparing Image... I 13:32:46 Contents: 9 Files, 14 Folders I 13:32:46 Content Type: BD Video I 13:32:46 Data Type: MODE1/2048 I 13:32:46 File System(s): UDF (2.50) I 13:32:46 Volume Label: The_International I 13:32:46 Size: 24,463,801,506 bytes I 13:32:46 Sectors: 11,945,222 I 13:32:46 Image Size: 24,464,850,944 bytes I 13:32:46 Image Sectors: 11,945,728 I 13:32:47 Operation Successfully Completed! - Duration: 00:00:01 I 13:32:47 Operation Started! I 13:32:47 Source File: -==/\/[bUILD IMAGE]\/\==- I 13:32:47 Source File Sectors: 11,945,728 (MODE1/2048) I 13:32:47 Source File Size: 24,464,850,944 bytes I 13:32:47 Source File Volume Identifier: The_International I 13:32:47 Source File Volume Set Identifier: 3E696C1700B64686 I 13:32:47 Source File Application Identifier: ImgBurn v2.5.5.0 I 13:32:47 Source File Implementation Identifier: ImgBurn I 13:32:47 Source File File System(s): UDF (2.50) I 13:32:47 Destination Device: [0:1:0] HL-DT-ST BD-RE GGW-H20L YL05 (E:) (ATA) I 13:32:47 Destination Media Type: BD-R (Disc ID: VERBAT-IMc-000) (Speeds: 2x, 4x, 6x) I 13:32:47 Destination Media Sectors: 12,219,392 I 13:32:47 Write Mode: BD I 13:32:47 Write Type: DAO I 13:32:47 Write Speed: 2x I 13:32:47 BD-R Verify Not Required: Yes I 13:32:47 Link Size: Auto I 13:32:47 Lock Volume: Yes I 13:32:47 Test Mode: No I 13:32:47 OPC: No I 13:32:47 BURN-Proof: Enabled I 13:32:47 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 13:32:58 Filling Buffer... (60 MB) I 13:32:59 Writing LeadIn... I 13:32:59 Writing Session 1 of 1... (1 Track, LBA: 0 - 11945727) I 13:32:59 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11945727) I 14:17:35 Synchronising Cache... I 14:17:37 Closing Track... I 14:17:38 Finalising Disc... I 14:17:48 Exporting Graph Data... I 14:17:48 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\ Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_WEDNESDAY-MARCH-09-2011_1-32_PM_VERBAT-IMc-000_2x.ibg I 14:17:48 Export Successfully Completed! I 14:17:48 Operation Successfully Completed! - Duration: 00:45:00 I 14:17:48 Average Write Rate: 8,931 KB/s (2.0x) - Maximum Write Rate: 9,268 KB/s (2.1x) I 14:17:48 Cycling Tray before Verify... snipped

Here's the latest one from today : ; //****************************************\\ ; ImgBurn Version 2.5.5.0 - Log ; Sunday, 13 March 2011, 16:16:36 ; \\****************************************// I 13:02:12 ImgBurn Version 2.5.5.0 started! I 13:02:12 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 13:02:12 Total Physical Memory: 3,128,624 KB - Available: 1,952,920 KB I 13:02:12 Initialising SPTI... I 13:02:12 Searching for SCSI / ATAPI devices... I 13:02:13 -> Drive 1 - Info: ATAPI DVD A DH16A1L KH3B (F:) (ATA) I 13:02:13 -> Drive 2 - Info: HL-DT-ST BD-RE GGW-H20L YL05 (E:) (ATA)I 13:02:13 -> Drive 3 - Info: Generic DVD-ROM 1.0 (G:) (SCSI) I 13:02:13 Found 1 DVD-ROM, 1 DVD±RW/RAM and 1 HD DVD-ROM/BD-RE! I 13:04:53 Operation Started! I 13:04:53 Building Image Tree... I 13:04:53 Calculating Totals... I 13:04:53 Preparing Image... I 13:04:53 Contents: 190 Files, 16 Folders I 13:04:53 Content Type: BD Video I 13:04:53 Data Type: MODE1/2048 I 13:04:53 File System(s): UDF (2.50) I 13:04:53 Volume Label: The_Thin_Red_Line I 13:04:53 Size: 49,843,403,916 bytes I 13:04:53 Sectors: 24,337,713 I 13:04:53 Image Size: 49,845,436,416 bytes I 13:04:53 Image Sectors: 24,338,592 I 13:05:00 Operation Successfully Completed! - Duration: 00:00:06 I 13:05:00 Operation Started! I 13:05:00 Source File: -==/\/[bUILD IMAGE]\/\==- I 13:05:00 Source File Sectors: 24,338,592 (MODE1/2048) I 13:05:00 Source File Size: 49,845,436,416 bytes I 13:05:00 Source File Volume Identifier: The_Thin_Red_Line I 13:05:00 Source File Volume Set Identifier: 3E6D689A01735F71 I 13:05:00 Source File Application Identifier: ImgBurn v2.5.5.0 I 13:05:00 Source File Implementation Identifier: ImgBurn I 13:05:00 Source File File System(s): UDF (2.50) I 13:05:00 Destination Device: [0:1:0] HL-DT-ST BD-RE GGW-H20L YL05 (E:) (ATA) I 13:05:00 Destination Media Type: BD-R (Disc ID: VERBAT-IMd-000) (Speeds: 2x, 4x) I 13:05:00 Destination Media Sectors: 24,438,784 I 13:05:00 Write Mode: BD I 13:05:00 Write Type: DAO I 13:05:00 Write Speed: 2x I 13:05:00 BD-R Verify Not Required: Yes I 13:05:00 Link Size: Auto I 13:05:00 Lock Volume: Yes I 13:05:00 Test Mode: No I 13:05:00 OPC: No I 13:05:00 BURN-Proof: Enabled I 13:05:00 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 13:05:49 Filling Buffer... (60 MB) I 13:05:50 Writing LeadIn... I 13:05:51 Writing Session 1 of 1... (1 Track, LBA: 0 - 24338591) I 13:05:51 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24338591) I 13:05:51 Writing Layer 0... (LBA: 0 - 12219391) I 14:38:44 Writing Layer 1... (LBA: 12219392 - 24338591) I 16:10:55 Synchronising Cache... I 16:10:57 Closing Track... I 16:10:58 Finalising Disc... I 16:11:22 Exporting Graph Data... I 16:11:22 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_SUNDAY-MARCH-13-2011_1-05_PM_VERBAT-IMd-000_2x.ibg I 16:11:22 Export Successfully Completed! I 16:11:22 Operation Successfully Completed! - Duration: 03:06:21 I 16:11:22 Average Write Rate: 4,384 KB/s (1.0x) - Maximum Write Rate: 4,698 KB/s (1.0x) I 16:16:36 Close Request Acknowledged I 16:16:36 Closing Down... I 16:16:36 Shutting down SPTI... I 16:16:36 ImgBurn closed!

I realize that this is not an Imgburn issue, but thought I may still find the answer here. Imgburn 2.5.5.0 PC: HP xw4600 workstation, core2 duo @ 3.0ghz, 4g ram C: drive @ 500gb, D: drive 1 TB with 400 gb free space Mode: Build, with an SATA LG GGW-H20l 6x BD burner as destination. Source Blu-ray files/structure are on D: drive 2X write speed, UDF file system selected. With Verbatim Verb-imd-00 2x,4x BD-dl 50gb media, I set the write speed to 2x and log shows successful. However, the burn proceeds at 1X write rate. 3 times now. (before a system crash and restore from a backup, 2X worked fine). CPU usage is ~6% and Page file is ~1100 (set to custom @2048-4092 for drive C and none for drive D, the source drive.) Although the media is rated 2x-4x is the 1x burn still a quality burn? I've read in my searching that a slower than rated speed can cause errors and jitter. My burner doesn't support Opti Drive, etc. so I can't test. BTW, BD-25 Verbatim burns fine @ 2x as well as other dvd/cd media at their selected speeds. It's only the BD-50 that drops to the slower speed. I don't run any other apps while burning. Any help is much appreciated. 3 hr burns are just a little too long. Incidently, would creating an image file first, and then burn, help the set speed at all? Or possibly creating a page file for the source drive ?

Thanks Lightning !

The default buffer size @ 40mb is always @100% when burning. Is there any advantage/benefit to making it larger, say 60 or 80 mb? (no, I havn't tried it yet)

There were other threads on this topic, this was one of them from Feb, without a follow up : http://forum.imgburn.com/index.php?showtopic=13782 The error : failed to write sectors xxxxx-xxxxx reason: a device attached to the system is not functioning. Happened 5 times in this BD burn but also in a DVD+R burn. Also did it in a "test mode" w/a DVD-R. Did a Google search and found nothing. BTW, the below burn log file plays fine in a standalone BD player in spite of the errors. I guess the retry function really works ! Thanks Lightning UK !! I 15:44:35 Destination Media Type: BD-R (Disc ID: VERBAT-IMc-00) (Speeds: 2x, 4x, 6x) I 15:44:35 Destination Media Sectors: 12,219,392 I 15:44:35 Write Mode: BD I 15:44:35 Write Type: DAO I 15:44:35 Write Speed: 2x I 15:44:35 BD-R Verify Not Required: Yes I 15:44:35 Link Size: Auto I 15:44:35 Lock Volume: Yes I 15:44:35 Test Mode: No I 15:44:35 OPC: No I 15:44:35 BURN-Proof: Enabled I 15:44:35 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 15:44:48 Filling Buffer... (40 MB) I 15:44:48 Writing LeadIn... I 15:44:49 Writing Session 1 of 1... (1 Track, LBA: 0 - 11841151) I 15:44:49 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11841151) W 15:47:54 Failed to Write Sectors 829504 - 829535 - Reason: A device attached to the system is not functioning. W 15:47:54 Retrying (1 of 20)... I 15:47:54 Writing Sectors... W 15:57:55 Failed to Write Sectors 3511072 - 3511103 - Reason: A device attached to the system is not functioning. W 15:57:55 Retrying (1 of 20)... I 15:57:55 Writing Sectors... W 16:07:55 Failed to Write Sectors 6191456 - 6191487 - Reason: A device attached to the system is not functioning. W 16:07:55 Retrying (1 of 20)... I 16:07:55 Writing Sectors... W 16:17:55 Failed to Write Sectors 8871872 - 8871903 - Reason: A device attached to the system is not functioning. W 16:17:56 Retrying (1 of 20)... I 16:17:56 Writing Sectors... W 16:27:56 Failed to Write Sectors 11551936 - 11551967 - Reason: A device attached to the system is not functioning. W 16:27:56 Retrying (1 of 20)... I 16:27:56 Writing Sectors... I 16:29:01 Synchronising Cache... I 16:29:03 Closing Track... I 16:29:04 Finalising Disc... I 16:29:14 Exporting Graph Data... I 16:29:14 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_THURSDAY-OCTOBER-21-2010_3-44_PM_VERBAT-IMc-00_2x.ibg I 16:29:14 Export Successfully Completed! I 16:29:14 Operation Successfully Completed! - Duration: 00:44:39 I 16:29:14 Average Write Rate: 8,929 KB/s (2.0x) - Maximum Write Rate: 9,693 KB/s (2.2x) I was using Imgburn 2.5.0.0 and never seen this before. The only changes to my system was upgrading to V 2.5.2.0 plus installing Adaptec udf driver (for some reason my Windows explorer was no longer reading udf disc files.) Well, the Adaptec driver didn't work, so I installed the Toshiba udf driver, which did work. So, I started the simple route and uninstalled both udf drivers, rebooted an problem solved. NO more failed to write errors. I'm posting this so that anyone else who runs into this problem won't look at Imgburn as the culprit. I'm still puzzled as to why the udf read drivers would affect the burning process. I never would have looked at them as the problem if it wasn't for the fact that there were only the 3 changes to my system.

Thanks Lightning...I thought that might be the case, but wanted to confirm because I don't get that warning on CD,DVD and DVD-DL burns.

This is my first burn of a Verbatim BD-R 4X on a LG GGW-H20L YL05 and I'm a little confused by the speed mismatch warning below. The burn was successful. The drive is rated @ 2x,4x,6x and the media, altough ImgBurn shows 2,4 6 capable, is rated @ 4X. So, the question is why , when I selct 4X write speed, does the log warn mismatch and says changed to 6X. Then the final write speed, the last line of the log, shows it is in fact written @ 4X ?? Log : I 10:44:10 Source File Application Identifier: ImgBurn v2.5.0.0 I 10:44:10 Source File Implementation Identifier: ImgBurn I 10:44:10 Source File File System(s): UDF (2.50) I 10:44:10 Destination Device: [0:1:0] HL-DT-ST BD-RE GGW-H20L YL05 (E:) (ATA) I 10:44:10 Destination Media Type: BD-R (Disc ID: VERBAT-IMc-00) (Speeds: 2x, 4x, 6x) I 10:44:10 Destination Media Sectors: 12,219,392 I 10:44:10 Write Mode: BD I 10:44:10 Write Type: DAO I 10:44:10 Write Speed: 4x I 10:44:10 BD-R Verify Not Required: Yes I 10:44:10 Link Size: Auto I 10:44:10 Lock Volume: Yes I 10:44:10 Test Mode: No I 10:44:10 OPC: No I 10:44:10 BURN-Proof: Enabled W 10:44:10 Write Speed Miscompare! - Wanted: 17,982 KB/s (4x), Got: 26,972 KB/s (6x)I 10:44:23 Filling Buffer... (40 MB) I 10:44:24 Writing LeadIn... I 10:44:24 Writing Session 1 of 1... (1 Track, LBA: 0 - 12044223) I 10:44:24 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12044223) I 11:07:01 Synchronising Cache... I 11:07:04 Closing Track... I 11:07:05 Finalising Disc... I 11:07:14 Exporting Graph Data... I 11:07:14 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_WEDNESDAY-NOVEMBER-04-2009_10-44_AM_VERBAT-IMc-00_4x.ibg I 11:07:14 Export Successfully Completed! I 11:07:14 Operation Successfully Completed! - Duration: 00:23:03 I 11:07:14 Average Write Rate: 17,764 KB/s (4.0x) - Maximum Write Rate: 18,720 KB/s (4.2x)

The 'write speed miscompare' line is a result of a simple query to the drive to get the current write speed from it. If it's not the same as the one you selected, a warning is issued. It's only as reliable as the drive is at reporting the configured speed. Thanks Lightning....I tried another burn since then and this time it was fine. Selected 8X and burned @ ~8X.

Imgburn V2.5 I've been using an LG drive to date with no problems. I just installed a new LG BD burner, latest fw, and when I burned my first dvd , 6X selected, I got a warning in the log that there was a speed mismatch, got 16.5X!. Yet, last line of the log shows an average of 3.9X : I 16:21:40 Destination Device: [0:1:0] HL-DT-ST BD-RE [b]GGW-H20L YL05 [/b](H:) (ATA) I 16:21:40 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 8x, 12x, 16x) I 16:21:40 Destination Media Sectors: 2,295,104 I 16:21:40 Write Mode: DVD I 16:21:40 Write Type: DAO I 16:21:40 Write Speed: 6x I 16:21:40 DVD+R Reserve Track: No I 16:21:40 Link Size: Auto I 16:21:40 Lock Volume: Yes I 16:21:40 Test Mode: No I 16:21:40 OPC: No I 16:21:40 BURN-Proof: Enabled [b][color="#FF00FF"]W 16:21:40 Write Speed Miscompare! - Wanted: 8,310 KB/s (6x), Got: 22,304 KB/s (16.5x)[/color][/b] I 16:21:40 Book Type Setting: DVD-ROM I 16:21:40 Filling Buffer... (40 MB) I 16:21:41 Writing LeadIn... I 16:21:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 2182751) I 16:21:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2182751) I 16:35:31 Synchronising Cache... I 16:35:32 Closing Track... I 16:35:35 Finalising Disc... I 16:36:25 Exporting Graph Data... I 16:36:25 Graph Data File: C:\Documents and Settings\Administrator\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_GGW-H20L_YL05_MONDAY-AUGUST-31-2009_4-21_PM_MCC-004-00_6x.ibg I 16:36:25 Export Successfully Completed! I 16:36:25 Operation Successfully Completed! - Duration: 00:14:45 I 16:36:25 [b][color="#FF00FF"]Average Write Rate: 5,343 KB/s (3.9x) - Maximum Write Rate: 5,592 KB/s (4.0x[/color][/b] This is the same Verbatim DVD-R media that I've been using. So, is this a function of Imgburn that's causing this strange mis match warning?

Thanks for the response. I do realize that SPTI and SPTD are not the same thing, but should have clarified my question.

According to Daemon T sptd is installed for ver 4.0 and above. I'm running 3.47 and also got the sptd warning. I noticed in the changelog for 2.5 that ---"Changed: The SPTI device enumeration method now defaults to 'Device Interface' on XP SP2/2003 SP2 + IMAPI v2.0, XP SP3, Vista and newer. I previously selected/defaulted to "Device Class" (running XP sp3) Which one should I set it to and will it affect the sptd warning ?

That makes sense ! Good programming Lightning. Thanks for the quick response. Now I'll give that burn a try.

When preparing to burn a standard video dvd ~8gb, a layer break box appears after using the "calculator", that suggests 1 or more layer break positions. However, this layer break info does NOT appear when preparing to burn an AVCHD video file structure or ISO (ie bdmv/certificate folders structure) It appears to treat it as it would a data file(s). So, my question is, when burning ~8gb AVCHD video DL disc, what does ImgBurn choose as the layer break, if any, or does it just fill the first layer to capacity and then move to the second layer. Inquiring minds (mine) would like to know. Thanks

The resulting root folder is the BDMV and it's sub folders. Yes, the options screen looks exactly like the one in the guide. Interestingly, if I create an image file (rather than burning) to the HDD, the resulting image contains the "certificate" folder. Whether I include the Certificate folder, or not, it will be there. If I then burn that image file, it contains the certificate folder. Interesting ! Edit : OK, problem solved. It was a combination of 2 bad DVD-RW and the fact that I had the files loaded on a virtual drive. The disk wasn't being read (even though the burn said successful) and I was then inadvertantly exploring the virtual drive, which had the original bdmv folder only.)

Using latest ver of Imgburn: Per the guide, I'm adding the bdmv and certificate folder to the file list. However, the burned dvd is missing the certificate folder (original is empty except for a "backup" folder, also empty.) In fact, from my understanding, if the certificate folder is not added to the file list, Imgburn will add it for you. Tried that, and it didn't. Any explanation would be appreciated. Edit: Log, if needed - I 13:37:05 Operation Started! I 13:37:05 Source File: -==/\/[bUILD IMAGE]\/\==- I 13:37:05 Source File Sectors: 1,158,416 (MODE1/2048) I 13:37:05 Source File Size: 2,372,435,968 bytes I 13:37:05 Source File Volume Identifier: test I 13:37:05 Source File Application Identifier: ImgBurn v2.4.2.0 I 13:37:05 Source File Implementation Identifier: ImgBurn I 13:37:05 Source File File System(s): UDF (2.50) I 13:37:05 Destination Device: [1:0:0] HL-DT-ST DVD+-RW GSA-H31L W618 (E:) (ATA) I 13:37:05 Destination Media Type: DVD+RW (Disc ID: MKM-A02-00) (Speeds: 4x) I 13:37:05 Destination Media Sectors: 2,295,104 I 13:37:05 Write Mode: DVD I 13:37:05 Write Type: DAO I 13:37:05 Write Speed: 4x I 13:37:05 Link Size: Auto I 13:37:05 Test Mode: No I 13:37:05 OPC: No I 13:37:05 BURN-Proof: Enabled I 13:37:05 Book Type Setting: N/A I 13:37:05 Filling Buffer... (40 MB) I 13:37:06 Writing LeadIn... I 13:37:26 Writing Session 1 of 1... (1 Track, LBA: 0 - 1158415) I 13:37:26 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1158415) I 13:44:33 Synchronising Cache... I 13:44:34 Closing Session...

Maybe more players than I thought. It is strange that Sammy enabled that playbck in the earlier model 1200 and then disabled the ability in the newer 1400. Don't know about the newest model 1500. I suspect that more and more folks will be making backups of their Blu-ray discs as the price of the media and the burners continue to decline. Especially with the pain of keeping up with FW updates on the SA's, in order to play new releases w/o problems. Samsung's are notorious for this.

Thanks Lightning. Most SA players don't play BD-R/RE discs, so making backups of movies, at this point, is a no-go for most of us. Edit : Interestingly my older Samsung 1200 will play BD-R/RE

Is Imgburn able to change the booktype on BR-R/RE discs to BD-Rom? Because most SA players (like my Sammy 1400, won't play these discs, according to the manual) Will future releases of Imgburn have greater support for Blu-ray ?

Is Imgburn able to change the booktype on BR-R/RE discs to BD-Rom? (I thought the op might have this problem) Because most SA players (like my Sammy 1400, won't play these discs, according to the manual) Will future releases of Imgburn have greater support for Blu-ray ?

Handler is correct. What I'm experiencing is exactly the opposite of your post. Layer 0 is the one with greater errors (as seen in the scan). It's not a problem, I was just curious why this was the case.