I have a Windows 2000 Professional RTM ISO with the following info: Size: 378.122.240 bytes SHA1: a64fc69b95e760e880534049a56bcc1455cb7fd6 CRC: 32b038b5 The ISO seems untouched, but shouldn't its CRC be FFFFFFFF? All files/folders have the same date/time, it was created with cdimage 2.27, it has AutoCRC at 0xA17F0 and at the end. I copied the data up to 0xA17FF to a new file and it has CRC FFFFFFFF, so the header is ok. I assume the problem must be a corrupt byte somewhere, but i don't have anything to compare it to. If someone has this ISO with the correct CRC, could you spare a few minutes to create a PAR file with a few recovery blocks? I'm sure that will fix it.
Thank you MaJo24! The damaged file inside the ISO was \SUPPORT\TOOLS\2000RKST.MSI, it had 89 bytes with different values. It is now fixed with the correct MD5, SHA1 and CRC
Hello! I'm not new to mydigitallife.net but now I decided to register and post here. I found that someone here have original Windows 2000 Pro RTM ISO file with SHA-1 checksum of d183812d681126789358bf3cccec98194b22f67c Can You please send it to me? I can give You FTP access to my computer if you need one. In exchange I can give you the original scene release of Windows.XP.Pro.Corporate.Final-DEVILS0WN back from year 2001 still in the .rar files!
Do you have any version at all? If you do, maybe PAR files from Majo24 can "fix" it. By the way, Windows.XP.Pro.Corporate.Final-DEVILS0W = SHA-1 A86FC914B3D487BD975E3A046CC3BAA2DEA17330? If so, already got it
@ Also as regards to Windows.XP.Pro.Corporate.Final-DEVILS0W on this forum it is classed as warez so links e.c.t.would not be allowed to be posted.
johnye_pt - I have Win2000 SP4 ISO image, but I doubt that it will help. urie - Yes, the DevilSl0w version really is the RTM volume licence that was posted on MSDN. The amazing thing is that it came out really early. I was searching very hard and long to get the "real" release, it is a piece of memorabilia for me. I will not post links here if it can hurt this forum.
You can find an ISO of Windows 2000 Professional if you really try. I don't want to desrespect the forum rules by posting unwanted links, so go to that page that as a pirate boat in the first page, find the link that ends in 3877368 and apply the PAR file to that ISO. That's all the help I can give you...
Thank You that's a very clear advice, will tell if this gives me the proper checksum for the ISO file. edit: I was able to apply the .PAR2 file to that ISO and I got the correct checksum! Also I compared it to W2K_PIS and later seems to be prerelease version or something, it have different EULA and floppy boot images.
Thank you, but I've already downloaded it, and the hashes are 0bd520fc45defb09568a8653aef27164 52665c3eb9c328f5a612c23670bd4abd5390a0d4 ABF9FD33 (MD5/SHA1/CRC) the size is 379,987,968 so as far as I understand, it is not the W2PFPP_EN, or it is, but was modified in some way(known hashes are aa2ee0404c5cb73b109481eca33b452c d183812d681126789358bf3cccec98194b22f67c FFFFFFFF), can't tell before I'll have the original what was altered. That's why I'm looking for the PAR that was posted here, or another PAR that will 'fix' ISO from winworldpc.com, or the delta that will roll ZRMPSEL_EN(f10b2a04acf4e928d6fd312f5831a7fa 58b6225943f9c81ac99d503d50abd48aa7af81c1 FFFFFFFF) back to W2PFPP_EN...
I'm guessing the same as those who collect stamps, lighters, keychains, pens, coins, etc... In my case I'm only interested in ISOs of Windows 2000 PT-PT or older. Since Microsoft removed them from MSDN after the Java settlement, I don't even have SHA1 hashes to pursue, so my only option is finding original CDs EDIT: typos...
Well, stamps (and others) can have some economic value in a future Surely old abandonware is worth absolutely nothing (and never will be)
You're absolutely right, abandonware will never have economic value, but for a company that has some valuable system that runs in a very old environment it can make the difference between having to develop/buy a replacement now, or sometime in the future. Same thing is about having old hardware which can do the work you need, so instead of buying a new machine which will have lots of redundant resources you can utilize the old one. In my case there is another option: I have a tiny win application that provides some services, I don't wanna have a monster that all that it has to do is to run it, more than that, I want it to run in virtual environment and to take as little HD space and catch as little resources as possible.