Jump to content

Burning fails


dacamboe

Recommended Posts

Hi there,

 

Recently I've purchased an external casing for my laptop, since I've purchased a new burner (for the new xbox 360 isos), but I'm having problems with it.

Below is the attached imgburn log.

 

I hope someone can help me out on this, burning other (older) games with my internal burner works fine.

 

I 16:43:45 ImgBurn Version 2.5.6.0 started!

I 16:43:45 Microsoft Windows Vista Home Basic Edition (6.0, Build 6002 : Service Pack 2)

I 16:43:45 Total Physical Memory: 3.012.056 KB - Available: 1.940.528 KB

W 16:43:45 Drive F:\ (FAT32) does not support single files > 4 GB in size.

I 16:43:45 Initialising SPTI...

I 16:43:45 Searching for SCSI / ATAPI devices...

I 16:43:46 -> Drive 1 - Info: TSSTcorp CDDVDW TS-L632H fs03 (E:) (ATA)

I 16:43:46 Found 1 DVD±RW/RAM!

W 16:49:32 Device Arrival Detected!

I 16:49:32 Searching for SCSI / ATAPI devices...

I 16:49:32 -> Drive 1 - Info: TSSTcorp CDDVDW TS-L632H fs03 (E:) (ATA)

I 16:49:33 -> Drive 2 - Info: ATAPI iHAS124 B AL0S (F:) (USB)

I 16:49:33 Found 2 DVD±RW/RAMs!

I 16:50:28 Operation Started!

I 16:50:28 Source File: C:\Users\Ad\Saved Games\complex-batmanac.dvd

I 16:50:28 Source File Sectors: 4.267.015 (MODE1/2048)

I 16:50:28 Source File Size: 8.738.846.720 bytes

I 16:50:28 Source File Volume Identifier: DVD_ROM

I 16:50:28 Source File Volume Set Identifier: ea214000MS UDFBridge

I 16:50:28 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 16:50:28 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 16:50:28 Source File File System(s): ISO9660; UDF (1.50)

I 16:50:28 Destination Device: [0:0:0] ATAPI iHAS124 B AL0S (F:) (USB)

I 16:50:28 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)

I 16:50:28 Destination Media Supported Write Speeds: 2,4x; 4x; 6x; 8x

I 16:50:28 Destination Media Sectors: 4.267.040

I 16:50:28 Write Mode: DVD

I 16:50:28 Write Type: DAO

I 16:50:28 Write Speed: 2,4x

I 16:50:28 Link Size: Auto

I 16:50:28 Lock Volume: Yes

I 16:50:28 Test Mode: No

I 16:50:28 OPC: No

I 16:50:28 BURN-Proof: Enabled

I 16:50:28 Write Speed Successfully Set! - Effective: 3.324 KB/s (2,4x)

I 16:50:28 Book Type Setting: DVD-ROM

I 16:50:28 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 16:50:28 Optimal L0 Data Zone Capacity: 2.133.520

I 16:50:28 Optimal L0 Data Zone Method: Copied From Original Disc

I 16:50:29 Set L0 Data Zone Capacity Succeeded!

I 16:50:29 Filling Buffer... (40 MB)

I 16:50:31 Writing LeadIn...

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

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

I 16:51:10 Writing Layer 0... (LBA: 0 - 2133519)

W 16:58:21 Failed to Write Sectors 696640 - 696671 - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:21 Retrying (1 of 20)...

W 16:58:22 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:22 Retrying (2 of 20)...

W 16:58:22 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:22 Retrying (3 of 20)...

W 16:58:23 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:23 Retrying (4 of 20)...

W 16:58:24 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:24 Retrying (5 of 20)...

W 16:58:25 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:25 Retrying (6 of 20)...

W 16:58:25 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:25 Retrying (7 of 20)...

W 16:58:26 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:26 Retrying (8 of 20)...

