Microsoft Windows 2000/ XP Info for Collectors

Discussion in 'Windows XP / Older OS' started by Oz, Feb 27, 2014.

  1. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    #21 Threat, Mar 23, 2014
    Last edited by a moderator: Apr 20, 2017
  2. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    #22 Threat, Mar 23, 2014
    Last edited by a moderator: Apr 20, 2017
    Hmm really odd

    I made F098F ...

    Code:
      File: XP_PRO_SP3-2008-06-17-F098F.iso
    CRC-32: 5b692c52
       MD4: 1f10e03206e0dddc25d8af53863a6ef6
       MD5: a9c508db7da45c5667e4ee2f847fdd6e
     SHA-1: 46f94d027c55ab1506a83869e820eb00c9e97cae
    Size: 624,754,688 bytes

    But that matches your YH3KD ?
     
  3. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #23 Oz, Mar 23, 2014
    Last edited by a moderator: Apr 20, 2017
    (OP)
    Code:
    
    Microsoft Windows XP Professional SP3   - 20080619 - F098F
    
      File: XP_PRO_SP3.iso
    CRC-32: 5b692c52
       MD4: 1f10e03206e0dddc25d8af53863a6ef6
       MD5: a9c508db7da45c5667e4ee2f847fdd6e
     SHA-1: 46f94d027c55ab1506a83869e820eb00c9e97cae
    
    Code:
    
    Microsoft Windows XP Professional SP3   - 20090819 - YH3KD
      
    File: XP_PRO_SP3.iso
    CRC-32: cd1ad34c
       MD4: 4af0ccbb685070d2767b5fc4aa14ccf0
       MD5: c4f614efbedc423b77bbd7b7b6df8368
     SHA-1: dd588e792ec5f4def5ca5bacf83854c461e86030
    
    Got them mixed up, will redo

    EDIT, hopefully right this time.

    I already had the F098F before EFA11 upped it, but I had it under a different label, wasn't sure which code belonged to that hash, but after EFA11 posted it I knew which the F098F really was.
     

    Attached Files:

  4. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    That one worked thanks :)
     
  5. EFA11

    EFA11 Avatar Guru

    Oct 7, 2010
    8,719
    6,741
    270
    I tossed the XP list out there becuase I lost control of myself and added unverified with verified, some named wrong etc. lol so I don't know whats right or not :p
     
  6. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    I'm sure between you me and Oz we will sort it ... or make an even bigger mess :tooth:
     
  7. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    #27 Threat, Mar 30, 2014
    Last edited by a moderator: Apr 20, 2017
    Checking my collection of OEM I seem to be missing 1 (WXHOEM_EN_v1)

    Could you post a delta

    Code:
    From : SP0 Home OEM  WXHOEM_EN_v2 5fcbae9b71d7d2d6d3d1b48b739f04f7cc99d17a
    To   : SP0 Home OEM  WXHOEM_EN_v1 8e203aa17d7891edf0251479bcd67923cd074779
    Thanks
     
  8. WinDev

    WinDev MDL Expert

    Jul 6, 2013
    1,226
    1,185
    60
    #28 WinDev, Mar 30, 2014
    Last edited by a moderator: Apr 20, 2017
    What is the difference between v1 and v2 versions? Maybe some updates added?
     
  9. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,063
    871
    60
    #29 Threat, Mar 30, 2014
    Last edited: Mar 31, 2014
    Well for the Pro v1/v2 - So glad you asked :eek:

    Both ISO's seem to have been mastered on the same date (20010808) - so I suspect they are not reissued media....

    There are 2 bytes in the section at the start of the iso (0x8050/0x8057) - in both cases v1 = 0x2F, v2 = 0x30, 4 bytes at the end of this section (0x97FC) probably a CRC32 or other checksum... v1 = 0x7B,0x06,0x7F,0x70 whilst v2 = 0x78,0x2C,0x81,0x1F.

    Some differences in the file system for an entry for a file "EULA.TXT" .... this causes all other file entries in the directory listing to contain 2 or 3 different bytes per file as the changes to EULA.TXT will move data further down (start/end block type stuff...)

    Then the changes in EULA.TXT itself are mostly 0x20 (white space) changed to 0x0D,0x0A (CR/LF) - i.e. they pressed enter to take out the need for wordwrap (LOL), and then they added the EULA contents in another language (one they missed off?). Some more spaces to CR/LF...

    The license file ending is changed (EULAID:WX.1_PRO_OEM_EN -> EULAID:WX.2_PRO_OEM_EN - hence the filename change), some padding to end of the sector/block.... Finally the last 4 bytes is new AutoCRC value which will be different of course...

    Bet you wish you never asked now!!!!!

    So to sum it up ... they changed the EULA to add another language and take out the need for wordwrap. LMAO.All other files are 100% binary identical so no "code" changes or updates or additional fixes/drivers etc. Nothing to exciting really.

    In all honesty since they were all on the same day, and the XP Home Retails Upgrade begins WX.4 I suspect this number is really and index and not a "version" of the same file. I suspect the 2 OEM Pro/Homes with v2 having more languages in EULA is down to it been more "global" and v1 was a more "regional" - like US(en) vs US(en)+EU where the EU would add in other languages like French, German, Spanish etc.... rather than it been a reissue "version". I suspect the CR/LF vs spaces was down to the person doing the typing of those license files not knowing about wordwrap vs pressing enter at the end of each line (probably paid some intern to type it up for them)

    Guessing v1 is US, v2 is EU

    EDIT: This was based on Pro since I had v1/v2 for this but suspect same will apply to Home v1/v2
     
  10. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    #30 Oz, Mar 31, 2014
    Last edited by a moderator: Apr 20, 2017
    (OP)
    Done......
     

    Attached Files:

  11. ibmpc5150

    ibmpc5150 MDL Member

    Apr 14, 2014
    168
    107
    10
    The very rare version of Windows 2000 must be follows.

    ZRMPFPP_JA : Windows 2000 Professional with SP4 (Japanese) for PC Compatible. (Not for PC-98x1) -- ja_win2000_pro_sp4.iso
    ZRMSFPP_JA : Windows 2000 Server with SP4 (Japanese) for PC Compatible. (Not for PC-98x1) -- ja_win2000_srv_sp4.iso
    ZRMAFPP_JA : Windows 2000 Advanced Servier with SP4 (Japanese) -- ja_win2000_advsrv_sp4.iso
    ZRMSFPP_KO : Windows 2000 Server with SP4 (Korean) -- ko_win2000_srv_sp4.iso
    ZRMAFPP_KO : Windows 2000 Advanced Servier with SP4 (Korean) -- ko_win2000_advsrv_sp4.iso

    It can't be found on the net.
     
  12. ibmpc5150

    ibmpc5150 MDL Member

    Apr 14, 2014
    168
    107
    10
  13. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
  14. ibmpc5150

    ibmpc5150 MDL Member

    Apr 14, 2014
    168
    107
    10
    #34 ibmpc5150, May 12, 2014
    Last edited: May 13, 2014
    Can anyone attach patch of the following from ZRMPFPP_EN or ZRMPSEL_EN?


    ZRMPOEM_EN feeceb7a86126422a04dff98cbfaf3b655bab983 ce9b012b8a13170a7de90cfd60b06fe2 ffffffff 386,809,856



    I've got the following one.

    ZRMPOEM_EN (A2?)95da60cc073f0189812adb59207957dc99ffe59d ed302a3447184cf1372f5d72dc72bd21 ffffffff 387,117,056


    I'll attach the patch later.


    P.S. Oops. my mistake. ZRMPOEM_EN (A2?) is overdumped. Now, I've fixed it.
    Yes, SHA1:feeceb7a86126422a04dff98cbfaf3b655bab983 is correct, sorry.
     
  15. Oz

    Oz MDL Expert

    Sep 1, 2009
    1,077
    743
    60
    1234567890
     

    Attached Files:

  16. lovestudio

    lovestudio MDL Member

    Mar 24, 2014
    101
    1
    10
    I would thanks to anyone who can give link for windows 2000 en original without cracks, possibly with latest service pack, cos here i do not understand all that.:confused:
     
  17. ogfrm

    ogfrm MDL Novice

    Feb 5, 2009
    26
    29
    0
    can anyone give me patch to YRMSOEM_EN.ISO file. I have ZRMPSEL_EN.ISO ZRMSFPP_EN.ISO files.
    Thank you
     
  18. Lila

    Lila MDL Novice

    Mar 24, 2014
    41
    0
    0
    Are the posted SHA1 values original from MSDN website?
     
  19. ibmpc5150

    ibmpc5150 MDL Member

    Apr 14, 2014
    168
    107
    10
    What is it?

    At least, Windows 2000 Professional (chk) (MSDN) is from MSDN Disc.