Jump to content
mooltittle

2.5.7.0 always hangs at 99% for writes and verifys

Recommended Posts

Hello -

 

This is my first post here, so I apologise if this has already been posted. I did scan the forum but couldn't find a thread on this issue.

 

When using ImgBurn 2.5.7.0, and two different CDs (data, if that matters), it will make image files of the CDs on my hard drive without complaint,

 

However, when I then ask it to verify the image file against the disk, it hangs at 99% - and after all the data has been read. Every time. After about 10 minutes, I aborted the verify.

 

When I then go ahead and use ImgBurn to write the image file to a blank disk, it again hangs at 99%, again after all the data has been written. After another 10 minutes, I aborted the write.

 

I tried to verify the newly-written disc against the image file, and again it hangs at 99%.

 

I then made a second image file from the same disk, and used a hex editor (frhed.exe) to compare it to the first image file, and they matched exactly.

 

I repeated the entire procedure above with a different data CD, and got the same results.

 

I then uninstalled v2.5.7.0 and reinstalled v2.5.6.0, and again did everything above, and this time, ImgBurn performed flawlessly - no hanging at 99%, and no errors. (Yes, I used the same two data CDs.)

 

Therefore, I must conclude that there is a bug in v2.5.7.0 that makes it not work correctly with my computer.

 

When I used v2.5.6.0 to compare the image file created with v2.5.6.0 to the CD original, it generated zero errors.

 

However, when I used v2.5.6.0 to compare the image file created with v2.5.7.0 to the CD original, it generated several errors, here is the log file:

 

I 16:02:03 ImgBurn Version 2.5.6.0 started!

I 16:02:03 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 16:02:03 Total Physical Memory: 8,116,364 KB - Available: 5,582,636 KB

I 16:02:03 Initialising SPTI...

I 16:02:03 Searching for SCSI / ATAPI devices...

I 16:02:03 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

I 16:02:03 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (O:) (SCSI)

I 16:02:04 -> Drive 3 - Info: HL-DT-ST BDDVDRW GGC-H20L 1.03 (F:) (RAID)

I 16:02:04 -> Drive 4 - Info: TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 16:02:04 Found 1 DVD±RW/RAM, 2 BD-ROM/HD DVD-ROMs and 1 BD-ROM/HD DVD-ROM/DVD±RW!

I 16:02:32 Operation Started!

I 16:02:32 Source Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 16:02:32 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)

I 16:02:32 Source Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x

I 16:02:32 Image File: G:\MRI\Right Hip.cue

I 16:02:32 Image File Sectors: 83,897 (MODE2/FORM1/2352)

I 16:02:32 Image File Size: 197,325,744 bytes

I 16:02:32 Image File File System(s): ISO9660, Joliet

I 16:02:32 Read Speed (Data/Audio): MAX / MAX

W 16:03:02 Session 1, Track 1 is smaller on the disc than it is in the image file.

W 16:03:02 Disc's Track Sectors: 83895 (TOC Sectors: 83897)

W 16:03:02 Image File's Track Sectors: 83897 (TOC Sectors: 83897)

I 16:03:02 Verifying Session 1 of 1... (1 Track, LBA: 0 - 83896)

I 16:03:02 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83896)

W 16:04:06 Miscompare at LBA: 83895, Offset: 1

W 16:04:06 Device: 0xFF

W 16:04:06 Image File: 0x00 (Empty Sector!)

W 16:04:06 Total Errors in Sector: 14

W 16:04:06 Note: The drive probably corrected the Sync/Header Area because it's wrong in the image file.

I 16:04:06 Verifying Sectors...

W 16:04:07 Miscompare at LBA: 83896, Offset: 1

W 16:04:07 Device: 0xFF

W 16:04:07 Image File: 0x00 (Empty Sector!)

W 16:04:08 Total Errors in Sector: 14

W 16:04:08 Note: The drive probably corrected the Sync/Header Area because it's wrong in the image file.

I 16:04:08 Verifying Sectors...

I 16:04:09 Exporting Graph Data...

I 16:04:09 Graph Data File: C:\Users\Tom - Admin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_4-02_PM_97m26s66f.ibg

I 16:04:09 Export Successfully Completed!

I 16:04:09 Operation Successfully Completed! - Duration: 00:01:35

I 16:04:09 Average Verify Rate: 2,964 KB/s (19.8x) - Maximum Verify Rate: 4,438 KB/s (29.6x)

Share this post


Link to post
Share on other sites

