I'm not sure what that's supposed to mean. Oz's thread is about INFO for collectors (verified hash's), not DOWNLOADS for collectors. Yes some stuff does get shared privately, some publicly. I don't see a massive contribution from you? and anyway this is an INFORMATION sharing site, not some warez site or torrent site.
I wonder just who's selfish. I have not seen that you make a mirror for the files you have begged here. god damn the twitter / facebook generation (social Network - seems more like antisocial Network)
I think he is just an @rse Anyway, removed nfo, taking it private Can a mod please close this thread, thanks
Has anyone ever found an untouched ZRMSSEL_PT? I have an original ZRMPSEL_PT and a modified ZRMSSEL_PT (created with Nero), so I recreated it and got SHA1 689E5BFEA87B16144C379180AEC9F3F03589B7F1. If nobody has one I'll assume this one is the correct SHA1. Steps taken: Spoiler source file: ed2k://|file|Windows.2000.Server.SP4.PT-PT.by.alex.pdclinks.net.rar|374577486|8944DCC9944F820FFA808C0D39B0EF0D|/ CRC32: B27BC4A9, password: pdclinks.net which contains Microsoft.Windows.2000.SP4.Server.PT-PT.iso (modified ZRMSSEL_PT with Nero) CRC32: CDB3FA05, SHA-1: 3BD77B3328068B787272CF379A8123ED4A1FD00E ISOs used for reconstruction: I have W2SSEL_EN (RTM Server Select) but not W2SSEL_PT, so I used W2SFPP_EN and W2SFPP_PT (RTM Server Retail) for SP4 integration and comparison to ZRMSSEL_EN and ZRMSSEL_PT (SP4 Server Select). STEP 1: integrate SP4 and compare to see what's different W2SFPP_EN + SP4 vs ZRMSSEL_EN: - content mismatch: - BOOTDISK\CDBOOT1/2/3/4.IMG - I386\EULA.TXT - I386\SETUPP.INI - I386\SETUPREG.HIV - SUPPORT\TOOLS\2000RKST.MSI - SUPPORT\TOOLS\DEPLOY.CAB - SUPPORT\TOOLS\SUPPORT.CAB - file/directory missing: - i386\ 59 files (RTM has java, SP4 doesn't, probably all related to that) STEP 2: repeat integration with PT ISO and check what's different W2SFPP_PT + SP4 vs modified ZRMSSEL_PT, with ZRMPSEL_PT files as support: - content mismatch: - BOOTDISK\CDBOOT1.IMG -> too many differences when hex-comparing to ZRMPSEL_PT, so compared files inside, all equal except for a lot of differences in TXTSETUP.SIF as expected - BOOTDISK\CDBOOT2.IMG -> same as ZRMPSEL_PT, except for 2 bytes before label and 2 bytes in 2 label locations - BOOTDISK\CDBOOT3.IMG -> same as ZRMPSEL_PT, except for 3 bytes before label and 2 bytes in 2 label locations - BOOTDISK\CDBOOT4.IMG -> same as ZRMPSEL_PT, except for 2 bytes before label and 2 bytes in 2 label locations - I386\EULA.TXT -> I'm assuming it's correct and not corrupted (EULA is for Server and Adv.Server as expected) - I386\IESUPP.CH_ -> same as ZRMPSEL_PT - I386\IEWEBHLP.CH_ -> same as ZRMPSEL_PT - I386\IIS5_01.CAB -> same as ZRMPSEL_PT, except for 1 byte that was 0x10 instead of 0x14, fixed - I386\NTOSKRNL.EX_ -> same as ZRMPSEL_PT, except for 1 byte that was 0x10 instead of 0x14, fixed - I386\SETUPP.INI -> I'm assuming it's correct (extradata is different between all ISOs, Pid for ZRMPSEL_EN = 51873270, ZRMSSEL_EN = 51876270, ZRMPSEL_PT = 52884270, so 52887270 for ZRMSSEL_PT seems correct) - I386\SETUPREG.HIV -> same as ZRMPSEL_PT - I386\SUPP_ED.CH_ -> same as ZRMPSEL_PT - I386\WEBHELP.CH_ -> same as ZRMPSEL_PT - I386\WMS4.CAB -> same as W2SFPP_PT, except for 1 byte that was 0x4A instead of 0x4E, fixed (doesn't exist in ZRMPSEL_PT) - I386\LANG\JPN\HWXJPN.DL_ -> same as ZRMPSEL_PT, except for 1 byte that was 0xC1 instead of 0xC5, fixed - SUPPORT\TOOLS\2000RKST.MSI -> same as ZRMPSEL_PT - SUPPORT\TOOLS\DEPLOY.CAB -> same as ZRMPSEL_PT - SUPPORT\TOOLS\SUPPORT.CAB -> same as ZRMPSEL_PT - file/directory missing: - i386\ 59 files (RTM has java, SP4 doesn't, probably all related to that) STEP3: check timestamps and bootsectors to recreate ISO ZRMPSEL_EN vs ZRMSSEL_EN: - same timestamp, 6/20/2003,12 (E4) - same boot sector, 8ef2b46c ZRMPSEL_PT: - timestamp 7/14/2003,12 (E4), modified ZRMSSEL_PT was 7/14/2003,13 (04) obviously because of NERO - boot sector 8ef2b46c ZRMSSEL_PT: - CDI_247M.EXE -nt -o -xx -bBOOT.IMG -g-7 -t7/14/2003,12 -l(you know what goes here) Final ZRMSSEL_PT SHA1: 689E5BFEA87B16144C379180AEC9F3F03589B7F1
Does VRMPFPP_PT exist? I have VRMPVOL_PT (08/04/2004,12) and VRMPOEM_PT (08/02/2007,12), the 2nd one was given to me yesterday, I thought the timestamp was weird because it's SP2 and CDs with SP2b have timestamp of 03/02/2006,12. But I can't argue with an original CD VRMPFPP_PT would be useful because I use the XP retail ISOs as "source" for other SVFs.
Yes it exists but don't know the hash nor any download link EDIT - The only files I believe in are : br_winxp_pro_with_sp2.iso pt_winxp_pro_with_sp2.iso (on MSDN). Don't know if they correspond to what you're looking for Nothing else to say
The one in MSDN (pt_winxp_pro_with_sp2.iso) is SP2b, with label VX2PFPP_PT. The one I don't have is SP2 with label VRMPFPP_PT. SP2 ISOs were replaced by SP2b ISOs to include an ActiveX related patch. They were probably on MSDN between August 2004 and August 2006 before being replaced.
Look in the ISO header at the timezone offset byte. SP2C was manufactured in the same timezone as SP3. Not got the details to hand - but india or something like that. SP2b and earlier are US (again I think)
That might be true to en-us ISOs, but pt-pt ISOs all have 0x04 at 0x833D for VRM and VX2 labels. So this new CD has SP2 label and SP2c timestamp. Do you have en-us SP2b and SP2c Pro OEM (or retail/VL) ISOs that you can compare to see the differences between both? Maybe that way I can confirm which version I have.
this might be help Code: sp2a: VRMPFPP_EN 9B1B8098395872B8E8E1012215F8D72AE7C5E030 *[ENU] en_winxp_pro_x86_with_sp2_cd1_FPP_20040804_vrm.iso sp2a: VRMPCCP_EN FCCE27A2B8B1220FDA94AF63B4A898666ADF7875 *[ENU] en_winxp_pro_x86_with_sp2_cd1_CCP_20040804_vrm.iso sp2a: VRMPEVL_EN 06BA65393058EAD4F3B0234BE5CF6A424D438099 *[ENU] en_winxp_pro_x86_with_sp2_cd1_EVL_20040804_vrm.iso sp2a: VRMPVOL_EN 3B1ADF497F24919E4A4F3C14C3B65D55EA997278 *[ENU] en_winxp_pro_x86_with_sp2_cd1_VOL_20040804_vrm.iso sp2a: VRMPOEM_EN 7F85CBB614CFB1E483342A206ECD663468643A2D *[ENU] en_winxp_pro_x86_with_sp2_cd1_OEM_20040804_vrm.iso sp2a: VRMPVOL_PT 2A3B676DF4B7C3572E3878585F913231AC15573E *[PTG] pt_winxp_pro_x86_with_sp2_cd1_VOL_20040804_vrm.iso sp2a: VRMHOEM_PT 952BEEBFCAAED539D4F28D3F848998645055D82B *[PTG] pt_winxp_home_x86_with_sp2_cd_OEM_20040804_vrm.iso sp2b: VX2PFPP_EN 7CD7058DBBFAB108316B20FE4CEF989ABEBF211F *[ENU] en_winxp_pro_x86_with_sp2_cd1_FPP_20060228_vx2.iso sp2b: VX2PCCP_EN 193EF7B525233E7CBCA9BB84DBFDD4986F5C50A1 *[ENU] en_winxp_pro_x86_with_sp2_cd1_CCP_20060228_vx2.iso sp2b: VX2PVCCP_EN 9323C7C6D7010767EFF86953F451CD8722D53041 *[ENU] en_winxp_pro_x86_with_sp2_cd1_CCP_VOL_20060228_vx2.iso sp2b: VX2POEM_EN D2A5F51504592E2F384D1066BE40EC8C215F5DD9 *[ENU] en_winxp_pro_x86_with_sp2_cd1_OEM_20060228_vx2.iso sp2b: VX2PFPP_BR 4DC9B40F054F4D5A4F82FD6E499F6D34CBD9BB10 *[PTB] br_winxp_pro_x86_with_sp2_cd1_FPP_20060302_vx2.iso sp2b: VX2PVOL_BR FB763D5963E7663D467B1C47BE72D70BA63097E0 *[PTB] br_winxp_pro_x86_with_sp2_cd1_VOL_20060302_vx2.iso sp2b: VX2PFPP_PT 47F4A8F7DCCB4362879E7BC956BCAF3974C90007 *[PTG] pt_winxp_pro_x86_with_sp2_cd1_FPP_20060302_vx2.iso sp2b: VX2PVOL_PT D535E303BDE92202A74B4BB8CB2C32B7995C94F2 *[PTG] pt_winxp_pro_x86_with_sp2_cd1_VOL_20060302_vx2.iso sp2c: VRMPOEM_EN 60FD730346C047A9B9C0108D63A71E62A37A1646 *[ENU] en_winxp_pro_x86_with_sp2_cd1_OEM_20070727_vrm.iso .. but SP2c had the same volume label as SP2b sp2a yes, some files inside i386 change, but the most important difference is: sp2.cat change (sp2c has a digital signature from 2007 - check file property)
Thanks for the info, file is now added to my collection. I also recreated all SP2 SVFs to include SHA1 instead of MD5. I'll do the same to the rest of the collection eventually, but it's in the bottom of my to-do list for now
MSDN VRM Combo (some) : BR_WINXP_1130.1.svf CS_WINXP_1169.1.svf DE_WINXP_1021.1.svf EL_WINXP_1366.1.svf EN_WINXP_1012.1.svf ES_WINXP_1085.1.svf FR_WINXP_1078.1.svf HK_WINXP_1125.1.svf HU_WINXP_1262.1.svf IT_WINXP_1119.2.svf KO_WINXP_1095.2.svf NL_WINXP_1132.1.svf NO_WINXP_1165.1.svf PL_WINXP_1264.2.svf PT_WINXP_1363.1.svf RU_WINXP_1170.1.svf SC_WINXP_1124.1.svf SV_WINXP_1134.1.svf TC_WINXP_1127.1.svf upload soon.
can you please make a picture / scan from your W2PCPP_ES Windows 2000 Professional Upgrade CD-ROM (and covers if you have). ? I have a suspect but can't prove it your CD-rip version Code: ;Lable : W2PCCP_ES ;Boot-sector: from beta3 version ;Size : 382482432 Bytes <- the valid size (dumped size) ;Master date: 19991216 TZ: 0x00 (GMT) ;MSCDCRC : AutoCRC is 0x7C2ED7A8 -> This file contains a VALID computed CRC indicating the contents of the file are correct. ffc721374c36bd07aabf1808307a2b66165ef48e *W2PCCP_ES.iso my M$ RTM master version: Code: ;Lable : W2PCCP_ES ;Boot-sector: RTM version ;Size : 382482432 Bytes ;Master date: 19991217 TZ: 0xE0 (GMT-08:00h) ;MSCDCRC : AutoCRC is 0x7C2ED7A8 -> This file contains a VALID computed CRC indicating the contents of the file are correct. B76AFA5C10EA94E6B0C8188E856900BF43297BE6 *[ESN] es_w2k_W2P_CCP_19991217.iso NOTE: both ISO have the same AutoCRC ! this is because the AutoCRC are split in 2 part - 1. AutoCRC generated from beginn - end of ISO header -> FFFF - 2. AutoCRC generated from beginn of Data Block - FFFF to END of iso MSCDCRC reports 2. AutoCRC this indicate only that the DATA-Block of the iso is the same but not the ISO HEADER -> thats why both iso have different SHA1 -> different File Date's -> different Boot-code (sector) -> but binary the same File contend