Jump to content

Recommended Posts

Posted

i used to have no problems at all burning iso images and other files but suddenly i was having all sorts of troubles. i don't if the problem lies on the blank media or the burner itself or something else. i really have no clue what else to do. i've got a BenQ DW 1620 and recently updated the firmware to B7W9. here's the error log:

 

I 12:15:15 ImgBurn Version 1.3.0.0 started!

I 12:15:15 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 12:15:15 Initialising SPTI...

I 12:15:15 Searching for SCSI / ATAPI devices...

I 12:15:15 Found 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

I 12:16:10 Operation Started!

I 12:16:10 Source File: F:\PS2 Torrent Downloads\e-suiko5.iso

I 12:16:10 Source File Sectors: 2,199,536 (MODE1/2048)

I 12:16:10 Source File Size: 4,504,649,728 bytes

I 12:16:10 Source File Application Identifier: PLAYSTATION

I 12:16:10 Source File Implementation Identifier: DVD-ROM GENERATOR

I 12:16:10 Source File UDF Revision: 1.02

I 12:16:10 Destination Device: [0:0:0] BENQ DVD DD DW1620 B7W9 (G:) (USB)

I 12:16:10 Destination Media Type: DVD-R (Disc ID: ProdiscF02) (Speeds: 2.4x, 4x, 8x, 12x, 16x)

I 12:16:10 Destination Media Sectors: 2,298,496

I 12:16:10 Write Mode: DVD

I 12:16:10 Write Type: DAO

I 12:16:10 Write Speed: 2.4x

I 12:16:10 Link Size: Auto

I 12:16:10 Test Mode: No

I 12:16:10 BURN-Proof: Enabled

I 12:16:10 Filling Buffer...

I 12:16:11 Writing LeadIn...

I 12:16:22 Writing Image...

I 12:39:55 Synchronising Cache...

I 12:40:52 Operation Successfully Completed! - Duration: 00:24:42

I 12:40:52 Average Write Rate: 3,115 KB/s (2.2x) - Maximum Write Rate: 3,390 KB/s (2.4x)

I 12:40:52 Cycling Tray before Verify...

W 12:40:58 Waiting for device to become ready...

I 12:41:12 Device Ready!

I 12:41:13 Operation Started!

I 12:41:13 Source Device: [0:0:0] BENQ DVD DD DW1620 B7W9 (G:) (USB)

I 12:41:13 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: ProdiscF02) (Speeds: 2.4x, 4x, 8x, 12x, 16x)

I 12:41:13 Image File: F:\PS2 Torrent Downloads\e-suiko5.iso

I 12:41:13 Image File Sectors: 2,199,536 (MODE1/2048)

I 12:41:13 Image File Size: 4,504,649,728 bytes

I 12:41:13 Image File Application Identifier: PLAYSTATION

I 12:41:13 Image File Implementation Identifier: DVD-ROM GENERATOR

I 12:41:13 Image File UDF Revision: 1.02

I 12:41:13 Verifying Sectors...

E 13:14:30 Failed to read Sector 237472 - The semaphore timeout period has expired.

E 13:14:30 Failed to Verify Sectors!

E 13:14:30 Operation Failed! - Duration: 00:33:17

I 13:14:30 Average Verify Rate: 237 KB/s (0.2x) - Maximum Verify Rate: 5,840 KB/s (4.2x)

Posted
Media Type: DVD-R (Book Type: DVD-R) (Disc ID: ProdiscF02) (Speeds: 2.4x, 4x, 8x, 12x, 16x)

 

Me thinks the type of media you're using has a lot to do with your problems.

Posted

Oh, Ok, I wasn't aware of that, I wonder why? Firmware?

ProdiscF02

Just the same tho, I don't think these are anything to brag about. :/

Posted

yeah i did hit reply but just stated the same error over and over. i was kinda hoping if i hit retry that it'd just continue on with the burning process. so basically BenQ drives are just picky with the media you're using? i'll try using memorex like i've been using before. for some reason when i used nero it also had an error finalizing the burn(could not perform disc-at-once) sorta thought that it might have had something to do with a bug in the program... any other suggestions of what i should do?

Posted

use MEMOREX :o you must be mad especially if its CMC MAG dye .Memorex makes some of the worst shit there is .Use Verbatim with MCC dye or Taiyo Yuden discs and you wont have any issues with media .Try reading those Memorex you burned to a while ago and see what happens ,they have a bad rep for becoming unreadable over time

Posted

The old semaphore timeout on USB pretty much means an old ALI chip set. Nothing you can do about it except return the drive if you can. The problem lies with the chipset firmware, which cannot be updated in most cases with ALI chipsets with firmware that does cause the timeout.

×
×
  • Create New...

Important Information

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