P.S. Here is the "graph data" file referenced in the log file above.

 

 

Also, I just used v2.5.6.0 to compare the same CD to an image file of the CD generated with v2.5.6.0, and it completed with no errors. Here are the results ("graph data" file also attached):

 

I 17:46:17 ImgBurn Version 2.5.6.0 started!

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

I 17:46:17 Total Physical Memory: 8,116,364 KB - Available: 5,319,520 KB

I 17:46:17 Initialising SPTI...

I 17:46:17 Searching for SCSI / ATAPI devices...

I 17:46:17 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

I 17:46:17 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (O:) (SCSI)

I 17:46:17 -> Drive 3 - Info: HL-DT-ST BDDVDRW GGC-H20L 1.03 (F:) (RAID)

I 17:46:17 -> Drive 4 - Info: TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 17:46:17 Found 1 DVD±RW/RAM, 2 BD-ROM/HD DVD-ROMs and 1 BD-ROM/HD DVD-ROM/DVD±RW!

I 17:46:27 Operation Started!

I 17:46:27 Source Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 17:46:27 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)

I 17:46:27 Source Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x

I 17:46:27 Image File: G:\MRI\hip1.cue

I 17:46:27 Image File Sectors: 83,895 (MODE2/FORM1/2352)

I 17:46:27 Image File Size: 197,321,040 bytes

I 17:46:27 Image File File System(s): ISO9660, Joliet

I 17:46:28 Read Speed (Data/Audio): MAX / MAX

I 17:46:42 Verifying Session 1 of 1... (1 Track, LBA: 0 - 83894)

I 17:46:42 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83894)

I 17:47:51 Exporting Graph Data...

I 17:47:51 Graph Data File: C:\Users\Tom\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_5-46_PM_97m26s66f.ibg

I 17:47:51 Export Successfully Completed!

I 17:47:51 Operation Successfully Completed! - Duration: 00:01:22

I 17:47:51 Average Verify Rate: 2,876 KB/s (19.2x) - Maximum Verify Rate: 3,460 KB/s (23.1x)

TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_4-02_PM_97m26s66f.ibg

TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_5-46_PM_97m26s66f.ibg

Share this post


Link to post
Share on other sites

What I need to see is the read operation from your source disc to the image file and then the write+verify operation of the image file to a blank disc.

 

All with 2.5.7.0 of course.

 

Thanks :)

Share this post


Link to post
Share on other sites

Thank you for the fast reply.

 

As requested, here are the results using v2.5.7.0.

 

The read operation (create image file from disk) completed without reporting any errors.

 

The write + verify operation again hung at 99% during the write phase. I went outside for a walk, and when I returned 40 minutes later, it was still stuck at 99%, so I aborted it. It popped up a message to the effect "write operation not complete; do you want to finalise the disk anyway?", to which I replied Yes.

 

I then attempted to verify the newly-written disk against the image file, since the write + verify never reached the verify phase. It almost immediately popped up an error message (see "verify - error msg1.jpg", attached). The verify operation proceeded, but again hung at 99%, and another error message popped up (see "verify - error msg2.jpg", attached). Notice that there are zero read errors and zero miscompares, but one retry (????). Before I could even begin to read the second error message, a third popped up, I clicked "Try Again", and a few seconds later error message 4 popped up, and I clicked Cancel.

 

The "graph file" generated by v2.5.7.0 is also attached below.

 

I then uninstalled v2.5.7.0, reinstalled v2.5.6.0, and did the same operations again, and all completed with zero errors or problems.

 

Here is the log file for v2.5.7.0:

 

 

I 18:13:01 ImgBurn Version 2.5.7.0 started!

I 18:13:01 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 18:13:01 Total Physical Memory: 8,116,364 KB - Available: 5,752,164 KB

I 18:13:01 Initialising SPTI...

I 18:13:01 Searching for SCSI / ATAPI devices...

I 18:13:01 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

I 18:13:01 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (O:) (SCSI)

I 18:13:01 -> Drive 3 - Info: HL-DT-ST BDDVDRW GGC-H20L 1.03 (F:) (RAID)

I 18:13:01 -> Drive 4 - Info: TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 18:13:01 Found 1 DVD±RW/RAM, 2 BD-ROM/HD DVD-ROMs and 1 BD-ROM/HD DVD-ROM/DVD±RW!

I 18:14:08 Operation Started!

I 18:14:08 Source Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 18:14:08 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)

I 18:14:08 Source Media Supported Read Speeds: 8x, 10x, 16x, 24x, 32x, 40x

