Jump to content
Sign in to follow this  
SilentMusic

2.5.6.0 Cycle tray before verify failure

Recommended Posts

In v2.5.6.0, I checked: Settings|Write|Page 1|Cycle Tray Before Verify

For mode="Write image file to disc", I unchecked Test Mode, and checked Verify.

The bug is that the tray did not open and close in between writing a verifying.

 

Below is my log file showing the failure. At "14:18:37 Synchronising Cache...", ImgBurn hung and I clicked Cancel. I then got success from the verification of the disc I just burned. Note, that Tools|Drive|Eject works with ImgBurn v2.5.6.0 and this drive.

 

With this same drive and PC, I did not experience the same bug with ImgBurn v2.5.5.0.

 

; //****************************************\\
;   ImgBurn Version 2.5.6.0 - Log
;   Sunday, 16 October 2011, 14:26:59
; \\****************************************//
;
;
I 14:08:16 ImgBurn Version 2.5.6.0 started!
I 14:08:16 Microsoft Windows 7 Professional Edition (6.1, Build 7601 : Service Pack 1)
I 14:08:16 Total Physical Memory: 3,651,164 KB  -  Available: 2,866,460 KB
I 14:08:16 Initialising SPTI...
I 14:08:16 Searching for SCSI / ATAPI devices...
I 14:08:17 -> Drive 1 - Info: ASUS DRW-2014L1T 1.02 (E:) (ATAPI)
I 14:08:17 -> Drive 2 - Info: TSSTcorp CDDVDW TS-L633C TM01 (D:) (ATAPI)
I 14:08:17 Found 2 DVD±RW/RAMs!
I 14:16:21 Operation Started!
I 14:16:21 Source File: C:\Installers\Hardware\MSI MS-1733-ID1=GE700\OCZ Vertex 2 solid-state drive 120GB\Bootable firmware updater\ocz_fwupd_1.672.12.05.iso
I 14:16:21 Source File Sectors: 71,734 (MODE1/2048)
I 14:16:21 Source File Size: 146,911,232 bytes
I 14:16:21 Source File Volume Identifier: OCZ_FWUPD
I 14:16:21 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 14:16:21 Source File Implementation Identifier: ULTRAISO
I 14:16:21 Source File File System(s): ISO9660 (Bootable)
I 14:16:21 Destination Device: [0:2:0] ASUS DRW-2014L1T 1.02 (E:) (ATAPI)
I 14:16:21 Destination Media Type: DVD-RW (Disc ID: MCC 01RW4X)
I 14:16:21 Destination Media Supported Write Speeds: 2x, 4x
I 14:16:21 Destination Media Sectors: 2,297,888
I 14:16:21 Write Mode: DVD
I 14:16:21 Write Type: DAO
I 14:16:21 Write Speed: 2x
I 14:16:21 Link Size: Auto
I 14:16:21 Lock Volume: Yes
I 14:16:21 Test Mode: No
I 14:16:21 OPC: No
I 14:16:21 BURN-Proof: Enabled
I 14:16:22 Write Speed Successfully Set! - Effective: 2,770 KB/s (2x)
I 14:16:22 Filling Buffer... (40 MB)
I 14:16:23 Writing LeadIn...
I 14:17:45 Writing Session 1 of 1... (1 Track, LBA: 0 - 71733)
I 14:17:45 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 71733)
I 14:18:37 Synchronising Cache...
I 14:23:51 Abort Request Acknowledged
E 14:24:22 Failed to Write Image!
I 14:24:22 Exporting Graph Data...
I 14:24:22 Graph Data File: C:\Users\me\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-2014L1T_1.02_SUNDAY-OCTOBER-16-2011_2-16_PM_MCC_01RW4X_2x.ibg
I 14:24:22 Export Successfully Completed!
E 14:24:22 Operation Aborted! - Duration: 00:08:01
I 14:24:22 Average Write Rate: 2,759 KB/s (2.0x) - Maximum Write Rate: 2,790 KB/s (2.0x)
I 14:25:04 Operation Started!
I 14:25:05 Source Device: [0:2:0] ASUS DRW-2014L1T 1.02 (E:) (ATAPI)
I 14:25:05 Source Media Type: DVD-RW (Book Type: DVD-RW) (Disc ID: MCC 01RW4X)
I 14:25:05 Source Media Supported Write Speeds: 2x, 4x
I 14:25:05 Image File: C:\Installers\Hardware\MSI MS-1733-ID1=GE700\OCZ Vertex 2 solid-state drive 120GB\Bootable firmware updater\ocz_fwupd_1.672.12.05.iso
I 14:25:05 Image File Sectors: 71,734 (MODE1/2048)
I 14:25:05 Image File Size: 146,911,232 bytes
I 14:25:05 Image File Volume Identifier: OCZ_FWUPD
I 14:25:05 Image File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 14:25:05 Image File Implementation Identifier: ULTRAISO
I 14:25:05 Image File File System(s): ISO9660 (Bootable)
I 14:25:05 Read Speed (Data/Audio): MAX / MAX
I 14:25:06 Verifying Session 1 of 1... (1 Track, LBA: 0 - 71733)
I 14:25:06 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 71733)
I 14:25:37 Exporting Graph Data...
I 14:25:37 Graph Data File: C:\Users\me\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-2014L1T_1.02_SUNDAY-OCTOBER-16-2011_2-25_PM_MCC_01RW4X.ibg
I 14:25:37 Export Successfully Completed!
I 14:25:37 Operation Successfully Completed! - Duration: 00:00:31
I 14:25:37 Average Verify Rate: 4,782 KB/s (3.5x) - Maximum Verify Rate: 5,113 KB/s (3.7x)
I 14:26:59 Close Request Acknowledged
I 14:26:59 Closing Down...
I 14:26:59 Shutting down SPTI...
I 14:26:59 ImgBurn closed!

