Jump to content

ImgBurn Layerbreak Miscompare Warning


ddebon1

Recommended Posts

Hi guys I'm new to the forum and did a search but was unable to find anything conclusive.

 

I just bought a new LG external burner Model: GE24LU20. I am using Memorex DVD+DL 8x. I have tried Verbatims and have gotten same error.

 

While burning backups I received the layerbreak miscompare warning, however the disc still burned and verified. The verification said that the layerbreak was 1913760 even though I got a warning during the writing process.

 

I also checked for firmware updates and there is none.

 

Here is the log:

 

I 18:10:20 ImgBurn Version 2.5.5.0 started!
I 18:10:20 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 18:10:20 Total Physical Memory: 6,273,096 KB  -  Available: 4,099,712 KB
I 18:10:20 Initialising SPTI...
I 18:10:20 Searching for SCSI / ATAPI devices...
I 18:10:20 -> Drive 1 - Info: Optiarc BD ROM BC-5500H 1.70 (G:) (ATAPI)
I 18:10:21 -> Drive 2 - Info: HL-DT-ST DVDRAM GE24LU20 OL00 (H:) (USB)
I 18:10:21 Found 1 DVD±RW/RAM and 1 BD-ROM/DVD±RW!
I 18:11:19 Operation Started!
I 18:11:19 Source File: C:\Users\---------\Xbox 360 Games\MX v ATV Alive SSv2\MXvATV.dvd
I 18:11:19 Source File Sectors: 3,827,488 (MODE1/2048)
I 18:11:19 Source File Size: 7,838,695,424 bytes
I 18:11:19 Source File Volume Identifier: DVD_ROM
I 18:11:19 Source File Volume Set Identifier: d0a44000MS UDFBridge
I 18:11:19 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 18:11:19 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 18:11:19 Source File File System(s): ISO9660, UDF (1.50)
I 18:11:19 Destination Device: [0:0:0] HL-DT-ST DVDRAM GE24LU20 OL00 (H:) (USB)
I 18:11:19 Destination Media Type: DVD+R DL (Disc ID: RITEK-S04-66) (Speeds: 2.4x, 4x, 6x, 8x)
I 18:11:19 Destination Media Sectors: 4,173,824
I 18:11:19 Write Mode: DVD
I 18:11:19 Write Type: DAO
I 18:11:19 Write Speed: MAX
I 18:11:19 Link Size: Auto
I 18:11:19 Lock Volume: Yes
I 18:11:19 Test Mode: No
I 18:11:19 OPC: No
I 18:11:19 BURN-Proof: Enabled
I 18:11:19 Write Speed Successfully Set! - Effective: 11,079 KB/s (8x)
I 18:11:19 Book Type Setting: DVD-ROM
I 18:11:19 User Specified L0 Data Zone Capacity: 1,913,760
W 18:11:19 L0 Data Zone Capacity Miscompare!
W 18:11:19 Wanted: 1913760, Got: 2086912
I 18:11:23 Filling Buffer... (40 MB)
I 18:11:24 Writing LeadIn...
I 18:12:08 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487)
I 18:12:08 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)
I 18:12:08 Writing Layer 0... (LBA: 0 - 1913759)
I 18:18:58 Writing Layer 1... (LBA: 1913760 - 3827487)
I 18:25:47 Synchronising Cache...
I 18:25:49 Closing Track...
I 18:25:53 Finalising Disc...
I 18:26:57 Exporting Graph Data...
I 18:26:57 Graph Data File: C:\Users\-----------\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GE24LU20_OL00_FRIDAY-MAY-13-2011_6-11_PM_RITEK-S04-66_MAX.ibg
I 18:26:57 Export Successfully Completed!
I 18:26:57 Operation Successfully Completed! - Duration: 00:15:38
I 18:26:57 Average Write Rate: 9,346 KB/s (6.7x) - Maximum Write Rate: 11,133 KB/s (8.0x)
I 18:26:57 Cycling Tray before Verify...
W 18:27:07 Waiting for device to become ready...
I 18:27:26 Device Ready!
I 18:27:29 Operation Started!
I 18:27:29 Source Device: [0:0:0] HL-DT-ST DVDRAM GE24LU20 OL00 (H:) (USB)
I 18:27:29 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: RITEK-S04-66) (Speeds: 2.4x, 4x, 6x, 8x)
I 18:27:29 Image File: C:\Users\-------\Xbox 360 Games\MX v ATV Alive SSv2\MXvATV.dvd
I 18:27:29 Image File Sectors: 3,827,488 (MODE1/2048)
I 18:27:29 Image File Size: 7,838,695,424 bytes
I 18:27:29 Image File Volume Identifier: DVD_ROM
I 18:27:29 Image File Volume Set Identifier: d0a44000MS UDFBridge
I 18:27:29 Image File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 18:27:29 Image File Implementation Identifier: Microsoft CDIMAGE UDF
I 18:27:29 Image File File System(s): ISO9660, UDF (1.50)
I 18:27:29 Read Speed (Data/Audio): MAX / MAX
I 18:27:29 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3827487)
I 18:27:29 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)
I 18:27:29 Verifying Layer 0... (LBA: 0 - 1913759)
I 18:33:04 Verifying Layer 1... (LBA: 1913760 - 3827487)
I 18:38:39 Exporting Graph Data...
I 18:38:39 Graph Data File: C:\Users\-------\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GE24LU20_OL00_FRIDAY-MAY-13-2011_6-11_PM_RITEK-S04-66_MAX.ibg
I 18:38:39 Export Successfully Completed!
I 18:38:39 Operation Successfully Completed! - Duration: 00:11:10
I 18:38:39 Average Verify Rate: 11,442 KB/s (8.3x) - Maximum Verify Rate: 16,554 KB/s (12.0x)

 

My question is did ImgBurn fix it itself. It burns fine and verifies. The game plays fine. Am I OK with this?

Edited by ddebon1
Link to comment
Share on other sites

I 18:11:19 User Specified L0 Data Zone Capacity: 1,913,760

W 18:11:19 L0 Data Zone Capacity Miscompare!

W 18:11:19 Wanted: 1913760, Got: 2086912

I 18:11:23 Filling Buffer... (40 MB)

I 18:11:24 Writing LeadIn...

I 18:12:08 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487)

I 18:12:08 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)

I 18:12:08 Writing Layer 0... (LBA: 0 - 1913759)

I 18:18:58 Writing Layer 1... (LBA: 1913760 - 3827487)

 

True, you got what you wanted. Not sure why the burner reported something else. :wacko:

Link to comment
Share on other sites

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

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

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

 

Bug in the firmware that they haven't yet solved, seems to affect only external burners. Or maybe their USB chipset is messing with the info and they didn't notice :doh:

Link to comment
Share on other sites

There was a bug in USB that could happen when SP1 was installed for Windows 7. Should be a fix on Windows Update. No idea if that one has something to do with the above issue.

Link to comment
Share on other sites

Thank You to everybody. The information was very helpful.

 

I used the 7601usbfix, however it said that my computer did not have the issue. Apparently I already downloaded the fix via Windows Update.

 

I guess I will just have to wait for an update. Good to know everything is OK.

Edited by ddebon1
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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