I 18:14:08 Source Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x

I 18:14:08 Source Media Sectors: 83,897

I 18:14:08 Source Media Size: 197,325,744 bytes

I 18:14:08 Source Media File System(s): ISO9660, Joliet

I 18:14:08 Read Speed (Data/Audio): MAX / 8x

I 18:14:08 Destination File: G:\ImgBurn test\hip.bin

I 18:14:08 Destination Free Space: 141,891,657,728 Bytes (138,566,072.00 KB) (135,318.43 MB) (132.15 GB)

I 18:14:08 Destination File System: NTFS

I 18:14:08 File Splitting: Auto

I 18:14:25 Reading Session 1 of 1... (1 Track, LBA: 0 - 83896)

I 18:14:25 Reading Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83896)

I 18:15:33 Exporting Graph Data...

I 18:15:33 Graph Data File: C:\Users\Tom - Admin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_6-14_PM_97m26s66f.ibg

I 18:15:33 Export Successfully Completed!

I 18:15:33 Operation Successfully Completed! - Duration: 00:01:24

I 18:15:33 Average Read Rate: 2,294 KB/s (13.3x) - Maximum Read Rate: 3,446 KB/s (20.0x)

I 18:19:14 Operation Started!

I 18:19:14 Source File: G:\ImgBurn test\hip.cue

I 18:19:14 Source File Sectors: 83,897 (MODE2/FORM1/2352)

I 18:19:14 Source File Size: 197,325,744 bytes

I 18:19:14 Source File File System(s): ISO9660, Joliet

I 18:19:14 Destination Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 18:19:14 Destination Media Type: CD-R (Disc ID: 97m27s66f, Ricoh Co.)

I 18:19:14 Destination Media Supported Write Speeds: 16x, 24x, 32x, 40x

I 18:19:14 Destination Media Sectors: 359,844

I 18:19:14 Write Mode: CD

I 18:19:14 Write Type: SAO

I 18:19:14 Write Speed: MAX

I 18:19:14 Lock Volume: Yes

I 18:19:14 Test Mode: No

I 18:19:14 OPC: No

I 18:19:14 BURN-Proof: Enabled

I 18:19:14 Write Speed Successfully Set! - Effective: 7,056 KB/s (40x)

I 18:19:14 Filling Buffer... (80 MB)

I 18:19:14 Writing LeadIn...

I 18:19:33 Writing Session 1 of 1... (1 Track, LBA: 0 - 83896)

I 18:19:33 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83896)

I 19:00:31 Abort Request Acknowledged

I 19:00:31 Synchronising Cache...

E 19:00:40 Failed to Write Image!

I 19:00:40 Exporting Graph Data...

I 19:00:40 Graph Data File: C:\Users\Tom - Admin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_6-19_PM_97m27s66f_MAX.ibg

I 19:00:40 Export Successfully Completed!

E 19:00:40 Operation Aborted! - Duration: 00:41:26

I 19:00:40 Average Write Rate: 78 KB/s (0.5x) - Maximum Write Rate: 5,083 KB/s (29.5x)

I 19:03:05 Operation Started!

I 19:03:06 Source Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 19:03:06 Source Media Type: CD-R (Disc ID: 97m27s66f, Ricoh Co.)

I 19:03:06 Source Media Supported Read Speeds: 8x, 10x, 16x, 24x, 32x, 40x

I 19:03:06 Source Media Supported Write Speeds: 16x, 24x, 32x, 40x

I 19:03:06 Image File: G:\ImgBurn test\hip.cue

I 19:03:06 Image File Sectors: 83,897 (MODE2/FORM1/2352)

I 19:03:06 Image File Size: 197,325,744 bytes

I 19:03:06 Image File File System(s): ISO9660, Joliet

I 19:03:06 Read Speed (Data/Audio): MAX / MAX

W 19:08:54 Session 1, Track 1 is smaller on the disc than it is in the image file.

W 19:08:54 Disc's Track Sectors: 83893 (TOC Sectors: 83895)

W 19:08:54 Image File's Track Sectors: 83897 (TOC Sectors: 83895)

I 19:08:54 Verifying Session 1 of 1... (1 Track, LBA: 0 - 83896)

I 19:08:54 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83896)

W 19:09:56 Failed to Read Sectors 83862 - 83888 - Reason: L-EC Uncorrectable Error

W 19:10:07 Failed to Read Sector 83888 - Reason: L-EC Uncorrectable Error

W 19:11:07 Retrying (1)...

