sounerfan Posted January 2, 2013 Share Posted January 2, 2013 please help I 18:15:06 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x) I 18:15:06 Filling Buffer... (80 MB) I 18:15:07 Writing LeadIn... W 18:15:07 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code W 18:15:07 Retrying (1 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (2 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (3 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (4 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (5 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (6 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (7 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (8 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (9 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (10 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (11 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (12 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (13 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (14 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (15 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (16 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (17 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (18 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (19 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:07 Retrying (20 of 20)... W 18:15:07 Retry Failed - Reason: Invalid Command Operation Code W 18:15:16 Retrying (21)... W 18:15:16 Retry Failed - Reason: Invalid Command Operation Code E 18:15:21 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code I 18:15:21 Synchronising Cache... W 18:15:24 Synchronise Cache Failed! - Reason: Invalid Command Operation Code W 18:15:31 Synchronise Cache Failed! - Reason: Invalid Command Operation Code W 18:15:35 User opted to skip the 'Close Track/Session/Disc' functions. E 18:15:35 Failed to Write Image! E 18:15:35 Operation Failed! - Duration: 00:00:29 I 18:15:35 Average Write Rate: N/A - Maximum Write Rate: N/A I 18:15:47 Operation Started! I 18:15:47 Source File: C:\Users\JohnL\Documents\DAZED_AND_CONFUSED.iso I 18:15:47 Source File Sectors: 16,238,304 (MODE1/2048) I 18:15:47 Source File Size: 33,256,046,592 bytes I 18:15:47 Source File Volume Identifier: DAZED_AND_CONFUSED I 18:15:47 Source File Volume Set Identifier: 8CDD93AF6E4B1907_VOLUME_SET_ID I 18:15:47 Source File Application Identifier: APPLICATION_ID I 18:15:47 Source File Implementation Identifier: IMPLEMENTATION_ID I 18:15:47 Source File File System(s): UDF (2.50) I 18:15:47 Destination Device: [2:1:0] ASUS BC-12B1ST 1.02 (E:) (ATA) I 18:15:47 Destination Media Type: BD-R (Disc ID: CMCMAG-DI6-000) I 18:15:47 Destination Media Sectors: 24,438,784 I 18:15:47 Write Mode: BD I 18:15:47 Write Type: DAO I 18:15:47 Write Speed: MAX I 18:15:47 Hardware Defect Management Active: No I 18:15:47 BD-R Verify Not Required: Yes I 18:15:47 Link Size: Auto I 18:15:47 Lock Volume: Yes I 18:15:47 Test Mode: No I 18:15:47 OPC: No I 18:15:47 BURN-Proof: Enabled I 18:15:47 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x) I 18:15:47 Filling Buffer... (80 MB) I 18:15:48 Writing LeadIn... W 18:15:48 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code W 18:15:48 Retrying (1 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (2 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (3 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (4 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (5 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (6 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (7 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (8 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (9 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (10 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (11 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (12 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (13 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (14 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (15 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (16 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (17 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (18 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (19 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code W 18:15:48 Retrying (20 of 20)... W 18:15:48 Retry Failed - Reason: Invalid Command Operation Code E 18:16:12 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code I 18:16:12 Synchronising Cache... W 18:16:12 Synchronise Cache Failed! - Reason: Invalid Command Operation Code E 18:16:15 Synchronise Cache Failed! - Reason: Invalid Command Operation Code W 18:16:17 User opted to skip the 'Close Track/Session/Disc' functions. E 18:16:17 Failed to Write Image! E 18:16:17 Operation Failed! - Duration: 00:00:30 I 18:16:17 Average Write Rate: N/A - Maximum Write Rate: N/A I 18:17:36 Operation Started! I 18:17:36 Source File: C:\Users\JohnL\Documents\DAZED_AND_CONFUSED.iso I 18:17:36 Source File Sectors: 16,238,304 (MODE1/2048) I 18:17:36 Source File Size: 33,256,046,592 bytes I 18:17:36 Source File Volume Identifier: DAZED_AND_CONFUSED I 18:17:36 Source File Volume Set Identifier: 8CDD93AF6E4B1907_VOLUME_SET_ID I 18:17:36 Source File Application Identifier: APPLICATION_ID I 18:17:36 Source File Implementation Identifier: IMPLEMENTATION_ID I 18:17:36 Source File File System(s): UDF (2.50) I 18:17:36 Destination Device: [2:1:0] ASUS BC-12B1ST 1.02 (E:) (ATA) I 18:17:36 Destination Media Type: BD-R (Disc ID: CMCMAG-DI6-000) I 18:17:36 Destination Media Sectors: 24,438,784 I 18:17:36 Write Mode: BD I 18:17:36 Write Type: DAO I 18:17:36 Write Speed: MAX I 18:17:36 Hardware Defect Management Active: No Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 2, 2013 Share Posted January 2, 2013 Post Full log Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 2, 2013 Share Posted January 2, 2013 That's a 'Combo' drive, it can *read* Blu-ray discs but it can't *write* to them. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 (edited) Correct me if im wrong but why does ImgBurn allow it to a drive that doesnt support writing bluray (souldn't it know not to)? Edited January 4, 2013 by Adrianvdh Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 4, 2013 Share Posted January 4, 2013 Honestly... I've never really played with combo drives or made any attempt at blocking anything within the program. Â I always try and leave it down to the user to decide what they want to do / not do and then the drive has the final say in what's actually possible / not possible. Â Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 (edited) Ahh damm so you cant add it in the program to block it? if not isnt it bad for the drives hardware Edited January 4, 2013 by Adrianvdh Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 4, 2013 Share Posted January 4, 2013 If I look into it and I can work out with 100% certainty that the disc in the drive can't be written to by the drive, yeah I can block it. Â Nope, it's not bad for the hardware. It knows it can't write to whatever is inside the drive tray and just errors out - as was the case in this thread. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 So are you going to add the feature? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 4, 2013 Share Posted January 4, 2013 I'll look into it. Â That said, according to the MMC-6 specs, a drive that can't write to the inserted media should report the disc status as 'Complete', not 'Empty'. Â If it was 'Complete', ImgBurn wouldn't have enabled the 'Write' button in the first place. Â 6.21.3.1.5 Disc StatusThe Disc Status field (Table 367) indicates the recorded status of the disc. A Drive that does not have the ability to write the inserted medium shall return only COMPLETE (10b) status. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 So its a bug then? correct me if I'm wrong... Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 4, 2013 Share Posted January 4, 2013 In the drive's firmware, yeah. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 So will there be a change in ImgBurn with this? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 4, 2013 Share Posted January 4, 2013 Like I said in post #9, I'll look into it. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 4, 2013 Share Posted January 4, 2013 Oh ok... Link to comment Share on other sites More sharing options...
Recommended Posts