Jump to content

Clavius

Members
 View Profile  See their activity

  • Posts

    33

  • Joined

  • Last visited

 Content Type 

Posts posted by Clavius

    Settings: Apply-Button and Defaults-behavior

    in ImgBurn Suggestions

    Posted

    @Cynthia:

    Uuups, my fault!

    Since the first ImgBurn version, I never pushed the restore button again, because I was afraid loosing all my changes immediately.

    (But sometimes I want to know what the original settings were, without having to visit the forum.)

     

     

    @LUK:

    I like to see if I already clicked something in the settings. With a grey apply button, which turns black when changes were made (and turns grey again, when have been pushed), this is possible.

    But if you don't like it, I will manage to survive without it! ;-)

     

     

    However: Thanks both of you for taking the time!!!

    Clavius

    Settings: Apply-Button and Defaults-behavior

    in ImgBurn Suggestions

    Posted

    Hello,

     

    I hope this has not been discussed before, could find nothing via search.

     

    First, how about an apply-button in the settings, which is grey until actually changed something?

     

    Second, when hitting the restore-defaults-button, all settings are restored, right?

    Maybe this can be changed, so that only the settings on the visible tab are restored (after hitting ok/apply)?

     

    greets

    clavius

    Life span of media

    in ImgBurn General

    Posted

    Hi,

     

    does anybody have an idea what life span I can expect from a decent burn (low pipo, jitter, etc) on a decent media (Verbatim DVD+R DL, for example)?

     

    I'm aware that the manufacturers claim up to 100 years.

    But I read in a magazine, that even with proper handling (storage in the dark, medium temperature and humidity, only touching at the edge, etc) that one cannot expect much more than 5 years on the average.

     

    I would find that a bit too short.

     

    What do you think?

     

    Clavius

    L0 Data Zone Capacity Miscompare

    in ImgBurn Support

    Posted

    Nope, I meant 'disc', not 'image'.

    I was just confused, because "tools -> iso -> display ifo layer break" only works for images, correct?

     

    It's the last couple of lines in the info panel on the right within ImgBurn.

    Here it is:

    ----------Original Disc:

    Current Profile: DVD-ROM

    Sectors: 2.719.811

    Size: 5.570.172.928 bytes

    Track Path: Parallel Track Path (PTP)

    First Physical Sector of Data Area: 196.608

    Last Physical Sector of Data Area: 1.801.976

    Last Physical Sector in Layer 0: 0

    Layer 0 Sectors: 1.605.369 (59,03%)

    Layer 1 Sectors: 1.114.442 (40,97%)

    ----------Burned Disc:

    Current Profile: DVD+R DL

    Sectors: 2.719.824

    Size: 5.570.199.552 bytes

    Track Path: Opposite Track Path (OTP)

    First Physical Sector of Data Area: 196.608

    Last Physical Sector of Data Area: 16.089.679

    Last Physical Sector in Layer 0: 1.801.983

    Layer 0 Sectors: 1.605.376 (59,02%)

    Layer 1 Sectors: 1.114.448 (40,98%)

     

    Maybe this is something: The original disc is the second disc from a 5-year-old 4-DVD-set.

    The 3 other discs all have

    Track Path: Opposite Track Path (OTP)

    but this one has

    Track Path: Parallel Track Path (PTP)!

    I think I read somewhere that OTP is mandatory for video-DVDs?

     

     

    However, who knows how studios master their DVDs these days!

    It's about 5 years old.

     

    except be happy that ImgBurn has adjusted the L0 zone for you.

    Of course I am! :D

     

    In the future, I'd start off by having files, not an ISO.

    In the past I did so, using PgcEdit to make the image and ImgBurn to burn.

    But I hated it to make decisions about the layerbreak position. Especially one time, when I had a DVD with multiple angles, and I did not know which one to chose.

    Also, I'm some sort of a neurotic perfectionist and like to have everything as close as possible to the original.

    And until now this was the only occurrence of this error ever since I practise the "direct ISO to burn methodology".

    Are there any other disadvantages?

     

    Clavius

    L0 Data Zone Capacity Miscompare

    in ImgBurn Support

    Posted

    The disc seems to play fine in both WinDVD and my standalone.

     

    But is there nothing I can do to fix this, and not having this warning when burning this image?

     

    And,

     

    is there a way to check if the layerbreak point is wrong? I have both IfoEdit and PgcEdit installed, but I don't know where to look.

    L0 Data Zone Capacity Miscompare

    in ImgBurn Support

    Posted

    Hi,

     

    I did a search on this, but the only two topics which came up had something to do with build-mode and 32k-padding.

    But I got this warnings with an image which was created by "an other tool" from LUK.

     

    W 11:39:21 L0 Data Zone Capacity Miscompare!

    W 11:39:21 Wanted: 1605369, Got: 1605376

     

    I burned dozens of images before, and a few after this one, without this warning.

    This image, I burned twice to see if it was a reproducible warning (it was!).

    Verify went ok, and I even did a file by file compare with the image contents and the burned disc.

     

    So I wonder if I have something to worry about?

     

     

     

    I 11:38:23 ImgBurn Version 2.1.0.0 started!

    I 11:38:23 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

    W 11:38:23 Drive D:\ (FAT32) does not support single files > 4 GB

    W 11:38:23 Drive E:\ (FAT32) does not support single files > 4 GB

    I 11:38:23 Initialising SPTI...

    I 11:38:23 Searching for SCSI / ATAPI devices...

    I 11:38:23 Found 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

    W 11:38:57 Program 'Debug Mode' has been Enabled!

    I 11:39:21 Operation Started!

    I 11:39:21 Source File: G:\TEST.MDS

    I 11:39:21 Source File Sectors: 2.719.811 (MODE1/2048)

    I 11:39:21 Source File Size: 5.570.172.928 bytes

    I 11:39:21 Source File Volume Identifier: TEST

    I 11:39:21 Source File Implementation Identifier: UDF Toshiba DVD Video

    I 11:39:21 Source File File System(s): ISO9660; UDF (1,02)

    I 11:39:21 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 11:39:21 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 11:39:21 Destination Media Sectors: 4.173.824

    I 11:39:21 Write Mode: DVD

    I 11:39:21 Write Type: DAO

    I 11:39:21 Write Speed: 2,4x

    I 11:39:21 Link Size: Auto

    I 11:39:21 Test Mode: No

    I 11:39:21 BURN-Proof: Enabled

    I 11:39:21 Optimal L0 Data Zone Capacity: 1.605.369

    I 11:39:21 Optimal L0 Data Zone Method: Copied From Original Disc

    W 11:39:21 L0 Data Zone Capacity Miscompare!

    W 11:39:21 Wanted: 1605369, Got: 1605376

    D 11:39:35 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    D 11:39:35 Device Buffer Size: 6.291.456 bytes.

    D 11:39:35 Device Buffer Available: 6.291.456 bytes.

    I 11:39:35 Filling Buffer...

    I 11:39:45 Writing LeadIn...

    I 11:40:26 Writing Image...

    I 11:40:26 Writing Layer 0... (LBA: 0 - 1605368)

    I 11:56:51 Writing Layer 1... (LBA: 1605369 - 2719810)

    I 12:08:18 Synchronising Cache...

    I 12:08:22 Closing Track...

    I 12:08:23 Finalising Disc...

    I 12:14:17 Image MD5: 9616e32cb4bedcfc9c8e91b57bec4725

    I 12:14:20 Exporting Graph Data...

    I 12:14:20 Graph Data File: G:\TEST_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 12:14:20 Export Successfully Completed!

    I 12:14:20 Operation Successfully Completed! - Duration: 00:34:56

    I 12:14:20 Average Write Rate: 3.255 KB/s (2.4x) - Maximum Write Rate: 3.360 KB/s (2.4x)

    I 12:14:20 Cycling Tray before Verify...

    I 12:14:56 Device Ready!

    I 12:14:59 Operation Started!

    I 12:14:59 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 12:14:59 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 12:14:59 Image File: G:\TEST.MDS

    I 12:14:59 Image File Sectors: 2.719.811 (MODE1/2048)

    I 12:14:59 Image File Size: 5.570.172.928 bytes

    I 12:14:59 Image File Volume Identifier: TEST

    I 12:14:59 Image File Implementation Identifier: UDF Toshiba DVD Video

    I 12:14:59 Image File File System(s): ISO9660; UDF (1,02)

    D 12:14:59 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    I 12:15:00 Verifying Sectors...

    I 12:26:58 Device MD5: 9616e32cb4bedcfc9c8e91b57bec4725

    I 12:26:58 Device (Padded) MD5: 6710682da3585f76b07e08b2517c95b2

    I 12:26:58 Image MD5: 9616e32cb4bedcfc9c8e91b57bec4725

    I 12:26:59 Exporting Graph Data...

    I 12:26:59 Graph Data File: G:\TEST_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 12:26:59 Export Successfully Completed!

    I 12:26:59 Operation Successfully Completed! - Duration: 00:11:59

    I 12:26:59 Average Verify Rate: 7.576 KB/s (5.5x) - Maximum Verify Rate: 10.134 KB/s (7.3x)

    I 12:43:05 Close Request Acknowledged

    I 12:43:05 Closing Down...

    I 12:43:05 Shutting down SPTI...

    I 12:43:05 ImgBurn closed!

    MDS Specifications?

    in ImgBurn Support

    Posted

    Sorry but you'll just have to wait until v2.2.0.0 gets released and then test that one. (No date planned as yet)

    Actually I'm very glad that you haven't just discarded this issue! :)

     

    (I guess I can't convince you to let me try out a beta-version? :rolleyes: )

    MDS Specifications?

    in ImgBurn Support

    Posted

    News from my MD5-issue:

     

    Something odd must have just happened the first time and the MD5 calculation code either never got started for the 'device' buffer or it gave an error part way through - which would then disable it. It's impossible to say what caused it without catching it in the act of failing.

    Feel free to keep logging the extra debug stuff (when you remember) until it happens again (if it happens again). Then let me see the log and maybe between us we can work out why it's happening.

    It happened again! :(

    And I'm afraid, there is no extra debug-message related to this! :mellow:

    (Only the PdhAddCounter-stuff, which we discussed in the previous posts)

     

     

    I 20:29:53 ImgBurn Version 2.1.0.0 started!

    I 20:29:53 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

    W 20:29:53 Drive D:\ (FAT32) does not support single files > 4 GB

    W 20:29:53 Drive E:\ (FAT32) does not support single files > 4 GB

    I 20:29:54 Initialising SPTI...

    I 20:29:54 Searching for SCSI / ATAPI devices...

    I 20:29:54 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW!

    W 20:30:10 Program 'Debug Mode' has been Enabled!

    I 20:30:14 Operation Started!

    I 20:30:14 Source File: G:\TEST3.MDS

    I 20:30:14 Source File Sectors: 2.140.328 (MODE1/2048)

    I 20:30:14 Source File Size: 4.383.391.744 bytes

    I 20:30:14 Source File Volume Identifier: TEST3

    I 20:30:14 Source File Implementation Identifier: Daikin U.S. Comtec Lab

    I 20:30:14 Source File File System(s): ISO9660; UDF (1,02)

    I 20:30:14 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 20:30:14 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 4x; 6x; 8x)

    I 20:30:14 Destination Media Sectors: 2.295.104

    I 20:30:14 Write Mode: DVD

    I 20:30:14 Write Type: DAO

    I 20:30:14 Write Speed: 2,4x

    I 20:30:14 Link Size: Auto

    I 20:30:14 Test Mode: No

    I 20:30:14 BURN-Proof: Enabled

    D 20:30:25 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    D 20:30:25 Device Buffer Size: 6.291.456 bytes.

    D 20:30:25 Device Buffer Available: 6.291.456 bytes.

    I 20:30:25 Filling Buffer...

    I 20:30:25 Writing LeadIn...

    I 20:30:48 Writing Image...

    I 20:43:57 Synchronising Cache...

    I 20:44:01 Closing Track...

    I 20:44:02 Finalising Disc...

    I 20:44:18 Image MD5: dd94dd55c1ecf054be129275368f7454

    I 20:44:19 Exporting Graph Data...

    I 20:44:19 Graph Data File: G:\TEST3_PLEXTOR_DVDR_PX-716A_1.10_RITEK-R03-02_2,4x.ibg

    I 20:44:19 Export Successfully Completed!

    I 20:44:19 Operation Successfully Completed! - Duration: 00:14:03

    I 20:44:19 Average Write Rate: 5.425 KB/s (3.9x) - Maximum Write Rate: 6.695 KB/s (4.8x)

    I 20:44:19 Cycling Tray before Verify...

    I 20:44:45 Device Ready!

    I 20:44:47 Operation Started!

    I 20:44:47 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 20:44:47 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: RITEK-R03-02) (Speeds: 4x; 6x; 8x)

    I 20:44:47 Image File: G:\TEST3.MDS

    I 20:44:47 Image File Sectors: 2.140.328 (MODE1/2048)

    I 20:44:47 Image File Size: 4.383.391.744 bytes

    I 20:44:47 Image File Volume Identifier: TEST3

    I 20:44:47 Image File Implementation Identifier: Daikin U.S. Comtec Lab

    I 20:44:47 Image File File System(s): ISO9660; UDF (1,02)

    D 20:44:48 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    I 20:44:48 Verifying Sectors...

    I 20:51:05 Image MD5: dd94dd55c1ecf054be129275368f7454

    I 20:51:05 Exporting Graph Data...

    I 20:51:05 Graph Data File: G:\TEST3_PLEXTOR_DVDR_PX-716A_1.10_RITEK-R03-02_2,4x.ibg

    I 20:51:05 Export Successfully Completed!

    I 20:51:05 Operation Successfully Completed! - Duration: 00:06:18

    I 20:51:05 Average Verify Rate: 11.354 KB/s (8.2x) - Maximum Verify Rate: 16.278 KB/s (11.8x)

    I 20:52:15 Close Request Acknowledged

    I 20:52:15 Closing Down...

    I 20:52:15 Shutting down SPTI...

    I 20:52:15 ImgBurn closed!

    MDS Specifications?

    in ImgBurn Support

    Posted

    No router here!

    Just one PC directly connected to the DSL-Modem!

    (Software-Firewall of course (Kerio))

     

    I know that I'm a bit paranoid, but I think I would rather live without the two graphs than enabling f+p sharing when I don't really need f+p sharing.

    OK, I could do it temporarily for one test-burn without connecting to the Internet during the test, but I'm to anxious that I mess something up.

     

    Write-speed and Verify-speed graphs are working, which is most important to me.

    MDS Specifications?

    in ImgBurn Support

    Posted

    Very weird, because task manager is working OK on my system.

    Unfortunately I have no knowledge about this performance monitor stuff, but ever since ImgBurn is capable of recording the CPU-usage, I get PerfNet error 2004 in eventviewer. And at eventid.net and in google-groups they say this error appears if the server service is not running, which may occur when disabling file and printer sharing.

    Don't know if this is really related, but to me it seems so.

     

    When maybe some time far in the future I will have more time, I will do some more research.

     

    Thank you anyway!

    MDS Specifications?

    in ImgBurn Support

    Posted

    Feel free to keep logging the extra debug stuff (when you remember) until it happens again (if it happens again). Then let me see the log and maybe between us we can work out why it's happening.

    Sounds good to me! :)

     

    So if you try to add a counter, do not get 'Processor' in the 'Performance Object' drop down list? (or anything like it?)

    Exactly! :(

    MDS Specifications?

    in ImgBurn Support

    Posted

    As for why it didn't work the first time... no idea, it's your pc, not mine ;)

    I'm reasonably sure that I changed nothing between the two burns. (Besides pressing F6)

     

    If I right click one of the 3 visible in the main screen and hit properties, this is the screen i get:

    First of all, thank you very much for your time!!!

     

    I did as you said and got only the second of your three entries.

    Actually, I got another PerfNet-Error immediately after opening perfmon.msc.

    I tried to add the other two entries, but could not find them in the list.

    After a little googleing I think it might be because I've disabled file and printer sharing due to paranoid security reasons. (I read that disabling it causes the server-service to disappear)

    So I guess I have to live without CPU- and Buffer-graphs!?

    (Buffer-graphs would be nice though!)

     

    Clavius

    MDS Specifications?

    in ImgBurn Support

    Posted

    OK, now this is strange:

     

    I did press F6 before my latest burn, and this time it worked!? I got both Device-MD5s, normal and padded.

     

    Furthermore, I got two times this entry:

    D 18:44:41 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

     

     

    2 Questions:

     

    1)

    Why did the MD5-stuff work correct this time, and will I have to press F6 every-time from now on?

     

    2)

    What does the debug-message mean?

    (Could it have to do with the fact that every-time I do a burn with ImgBurn, I get a "PerfNet"-error in eventviewer, and that I get no CPU- and Buffer-Graphs in DVDInfo?)

     

     

    Thanks in advance

    Clavius

     

     

     

    I 18:44:14 ImgBurn Version 2.1.0.0 started!

    I 18:44:14 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

    W 18:44:14 Drive D:\ (FAT32) does not support single files > 4 GB

    W 18:44:14 Drive E:\ (FAT32) does not support single files > 4 GB

    W 18:44:14 Drive S:\ (FAT32) does not support single files > 4 GB

    I 18:44:14 Initialising SPTI...

    I 18:44:14 Searching for SCSI / ATAPI devices...

    I 18:44:14 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW!

    W 18:44:17 Program 'Debug Mode' has been Enabled!

    I 18:44:25 Operation Started!

    I 18:44:25 Source File: G:\test2.MDS

    I 18:44:25 Source File Sectors: 2.858.954 (MODE1/2048)

    I 18:44:25 Source File Size: 5.855.137.792 bytes

    I 18:44:25 Source File Volume Identifier: test2

    I 18:44:25 Source File Implementation Identifier: Spruce Technologies

    I 18:44:25 Source File File System(s): ISO9660; UDF (1,02)

    I 18:44:25 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 18:44:25 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 18:44:25 Destination Media Sectors: 4.173.824

    I 18:44:25 Write Mode: DVD

    I 18:44:25 Write Type: DAO

    I 18:44:25 Write Speed: 2,4x

    I 18:44:25 Link Size: Auto

    I 18:44:25 Test Mode: No

    I 18:44:25 BURN-Proof: Enabled

    I 18:44:25 Optimal L0 Data Zone Capacity: 1.713.264

    I 18:44:25 Optimal L0 Data Zone Method: Copied From Original Disc

    D 18:44:41 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    D 18:44:41 Device Buffer Size: 6.291.456 bytes.

    D 18:44:41 Device Buffer Available: 6.291.456 bytes.

    I 18:44:41 Filling Buffer...

    I 18:44:42 Writing LeadIn...

    I 18:45:23 Writing Image...

    I 18:45:23 Writing Layer 0... (LBA: 0 - 1713263)

    I 19:02:55 Writing Layer 1... (LBA: 1713264 - 2858953)

    I 19:14:40 Synchronising Cache...

    I 19:14:44 Closing Track...

    I 19:14:45 Finalising Disc...

    I 19:21:27 Image MD5: 4f15842128dba922d5b9fae7d36d917b

    I 19:21:29 Exporting Graph Data...

    I 19:21:29 Graph Data File: G:\test2_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 19:21:29 Export Successfully Completed!

    I 19:21:29 Operation Successfully Completed! - Duration: 00:37:02

    I 19:21:29 Average Write Rate: 3.254 KB/s (2.3x) - Maximum Write Rate: 4.015 KB/s (2.9x)

    I 19:21:29 Cycling Tray before Verify...

    I 19:22:05 Device Ready!

    I 19:22:07 Operation Started!

    I 19:22:07 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 19:22:07 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 19:22:07 Image File: G:\test2.MDS

    I 19:22:07 Image File Sectors: 2.858.954 (MODE1/2048)

    I 19:22:07 Image File Size: 5.855.137.792 bytes

    I 19:22:07 Image File Volume Identifier: test2

    I 19:22:07 Image File Implementation Identifier: Spruce Technologies

    I 19:22:07 Image File File System(s): ISO9660; UDF (1,02)

    D 19:22:07 PdhAddCounter Failed! - Error Code: 0xC0000BB8 - Interpretation: The specified object is not found on the system.

    I 19:22:07 Verifying Sectors...

    I 19:34:26 Device MD5: 4f15842128dba922d5b9fae7d36d917b

    I 19:34:26 Device (Padded) MD5: 4511b6b9897bef84759381d4cb707df5

    I 19:34:26 Image MD5: 4f15842128dba922d5b9fae7d36d917b

    I 19:34:27 Exporting Graph Data...

    I 19:34:27 Graph Data File: G:\test2_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 19:34:27 Export Successfully Completed!

    I 19:34:27 Operation Successfully Completed! - Duration: 00:12:19

    I 19:34:27 Average Verify Rate: 7.737 KB/s (5.6x) - Maximum Verify Rate: 10.318 KB/s (7.4x)

    I 00:01:43 Close Request Acknowledged

    I 00:01:43 Closing Down...

    I 00:01:43 Shutting down SPTI...

    I 00:01:43 ImgBurn closed!

    MDS Specifications?

    in ImgBurn Support

    Posted · Edited by Clavius

    What can I do to pinpoint that reason?

     

    (Is it likely that I made mistake or that is has to do with my configuration? Or may it even be possible that it is some kind of bug in the code? (I don't want to sound blasphemic, though ;) )

     

    (I am sorry if I'm annoying you with this, but I would really love to have this feature working.)

     

     

    EDIT: Spelling

    MDS Specifications?

    in ImgBurn Support

    Posted

    I'll still leave the 'Device (Padded) MD5: xxxxxxx' value in the log though for times when you're burning images that don't align to ECC blocks properly and so the drive DOES have to do its own padding.
    Added: An alternative 'Padded' MD5 calculation for when burning + verifying an image on DVD+R media where the drive automatically pads the image so the last sector is divisible by 16.

    I can't find the 'Device (Padded) MD5: xxxxxxx'-entry in the log!

    Or am I missing something?

    (FYI: On a previous burn from an image which was divisible by 16, there was the normal 'Device MD5: xxxxxx'-entry in the log, as in version 2.0.0.0.

    But with this image , which is not divisible by 16, I can't find neither the 'Device MD5'- nor the 'Device (Padded) MD5'-entry in the log)

    (Or is it supposed to work only for DVD+R but not for DVD+R DL?)

     

    I 20:52:49 ImgBurn Version 2.1.0.0 started!

    I 20:52:49 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

    W 20:52:49 Drive D:\ (FAT32) does not support single files > 4 GB

    W 20:52:49 Drive E:\ (FAT32) does not support single files > 4 GB

    W 20:52:49 Drive S:\ (FAT32) does not support single files > 4 GB

    I 20:52:49 Initialising SPTI...

    I 20:52:49 Searching for SCSI / ATAPI devices...

    I 20:52:50 Found 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

    I 20:52:54 Operation Started!

    I 20:52:54 Source File: G:\test1.MDS

    I 20:52:54 Source File Sectors: 3.340.287 (MODE1/2048)

    I 20:52:54 Source File Size: 6.840.907.776 bytes

    I 20:52:54 Source File Volume Identifier: test1

    I 20:52:54 Source File Implementation Identifier: Spruce Technologies

    I 20:52:54 Source File File System(s): ISO9660; UDF (1,02)

    I 20:52:54 Destination Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 20:52:54 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 20:52:54 Destination Media Sectors: 4.173.824

    I 20:52:54 Write Mode: DVD

    I 20:52:54 Write Type: DAO

    I 20:52:54 Write Speed: 2,4x

    I 20:52:54 Link Size: Auto

    I 20:52:54 Test Mode: No

    I 20:52:54 BURN-Proof: Enabled

    I 20:52:54 Optimal L0 Data Zone Capacity: 2.075.264

    I 20:52:54 Optimal L0 Data Zone Method: Copied From Original Disc

    I 20:53:12 Filling Buffer...

    I 20:53:13 Writing LeadIn...

    I 20:53:51 Writing Image...

    I 20:53:51 Writing Layer 0... (LBA: 0 - 2075263)

    I 21:15:05 Writing Layer 1... (LBA: 2075264 - 3340286)

    I 21:28:04 Synchronising Cache...

    I 21:28:08 Closing Track...

    I 21:28:09 Finalising Disc...

    I 21:37:19 Image MD5: b95dfddde270e34a980ff709551f8550

    I 21:37:22 Exporting Graph Data...

    I 21:37:22 Graph Data File: G:\test1_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 21:37:22 Export Successfully Completed!

    I 21:37:22 Operation Successfully Completed! - Duration: 00:44:25

    I 21:37:22 Average Write Rate: 3.255 KB/s (2.4x) - Maximum Write Rate: 3.385 KB/s (2.4x)

    I 21:37:22 Cycling Tray before Verify...

    I 21:38:04 Device Ready!

    I 21:38:06 Operation Started!

    I 21:38:06 Source Device: [3:0:0] PLEXTOR DVDR PX-716A 1.10 (Y:) (ATAPI)

    I 21:38:06 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x; 4x; 6x)

    I 21:38:06 Image File: G:\test1.MDS

    I 21:38:06 Image File Sectors: 3.340.287 (MODE1/2048)

    I 21:38:06 Image File Size: 6.840.907.776 bytes

    I 21:38:06 Image File Volume Identifier: test1

    I 21:38:06 Image File Implementation Identifier: Spruce Technologies

    I 21:38:06 Image File File System(s): ISO9660; UDF (1,02)

    I 21:38:06 Verifying Sectors...

    I 21:51:37 Image MD5: b95dfddde270e34a980ff709551f8550

    I 21:51:37 Exporting Graph Data...

    I 21:51:37 Graph Data File: G:\test1_PLEXTOR_DVDR_PX-716A_1.10_MKM-001-00_2,4x.ibg

    I 21:51:37 Export Successfully Completed!

    I 21:51:37 Operation Successfully Completed! - Duration: 00:13:30

    I 21:51:37 Average Verify Rate: 8.247 KB/s (6.0x) - Maximum Verify Rate: 11.180 KB/s (8.1x)

    I 21:57:16 Close Request Acknowledged

    I 21:57:16 Closing Down...

    I 21:57:16 Shutting down SPTI...

    I 21:57:16 ImgBurn closed!

    MDS Specifications?

    in ImgBurn Support

    Posted

    Hmm you've actually brought another problem to my attention now with this thread.
    I'm glad if i could help! ;)
    I'll still leave the 'Device (Padded) MD5: xxxxxxx' value in the log though for times when you're burning images that don't align to ECC blocks properly and so the drive DOES have to do its own padding.
    That would be great! :)

    MDS Specifications?

    in ImgBurn Support

    Posted

    So whilst it might seem logical to read ALL the sectors on a disc, even when comparing to a smaller image, it doesn't work in practice.

    That absolutely makes sense to me, but I thought the MD5 of the Disc could somehow be calculated/extrapolated!?

     

    I do not know anything about the MD5-algorithm, but I thought, since ImgBurn knows the size of the original image on HD, it must be possible to calculate the resulting size on the disc, taking the DVD+R-padding into account.

    And since these padding-bytes are all zero (or whatever), I thought it might be possible to calculate the MD5 with padding-bytes from the MD5 without padding-bytes.

    But presumably I am very wrong!?

     

    Clavius

    MDS Specifications?

    in ImgBurn Support

    Posted

    It calculates it based on the number of sectors it has to read or write.
    I understand! Thought something like that.

     

    I will not be changing anything in that respect, sorry.
    That's too bad! I don't quite understand what it's good for then! At least concerning DVD+ media.

     

    But I figured out a workaround for me:

    Since the file-size of the original image is given in the ImgBurn-log, I can truncate the re-read image to its original size and do the MD5-calculation.

     

     

    BTW: I don't want to sound as if I don't appreciate your work!

    I love ImgBurn more than ever!!! :-)

     

    Clavius

    MDS Specifications?

    in ImgBurn Support

    Posted

    Burning to DVD+ format media will always burn up to a sector that's divisible by 16.
    Only if you calculate it from the DVD+R image. It won't grow again after it's been burnt to DVD+R once.

    So you'd need to burn and then read it back again. Do the checksum on that new image.

    I would like to know, how you have addressed this issue with the new md5-function in the new 2.0.0.0-version.

     

    I just burned an image from my HD to a DVD+R DL.

     

    The original image had:

    MD5 = 4de18742714d5b4018bcac5a76376e6f

     

    The burned, an then re-read image had:

    MD5 = ca1f18e1ba53ae230d536bab67eaf97e

     

    So far, so good, from your explanations above, but:

     

    When I verify the DVD+R DL against the ORIGINAL image in ImgBurn, the logfile says:

    I 18:15:19 Device MD5: 4de18742714d5b4018bcac5a76376e6f

    I 18:15:19 Image MD5: 4de18742714d5b4018bcac5a76376e6f

     

    When I verify the SAME DVD+R DL against the RE-READ image, the logfile says:

    I 18:43:22 Device MD5: ca1f18e1ba53ae230d536bab67eaf97e

    I 18:43:22 Image MD5: ca1f18e1ba53ae230d536bab67eaf97e

     

    ???

     

    Unfortunately the MD5 which the ImgBurn-log provides after a burn is the first one, but what I would like to have for future reference is the second one (or both).

    Wouldn't it be possible to calculate that second one too?

     

    Thanx

    Clavius

×
×
  • Create New...

Important Information

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

  I accept