W 19:12:00 Miscompare at LBA: 83887, Offset: 18

W 19:12:00 Device: 0xE4

W 19:12:00 Image File: 0x00

W 19:12:00 Total Errors in Sector: 757

W 19:12:00 Note: The drive probably corrected the Sync/Header Area because it's wrong in the image file.

I 19:12:00 Verifying Sectors...

W 19:12:07 Retry Failed - Reason: L-EC Uncorrectable Error

E 19:12:38 Failed to Read Sector 83888 - Reason: L-EC Uncorrectable Error

E 19:12:39 Failed to Verify Sectors!

I 19:12:40 Exporting Graph Data...

I 19:12:40 Graph Data File: C:\Users\Tom - Admin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_7-03_PM_97m27s66f.ibg

I 19:12:40 Export Successfully Completed!

E 19:12:40 Operation Failed! - Duration: 00:09:33

I 19:12:40 Average Verify Rate: 860 KB/s (5.7x) - Maximum Verify Rate: 4,407 KB/s (29.4x)

TSSTcorp_CDDVDW_SH-222AB_SB00_WEDNESDAY-DECEMBER-05-2012_6-14_PM_97m26s66f.ibg

post-49453-0-63147800-1354755296_thumb.jpg

post-49453-0-97913100-1354755296_thumb.jpg

post-49453-0-27570600-1354755297_thumb.jpg

post-49453-0-55446600-1354755297_thumb.jpg

Share this post


Link to post
Share on other sites

Right, I've had a look and I'm 99% sure it's waiting at the end of the write operation because the image you're trying to burn came from a disc recorded in TAO mode (rather than SAO/DAO). It's waiting for some extra data to arrive that just isn't ever going to.

 

This is the same issue that causes the buffer to never finish filling up - thus preventing the burn from starting. Only, because your image is larger than the buffer, you aren't hitting that problem.

 

I've already fixed the buffer not filling up issue and therefore the one you're seeing with the write not finishing should be fixed too.

 

I'm still looking into any issues that may occur after that.

Share this post


Link to post
Share on other sites
ok and could you also please attach the cue that 2.5.7.0 created from your source disc, thanks.

 

No problem; attached below. Thank you!

 

Right, I've had a look and I'm 99% sure it's waiting at the end of the write operation because the image you're trying to burn came from a disc recorded in TAO mode (rather than SAO/DAO). It's waiting for some extra data to arrive that just isn't ever going to.

 

I'm sure you noticed that v2.5.6.0 (apparently correctly) identifies the disk as having 83,895 sectors, while v2.5.7.0 for whatever reason insists that, No, it actually has 83,897 sectors???? The errors / hangs appear to occur when v2.5.7.0 is searching or waiting for those "missing" extra sectors.

 

I might add that copies of the disk created with v2.5.6.0 work perfectly in other computers, and I have tried them in several. For that matter, despite the errors, copies made with v2.5.7.0 seem to work perfectly as well - remember that my hex editor says that the data is the same either way.

 

I don't know what TAO or SAO/DAO modes are; the disks that I need to copy were given to me, I didn't compile or record the originals. I just know that everything works without a hitch in v2.5.6.0. I'm grateful that you are on top of this, and I'm sure you will get it sorted out.

 

If you have a beta version of v2.5.8.0 that you would like me to test that has a fix for this issue, then I am happy to help.

 

Thank you again.

hip.cue

Share this post


Link to post
Share on other sites

The quick fix for you right now is to edit the cue created by 2.5.7.0 and remove the last 2 lines.

 

It'll then burn and verify with both versions just fine.

 

If you look at the read operation from 2.5.6.0, you'll see it also says it's reading sectors 0 - 83896... so that's 83897 in total.

 

The difference between them is that it didn't include info about the unreadable 2 sector TAO gaps at the end of the disc in the CUE file and 2.5.7.0 does. I must have found something that made 2.5.6.0 fail, because that's the only reason why I would have changed it in 2.5.7.0.

 

TAO is Track At Once

DAO/SAO are Disc/Session at Once.

They're different writing methods supported by drives.

 

TAO is, I guess, the original method of burning but it's not flexible and so hardly used these days. Each track on a TAO recorded disc has 2 seconds (150 sectors) between them. Aside from those 150 sectors between tracks, drives also appear to add 2 seconds of unreadable data at the end of each track - that's my TAOGAP entry in the CUE file.

 

With DAO/SAO you can have any length gap you want (or no gap at all) making it much better for Audio discs etc. where you might want one track to flow directly into the next.

 