Share this post


Link to post
Share on other sites

It didn't hang, the drive was still doing its job. Have a little patience.

 

It won't cycle the tray if the write failed because the verify isn't ever meant to start.

 

Why it started for you is unclear at the moment. Are you sure you didn't start it manually?!

 

EDIT: Actually, I can see for a fact that you started the Verfiy operation manually.

 

So I'm sorry but the bug here appears to be with your recollection of events. :D

Share this post


Link to post
Share on other sites

Please look at my post and log again. The log shows that there was 5 minutes between "14:18:37 Synchronising Cache..." and "14:23:51 Abort Request Acknowledged

", which is where I clicked cancel.

 

Have a little patience.

 

The write completed very quickly because it was just 146MB on a DVD. After the write progress display showed completion, I waited 5 minutes for ImgBurn to automatically open and close the tray. Are you seriously suggesting that ImgBurn just needed more time before it was good and ready to open the tray? It looks to me like ImgBurn couldn't verify with this drive, and hung on "Synchronising Cache...", because this drive doesn't present DVD files to the OS until after the newly-burned DVD is cycled in the tray. This is why I checked: Settings|Write|Page 1|Cycle Tray Before Verify.

 

Actually, I can see for a fact that you started the Verfiy operation manually.

 

Yes, as I mentioned "ImgBurn hung and I clicked Cancel," the only way I could have started the Verify operation was manually. Thus, my recollection of events matches the log. :rolleyes:

Share this post


Link to post
Share on other sites

You were burning at 2x, that's slow as hell.

 

You can't write less than 1GB to a DVD-RW disc, the drive will make up whatever you don't use.

 

Yes, the drive (not the program) just needed a little more time to finish burning that 1GB (which included your 146MB).

 

If you'd left it a little while longer it would have done everything it was supposed to.

 

'Cycle Tray Before Verify' is on by default.

Share this post


Link to post
Share on other sites

OK, I accept your explanation.

 

I suggest that the progress bar for writing reflects the 1GB instead of the 146MB. 5 minutes of "Synchronising Cache..." gives the user the impression that something went wrong.

Share this post


Link to post
Share on other sites

It's not the program doing extra stuff, it's the drive.

 

Ideally, the drive would return a % complete for the sync cache process - and that info is already displayed in the status bar when it's available.

Share this post


Link to post
Share on other sites

Are you saying that ImgBurn only writes 146MB in this case, but the drive is padding the data to write a total of 1GB? If so, couldn't ImgBurn provide more descriptive status to the user, such as "Waiting for the drive to pad data to the minimum of 1GB"?

Share this post


Link to post
Share on other sites

Yes, ImgBurn only writes what you tell it. Upon issuing the 'sync cache' command to the drive, the drive is then doing whatever else it wants to do internally.

 

Yes, if I wanted to I could make it mention the 1GB thing in the log.

 

I prefer to go with what's being done command wise though rather than making special exceptions for certain amounts of data on certain media formats for what may or may not be certain drives.

 

You know what's happening and why it's happening, so hopefully you'll be ok now.

Share this post


Link to post
Share on other sites

As a fellow programmer, I understand with generic log entries. I now understand what was happening with my drive using DVD-RW. However, I do think there is an opportunity to make ImgBurn more user friendly. On the screen where the user selects the ISO or files to write, ImgBurn could notice that the image size is less than the minimum required by SOME drives, and then warn the user about the write potentially taking extra time because of the padding performed by some drives.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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