[Answered] I has the physical disk of Windows XP Pro Service Pack 1a, my checksums are genuine?

Discussion in 'Windows XP / Older OS' started by bencu55, Sep 6, 2025.

Thread Status:
Not open for further replies.
  1. bencu55

    bencu55 MDL Novice

    Sep 4, 2025
    33
    9
    0
    SHA1: a1254fd653b62175b8b12a4918ae15aebe504b3a

    MD5: ab144054cf58463261c5e506e991c13d

    Certificate of authenticy is on backside, my license key not used.

    Are the checksums valid?
     
  2. bencu55

    bencu55 MDL Novice

    Sep 4, 2025
    33
    9
    0
    #3 bencu55, Sep 6, 2025
    Last edited: Sep 6, 2025
    (OP)
    I use 7-zip file manager to create iso from my dvd directory, worked with win7 the checksums find on files.rg adguard.
    I have fake xp copy ? or is it my fault? It is hungarian version of Windows XP Pro.
     
  3. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    I must have missed something. Since when can 7-zip be used to create an iso file?
     
  4. bencu55

    bencu55 MDL Novice

    Sep 4, 2025
    33
    9
    0
  5. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    3,255
    4,407
    120
    @bencu55
    Load your XP cd into your cd drive and run in cmd:
    Code:
    crc.exe x:
    
    ("x" is letter of your cd drive)
    That's your baseline.

    Redump with 7z and see if you get same value...
     

    Attached Files:

  6. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    I can't speak for @bencu55, but dumping a physical dvd to iso using 7zip worked fine for me. The crc's matched. Used a physical vista sp2 disk in my case.
     
  7. WinDev

    WinDev MDL Expert

    Jul 6, 2013
    1,233
    1,196
    60
    These are checksums for English version:

    XRMPFPP_EN.iso
    Filesize: 565 854 208 bytes (539.64 MB)
    MD5: CAE234FB80361EDAACEFE5F48B203B86
    SHA1: 02695740D94FFB094FC3E80A7111C9501D534F6D
    CRC32: FFFFFFFF

    There is no evidence about Hungarian version.
     
  8. bencu55

    bencu55 MDL Novice

    Sep 4, 2025
    33
    9
    0
    Sorry for late reply, here is my results:
    upload_2025-9-11_14-30-44.png
     
  9. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    I am marking this solved, and closing, since you already got confirmation from an MS advisor that your disk is genuine.
     
  10. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    19,079
    19,893
    340
    @CaptainKirk1966

    Sorry for the intervention, but I had to reopen it.

    First of all, the moderator of the Microsoft Q&A forums delivered a generic reply without citing anything useful. Moreover, @Sajjo is actively communicating with @bencu55 to get a proper image without overdumping, so they still need a place for discussion.
     
  11. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    #16 CaptainKirk1966, Sep 11, 2025
    Last edited: Sep 11, 2025
    Sorry, my bad. I thought the discussion here may have been going off the rail.
     
  12. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    3,255
    4,407
    120
    He did (or did not :) , how he could verify a oem image in the first place was, well, don't see that often)
    Anyway, i can relay convo with @bencu55 best i can

    0.png
    There is now :) , however, if OP like to upload image or not is entirely up to him. :)
     
  13. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    #18 CaptainKirk1966, Sep 11, 2025
    Last edited: Sep 11, 2025
    Feeling guilty after closing too early, so I would ask some questions..

    @bencu55 - If you have, using 7zip, created an iso from the physical disk, does the crc of the iso match that of the physical disk posted in #13 above?

    Can you now use the built in function of 7Zip to compute md5, sha1, sha256 of that iso? Does that match what you posted in #1 above?

    There is also hu_windows_xp_professional_with_service_pack_3_x86_cd_x14-80456.iso on archive.org that doesn't match anything posted here so far. (non-oem most likely)
     
  14. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    3,255
    4,407
    120
    #19 Sajjo, Sep 12, 2025
    Last edited: Sep 12, 2025
    There is a tool (similar to the CRC posted above) - MSCDCRC 4.11 CD-ROM Disc Verification Utility Copyright (C) Microsoft, 1992-2004 upgraded with SHA-1.
    So far it's still not shared but there are some references:
    Code:
    MSCDCRC 4.22 CD-ROM Disc Verification Utility
    Copyright (C) Microsoft, 1992-2004
    
    MSCDCRC: Verifying disc in drive D: (1,479,409,664 bytes)
    
    100% complete
    
    MSCDCRC: Computed CRC is 0x8F7459EA
    MSCDCRC: SHA1 hash is 0xED7CC8AF67FF4031E450DBA2338089B91F0DEC6A
    [REQUEST/INFO] MS Windows Security Update CD - February 2004 [Multilanguage]
    Code:
    MSCDCRC 4.26 CD-ROM Disc Verification Utility
    Copyright (C) Microsoft, 1992-2004
    DDP (R) is trademark of DCA Inc. and is Licensed from DCA Inc.
    
    MSCDCRC: Verifying file Microsoft Windows Security Update CD (2004-02)\SECURITY9_CHS_12.iso (489,734,144 bytes)
    
    100% complete
    
    MSCDCRC: AutoCRC is 0xF4AD1F18
    MSCDCRC: Computed CRC is 0xFFFFFFFF
    MSCDCRC: SHA1 hash is 0x579EC3B0F6D082C1915602FEC943F32A8F399E0C
    
    MSCDCRC: This file contains a VALID computed CRC indicating the contents
             of the file are correct.
    This reads the true blocksize of a iso without trailing padding.
    You can do this in a hex editor as well, opening a logical drive and calculate checksum but normally you would calculate the hole block, including trailing padding.
    That gives a different checksum (usually called padded/overpadded etc)

    Size is found at 0x8050-0x8053 and 0x8054-0x8057 (difference is reversed endianess)
    Select 0x8054-0x8057 value, remove whitespace (xx xx xx xx -> xxxxxxxx) and convert this hex value to decimal value
    We continue using decimal values
    This poop's out total sector's value, take this value and multiply with 2048 (sector size value) and you get total (true) bytesize value of iso
    You can now select block size offset start 0 to offset end bytesize
    (remember - total bytesize starts from 1 but in a hexeditor we start at 0 so you must subtract total bytesize by 1)
    Calculate checksum of this block - done.

    Since this iso has AutoCRC, you can test that you selected correct blocksize and offsets by calculating CRC-32, this should output CRC-32: FFFFFFFF

    (if anyone wondered how :D )
     
  15. CaptainKirk1966

    CaptainKirk1966 One of the Green Guys
    Staff Member

    Oct 31, 2009
    2,924
    1,940
    90
    @Sajjo - Possible information overload in that previous post??? :)

    Anyhow, back to that vista sp2 disk I was playing with earlier. I have now experimented with 7-zip, PowerIso, ImgBurn, and dd on linux to create image of the raw disc. Surprise!! Only 7-zip created an image file with a crc that matched the physical disk, and the sha-1 of that image also matched what is posted on rg-adguard. The others all created an image that was slightly larger, and didn't match crc with the physical disk. (trailing padding?)

    So I am still thinking OP, @bencu55, is best off creating the iso with 7-zip, check for crc match, then check md5 and sha-1 of the iso thus created.