I'm currently trying to go through every possible combination of TAO image burning in TAO or DAO/SAO write modes, and SAO image burning in TAO or DAO/SAO write modes to make sure everything is now working as it should do.

Share this post


Link to post
Share on other sites
The quick fix for you right now is to edit the cue created by 2.5.7.0 and remove the last 2 lines.

 

OK, I removed the last 2 lines of the cue file, and I reinstalled v2.5.7.0.

 

I then did a verify of the original disk vs. the image file created with v2.5.7.0.

 

This time, as you predicted, it completed without errors.

 

If you look at the read operation from 2.5.6.0, you'll see it also says it's reading sectors 0 - 83896... so that's 83897 in total.

 

Where? The only time that I see v2.5.6.0 counting 83,897 sectors was when analyzing the image file created by v2.5.7.0! Otherwise, v2.5.6.0 consistently counted 83,895 sectors. With the corrected (last two lines removed) cue file, v2.5.7.0 is also counting 83,895 sectors, on both the disk and in the image, same as v2.5.6.0, not 83,897; see log file below. Graph data file also attached.

 

Thank you again, and HTH.

 

I 19:57:11 ImgBurn Version 2.5.7.0 started!

I 19:57:11 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 19:57:11 Total Physical Memory: 8,116,364 KB - Available: 4,807,476 KB

I 19:57:11 Initialising SPTI...

I 19:57:11 Searching for SCSI / ATAPI devices...

I 19:57:11 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (I:) (SCSI)

I 19:57:11 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (O:) (SCSI)

I 19:57:12 -> Drive 3 - Info: HL-DT-ST BDDVDRW GGC-H20L 1.03 (F:) (RAID)

I 19:57:12 -> Drive 4 - Info: TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 19:57:12 Found 1 DVD±RW/RAM, 2 BD-ROM/HD DVD-ROMs and 1 BD-ROM/HD DVD-ROM/DVD±RW!

I 19:58:11 Operation Started!

I 19:58:11 Source Device: [2:2:0] TSSTcorp CDDVDW SH-222AB SB00 (E:) (RAID)

I 19:58:11 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)

I 19:58:11 Source Media Supported Read Speeds: 8x, 10x, 16x, 24x, 32x, 40x

I 19:58:11 Source Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x

I 19:58:11 Image File: G:\ImgBurn test\hip.cue

I 19:58:11 Image File Sectors: 83,895 (MODE2/FORM1/2352)

I 19:58:11 Image File Size: 197,321,040 bytes

I 19:58:11 Image File File System(s): ISO9660, Joliet

I 19:58:11 Read Speed (Data/Audio): MAX / MAX

I 19:58:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 83894)

I 19:58:25 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 83894)

I 19:59:36 Exporting Graph Data...

I 19:59:36 Graph Data File: C:\Users\Tom - Admin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-222AB_SB00_THURSDAY-DECEMBER-06-2012_7-58_PM_97m26s66f.ibg

I 19:59:36 Export Successfully Completed!

I 19:59:36 Operation Successfully Completed! - Duration: 00:01:24

I 19:59:36 Average Verify Rate: 2,792 KB/s (18.6x) - Maximum Verify Rate: 3,487 KB/s (23.2x)

TSSTcorp_CDDVDW_SH-222AB_SB00_THURSDAY-DECEMBER-06-2012_7-58_PM_97m26s66f.ibg

Share this post


Link to post
Share on other sites

P.S. Thank you for the interesting explanation of the differences between TAO, and DAO/SAO.

 

The disk that I am copying contains an MRI scan of my hip, and was given to me by the hospital. I have no idea why their machine uses the apparently antiquated TAO method; I don't think their machine is that old. It is probably a legacy from code originally written for earlier MRI machines that no one has seen the need to change. ????

Share this post


Link to post
Share on other sites

Where? The only time that I see v2.5.6.0 counting 83,897 sectors was when analyzing the image file created by v2.5.7.0! Otherwise, v2.5.6.0 consistently counted 83,895 sectors.

 

I'm talking about when reading the source (TAO) disc.

 

...and when I say reading, I mean in Read mode.

Share this post


Link to post
Share on other sites

Oh, OK. Thanks. When I get the time, I will check that three ways: v2.5.6.0, v2.5.7.0, and v2.5.7.0 with the edited cue file.

 

Thank you. :beer: :beer:

Share this post


Link to post
Share on other sites

×

Important Information

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