Jump to content

Knightofoldcode

Members
  • Content Count

    14
  • Joined

  • Last visited

About Knightofoldcode

  • Rank
    ISF Newbie
  1. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Sweet...... Thank you! Knight.
  2. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Sounds good, and I totally understand that flagging an error on a good disc would be bad. Is there anyway you could add a feature for me (that is disabled by default), that would compare the md5sums and flag a error if they don't sync? Please? Knight.
  3. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Not at all, I'm not upset in anyway that the disc didn't read back properly, as you've said it's helped out with you, and that's well worth the bad disc, or even the entire spindle. I'm just trying to understand. As far as I see it, ImgBurn is still having an issue because it's not using MD5sum to verify the disc. Obviously in some cases a MD5Sum can be superior verification then a byte by byte, since in this particular case, the MD5sum is the only thing that caught the error, and of course that was by me noticing it, since ImgBurn isn't comparing them itself, it's just presenting them, and making the user check them. Also when you state, "The verify only shows that the drive you verify in can read it at that moment in time.", this to me infers that you think this has occcured only once. I can make ImgBurn verify the CD many many times, with this drive, every time it will say that it was successful, yet the md5sums don't match. I didn't know if you understood that portion of my posts, if you did, that's fine, no harm. Don't think I'm upset with the disc/drive, or even your responses and help. I'm glad I have been of help, and I'll look into the Taiyo Yuden cd's, I just love the ability to buy locally. btw, this is a Memorex CD. Knight.
  4. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    So are you saying that the CD is still good? Because if I try to verify/read on any other drive, it fails. EDIT: Also, when I try to reburn on same drive, same ISO, it creates a proper cd with matching MD5sums. So this was just a weird fluke. Knight.
  5. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    I totally understand....anything I can do to help.... I can't even reproduce this error, actually. With a different CD, that is. Yes, it does it without errors, however it appears to all be empty. Done, see attached. Knight. ImgBurn___Read.log ImgBurn___Verify.log
  6. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    On my original post, I said I initially burned the disc with my Internal SATA drive, that was incorrect, it was burned with an external USB based drive (SONY DVD RW DW-D22A BYS2 (USB)), hopefully that hasn't confused anyone. Knight.
  7. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Part A ) It came from a 'Read' mode from ImgBurn, using the 'SONY DVD RW DW-D22A BYS2 (USB)' Drive, this is also the drive that burned the bad disc. Part B ) I haven't attempted to 'Read' this bad disc from a different drive because previously I attempted to 'Verify' this bad disc from a different drive, at that time ImgBurn told me it couldn't read certain sectors, I think, but whatever it did say, it failed to verify part way through the verification, and did not complete. No, this is the primary issue and reason for bringing this up. When I burn anything with ImgBurn I always tell it to 'Verify' by checking off the box while it's burning, of course it stays checked off. After the burn, (using: SONY DVD RW DW-D22A BYS2 (USB)) it cycled the drive tray, then verified the disc. It verified the disc without any problems reported, and said everything was fine. However, I just happened to notice that the MD5Sums were not consistent from Image to Device. So I then attempted to 'Verify' from the original ISO and the Disc, using a different drive. Both different drives failed verification, however when I then verified with the same drive that burned this bad disc, it said it verified successfully, but again, the MD5sums did not match. I'm not concerned that it failed. I'm concerned that ImgBurn didn't notice that it failed, based on MD5sums. Knight.
  8. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Comp won't work because the file sizes are different (I think), unless there's a command line parameter to tell it to ignore different file sizes. Knight.
  9. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Here is the bad burned disc that was successfully verified: SONY DVD RW DW-D22A BYS2 (USB) Current Profile: CD-R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 329,184 Size: 674,168,832 bytes Time: 73:11:09 (MM:SS:FF) TOC Information: Session 1... (LBA: 0 - 329184) -> Track 01 (Mode 1, LBA: 0 - 329183) -> LeadOut (LBA: 329184) Track Information: Session 1... -> Track 01 (LTSA: 0, TS: 329182, LRA: 329181) ATIP Information: Start Time of LeadIn (MID): 97m26s66f Last Possible Start Time of LeadOut: 79m59s71f And here it is from a successfully burned, and correctly burned copy of the same correct ISO: SONY DVD RW DW-D22A BYS2 (USB) Current Profile: CD-R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 329,184 Size: 674,168,832 bytes Time: 73:11:09 (MM:SS:FF) TOC Information: Session 1... (LBA: 0 - 329184) -> Track 01 (Mode 1, LBA: 0 - 329183) -> LeadOut (LBA: 329184) Track Information: Session 1... -> Track 01 (LTSA: 0, TS: 329182, LRA: 329181) ATIP Information: Start Time of LeadIn (MID): 97m26s66f Last Possible Start Time of LeadOut: 79m59s71f They are identical. I got the sectors that you requested above by copying it from the left side after loading the respective ISO's. Here is the bad disc from another drive, Internal ATA. Optiarc DVD RW AD-7170S 1.82 (ATA) Current Profile: CD-R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 329,184 Size: 674,168,832 bytes Time: 73:11:09 (MM:SS:FF) TOC Information: Session 1... (LBA: 0 - 329184) -> Track 01 (Mode 1, LBA: 0 - 329183) -> LeadOut (LBA: 329184) Track Information: Session 1... -> Track 01 (LTSA: 0, TS: 329182, LRA: 0) ATIP Information: Start Time of LeadIn (MID): 97m26s66f Last Possible Start Time of LeadOut: 79m59s71f And the good disc from the Internal SATA drive: Optiarc DVD RW AD-7170S 1.82 (ATA) Current Profile: CD-R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 329,184 Size: 674,168,832 bytes Time: 73:11:09 (MM:SS:FF) TOC Information: Session 1... (LBA: 0 - 329184) -> Track 01 (Mode 1, LBA: 0 - 329183) -> LeadOut (LBA: 329184) Track Information: Session 1... -> Track 01 (LTSA: 0, TS: 329182, LRA: 0) ATIP Information: Start Time of LeadIn (MID): 97m26s66f Last Possible Start Time of LeadOut: 79m59s71f The two from the different drive are identical, but from the USB, and the SATA they are different. Yes, I'm positive I'm putting the correct CD's in, the data is identical, I promise. Knight.
  10. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    No, it's off by two sectors: Good ISO Sectors: 329,184 Good ISO Size: 674,168,832 Bytes Bad ISO Sectors: 329,182 Bad ISO Size: 674,164,736 Bytes I'll get back with you on the file comparison. Knight.
  11. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Any suggestions on what software to use? I did a search on these forums and didn't see any prefered software for comparing ISO's. Knight.
  12. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Okay, using ImgBurn I read the bad burn into an ISO. Then I did a md5sum (using 3rd party md5sum program) on it. It returned the same MD5sum that ImgBurn did for the Device's MD5sum: 0cd4b8871b4006644a31e11bfd711c77 I am personally not as concerned that the burn failed, but more concerned that ImgBurn didn't catch that it failed. If I hadn't been looking at the two MD5sums, I would have thought the disc was correctly burned. So, I guess ImgBurn needs to look at both MD5sums as well as the byte by byte analysis? Let me know if there is anything else I can do to help you, Lightning. Knight.
  13. Knightofoldcode

    MD5Sums don't match, yet verification was "Successful".

    Okay, so I'm not going nuts. So ImgBurn verifies the disc by byte by byte and not by the md5sums? Of course they *should* be the same, but obviously in some cases.... I'm still playing and trying to figure out the cause, whether the drive is at fault and causing bad burns or if it's the media at fault. I've only got a few discs left of this media (kinda scary, actually) so I don't know if I will be able to play much more. I'm going to read back this failed burn (in the drive that burned it, and that successfully verified it), into a ISO, and do a md5sum on it and report back. One thing I failed to mention in the original post was that the original ISO's md5sum was verified with a 3rd party program, so ImgBurn is correctly identifying the image's md5sum. Knight.
  14. I'm not certain this is a bug, but I would certainly consider it one. I slip streamed my Windows XP Service pack 2, with Service pack 3, and burned the resulting ISO to a printable Memorex 52X CD-R. I burned on internal SATA drive, it completed and said the verification was complete, but the md5sum's don't match. Are they supposed to? I would think so. If not, I need to learn why, since I'm storing the image MD5Sums, (and printing them on the CD itself), hoping to use it to verify data integrity. After the initial burn I didn't look at the MD5Sum and tried to verify on a second USB burner, it failed. Then I tried to verify on a third USB drive, it failed at a different area. Then I tried to verify on original Internal SATA Drive, it completed successfully, but MD5sums don't match..... Am I going nuts here? Thanks, Knightofoldcode. I 15:54:27 ImgBurn Version 2.4.2.0 started!I 15:54:27 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 15:54:27 Total Physical Memory: 3,407,084 KB - Available: 2,647,340 KB I 15:54:27 Initialising SPTI... I 15:54:27 Searching for SCSI / ATAPI devices... I 15:54:27 Found 1 DVD
×

Important Information

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