Details for this torrent 


Windows.Vista.Iso.BillGates.To.Legit.MSDN.PATCH
Type:
Applications > Windows
Files:
2
Size:
602.43 KB

Quality:
+0 / -0 (0)

Uploaded:
Nov 13, 2006
By:
-=robotnick=-



If you dowload Vista x86 "BillGates" release
(md5 = c7792c31aeea98be645ab295d35e8eef, size - 2 678 614 016),

It is possible to transform this release into legit MSDN release
(md5 = d1ff9802d93871c9b90fe5542e84f89e, size - the same).

Start ppf-o-matic3, choose the ISO from BillGates, and a patch bg-msdn.ppf to apply,
and at you a proper image from MSDN.
For check the resulted md5 control sums are applied of an image before patch, and after,
and finaly a md5 of MSDN image contents.

Enjoy.

Comments

sure would be nice if ya seeded it
what is the meaning of MSDN?
F@TMAN MSDN=microsoft developing network
more specifically, what is the difference between MSDN and the RTM releases already on the net? Activation etc?
glad to see that im not the only one confused... does anyone know exactly what this prog does?? I downloaded it and it doesn't like my iso
it's about "true" and "proper", if you dont want use a _ostensibly_ messed up "BillGates" .iso

but rtm activation (not rc2 like) still an actual issue.
"BillGates" iso has a little difference from original MS iso. this patch fix it.
Ok this patch fixes difference in BillGates ISO so
it matches MSDN ISO. But does this help with the
ACTIVATION?!
Patch to MSDN Iso? Vista isn't on MSDN yet.
What exactly is changed with this patch?
"What exactly is changed with this patch?"

Installation with BillGates version didn't work, and with this it does.

