I just tried it from a VM and got nowhere but that might be me doing something wrong. The MD5-SHA hashes are important in verifying that the content of the ISO hasn't been interfered with in any way so until someone can grab an ISO using this method, it would have to be flagged as unsafe. The recent Linux Mint hack should reinforce that view.
I know that my "fully incorporated" ISO also cannot be verified but I did say it was for regulars only and hopefully, I do hold some trust among long time board members. However, I should have qualified my original offer with this warning and also offered the original untouched and verifiable ISO's.
Out of interest, if anyone needs to check Win7 SP1 ISO's, the following hashes are correct:
Windows 7 Home Premium 32Bit
SHA1 Hash value: 6071B4553FCF0EA53D589A846B5AE76743DD68FC
Windows 7 Home Premium 64Bit
SHA1 Hash value: 6C9058389C1E2E5122B7C933275F963EDF1C07B9
Windows 7 Professional 32Bit
SHA1 Hash value: D89937DF3A9BC2EC1A1486195FD308CD3DADE928
Windows 7 Professional 64Bit
SHA1 Hash value: 0BCFC54019EA175B1EE51F6D2B207A3D14DD2B58
Windows 7 Ultimate 32Bit
SHA1 Hash value: 65FCE0F445D9BF7E78E43F17E441E08C63722657
Windows 7 Ultimate 64Bit
SHA1 Hash value: 36AE90DEFBAD9D9539E649B193AE573B77A71C83
How to compute the MD5 or SHA-1 cryptographic hash values for a file.