W 16:58:27 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:27 Retrying (9 of 20)...

W 16:58:28 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:28 Retrying (10 of 20)...

W 16:58:28 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:28 Retrying (11 of 20)...

W 16:58:29 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:29 Retrying (12 of 20)...

W 16:58:30 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:30 Retrying (13 of 20)...

W 16:58:31 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:31 Retrying (14 of 20)...

W 16:58:32 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:32 Retrying (15 of 20)...

W 16:58:32 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:32 Retrying (16 of 20)...

W 16:58:33 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:33 Retrying (17 of 20)...

W 16:58:34 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:34 Retrying (18 of 20)...

W 16:58:35 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:35 Retrying (19 of 20)...

W 16:58:35 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:35 Retrying (20 of 20)...

W 16:58:36 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:47 Retrying (21)...

W 16:58:48 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:49 Retrying (22)...

W 16:58:50 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:51 Retrying (23)...

W 16:58:51 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:52 Retrying (24)...

W 16:58:52 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:58:53 Retrying (25)...

W 16:58:53 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:59:21 Retrying (26)...

W 16:59:21 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

W 16:59:56 Retrying (27)...

W 16:59:56 Retry Failed - Reason: De time-outperiode van de semafoor is verlopen.

E 17:12:16 Failed to Write Sectors 696640 - 696671 - Reason: De time-outperiode van de semafoor is verlopen.

I 17:12:16 Synchronising Cache...

W 17:12:16 Synchronise Cache Failed! - Reason: De time-outperiode van de semafoor is verlopen.

E 17:12:19 Synchronise Cache Failed! - Reason: De time-outperiode van de semafoor is verlopen.

I 17:12:23 Closing Track...

W 17:12:23 Close Track Failed! - Reason: De time-outperiode van de semafoor is verlopen.

E 17:12:27 Close Track Failed! - Reason: De time-outperiode van de semafoor is verlopen.

I 17:12:27 Finalising Disc...

W 17:12:27 Finalise Disc Failed! - Reason: De time-outperiode van de semafoor is verlopen.

W 17:12:30 Finalise Disc Failed! - Reason: De time-outperiode van de semafoor is verlopen.

E 17:12:30 Failed to Write Image!

I 17:13:30 Exporting Graph Data...

I 17:13:30 Graph Data File: C:\Users\Ad\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS124_B_AL0S_VRIJDAG-11-NOVEMBER-2011_16-50_MKM-003-00_2,4x.ibg

I 17:13:30 Export Successfully Completed!

E 17:13:30 Operation Failed! - Duration: 00:22:02

I 17:13:30 Average Write Rate: 1.101 KB/s (0.8x) - Maximum Write Rate: 3.391 KB/s (2.4x)

Link to comment
Share on other sites

Nobody really knows the reason behind the 'semaphore timeout' issue, it's just one of those things and we've chalked it up to a conflict between the USB chipset in the enclosure and the USB chipset on the motherboard.

 

So all I can suggest at the moment is trying a different enclosure.

 

Out of interest, which one did you buy?

Link to comment
Share on other sites

Nobody really knows the reason behind the 'semaphore timeout' issue, it's just one of those things and we've chalked it up to a conflict between the USB chipset in the enclosure and the USB chipset on the motherboard.

 

So all I can suggest at the moment is trying a different enclosure.

 

Out of interest, which one did you buy?

 

 

Wow fast reaction, thanks.

I bought a Sabrent 5.25" SATA CD/DVD-RW Aluminium Enclosure Case

 

So the only thing I can do is order another enclosure?

 

How can I check which chipset the enclosure has by the way?

Edited by dacamboe
Link to comment
Share on other sites

Last one of those I got was a Sumvision Tempest.

 

can I fix this problem with just buying a usb card like you said or do I really need another casing?

 

I can't answer that. You just have to try things yourself.

 

Buying either of them could fix the problem. Worst case scenario, you have to buy both.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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