Dunno if there's something else...
I don't think installation is an issue, most newbs have simply tried to install w/o formatting their hdd. Many ppl claim successful install using billgates with rc1 patch. Still not sold as to why MSDN is better than RTM?
"BillGates" .iso has been changed In comparison with original "Microsoft RTM Retail" .iso, for reason, i think, for that their registration number would work.
"BillGates" .iso has "Checksum did not match" error In following files:
*sources\install.wim (!!!)
*sources\migcore.dll
*support\migwiz\migcore.dll
This patch does these files Genuine.
Afterall, "BillGates" .iso gave only 3 days for activation, proper Microsoft Retail .iso without any serials gives 30 days trial.
Thats enough for a first time. =)
the reason some users have only 3 days to activate is if they enter an INCORRECT cd-key, not anything to do with the ISO image as far as I'm aware
How the hell could you possibly go thru installation with an incorrect cd-key??? I could not install with the BillGates version. After 30% of files copied I got a message saying the rest of the files are corrupt. after applying this corrective patch everything went a-ok. Thanx robotnick, you`re a real life-saver.
skofritt, I believe you'll find you don't have to use a cd-key at all and the installation will still continue (windows has an in-built key for testing purposes), it will simply mean that you will need to enter one within the 30 day period. If vista thinks the cd-key you do enter is incorrect, it will only allow you 3 days to activate, otherwise restricting the user to limited access....
I installed the original BillGates version on VMware and the installation worked fine, so what is the reason for this -=robotnick=-?
Is this "http://thepiratebay.ee/tor/3556232/MSDN_Vista_RTM.iso" the proper torrent to download vs the BillGates one? If the BillGates really was changed from the original MSDN ISO then why isn't this one on nforce?
skowfritt: it is not necessary to thank me. AlexBX - here the present hero who has made this patch! Many thanks AlexBX, Suzuki, xxxalien, Samlab, SHV.
If what you are saying is true, then indeed we owe you many thanks. I'm just curious as to how you guys did this when the image is not on MSDN yet. How did you know which files were changed and how to change them to what they should be?
Robotnick

is this file usable within AIO 32 and 64 its (4.42 GB) file???
smoke420: If the image is not accessible to DL with MSDN it doesn't mean that does not exist at all (in any case, i think, that a MS Partnership provides different levels of access). Guys have taken original Microsoft image and a "BillGates" image and have compared, then a difference have been released like a patch. Probably, after 17th on MSDN will be other image which is distinct from 02.10.06 (if MS will want, rebuild will not borrow a lot of time).

tugunska2: of course not. it's for "BillGates" release only.
02.11.06 of course.
But you still need a valid key if you want to use it for more than three days. You can use the Patch to make it run but it would still be an invalid key for all the online verifications available. Like Windows Update, ultimate extras and so on.
Thank you for your explanation -=robotnick=-. Could you please let us know about "http://thepiratebay.ee/tor/3556232/MSDN_Vista_RTM.iso" Does this file have the same MD5 as BillGates after using your patch (d1ff9802d93871c9b90fe5542e84f89e) ???
The patch screwd up my iso. It freezes during the end of the installation. The 'pure' Gates works allright, though - with the key provided and (later) with my msdn-key for activation.
Can anyone else confirm this?
Well, the only key I have is the RC2 one. Burning this stuff onto a DVD is not an option for me as I do not have a DVD-RW drive. Daemon tools has not worked with the most recent RC isos So I extract everything from the iso with POWERiso, put the contents in a folder and copy the whole kittenkaboodle over to my external firewire drive and run setup.exe from there. Always works eacept with this glitch with the BillGates iso. After applying this patch the glitch was gone. Right now my machine is running vista home basic. I`ve used the small app called "windows vista activation reset" which runs SLReArmWindows after every boot and thereby hangs the tale with me. Yes, my activation time is only 3 days.
That activation reset crap did not work. Neither did the ReeBSaW thing. It screwed up the whole activation process and welcome center screen.
The ReeBSaW thing worked for me. I now have a fully functional "evaluation" version with build 6000. I don't know if it expires after 30 days but when that happens I will probaly have a valid key.
iSEPIC`s activation instructions WILL activate vista.
My screen now says "Windows is activated" and off to the left is that blessed MICROSOFT GENUINE SOFTWARE logo.
Where can we find iSEPIC instructions?
skowfritt: whos a hell talks about activation?! it's an .iso image patch. thats it.

denlion: ReeBSaW crack replaces original files with the old from RC1 (pkeyconfig.xrm-ms; tokens.dat) to it the key from RC1 also works, but it does impossible reception of next RTM updates (windowsupdate will think youre still on the RC1(2) build). it's a crap.\
IMHO Most useble behavior for a present moment - 30 days trial + Rearm 2-3 times and patience =)) (for take a 30 days trial win must be installed without any crapy keys)
OK, so this is the best method to use if you want to use RC2 files. What about the method of changing your BIOS to year 2099 before install? Can anyone confirm this working?
robotnick, you`re an idiot. activation is accomplished. you wanna split hairs over this thread pertaining specifically to the patch???
besides, if you`re such a bright boy, how come you didn`t come up with the activation formula before iSEPIC? silly me. I keep forgetting. activation`s not important...especially in this thread.
robotnick

thanks for the answer!
I'll try both systems!!
its your time to waste.
i have the BillGates thing , when i try to install it has error on 48% ... i download this patch but he is giving me error too ... it says that cant open iso file .... what to do ?
thankssssssss
"If you dowload Vista x86 "BillGates" release
(md5 = c7792c31aeea98be645ab295d35e8eef, size - 2 678 614 016),

It is possible to transform this release into legit MSDN release
(md5 = d1ff9802d93871c9b90fe5542e84f89e, size - the same).

Start ppf-o-matic3, choose the ISO from BillGates, and a patch bg-msdn.ppf to apply,
and at you a proper image from MSDN.
For check the resulted md5 control sums are applied of an image before patch, and after,
and finaly a md5 of MSDN image contents.

Enjoy."

Do you proofread your writing before you submit? This is horrible English. FFS, either proofread what you write before you submit, or relearn English!
Need seeders, please.