MS Windows Server 2003 (''.NET Server'' 5.2.3790.1232) Pro

[mrpijey]

Full filename: Microsoft Windows Server 2003 (''.NET Server'' 5.2.3790.1232) (Professional beta).rar

I am adding a little bit of extra information here on the request by the anonymous source that has provided this build to us.

Build: Windows Server 2003 ".NET Server" (5.2.3790.1232 Professional Beta)

Compiled: 19th August 2004

This build is a pain in the neck. It should really be called 'Windows Server 2003 "We have no clue what this thing is called because Microsoft are lazy people and don't give proper names to a lot of their project reset builds" (5.2.3790.1232) (Professional Beta)'. This 3790.1232 can be considered a Windows Server 2003 Post-RTM but this particular build was built by the Winmain lab, odd for a server build. What really happened was the Winmain lab taking .NET Server 5.2.3790.1232 when Microsoft were resetting the Longhorn project and decided to toy around with it. You could call this pre-Longhorn Omega-13 if you really wanted, but there isn't really a name for this build, except for "Windows Pain in the neck". While the Longhorn EULA is in there, it isn't necessarily a Longhorn build. It was merely a test build for Microsoft to play with before they moved to Longhorn post-reset pre-beta.

Let's put this on a timeline to make it understandable.

• Build 4094 declared a mess, Microsoft decide to reset the project
• While Microsoft decide to reset the project, it just so happens 5.2.3790.1232 happens to be the latest code
• Microsoft take it and tell the Winmain lab to compile it for the sole reason of playing with it
• Microsoft decide to use this as base and move on to begin Longhorn development

I bet you did not understand a word of that whatsoever. Basically, this build is what Longhorn is based on, but it is not strictly Longhorn. It's basically a Server 2003 RTM with SP1 Release Candidate slipstreamed and given a Professional client SKU. This means all the server goodies were removed.

I've had a thorough discussion with the source and I agree on these points. We can name it any way we want, but given the date and state of this build we've chose to name it according to its present status at the time of compile. I've labeled the filename according to the names provided by Daniel in this post.

If anyone has any opinions, this is the thread to voice them in. Any other threads relating directly to this build will either be merged into this one or deleted.

[t764010]

This build will appear on the FTP shortly. Its already uploaded privately and is being packed. Also known as a Server 2003 build.

NFO:

