Jump to content

Recommended Posts

Posted

I have been using Imgburn for years and never gotten this problem. I have used 3 different kind of +RW disks and all of them give this error. I also used a brand new disk and a different source the last time. As I type this, the writer is still synchronising, although the operation light is not flashing. What could be the problem?

 

 

 

I 17:55:24 ImgBurn Version 2.5.6.0 started!

I 17:55:24 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 17:55:24 Total Physical Memory: 4.184.204 KB - Available: 2.386.476 KB

I 17:55:24 Initialising SPTI...

I 17:55:24 Searching for SCSI / ATAPI devices...

I 17:55:24 -> Drive 1 - Info: Optiarc DVD RW AD-7240S 1.03 (H:) (RAID)

I 17:55:24 Found 1 DVD±RW/RAM!

I 17:56:01 Operation Started!

I 17:56:01 Device: [2:4:0] Optiarc DVD RW AD-7240S 1.03 (H:) (RAID)

I 17:56:01 Media Type: DVD+RW (Disc ID: MKM-A02-00)

I 17:56:01 Media Supported Write Speeds: 4x

I 17:56:01 Quick Erase: No

I 17:56:01 Format Properly: Yes

I 17:56:01 Format Size: Preferred

I 17:56:01 Erasing Disc...

I 18:10:43 Operation Successfully Completed! - Duration: 00:14:41

I 18:10:44 Operation Started!

I 18:10:44 Building Image Tree...

I 18:10:44 Checking Directory Depth...

I 18:10:44 Calculating Totals...

I 18:10:44 Preparing Image...

I 18:10:44 Checking Path Length...

I 18:10:44 Contents: 18 Files, 2 Folders

I 18:10:44 Content Type: DVD Video

I 18:10:44 Data Type: MODE1/2048

I 18:10:44 File System(s): ISO9660, UDF (1.02)

I 18:10:44 Volume Label: Disk_3

I 18:10:44 IFO/BUP 32K Padding: Enabled

I 18:10:44 Region Code: 1; 2; 3; 4; 5; 6; 8

I 18:10:44 TV System: PAL

I 18:10:44 Size: 4.496.089.088 bytes

I 18:10:44 Sectors: 2.195.356

I 18:10:44 Image Size: 4.496.687.104 bytes

I 18:10:44 Image Sectors: 2.195.648

I 18:23:47 Operation Successfully Completed! - Duration: 00:13:03

I 18:23:47 Operation Started!

I 18:23:47 Source File: -==/\/[bUILD IMAGE]\/\==-

I 18:23:47 Source File Sectors: 2.195.648 (MODE1/2048)

I 18:23:47 Source File Size: 4.496.687.104 bytes

I 18:23:47 Source File Volume Identifier: Disk_3

I 18:23:47 Source File Volume Set Identifier: 3F909156002180BC

I 18:23:47 Source File Application Identifier: IMGBURN V2.5.6.0 - THE ULTIMATE IMAGE BURNER!

I 18:23:47 Source File Implementation Identifier: ImgBurn

I 18:23:47 Source File File System(s): ISO9660; UDF (1.02)

I 18:23:47 Destination Device: [2:4:0] Optiarc DVD RW AD-7240S 1.03 (H:) (RAID)

I 18:23:47 Destination Media Type: DVD+RW (Disc ID: MKM-A02-00)

I 18:23:47 Destination Media Supported Write Speeds: 4x

I 18:23:47 Destination Media Sectors: 2.295.104

I 18:23:47 Write Mode: DVD

I 18:23:47 Write Type: DAO

I 18:23:47 Write Speed: MAX

I 18:23:47 Link Size: Auto

I 18:23:47 Lock Volume: Yes

I 18:23:47 Test Mode: No

I 18:23:47 OPC: No

I 18:23:47 BURN-Proof: Enabled

I 18:23:47 Write Speed Successfully Set! - Effective: 5.540 KB/s (4x)

I 18:23:48 Book Type Setting: DVD+RW

I 18:23:48 Filling Buffer... (40 MB)

I 18:23:48 Writing LeadIn...

I 18:23:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 2195647)

I 18:23:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2195647)

I 18:37:25 Synchronising Cache...

Posted

What controller is that drive attached to? This issue is often due to the controller, 'mode' of said controller (in your case, RAID) and the drivers.

 

ImgBurn hasn't hung, it's just waiting for your drive to say it's finished.

Posted (edited)

It is attached to the sata controller built in the SB750 southbridge. It has always operated in raid mode. I did do a reinstall a couple of weeks ago, because I bought a SSD, so I probably used a different driver on my old install. I'll try a different driver and when that does not work I'll turn on the other controller in the BIOS.

 

edit: now that I have thought about it: I used exactly the same drivers as on my old install. Those still were on my memorystick which I used during installation.

Edited by ABD
Posted

I have already installed the drivers you suggested, but it did not work. I have really no idea what has changed, I have been using that writer for about 2 years now on said controller in RAID mode. Anyway, I turned on the other controller, a shitty JMicron, and all works well again. I guess I have to get used to waiting 5 more seconds booting up;)

 

Thank you for the support.

Posted (edited)

I do have another question: because of the problem I had, I was looking at the log and I noticed this

 

 

Book Type Setting: N/A (Reason: The semaphore timeout period has expired.)

 

What is this and what can I do to fix it? I have a gigabyte mobo with 790x + sb750 chipset and extra gigabyte(JMicron)satacontroller. Must be the gigabyte controller.

Edited by ABD
×
×
  • Create New...

Important Information

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