All sorted now thanks Looking for this last one. label will be: As far as I can find out, SHA1 hash is: There is a W2ASEL_EN, that's the Select version, have that already thanks for any help
If you already have the select edition (W2ASEL_EN with SHA1 of 844f248d371be8bb51039610f0418daf60c1ee47), then you can produce the retail edition with the help of a small diff. 1.) Get xdelta from Code: code. google. com/p/xdelta/downloads/detail?name=xdelta3.0z.x86-32.exe&can=2&q= (remove spaces from link) 2.) Get SEL2FPP.delta from the attached zip file. 3.) Place the ISO image of the select edition mentioned above somewhere you can access it (I assume it is called W2ASEL_EN.iso, but any name will do). 4.) Generate the retail edition by applying the delta (a file called W2AFPP_EN.iso will be generated): Code: xdelta3.0z.x86-32.exe decode -s W2ASEL_EN.iso SEL2FPP.delta That should do it ...
That was almost to easy, many thanks. Never heard of that xdelta. There was another program which did similar things, as in change one ISO into another, but don't recall name. These are the 6 I have now: 73060bab874ab6068016a83daa883fda7fcad3bd *W2AFPP_EN.ISO 844f248d371be8bb51039610f0418daf60c1ee47 *W2ASEL_EN.ISO d183812d681126789358bf3cccec98194b22f67c *W2PFPP_EN.ISO d27ef2d12c64e0c660304499c2cf0ed8130ddd11 *W2PSEL_EN.ISO 0e5986b46e60a94b39efab6e3f3967fcc907e146 *W2SFPP_EN.ISO 84c321dcc18d316d0fbaf813c9a09349d0b27e4d *W2SSEL_EN.ISO However, I have come across this list: en_win2000_advsrv.iso OJAMAJOxI1 425,078,784 73060bab874ab6068016a83daa883fda7fcad3bd en_win2000_advsrv_sel.iso OJAMAJOxI1 425,078,784 844f248d371be8bb51039610f0418daf60c1ee47 en_win2000_pro.iso OJAMAJOxI1 378,122,240 d183812d681126789358bf3cccec98194b22f67c en_win2000_pro_sel.iso OJAMAJOxI1 378,122,240 9ecbe74b1357f3fe131abd86428204539b6b38e5 en_win2000_server.iso OJAMAJOxI1 423,755,776 0e5986b46e60a94b39efab6e3f3967fcc907e146 en_win2000_server_sel.iso OJAMAJOxI1 423,755,776 84c321dcc18d316d0fbaf813c9a09349d0b27e4d It seems my W2PSEL_EN.ISO is a different hash. Do you have the PRO SEL as well, would be interested if you could confirm either checksum. Once again, really appreciate your help in getting this last elusive ISO
xdelta is a generic diff tool, implementing the VCDIFF standard, i.e. it's not limited to ISOs. Pretty useful. The SHA1 of my W2PSEL_EN is the same as yours. I also wondered about the hash mismatch and compared the image to W2PFPP_EN on a binary level. They are almost identical (as expected). The only differences are: image name ExclCRC/AutoCRC values boot disk image names and access stamps setupp.ini The differences are exactly the same that also appear when comparing the other editions (e.g. W2SSEL_EN vs. W2SFPP_EN) The list you mentioned also sometimes names the AutoCRC value of the image, 0x903e4188. That one is identical to that stored in our image and is valid. While it is possible to fake the AutoCRC value, it is quite unlikely that this has happened here. There are actually only 43 bytes that might have been tampered with, and all of them are in rather insignificant places (12 in the access stamps of the boot disk images and 31 in the ExtraData key in setupp.ini). I assume that the hash value in the list is either simply wrong or there were some empty sectors at the end of the image when the hash was calculated.
Thanks MaJo24 I was thinking a bit the same, that there probably was zeros after the true image. Guess we'll call the top list the right one. I have checked Pro SEL against a 200GB torrent with allot of MS images, and it did come up a 100% Yes xdelta is a neat tool, I think the other one I have used for ISO changing was PPF-O-Matic. I have to read up on xdelta, as in how to use it. The access stamp in boot images as you call them, I assume that's the sectors just before the name? Have been wondering what that was. I have been trying to change my 3 2000 SP4 FPP to SEL, but that is the one thing I can't figure out. Other than that it's quite simple to remake SP4 with the right CDIMAGE. Do you know what program MS uses to make their boot floppies? Thanks again for your time.
You're welcome! I never found any seeds for that 200 GB torrent. Could you download from it? Yes, I referred to the four bytes right before the labels. The name "access stamps" was a bit misleading, though. Actually, these are the volume serial numbers. As such, they can be basically arbitrary data. I only noticed that they were in an ascending order, and thus I assumed that a timestamp was used to generate them. I don't see any clear pattern, though, so we'll most likely not be able to reproduce them. I don't know which program Microsoft used to generate the floppy images (if any at all). Do you have reliable checksums for ZRM*SEL_EN images? I've got a ZRMPSEL_EN, but I could never verify it (SHA1 1708c8ad3c33e8ae94a06b977d23929c9ba05681 / MD5 0b19b2a88abddc20425cafe973fdb38e).
I do not know what was used for the floppies, but you can surely create one by hand with HxD All you need is the actual bootrecord: Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 EB 3C 90 4D 53 44 4F 53 35 2E 30 00 02 01 01 00 ë<.MSDOS5.0..... 00000010 02 E0 00 40 0B F0 09 00 12 00 02 00 00 00 00 00 .à.@.ð.......... 00000020 00 00 00 00 00 00 29 81 1E 27 8C 4E 4F 20 4E 41 ......)..'ŒNO NA 00000030 4D 45 20 20 20 20 46 41 54 31 32 20 20 20 33 C0 ME FAT12 3À 00000040 8E D0 BC 00 7C 68 C0 07 1F A0 10 00 F7 26 16 00 ŽÐ¼.|hÀ..*..÷&.. 00000050 03 06 0E 00 50 91 B8 20 00 F7 26 11 00 8B 1E 0B ....P‘¸ .÷&..‹.. 00000060 00 03 C3 48 F7 F3 03 C8 89 0E 08 02 68 00 10 07 ..ÃH÷ó.ȉ...h... 00000070 33 DB 8F 06 13 02 89 1E 15 02 0E E8 90 00 72 57 3Û....‰....è..rW 00000080 33 DB 8B 0E 11 00 8B FB 51 B9 0B 00 BE DC 01 F3 3Û‹...‹ûQ¹..¾Ü.ó 00000090 A6 59 74 05 83 C3 20 E2 ED E3 37 26 8B 57 1A 52 ¦Yt.ƒÃ âíã7&‹W.R 000000A0 B8 01 00 68 00 20 07 33 DB 0E E8 48 00 72 28 5B ¸..h. .3Û.èH.r([ 000000B0 8D 36 0B 00 8D 3E 0B 02 1E 8F 45 02 C7 05 F5 00 .6...>....E.Ç.õ. 000000C0 1E 8F 45 06 C7 45 04 0E 01 8A 16 24 00 EA 03 00 ..E.ÇE...Š.$.ê.. 000000D0 00 20 BE 86 01 EB 03 BE A2 01 E8 09 00 BE C1 01 . ¾†.ë.¾¢.è..¾Á. 000000E0 E8 03 00 FB EB FE AC 0A C0 74 09 B4 0E BB 07 00 è..ûëþ¬.Àt.´.».. 000000F0 CD 10 EB F2 C3 50 4A 4A A0 0D 00 32 E4 F7 E2 03 Í.ëòÃPJJ*..2ä÷â. 00000100 06 08 02 83 D2 00 A3 13 02 89 16 15 02 58 A2 07 ...ƒÒ.£..‰...X¢. 00000110 02 A1 13 02 8B 16 15 02 03 06 1C 00 13 16 1E 00 .¡..‹........... 00000120 F7 36 18 00 FE C2 88 16 06 02 33 D2 F7 36 1A 00 ÷6..þˆ...3Ò÷6.. 00000130 88 16 25 00 A3 04 02 A1 18 00 2A 06 06 02 40 3A ˆ.%.£..¡..*...@: 00000140 06 07 02 76 05 A0 07 02 32 E4 50 B4 02 8B 0E 04 ...v.*..2äP´.‹.. 00000150 02 C0 E5 06 0A 2E 06 02 86 E9 8B 16 24 00 CD 13 .Àå.....†é‹.$.Í. 00000160 0F 83 05 00 83 C4 02 F9 CB 58 28 06 07 02 76 11 .ƒ..ƒÄ.ùËX(...v. 00000170 01 06 13 02 83 16 15 02 00 F7 26 0B 00 03 D8 EB ....ƒ....÷&...Øë 00000180 90 A2 07 02 F8 CB 42 4F 4F 54 3A 20 43 6F 75 6C .¢..øËBOOT: Coul 00000190 64 6E 27 74 20 66 69 6E 64 20 4E 54 4C 44 52 0D dn't find NTLDR. 000001A0 0A 00 42 4F 4F 54 3A 20 49 2F 4F 20 65 72 72 6F ..BOOT: I/O erro 000001B0 72 20 72 65 61 64 69 6E 67 20 64 69 73 6B 0D 0A r reading disk.. 000001C0 00 50 6C 65 61 73 65 20 69 6E 73 65 72 74 20 61 .Please insert a 000001D0 6E 6F 74 68 65 72 20 64 69 73 6B 00 53 45 54 55 nother disk.SETU 000001E0 50 4C 44 52 42 49 4E 00 00 00 00 00 00 00 00 00 PLDRBIN......... 000001F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............Uª and then you copy the extra few files to disk 1: biosinfo.inf ntdetect.com setupldr.bin txtsetup.si_ disk101 sebus
Nope, don't think I ever got a single byte from that torrent, just tested my completed images against it. I don't have any check sums for the SP4 SEL's. I found one image once, but CRC was not even FFF... so deleted it straight away. The 200Gb torrent has this in it, you tried to run yours against, byte sizes are correct. No Advanced though. EN_WIN2000_SRV_SP4_SEL[ZRMSSEL_EN].iso EN_WIN2000_PRO_SP4_SEL[ZRMPSEL_EN].ISO Does your floppy images in your SEL have the correct volume label? If so, do you mind upping them and the setupp.ini, then I'll see if I can recreate your checksum with CDIMAGE. I'm sort of leaning towards MS having a command line program as CDIMAGE to make floppy images. Maybe they have some unknown switches in CDIMAGE.
Heh, had a feeling you be following this thread Sebus Yes I know they can be quite easily created, but the stumbling block is the above mentioned "time stamp"
I just grabbed the faulty ISO again, it's the ZRMPSEL_EN. I compared it to the FPP and there was an error in the top, some data where it was supposed to be blank. Used the boot floppy images and setupp.ini with files from FPP and got: File: ZRMPSEL_EN.ISO CRC-32: ffffffff MD4: 3e1d9f9b6b873eb03fc57fa9e99609ed MD5: 0b19b2a88abddc20425cafe973fdb38e SHA-1: bc5420519edcef165232568de6e697f3271938cb That matches 100% with the 200Gb torrent. Also, if I blank out the errors in the downloaded ISO, I end up with same hash as my homemade one.
Seems like our ZRMPSEL_EN images are identical, then. I can't remember where I got mine, but I compared it to the FPP one and the differences were once again exactly those that one would expect. The floppy image names are correct, only the volume serials differ. I assume this image to be correct. I don't think CDIMAGE has the ability to produce floppy images -- at least there are no indicators (like boot sectors etc.) in the .exe. Now we're just missing the Server and Advanced server images ...
But you mentioned yours was: SHA1 - 1708c8ad3c33e8ae94a06b977d23929c9ba05681 Mine is SHA1 - bc5420519edcef165232568de6e697f3271938cb Yeah I don't know with the floppy capabilities in CDIMAGE, but doubt boot sectors with be a stumbling block since it does not have for CD/DVD images either.
Sorry, my mistake, I posted the wrong SHA1. Here's the output after a second run: Code: AutoCRC signature detected (78cff5be, VALID) MD5 : 0b19b2a88abddc20425cafe973fdb38e SHA1 : bc5420519edcef165232568de6e697f3271938cb Of course you're right about the boot sectors not being a hindrance, though the boot sectors of floppies are much more intertwined with the file system than those of ISO images. By the way: Did you get your ZRMPSEL_EN image from djxmmx? I seem to recall that is where I got mine ...
Google bda44621632c933dad3c0ab88e67848d31cd9928 and you'll see where I got it, RS links. That's the faulty one, I cannibalized/ zeroed error. So yes 2 to go.
Found some original M$ media in my draw Windows 2000 Advanced Server with Service Pack 4 ZRMASEL_EN.iso 432,314,368 bytes CRC32: FFFFFFFF MD5: D5BACDBE1678A149417E1D2E989B83A7 SHA-1: B797DC9BE48D99AEF224399AE80CF7E04DCA225F Windows 2000 Server with Service Pack 4 ZRMSSEL_EN.iso 431,202,304 bytes CRC32: FFFFFFFF MD5: 9DDD017E995E66263109DA9A924AE789 SHA-1: 98C0AB4C18C4E3DAC7F5436B0A28CBA9DE830C8C Windows 2000 Pro with Service Pack 4 ZRMPSEL_EN.iso 386,859,008 bytes CRC32: FFFFFFFF MD5: 0B19B2A88ABDDC20425CAFE973FDB38E SHA-1: BC5420519EDCEF165232568DE6E697F3271938CB sebus
Once again Sebus has the goods. Thanks for confirming the Pro hash. Any chance I could talk you into upping the floppy boot images and the setupp.ini from Advanced Server and Server? Then I can make those 2 myself from my FPP copies.