Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in CDB

[frilock]

hi guys i have a LG GP08LU30 and the firmware on it is 1.01 im trying to make a backup copy of my xb game (and yes i do own the original) but it keeps giving me this Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in CDB but if i use my other burner it works fine it comes up with a box to click cancel, try again or continue any ideas as to why its saying this ?? in running windows 7

 

 

I 17:11:55 ImgBurn Version 2.5.6.0 started!

I 17:11:55 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600)

I 17:11:55 Total Physical Memory: 2,879,692 KB - Available: 1,258,108 KB

W 17:11:55 Drive E:\ (FAT32) does not support single files > 4 GB in size.

W 17:11:55 Drive Z:\ (FAT) might not support single files > 4 GB in size.

W 17:11:55 Duplex Secure's SPTD driver can have a detrimental effect on drive performance.

I 17:11:55 Initialising SPTI...

I 17:11:55 Searching for SCSI / ATAPI devices...

I 17:11:55 -> Drive 1 - Info: hp DVDRAM GT30L mP04 (F:) (SATA)

I 17:11:55 -> Drive 2 - Info: UTSRY I3ST634 3.5Z (G:) (SCSI)

I 17:11:55 -> Drive 3 - Info: HL-DT-ST DVDRAM GP08LU30 1.01-10 (H:) (USB)

I 17:11:56 Found 2 DVD±RW/RAMs and 1 BD-ROM/HD DVD-ROM!

W 17:12:39 User accepted disc space warning and is attempting to truncate!

I 17:12:39 Operation Started!

I 17:12:39 Source File: C:\Users\trin\active\backup\fifa11.dvd

I 17:12:39 Source File Sectors: 4,267,015 (MODE1/2048)

I 17:12:39 Source File Size: 8,738,846,720 bytes

I 17:12:39 Source File Volume Identifier: DVD_ROM

I 17:12:39 Source File Volume Set Identifier: 67d90000MS UDFBridge

I 17:12:39 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 17:12:39 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 17:12:39 Source File File System(s): ISO9660, UDF (1.50)

I 17:12:39 Destination Device: [0:0:0] HL-DT-ST DVDRAM GP08LU30 1.01 (H:) (USB)

I 17:12:39 Destination Media Type: DVD+R DL (Disc ID: RITEK-S04-66)

I 17:12:39 Destination Media Supported Write Speeds: 2.4x, 4x, 6x

I 17:12:39 Destination Media Sectors: 4,173,824

I 17:12:39 Write Mode: DVD

I 17:12:39 Write Type: DAO

I 17:12:39 Write Speed: 2.4x

I 17:12:39 Link Size: Auto

I 17:12:39 Lock Volume: Yes

I 17:12:39 Test Mode: No

I 17:12:39 OPC: No

I 17:12:39 BURN-Proof: Enabled

I 17:12:39 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x)

I 17:12:39 Book Type Setting: N/A (Reason: Invalid Command Operation Code)

W 17:12:42 Optimal layer break position exceeds L0 capacity.

W 17:12:42 Optimal L0 Sectors: 2,133,520

W 17:12:42 Maximum L0 Sectors: 2,086,912

I 17:12:42 Optimal L0 Data Zone Capacity: 2,133,520

I 17:12:42 Optimal L0 Data Zone Method: Copied From Original Disc

W 17:12:42 Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in CDB

W 17:12:50 Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in CDB

I 17:12:50 Filling Buffer... (40 MB)

I 17:12:51 Writing LeadIn...

I 17:13:16 Writing Session 1 of 1... (1 Track, LBA: 0 - 4267014)

I 17:13:16 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4267014)

I 17:13:16 Writing Layer 0... (LBA: 0 - 2086911)

[mmalves]

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

 

You should also enable Windows Update.

[frilock]

Ok so in other words my drive is rubbish and i should just get another one? just want to make sure before i send it back in thank you for your time

[frilock]

O and if i do have to replace the drive can anyone recommend a new good drive that supports 2.4x and above ...i really wanted a slim drive due to space issues but if there rubbish id rather steer clear of them thanks again

[LIGHTNING UK!]

You're getting the error due to a bug in the drive's firmware. The drive *should* be erroring out (because you're attempting to use a layer break position that is beyond the maximum possible) but it should be returning a different error to that.

[frilock]

Hummm I have the latest firmware is there custom firmware I can use or something else I could do to fix the problem ? I still find it strange that my other drive didn't have a problem with the layer brake

[LIGHTNING UK!]

Your other drive would have errored out too... but it's an 'expected error' when the drive returns the correct error code and the program semi ignores it (you won't get the prompt).