Code: Select all

        ((((((((((()       |        |    |  MiCROSOFT WiNDOWS
       /  _____   /|       |        |    |  CODENAME "Longhorn" 
      /  /____/  /-|       |        |    |  BUiLD 3790.winmain.040819-1629
     /          /--|       |        |    |  POST-RESET
    /          /---|       |        |----|  RELEASE BY "KiTTY"
   /__________/----|       |        |    |
       |-----------|       |        |    |
       |-----------|       |        |    |
       '-----------'        ------  
 ////////////////////////////////////////////////////////////////
 ===============================================================
 | RELEASE iNFO ...                                            |
 | ---                                                         |
 | An old build of Windows Longhorn, this was the very first   |
 | build to be compiled after the reset. It's the very same    |
 | build that Grabberslasher documented at his great           |
 | uxUnleaked blog. Similar to Windows Server 2003.            |
 |_____________________________________________________________|
 | PROTECTION ...                                              |
 | ---                                                         |
 | 1) Zero-Day Activation                                      |
 | 2) Timebomb                                                 |
 |_____________________________________________________________|
 | iNSTRUCTIONS ...                                            |
 | ---                                                         |
 | 1) Change BIOS date to 08/19/04.                            |
 | 2) Use the following product key:                           |
 |        CKY24-Q8QRH-X3KMR-C6BCY-T847Y                        |
 | 3) Boot into Safe Mode WITHOUT Networking.                  |
 | 4) Use included AntiWAT to crack activation.                |
 | 5) Give hoarders hell for keeping this unleaked             |
 |    for so long.                                             |
 |_____________________________________________________________|
 | MESSAGE FROM KiTTY                                          |
 | ---                                                         |
 | This release in honor of all those who have had to deal     |
 | with the elitist jerks who keep their old as hell boring    |
 | builds to themselves for little to no reason. I understand  |
 | not wanting to share new builds.. that, of course, is risky.|
 | But this is an old build that nobody, especially not MSFT,  |
 | will care about. Those who have had this and other similar  |
 | builds, get ready... this is just the beginning. There are  |
 | more leaks on the way.                                      |
 |_____________________________________________________________|
 | Want to donate a build? You know where to find us.          |
 |_____________________________________________________________|
  \___________________________________________________________/

For information on this build check out uxUnleaked here. http://uxunleaked.blogspot.com/2008/05/ ... -1629.html
Enjoy yourselves when the FTP admin finishes processing it, and remember to thank KiTTY for a fine first release. Keep an eye out.
EDIT: It's now on the FTP.

[TheCollector1988]

thanks to KiTTY, it is now on the FTP.

[Windows 8 Beta Fan]

OMG this is a Great Moment in LH History!

[Patrick]

Thank you for sharing this piece of history with us.

[fzajac]

Nice one

[soulman]

It was not KiTTY who leaked this. This was an anonymous leak according to mrpijey.

[mrpijey]

It's useless to speculate who leaked this build, so do not attempt to guess or credit anyone for this leak other than to the anonymous leaker. Only I knows who the leaker is, and this will remain a secret. Keep your speculations to yourselves.

Be happy it got leaked instead.

[Derf]

Figured this would leak sooner or later, enjoy everyone and thanks to KiTTY / anonymous source / whomever.

[Barabba]

maybe its better to say that this was base for Vista and not Longhorn
(no confusion then even if 5048/60 were called Longhorn)

MESSAGE FROM KiTTY
...
get ready... this is just the beginning. There are more leaks on the way.

this is nice to see

[XDude]

Figured this would leak sooner or later, enjoy everyone and thanks to KiTTY / anonymous source / whomever.

Indeed this is very close to the borders of the public domain. It's sooner or later.

[Spider-Vice]

I actually expected this. Also it wasn't KiTTY, was an anonymous person as mrpijey said. Nice to see the leak though.

[mrpijey]

maybe its better to say that this was base for Vista and not Longhorn

Vista kept the codename "Longhorn" throughout its development, prior and after its gritty reboot. So this was the base for the post-reboot Longhorn, which became Vista.

[soulman]

From what I understand of the leaker's readme/nfo, this was used for MS to test the new build process and play with 3790 for use as a longhorn base.

[ASV93]

I actually expected this...

Me too but i didn't know that was a Server build...
I hope the leaker release more LH builds

[Derf]

I actually expected this...

Me too but i didn't know that was a Server build...
I hope the leaker release more LH builds

It's not strictly speaking a server build - it's a client compile of Server 2003's code.

[hounsell]

This build will appear on the FTP shortly. Its already uploaded privately and is being packed. Also known as a Server 2003 build.
~snip~
For information on this build check out uxUnleaked here. http://uxunleaked.blogspot.com/2008/05/ ... -1629.html
Enjoy yourselves when the FTP admin finishes processing it, and remember to thank KiTTY for a fine first release. Keep an eye out.
EDIT: It's now on the FTP.

It's funny because this post is complete crap. It's MSBP all over again

Don't expect any more leaks in the near future. It's not going to happen. This was a one-hit wonder.

[mrpijey]

Don't expect any more leaks in the near future. It's not going to happen. This was a one-hit wonder.

You hardly control the amount of leaks on this or any other site, so you can't say this. Who decides to leak to this site and when is not up to you.

[hounsell]

Don't expect any more leaks in the near future. It's not going to happen. This was a one-hit wonder.

You hardly control the amount of leaks on this or any other site, so you can't say this. Who decides to leak to this site and when is not up to you.

No, but I'm not oblivious to what's going on. I'm fully aware that this particular source has nothing left to offer, and that "KiTTY"'s promises of further leaks are empty promises that can't be fulfilled, so there's little point in people getting their hopes up.

[Derf]

Don't expect any more leaks in the near future. It's not going to happen. This was a one-hit wonder.

You hardly control the amount of leaks on this or any other site, so you can't say this. Who decides to leak to this site and when is not up to you.

No, but I'm not oblivious to what's going on. I'm fully aware that this particular source has nothing left to offer, and that "KiTTY"'s promises of further leaks are empty promises that can't be fulfilled, so there's little point in people getting their hopes up.

There are plenty of other people with plenty of other builds. All that's required is for another little kiddie with a build to decide that he needs a little ego boost and leak another one.

[mrpijey]

Well, we will see what happens in the future. I for one am glad these builds surfaces and don't get forgotten and lost in some digital cellar.

[hounsell]

Don't expect any more leaks in the near future. It's not going to happen. This was a one-hit wonder.

You hardly control the amount of leaks on this or any other site, so you can't say this. Who decides to leak to this site and when is not up to you.

No, but I'm not oblivious to what's going on. I'm fully aware that this particular source has nothing left to offer, and that "KiTTY"'s promises of further leaks are empty promises that can't be fulfilled, so there's little point in people getting their hopes up.

There are plenty of other people with plenty of other builds. All that's required is for another little kiddie with a build to decide that he needs a little ego boost and leak another one.

except with all the leaks we've had lately, we've not got half as many kids with builds. and Kitty certainly isn't one of them, so any promises they make about leaks should be treated as lies.

[RichardG867]

About time this leaked.

[soulman]

Anyway, thanks to the person who really leaked this! A good addition to the collection and to the history of Longhorn

[Nightsteed]

Thanks to whomever that leaked this. This is just a piece of history