Jump to content

Recommended Posts

Posted

I'm backing up a DVD and have prepared an image using DVDShrink. I did this with another DVD yesterday, same kit, same procedure, same kind of blank media and it worked. I ran IMGBurn in test mode and it took less than an hour. I moved on to burning. Imgburn got stuck towards the end - about 93%. Write speed was zero and the DVD burner light was off. According to the log, Imgburn was engaged in "writing image". I was not using the PC for anything else at the time. So after about 75 minutes I gave up and tried to abort. My abort request was acknowledged. But 10 minutes later, nothing else had happened. So I unplugged the USB cable for the writer. Questions:

 

(i) Where might the problem be? If it's the media why doesn't it fail in test mode?

 

(ii) Does Imgburn not have a feature which makes it realise it's stuck after a while? Should it?

 

(iii) Why won't it respond properly to the abort command? Pulling the cable isn't the ideal exit route.

 

Here is the log

 

 

I 08:17:01 ImgBurn Version 1.2.0.0 started!

I 08:17:01 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 08:17:02 Initialising SPTI...

I 08:17:02 Searching for SCSI / ATAPI devices...

I 08:17:12 Found 1 DVD-RW and 1 DVD?RW!

I 08:17:37 Operation Started!

I 08:17:37 Source File: C:\disctobackup.MDS

I 08:17:37 Source File Sectors: 2,285,899 (MODE1/2048)

I 08:17:37 Source File Size: 4,681,521,152 bytes

I 08:17:37 Source File Implementation Identifier: DVD Shrink

I 08:17:37 Destination Device: [0:0:0] TOSHIBA DVD-ROM SD-R6112 1030 (H:) (USB)

I 08:17:37 Destination Media Type: DVD-R (Disc ID: INFOSMART01) (Speeds: 1x, 2x)

I 08:17:37 Destination Media Sectors: 2,298,496

I 08:17:37 Write Mode: DVD

I 08:17:37 Write Type: DAO

I 08:17:37 Write Speed: MAX

I 08:17:37 Link Size: Auto

I 08:17:37 Test Mode: No

I 08:17:37 BURN-Proof: Enabled

I 08:17:37 Filling Buffer...

I 08:17:38 Writing LeadIn...

I 08:18:58 Writing Image...

I 09:34:22 Abort Request Acknowledged

W 09:43:40 Failed to Write Sectors 2204800 - 2204831 - The semaphore timeout period has expired.

W 09:43:41 Retrying (1 of 20)...

I 09:43:41 Synchronising Cache...

E 09:43:41 Failed to Write Image!

E 09:43:43 Operation Aborted! - Duration: 01:26:04

I 09:43:43 Average Write Rate: 867 KB/s (0.6x) - Maximum Write Rate: 1,407 KB/s (1.0x)

E 09:43:57 CreateFile Failed! - Device: '\\.\CdRom4'

E 09:43:57 Reason: The system cannot find the file specified.

 

I like Imgburner almost as much as I liked its predecessor!

Posted

As mentioned in another thread a couple of hours earlier, once a command has been sent to the drive, it sits and waits for a response.

 

If it doesn't get one, it waits and waits and waits. To put a timeout on such things not really a good idea. Firstly, it's hard to know what to set it to - all drives do things differently and what works for one may not be enough for another.

Putting a timeout on a command has the effect of resetting the bus when that timeout expires. Resetting the bus is not a good thing as it brings everything else down with it.

 

You cannot abort whilst it's waiting for a response because ImgBurn is not in control at that point. To terminate something internally would not mean your system jumps back to life - turning off the usb enclosure is pretty much the only way out.

 

Test mode isn't actually burning to the media, so really it's just testing the speed of your machine. It won't necessarily find all problems that can occur during an actual burn.

That said, Infosmart media is baaaaaaadddddd!

×
×
  • Create New...

Important Information

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