Jump to content
Posted 27 April 2009 - 23:12
Posted 27 April 2009 - 23:50
ahh well that just sucks !
some people just live to be assclowns
Windows 7 RC 1 Build 7100 Compiled
The build is correct. The rumor is incorrect. The RC build 7100 was leaked and it is the real thing. Here are the CRC32 and SHA1 for the authentic ISO images.
7100.0.090421-1700_x86fre_client_en-us_Retail_Ultimate-GRC1CULFRER_EN_DVD.iso Size: 2.35GB MD5: 8867C13330F56A93944BCD46DCD73590 SHA-1: 7D1F486CA569EFFFFB719CFB48355BB7BF499712 CRC32: E8A1C394
7100.0.090421-1700_x64fre_client_en-us_Retail_Ultimate-GRC1CULXFRER_EN_DVD.iso Size: 3.04GB MD5: 98341af35655137966e382c4feaa282d SHA-1: fc867fe1ab2e0a9796f9e4d155b44ea6998f4874 CRC32: 58fb2be0
Posted 27 April 2009 - 23:59
Unfortunately that's true.
Below the specs of the original isos: if the check sums match those of your isos you've got the real stuff - unaltered.
PS: You cannot upgrade from any WIN7 Beta release to the RC1 (unless you manipulate some registry keys) and there is a good reason to that. Some new features are not compatible with the beta releases.
Posted 28 April 2009 - 00:05
Posted 28 April 2009 - 00:23
Posted 28 April 2009 - 00:25
How can we check our MD5 hash keys?
This thread has me worried now and im sure there might be a few more people who are going to ask how to check as well...
Posted 28 April 2009 - 00:26
Posted 28 April 2009 - 00:32
Posted 28 April 2009 - 00:35
Posted 28 April 2009 - 00:42
Posted 28 April 2009 - 00:44
it's only a few days away, might as well just wait to get it from the real source...
Posted 28 April 2009 - 00:47
Yup my x64 iso checks out according to those hashes. Thanks Lord Ba'al
Hashes for the clean, untouched x64 iso:
size: 3,270,828,032 bytes
Hashes can be easy calculated using the HashTab Explorer plugin. It works fine in any build, including 7100
It even gives you a convenient option to compare hashes.
Posted 28 April 2009 - 01:44
Odd.... 7100 must not be the RC according to this logic since I upgraded from 7000 to 7100 just fine and all my hashes match the that of the ones for the original iso.
Stuff like this tarnishes torrents' reputation of efficiently distributing large disc images. Obvious solution is to get the torrent header file from a trusted source (for instance, Canonical's servers if you were to get a copy of Ubuntu), but that won't hold with large corporations like MS.
I did run across this same problem in an earlier leaked build. Lesson learned: check to make sure setup.exe has a digital signature intact before burning or copying to a USB drive.