rexxpro Posted May 27, 2013 Share Posted May 27, 2013 (edited) Hi all I have used ImgBurn, burner max and vertatim discs before with success but just bought a new spindle of blank dual layers. Now I get the Semaphore error just after the burning lead in starts. The drive then disappears and an I/0 error happens. Just to check, I have formatted my pc and burnt a disc out of this spindle without burner max on another burner. I have only just also changed the drive advanced settings to enable FHT. Before format I didn't change anything with ImgBurn and it worked with previous spindle of blanks. Is there anyway (apart from trying a new spindle of blanks) to rectify this problem? I have a Liteon Ihas 524 D burner. Cheers Here is the status report I get I 22:32:23 Source File Sectors: 4,267,015 (MODE1/2048)I 22:32:23 Source File Size: 8,738,846,720 bytesI 22:32:23 Source File Volume Identifier: DVD_ROMI 22:32:23 Source File Volume Set Identifier: 384e0000MS UDFBridgeI 22:32:23 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)I 22:32:23 Source File Implementation Identifier: Microsoft CDIMAGE UDFI 22:32:23 Source File File System(s): ISO9660, UDF (1.50)I 22:32:23 Destination Device: [0:0:0] ATAPI iHAS524 D 8L25 (E:) (USB)I 22:32:23 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)I 22:32:23 Destination Media Supported Write Speeds: 4x, 6x, 8xI 22:32:23 Destination Media Sectors: 4,267,040I 22:32:23 Write Mode: DVDI 22:32:23 Write Type: DAOI 22:32:23 Write Speed: 4xI 22:32:23 DVD+R DL Reserve Track: NoI 22:32:23 Link Size: AutoI 22:32:23 Lock Volume: YesI 22:32:23 Test Mode: NoI 22:32:23 OPC: NoI 22:32:23 BURN-Proof: EnabledI 22:32:23 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)I 22:32:24 Book Type Setting: DVD-ROMI 22:32:24 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: YesI 22:32:24 Optimal L0 Data Zone Capacity: 2,133,520I 22:32:24 Optimal L0 Data Zone Method: Copied From Original DiscI 22:32:24 Set L0 Data Zone Capacity Succeeded!I 22:32:24 Filling Buffer... (80 MB)I 22:32:25 Writing LeadIn...W 22:32:53 Failed to Write Sectors 0 - 31 - Reason: The semaphore timeout period has expired.W 22:32:53 Retrying (1 of 20)...W 22:32:53 Retry Failed - Reason: The device is not connected.W 22:32:53 Retrying (2 of 20)...W 22:32:53 Retry Failed - Reason: The device is not connected.W 22:32:53 Retrying (3 of 20)...W 22:32:53 Retry Failed - Reason: The device is not connected.W 22:32:53 Retrying (4 of 20)...W 22:32:53 Retry Failed - Reason: The device is not connected.W 22:32:53 Retrying (5 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Device Removal Detected!W 22:32:54 The device list will be refreshed at the next available opportunity.W 22:32:54 Retrying (6 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (7 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (8 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (9 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (10 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (11 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (12 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (13 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (14 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (15 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (16 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (17 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (18 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (19 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.W 22:32:54 Retrying (20 of 20)...W 22:32:54 Retry Failed - Reason: The device is not connected.E 22:33:00 Failed to Write Sectors 0 - 31 - Reason: The semaphore timeout period has expired.I 22:33:00 Synchronising Cache...W 22:33:00 Synchronise Cache Failed! - Reason: The device is not connected.E 22:33:02 Synchronise Cache Failed! - Reason: The device is not connected.W 22:33:07 User opted to skip the 'Close Track/Session/Disc' functions.E 22:33:07 Failed to Write Image!E 22:33:07 Operation Failed! - Duration: 00:00:44I 22:33:07 Average Write Rate: N/A - Maximum Write Rate: N/AW 22:33:08 Device Removal Detected! Edited May 27, 2013 by rexxpro Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 28, 2013 Share Posted May 28, 2013 The semaphone timeout issue is related to your usb controller / adapter combo. It's nothing to do with ImgBurn itself. Try other cables / ports. Link to comment Share on other sites More sharing options...
rexxpro Posted May 28, 2013 Author Share Posted May 28, 2013 Hi, I have read up about the semaphore error and it is usually put down to usb controller / cable issues, however this does not explain how the burns worked fine with previous spindle of verb blanks. Also does not explain why with the new spindle I get semaphore error, then after closing and re-opening imgburn and try a ridata blank it burns fine with same controller, cable etc. Last night I got the burn working with new spindle. The verbs are the mkm-003-00. I checked the perform OPC before burn option in the settings / write. Then I got error at the 49% mark of the verify burn and the game comes up but then disc not readable error on the 360. Any ideas? Thanks Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 28, 2013 Share Posted May 28, 2013 Sorry, I can't offer any additional advice. I send the commands and they're erroring out. You know as much as I do at this point - the OS is reporting the semaphone timeout error, it isn't from the drive itself. Link to comment Share on other sites More sharing options...
rexxpro Posted May 29, 2013 Author Share Posted May 29, 2013 Hi, it turns out it is an issue somewhere with LiteOn burner, ImgBurn and Verbatim mkm-003-00 blank dvd+r dl discs. I managed to burn the game from the same iso onto one of these discs last night. Although I only burned at 4x I had ImgBurn overburn enabled. Again having this on did not affect burning of other types of blanks. Interesting Link to comment Share on other sites More sharing options...
Recommended Posts