Code: 9.Windows Server 2003 R2, Enterprise Edition - VL (Simplified Chinese) *DVD.21 Windows Server 2003 R2, Enterprise Edition - Disc 1 - VL (Simplified Chinese) Date/Time Posted: File: sc_win_srv_2003_r2_enterprise_vl_cd1.iso ISO-9660 CD Image File Size: SHA-1 Hash: 95BBAB37520F32163E1858E3130AFED58A138C97 MD5: C60177C96A5C7D72CC744903D72BB2B3 AutoCRC signature for media in BRMEVOL_CN.iso <609118208 bytes> is 0x5A88C6FC AutoCRC indicates the media in BRMEVOL_CN.iso is VALID this hash value seems to be not original in my thought.
afaik BRM_XX = ARM_XX with - EULA.TXT from BX2_XX <- FPP = VOL - MDMSSYS.IN_ <- changed header (;UUIDREF=....) not unify for all language (the valid one can be found on MSDN cd's / dvd's) FPP = VOL - all other files binary the same as ARM BRM -> BX2 is total diffrent (some new files, some .XX_ cabfiles extract to plain file, some update files) ther are much more diffrent then the 2 dll you mentioned
this two can be differ my one is jan 2006 (like FPP) BRMEVOL_CN = BRMEFPP_CN 0xE4 2006011712000000 BRMEVOL_HK = BRMEFPP_CN 0xE4 2006011712000000 may be there are older version like all other from nov / dec 2005 with 0xE0 TZ can you send me your BRMEVOL_CN.iso to compare ?
hmm the same Web page list BRMSCD2FRE_CN.iso with a wrong Hash Code: 9.Windows Server 2003 R2, Enterprise Edition - VL (Simplified Chinese) *DVD.21 ...... Windows Server 2003 R2, Enterprise Edition - Disc 2 - VL (Simplified Chinese) Date/Time Posted: File: sc_win_srv_2003_r2_enterprise_vl_cd2.iso ISO-9660 CD Image File Size: SHA-1 Hash: 5036C3C571850E33B5889D3F5D916F5FE547B030 MD5: 528EF28A335FDFD5D5EB016D41C70628 AutoCRC signature for media in BRMECD2FRE_CN.iso <129828864 bytes> is 0xE9211532 AutoCRC indicates the media in BRMECD2FRE_CN.iso is VALID this is the right hash for all channel FPP VOL EVL OEM (see MSDN) 1FA510F94BAFFC31437B14004D9847BAC6F03275 *[CHS-cd2_ALL] BRMECD2FRE_CN.iso BRMECD2FRE_CN so i guess 95BBAB37520F32163E1858E3130AFED58A138C97 BRMEVOL_CN.iso (sc_win_srv_2003_r2_enterprise_vl_cd2.iso ISO-9660 CD Image) is also wrong
both are the same (base-)ISO Code: E4921c14c812ccaa7442c293b96c83d43e57e4f9 *jp_win_srv_withsp1_ia64.iso ARMEIFPP_JA inofficially MSDN-Shipment CD/DVD (no UUIDREF) 07E4352CFCEFD44240CFF4AEDA48DD4D40CC0A00 *ja_windows_server_2003_with_sp1_enterprise_ia64_dvd.iso ARMEIFPP_JA officially MSDN release (with UUIDREF patch) courious: the officially MSDN release for UDF-iso's are patched by M$ (coz cdimage have only a switch for AutoCRC and UUIDREF "-xx" - no standalone UUIDREF switch) cdimage2.52.exe -u1 -xx.\_ARM_UUIDREF.txt ..... - > ERROR: With -u1 and -u2, cannot use -a, -s, or -x (AutoCRC part breaks UDF rules for the last UDF-ISO sector)
MSDN Bug Windows Server 2003 Standard Edition with SP1 (Hungarian) Bug on the MSDN server - the listed SHA is wrong (iso has a big hole with "00" bytes) -> 28 files in i386 defect Code: ;MSDN Name: hu_ws_2003_std_with_sp1.iso ; ;MSDN sha : 761F3ECBB5052B87D8C0C40995AE19DCF1DF56D2 *hu_ws_2003_std_with_sp1.iso ; MSCDCRC: AutoCRC is 0x15689E4A ; MSCDCRC: This file contains an INCORRECT computed CRC value indicating ; that some of the data in the file is corrupt or was not read ; correctly from the file. ; ;MSDN fix : A3F5B8303021097E0AC067D3E82877CE82D3CC77 *hu_ws_2003_std_with_sp1.iso ; MSCDCRC: AutoCRC is 0x15689E4A ; MSCDCRC: This file contains a VALID computed CRC indicating the contents ; of the file are correct. ; A3F5B8303021097E0AC067D3E82877CE82D3CC77 *[HUN] hu_ws_2003_std_with_sp1_FPP_arm.iso
Code: Windows Small Business Server 2003 OPK NRMLOPK_EN CRC32: FFFFFFFF MD5: 398BE63C76FB87505C799108F58198AC SHA-1: 6AE73BC32F3536FB9987DBDF5804E9092268FFCD Windows Server 2003 R2 OPK BRMOPK_EN CRC32: FFFFFFFF MD5: 99D593F5C8576EC1D3BB2DF9A3AA1FF4 SHA-1: D6D930090658820333772A3A5A76AF949D95F3DC Windows Server 2003 Standard 180-days Evaluation NRMSEVL_NL CRC32: FFFFFFFF MD5: 9C71C6FD8E3C78111981BF1EB04BBA68 SHA-1: E4444421394C25C634EF069CEC652F81764AE626
Can somebody share: Windows 2003 SP2+x64 & XP SP3+x64 MUI (Multilanguage User Interface Pack) 5CD/1DVD PACK Thanks.
thx, but this is server 2003 R2 SP2 (CRM...) wich i have already we are behind server 2003 RTM (NRM...) iso's
NRMDFPP_EN Spoiler Code: File: en_windows_server_2003_datacenter.iso CRC-32: ffffffff MD4: 903867a493049ced0c302cebeb9848c4 MD5: 251a09cac98fe376cb065d506d1453c8 SHA-1: efadcddc907ea5885cd4116516a4c0bcf423b4ca
Windows Small Business Server 2003 R2 180-days Evaluation DISC1 : BRMLEVL_EN1 CRC32: FFFFFFFF MD5: D8C13DFFDEFB4500E7AFF02B4165ED5A SHA-1: 6723ED40D46ADCA16B72865C58453F4AFFA2F134 DISC2 : ARMLEVL_EN2 CRC32: FFFFFFFF MD5: 4A9CD1B13D97C6AF7B811B16516BC6AB SHA-1: 58E93EFECA6C443CAF1FF601FBC91C3E82BD6473 DISC3 : ARMLFPP_EN3 DISC4 : ARMLFPP_EN4 DISC5 : Outlook 2003 DISC6 : BRMLEVL_EN6 CRC32: FFFFFFFF MD5: B678E732E310C50A2663020540ADB824 SHA-1: C5E20B93F056A53022C026F5C70C97F43946E240 Premium Technologies DISC1 : BRMLEVL_ENP1 CRC32: FFFFFFFF MD5: 5D490AACC4739C4DAAD49B63761FEBFD SHA-1: 5778DCA3BF0532DC418374015AA57B689ED93FC1 Premium Technologies DISC2 : BRMLEVL_ENP2 CRC32: FFFFFFFF MD5: E20AEA59A11CE6DCE106C4C779E3AE87 SHA-1: 5325D1DB76684C592EB68BBB2C8789F4956073D5
NRMLEVL_EN1 CRC32: FFFFFFFF MD5: E0E754699EF4F2184DEB4DE4E9FABFC6 SHA-1: F17EEFFA1A194861213C2180CC88FA0EEFCBD3FC NRMLEVL_EN2 CRC32: FFFFFFFF MD5: 48E203DBCB50CFC14E7A5A3DECBD0D8B SHA-1: 0B96B264A89D6CDA00BF5E1C0A24F3A5C42DE8B5 NRMLEVL_EN3 CRC32: FFFFFFFF MD5: 26E551B8E1D5678D282A8247D97A7C70 SHA-1: A3A78C804FA72D1A0EE2F2C6F647C1F020AA3DBD
NRMLFPP_CN1 CRC32: FFFFFFFF MD5: 60F4C5A43A6CD592E884700AE3166DB5 SHA-1: 08AD8EE7F12D35BCA259C137B7AED52C12E9A389 NRMLFPP_CN2 CRC32: FFFFFFFF MD5: 46C846AD06D9A90EB9BA47FC47526021 SHA-1: 1092614B0B0AF042CCE4F752A10A5CD6EE0E3BAA NRMLFPP_CN3 CRC32: FFFFFFFF MD5: 629EF194B71E18C0BD8ECB5424181A0F SHA-1: 9AAA1B1948F7C2E568E35C8EBE919ABEBAFF86DD NRMLFPP_CNP CRC32: FFFFFFFF MD5: A74A2F58AF94855037ACCCF35AC919B0 SHA-1: E48418A07EE7B4E4FB2425130F54D6C426C54B0C