Cynthia Posted March 8, 2006 Posted March 8, 2006 (edited) Curious - you start a test burn and abort it. Why does it run a complete "Synchronising Cache" instead of just aborting. I 08:33:26 ImgBurn Version 1.2.0.0 started! I 08:33:26 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 08:33:26 Initialising SPTI... I 08:33:26 Searching for SCSI / ATAPI devices... I 08:33:26 Found 1 DVD?RW and 1 DVD?RW/RAM! I 08:33:44 Operation Started! I 08:33:44 Source File: H:\TEST.ISO I 08:33:44 Source File Sectors: 2 294 040 (MODE1/2048) I 08:33:44 Source File Size: 4 698 193 920 bytes I 08:33:44 Source File Implementation Identifier: None I 08:33:44 Destination Device: [1:0:0] _NEC DVD_RW ND-4551A 1-07 (F:) (ATA) I 08:33:44 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 2x; 4x; 6x; 8x; 12x; 16x) I 08:33:44 Destination Media Sectors: 2 297 888 I 08:33:44 Write Mode: DVD I 08:33:44 Write Type: DAO I 08:33:44 Write Speed: 8x I 08:33:44 Link Size: Auto I 08:33:44 Test Mode: Yes I 08:33:44 BURN-Proof: Enabled I 08:33:45 Filling Buffer... I 08:33:45 Writing LeadIn... I 08:34:07 Writing Image... I 08:34:38 Abort Request Acknowledged I 08:34:38 Synchronising Cache... E 08:48:06 Failed to Write Image! E 08:48:10 Operation Aborted! - Duration: 00:14:21 I 08:48:10 Average Write Rate: 5 787 KB/s (4.2x) - Maximum Write Rate: 5 878 KB/s (4.2x) Edited March 8, 2006 by cynthia
LIGHTNING UK! Posted March 8, 2006 Posted March 8, 2006 Some driives expect a certain set of commands. If you abort and don't do the last few they can get stuck and wont accept any 'wrong' ones until the 'right' ones have been sent. All you end up getting is a 'command sequence' error.
grampaw Posted March 8, 2006 Posted March 8, 2006 Why would one want to abort the test burn if it takes a full 14 minutes to complete the abort process? Seems to me it would take signicantly less time at an 8X burn rate to just complete the test.
Recommended Posts