Rincewind Posted December 7, 2010 Share Posted December 7, 2010 (edited) Interesting problem with imgburn 2.5.3. I am trying to burn a CD, and for some reason now my system is extremely sluggish. The device buffer itself is no longer at 89%, but goes all the way down to 10%. And instead of burning at 16x, it goes down to 9x. I am burning a Data CD. I have never had this issue before, and I am waiting to see what happens when imgburn 'completes' the task. I don't know if I will have this kind of trouble with DVDs. The CD in question is TDK(CMC-Mag), however in the prior version of imgburn (2.5.2), no such issues like I am experiencing now... Also during verification the system again is slow, taskmgr shows CPU at 100%, and imgburn is what is shown as what is taken up the most resource. ; //****************************************\\ ; ImgBurn Version 2.5.3.0 - Log ; Tuesday, 07 December 2010, 15:03:20 ; \\****************************************// ; ; I 14:46:52 ImgBurn Version 2.5.3.0 started! I 14:46:52 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 14:46:52 Total Physical Memory: 523,764 KB - Available: 200,356 KB W 14:46:52 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 14:46:52 Initialising ASPI... I 14:46:52 WNASPI32.DLL - Adaptec's ASPI Layer - ASPI for Win32 (95/NT) DLL - Version 4.6.0.1021 I 14:46:52 Searching for SCSI / ATAPI devices... I 14:46:52 -> Drive 1 - Info: HL-DT-ST DVD-RAM GH22NP20 2.00 (F:) (ATA) I 14:46:52 -> Drive 2 - Info: RET BSLYN4LQZK 1.03 (D:) (SCSI) I 14:46:52 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM! I 14:47:04 Operation Started! I 14:47:04 Source File: C:\Documents and Settings\parents\Desktop\BOOK.mds I 14:47:04 Source File Sectors: 359,776 (MODE1/2048) I 14:47:04 Source File Size: 736,821,248 bytes I 14:47:04 Source File Volume Identifier: BOOK I 14:47:04 Source File Volume Set Identifier: 3D87755C00057ACE I 14:47:04 Source File Application Identifier: ImgBurn v2.5.3.0 - The Ultimate Image Burner! I 14:47:04 Source File Implementation Identifier: ImgBurn I 14:47:04 Source File File System(s): ISO9660, Joliet, UDF (2.60) I 14:47:04 Destination Device: [1:0:0] HL-DT-ST DVD-RAM GH22NP20 2.00 (F:) (ATA) I 14:47:04 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) (Speeds: 16x, 24x, 40x, 48x) I 14:47:04 Destination Media Sectors: 359,844 I 14:47:04 Write Mode: CD I 14:47:04 Write Type: SAO I 14:47:04 Write Speed: 16x I 14:47:04 Lock Volume: Yes I 14:47:04 Test Mode: No I 14:47:04 OPC: Yes I 14:47:04 BURN-Proof: Enabled I 14:47:04 Write Speed Successfully Set! - Effective: 2,822 KB/s (16x) I 14:47:04 Filling Buffer... (40 MB) I 14:47:05 Writing LeadIn... I 14:47:23 Writing Session 1 of 1... (1 Track, LBA: 0 - 359775) I 14:47:23 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 359775) I 14:55:54 Synchronising Cache... I 14:56:01 Image MD5: f3eb82f600bc8899006a4e82dbfe4306 I 14:56:01 Operation Successfully Completed! - Duration: 00:08:56 I 14:56:01 Average Write Rate: 1,410 KB/s (9.4x) - Maximum Write Rate: 1,654 KB/s (11.0x) I 14:56:01 Cycling Tray before Verify... W 14:56:09 Waiting for device to become ready... I 14:56:18 Device Ready! I 14:56:21 Operation Started! I 14:56:21 Source Device: [1:0:0] HL-DT-ST DVD-RAM GH22NP20 2.00 (F:) (ATA) I 14:56:21 Source Media Type: CD-R (Speeds: 16x, 24x, 40x, 48x) I 14:56:21 Image File: C:\Documents and Settings\parents\Desktop\BOOK.mds I 14:56:21 Image File Sectors: 359,776 (MODE1/2048) I 14:56:21 Image File Size: 736,821,248 bytes I 14:56:21 Image File Volume Identifier: BOOK I 14:56:21 Image File Volume Set Identifier: 3D87755C00057ACE I 14:56:21 Image File Application Identifier: ImgBurn v2.5.3.0 - The Ultimate Image Burner! I 14:56:21 Image File Implementation Identifier: ImgBurn I 14:56:21 Image File File System(s): ISO9660, Joliet, UDF (2.60) I 14:56:21 Read Speed (Data/Audio): MAX / MAX I 14:56:21 Verifying Session 1 of 1... (1 Track, LBA: 0 - 359775) I 14:56:21 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 359775) I 15:02:55 Device MD5: f3eb82f600bc8899006a4e82dbfe4306 I 15:02:55 Image MD5: f3eb82f600bc8899006a4e82dbfe4306 I 15:03:02 File Successfully Deleted: C:\Documents and Settings\parents\Desktop\BOOK.iso I 15:03:02 File Successfully Deleted: C:\Documents and Settings\parents\Desktop\BOOK.mds I 15:03:02 Operation Successfully Completed! - Duration: 00:06:34 I 15:03:02 Average Verify Rate: 1,830 KB/s (12.2x) - Maximum Verify Rate: 2,064 KB/s (13.8x) I 15:03:20 Close Request Acknowledged I 15:03:20 Closing Down... I 15:03:20 Shutting down ASPI... I 15:03:20 ImgBurn closed! P.S. I am not doing anything out of the ordinary either. I am not opening up any other files or doing anything that would interfere with imgburn, usually when I burn something I just wait for imgburn to finish before even surfing the web. I am considering downgrading back to 2.5.2, but will hold off if anyone has any suggestions. Edited December 7, 2010 by Rincewind Link to comment Share on other sites More sharing options...
mmalves Posted December 7, 2010 Share Posted December 7, 2010 You have DMA issues, so please read the 2nd post from the FAQ thread. Link to comment Share on other sites More sharing options...
Rincewind Posted December 7, 2010 Author Share Posted December 7, 2010 I will check that thanks, but curious that this only happens after upgrading from 2.5.2. NO such issues then. *shrug* Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 7, 2010 Share Posted December 7, 2010 It's not related to the app at all. The OS deals with DMA and when it gets stepped down to PIO etc - usually when it detects multiple I/O errors. (like from reading a bad disc - bad sectors etc) Just click Tools -> Reset DMA, then reboot and you should be back to normal. Link to comment Share on other sites More sharing options...
Rincewind Posted December 7, 2010 Author Share Posted December 7, 2010 Ladies and gentlemen I am a retard! *facepalm* I should have checked the cables actually. I recently disconnected the burner to connect a neighbor's hd to copy their data onto their external, and I wasn't paying attention and while reconnecting the burner, I should have made sure that the secondary was properly set to DMA, instead it was PIO. *facepalm again*.. DERP! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted December 7, 2010 Share Posted December 7, 2010 This is the one you're looking for... Link to comment Share on other sites More sharing options...
Recommended Posts