Yes, I know. But when I installed Chicago, I think, #117 it said something along the lines of "You need to be an authorized MS beta tester to use this software, please verify blah blah..." That's where this comes in handy.
There is another way to get around this protection: you have to boot your computer from a special bootdisk, which contains pre-installed Chicago system. Setup won't ask you for beta numbers!
There is another way to get around this protection: you have to boot your computer from a special bootdisk, which contains pre-installed Chicago system. Setup won't ask you for beta numbers!
can you provide sich a disc?
_________________ "Theory is when you know something, but it doesn't work. Practice is when something works, but you don't know why. Programmers combine theory and practice: Nothing works and they don't know why."
This is floppy image supplied with Windows Chicago build 73G.
From Release's NFO
Quote:
(...) This fix of 73g does'nt ask for a beta sight ID number or Password number if used with the boot-disk supplied. If you install it as an upgrade on Win3x and need a number it is as such (...)
When I used this floppy, Chicago hadn't asked for beta IDs. But it is possible, that there are some modifications in Windows Chicago itself, for example in installer's INI files.
_________________ "Theory is when you know something, but it doesn't work. Practice is when something works, but you don't know why. Programmers combine theory and practice: Nothing works and they don't know why."
4033 leaked from osba used TCP8W, the c0d3rz leak used the CKY24 key
... where is the difference between this 2 builds?
From memory one of them had a different setupp.ini & pidgen.dll, not the original one. Which of the 2 I cannot remember at the moment, but I do remember wondering that myself when either of them leaked & did a quick check myself.
although this was a while, I can tell that the osba leak was the orginal, c0d3erz had modifly the 2 files like winbeta did to 4051 and whoever leaked 4053 had that modification. If anyone evry gets a gold of the MSDN 4051 x86 will know that it takes the TCP8W key not CKY24. But the TCP87W key was not leaked at that time, therefore modifcations are equire to install with an old key.
Quote:
On another tangent... does anybody have a serial for the rare 4074 x64 edition that was given away at some collage campuses...
4074 x64 should take the TCP8W key, if it was MSDN orginal. I believe that the build around around in the old days took the TCP8W key.
Now, does anyone have the ultra-rare 4051 MSDN iso?
Why dont we just provide a list with all the known leake (even if provate) and then you can ask if ynyone has this or that build..
btw. has anyone 4050.
Here is a trick for remembering what to set your date to if your installing whistler find the date of a file on the iso and add a few months to it Yes I know its simple but some people who aren't eXPerienced with betas might know to turn their date back but not know to what Back in the day after they expired when I revisited the old betas thats what I did through trial and error before i knew of OSBA
Here is a trick for remembering what to set your date to if your installing whistler find the date of a file on the iso and add a few months to it Yes I know its simple but some people who aren't eXPerienced with betas might know to turn their date back but not know to what Back in the day after they expired when I revisited the old betas thats what I did through trial and error before i knew of OSBA
Might work on most builds, won't work on 2202 \ 2211...
The NT5.cat appears to run out 3 weeks after it was compiled on these
builds, attempting to install after the 3 week window just errors everytime...
I found the date that the NT5.cat was dated ( after extracting it ) to be
the best time to install the Whistler betas...
Personal experience based on un-modified original ISO's that is...
Here is a trick for remembering what to set your date to if your installing whistler find the date of a file on the iso and add a few months to it Yes I know its simple but some people who aren't eXPerienced with betas might know to turn their date back but not know to what Back in the day after they expired when I revisited the old betas thats what I did through trial and error before i knew of OSBA
Might work on most builds, won't work on 2202 \ 2211... The NT5.cat appears to run out 3 weeks after it was compiled on these builds, attempting to install after the 3 week window just errors everytime...
I found the date that the NT5.cat was dated ( after extracting it ) to be the best time to install the Whistler betas... Personal experience based on un-modified original ISO's that is...
That is a precise way of doing it, very cool thanks
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum
All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.