ellentk Posted August 25, 2011 Posted August 25, 2011 ImgBurn failed after burning about 75% of a disc due to a "semaphore timeout period has expired" error and then a "Cannot Write Medium - Incompatible Format" retry error. This is the first and only time this error happened. The burner is about 3 years old. In the past week, I burned eight Verbatim DigitalMovie DVD-R discs with no problem. My research on this problem indicates that the semaphore timeout error can happen either because of a conflict between ALI chips and USB hardware, defective cables, incorrect burn speed, poor quality media, using DVD-R discs. I think I know what to try, and in what order, but it's quite possible I've missed something and wanted to run my thinking by the experts here. (Error log below.) INFO ON MY SETUP: Hardware: Asus SDRW-08D1S-U connected to USB 2 adaptor on Thinkpad T23 via USB 2 port powered by Macally USB 2 hub (model mHub) DMA: enabled Software (to burn DVD): ImgBurn v. 2.5.5.0 (according to properties of exe file), 2.4.4.0 (according to error report) launched by DVD Flick, version 1.307.0738, ASUS driver: microsoft version 5.1.2535.0, 7/1/01 (latest version) O/S: xp(3) Software running in background: Sygate firewall, Memturbo memory manager Firewall log indicates no traffic blocked or allowed at time of write failure MemTurbo has no logs, but don't believe it optimized system at all during burn as only burning programs were running and they don't use much memory Media: Verbatim DigitalMovie DVD-R, single layer, propriatary AZO dye Burn Speed: 4x WHAT I THINK I SHOULD TRY I learned (too late) that Asus support pages say the max write speed for DVD-R discs in the SDRW-08D1S-U is 6x. The 4x I used is more than half the recommended max speed. Should I try burning with a DVD-R disc at 2x? I've also read that DVD+R are more stable, perhaps the second thing I should try is using a high-quality DVD+R.disc at 4x or 2x? Next, should I change the cable between the burner and the USB hub to test for conflicts between ALI chips and USB hardware? (I was unable to find out if the mHub uses the ALI chips in a preliminary search.) And last, but probably not worth it in this case, would be to find a USB hub that didn't use the ALI chip, assuming the mHub does? Thanks for any and all help. Ellen -- ERROR LOG I 13:23:48 ImgBurn Version 2.4.4.0 started! I 13:23:48 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 13:23:48 Total Physical Memory: 1,047,536 KB - Available: 647,940 KB W 13:23:48 Drive D:\ (FAT) does not support single files > 4 GB in size. I 13:23:49 Initialising SPTI... I 13:23:49 Searching for SCSI / ATAPI devices... I 13:23:49 Found 1 DVD-ROM and 1 DVD±RW/RAM! I 13:23:50 Operation Started! I 13:23:50 Building Image Tree... I 13:23:50 Checking Directory Depth... I 13:23:50 Calculating Totals... I 13:23:50 Preparing Image... I 13:23:51 Checking Path Length... I 13:23:51 Contents: 11 Files, 2 Folders I 13:23:51 Content Type: DVD Video I 13:23:51 File System(s): ISO9660, UDF (1.02) I 13:23:51 Volume Label: DVD Video I 13:23:51 IFO/BUP 32K Padding: Enabled I 13:23:51 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 13:23:51 TV System: NTSC I 13:23:51 Size: 4,644,378,624 bytes I 13:23:51 Sectors: 2,267,763 I 13:23:51 Image Size: 4,644,962,304 bytes I 13:23:51 Image Sectors: 2,268,048 I 13:23:51 Operation Successfully Completed! - Duration: 00:00:00 I 13:23:51 Operation Started! I 13:23:51 Source File: -==/\/[bUILD IMAGE]\/\==- I 13:23:51 Source File Sectors: 2,268,048 (MODE1/2048) I 13:23:51 Source File Size: 4,644,962,304 bytes I 13:23:51 Source File Volume Identifier: DVD Video I 13:23:51 Source File Application Identifier: IMGBURN V2.4.4.0 - THE ULTIMATE IMAGE BURNER! I 13:23:51 Source File Implementation Identifier: ImgBurn I 13:23:51 Source File File System(s): ISO9660, UDF (1.02) I 13:23:51 Destination Device: [0:0:0] ASUS SDRW-08D1S-U 1.02 (G:) (USB) I 13:23:51 Destination Media Type: DVD-R (Disc ID: MCC 02RG20) (Speeds: 4x, 8x) I 13:23:51 Destination Media Sectors: 2,297,888 I 13:23:51 Write Mode: DVD I 13:23:51 Write Type: DAO I 13:23:51 Write Speed: 4x I 13:23:51 Link Size: Auto I 13:23:51 Lock Volume: Yes I 13:23:51 Test Mode: No I 13:23:51 OPC: No I 13:23:51 BURN-Proof: Enabled I 13:24:00 Filling Buffer... (40 MB) I 13:24:03 Writing LeadIn... I 13:24:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 2268047) I 13:24:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2268047) W 13:35:37 Failed to Write Sectors 1691552 - 1691583 - Reason: The semaphore timeout period has expired. W 13:35:37 Retrying (1 of 20)... W 13:35:41 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred W 13:35:41 Retrying (2 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (3 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (4 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (5 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (6 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (7 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (8 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (9 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (10 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (11 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (12 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (13 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (14 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (15 of 20)... W 13:35:41 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:41 Retrying (16 of 20)... W 13:35:42 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:42 Retrying (17 of 20)... W 13:35:42 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:42 Retrying (18 of 20)... W 13:35:42 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:42 Retrying (19 of 20)... W 13:35:42 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:35:42 Retrying (20 of 20)... W 13:35:42 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:39:49 Retrying (21)... W 13:39:49 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:00 Retrying (22)... W 13:41:00 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:02 Retrying (23)... W 13:41:02 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:03 Retrying (24)... W 13:41:03 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:05 Retrying (25)... W 13:41:05 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:06 Retrying (26)... W 13:41:06 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:07 Retrying (27)... W 13:41:07 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:08 Retrying (28)... W 13:41:08 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:09 Retrying (29)... W 13:41:09 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:10 Retrying (30)... W 13:41:10 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:11 Retrying (31)... W 13:41:11 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:12 Retrying (32)... W 13:41:12 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:21 Retrying (33)... W 13:41:21 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:24 Retrying (34)... W 13:41:24 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:24 Retrying (35)... W 13:41:24 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:25 Retrying (36)... W 13:41:25 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:26 Retrying (37)... W 13:41:26 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:26 Retrying (38)... W 13:41:26 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:28 Retrying (39)... W 13:41:28 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:28 Retrying (40)... W 13:41:28 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:29 Retrying (41)... W 13:41:29 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:29 Retrying (42)... W 13:41:29 Retry Failed - Reason: Cannot Write Medium - Incompatible Format W 13:41:30 Retrying (43)... W 13:41:30 Retry Failed - Reason: Cannot Write Medium - Incompatible Format E 13:41:32 Failed to Write Sectors 1691552 - 1691583 - Reason: The semaphore timeout period has expired. I 13:41:32 Synchronising Cache... E 13:41:40 Failed to Write Image! E 13:41:41 Operation Failed! - Duration: 00:17:49 I 13:41:41 Average Write Rate: 3,393 KB/s (2.4x) - Maximum Write Rate: 5,612 KB/s (4.1x) I 13:41:42 Close Request Acknowledged I 13:41:42 Closing Down... I 13:41:42 Shutting down SPTI... I 13:41:42 ImgBurn closed!
mmalves Posted August 26, 2011 Posted August 26, 2011 Can't you plug the burner directly to the computer?
LIGHTNING UK! Posted August 26, 2011 Posted August 26, 2011 DVD Flick has it's own local copy of ImgBurn.exe - which appears to be 2.4.4.0 If you've installed 2.5.5.0 as a standalone version, you need to copy the exe file to DVD Flick's folder and overwrite its version.
ellentk Posted August 26, 2011 Author Posted August 26, 2011 Can't you plug the burner directly to the computer? The thinkpad doesn't have enough power to run the burner.
ellentk Posted August 26, 2011 Author Posted August 26, 2011 DVD Flick has it's own local copy of ImgBurn.exe - which appears to be 2.4.4.0 If you've installed 2.5.5.0 as a standalone version, you need to copy the exe file to DVD Flick's folder and overwrite its version. Done! Thanks. Do you think this is enough to cure the semaphore timeout error?
LIGHTNING UK! Posted August 26, 2011 Posted August 26, 2011 I doubt it. It's not ImgBurn's timeout that's expiring. Does the burner already use a Y USB cable? (So it takes power from 2 ports) If not, you could get one of those and try it directly.
ellentk Posted August 26, 2011 Author Posted August 26, 2011 I doubt it. It's not ImgBurn's timeout that's expiring. Does the burner already use a Y USB cable? (So it takes power from 2 ports) If not, you could get one of those and try it directly. The burner comes with a Y cable and I use it to connect the burner to two ports on a powered USB hub. I upgraded DVD Flick's version of ImgBurn to 2.5.5.0, used DVD Flick to burn the same file on the same type of disc that turned into a coaster (Verbatim DigitalMovie DVD-R) and it worked perfectly. The only difference besides the ImgBurn upgrade was that I turned off automatic updates on avast anti-virus. (I had turned off avast's real-time protection when the burn failed but not auto updates and avast updates frequently.) Without much RAM (the thinkpad has 1gb) could a semaphore timeout error happen if a program was trying to get an update? Do semaphore timeout errors happen sporadically? Would they be less likely to occur if I disconnected from the net while I burn a disc? Would a bad disc cause it? Thanks very much for your help. I learned a bit more about computers, which always makes me happy. Ellen
spinningwheel Posted August 27, 2011 Posted August 27, 2011 Yes and yes. The best way to assure a good burn on most systems is to ensure that nothing else is going on with the computer at the time of burning. I use EndItAll when I burn.
ellentk Posted August 30, 2011 Author Posted August 30, 2011 Yes and yes. The best way to assure a good burn on most systems is to ensure that nothing else is going on with the computer at the time of burning. I use EndItAll when I burn. Thanks for the confirmation and recommendation.
Recommended Posts