 |
|
| Desktop and Start Menu | |
| Status | Leaked |
|---|---|
| Kernel version | 5.2 |
| CPU architecture | x86 |
| Edition | Home Edition, Professional |
| Compile date | 19 August 2004 |
| BIOS date | 19 August 2004 |
| Timebomb | 360 days |
| Product key | CKY24-Q8QRH-X3KMR-C6BCY-T847Y |
| BA Database | Home Professional Professional alt |
| BetaWiki | Available |
| TCB | Available |
Windows "Longhorn" build 3790 (with a build tag of 3790.1232.winmain.040819-1629), is the first "Longhorn" build compiled after the development reset. There is no evidence that this is a "Longhorn" build except for references in the End-User License Agreement. It was described by Grabberslasher on his UX.Unleaked blog on 2 May 2008,[1] and leaked on 14 August 2011.
Issues
- Zero-day activation - The build must be activated before logon.[1]
- Missing files - During setup it will ask to locate some missing files. The default location is the CD drive, but they are in the i386 folder of the CD. Skipping those files will result in the loss of theme files and applications like Windows Movie Maker, Internet Explorer, and Outlook Express.
Name
According to BetaArchive user hounsell:
It's a common mistake to assume that 3790.1232 is a Longhorn build - it is not. It's a Server 2003 build. There is nothing Longhorn in it (an EULA doesn't count).
Build 5000.0 would be the first Longhorn build.
— hounsell, Re: Build 3790, [2]
xXxWindows8_FANxXx wrote:
i love you hounsell from the deepest depths but i disagree ... its the starting point of the newest longhorn builds , so this is longhorn . whether or not you call it that is up to you ... but this is longhorn.
Believe what you want. Doesn't change the facts. What you are saying is that if a model of car is built in one factory, then moves to another, that it represents a different car, even though they are exactly the same. 5000 was the first build to have changes, and there were literally loads of recompiles of that and of 5001. There is only one 5.2.3790.1232.winmain.040819-162, and that's because it's just a test run, as XDude and Vista custo says. How many people with a far greater understanding of it have to say it before you think there might be merit to the most logical conclusion?
— hounsell, Re: Build 3790, [3]
On the BetaArchive FTP, the build is labeled "MS Windows Server 2003 (.NET Server 5.2.3790.1232) Pro".[4]
Leak
The build was leaked at BetaArchive on 14 August 2011, by an anonymous source along with this bit of information:
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.
— mrpijey, quoting the "anonymous source that has provided this build", MS Windows Server 2003 (.NET Server 5.2.3790.1232) Pro, [4]
BetaArchive user t764010 replied to mrpijey's post quoted above with the NFO below:[5]
((((((((((() | | | 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. |
|_____________________________________________________________|
\___________________________________________________________/
Gallery
More screenshots are available here.
GUI setup
Boot screen
Winver and EULA
References
- ↑ 1.0 1.1 Grabberslasher (2 May 2008). 5.2.3790.1232.winmain.040819-1629. Si vis pacem, para bellum. Retrieved on 18 April 2022.
- ↑ hounsell (6 August 2011). Re: Build 3790. BetaArchive. Retrieved on 18 April 2022.
- ↑ hounsell (7 August 2011). Re: Build 3790. BetaArchive. Retrieved on 18 April 2022.
- ↑ 4.0 4.1 mrpijey (14 August 2011). MS Windows Server 2003 (".NET Server" 5.2.3790.1232) Pro. BetaArchive. Retrieved on 18 April 2022.
- ↑ t764010 (14 August 2011). Re: MS Windows Server 2003 (.NET Server 5.2.3790.1232) Pro. BetaArchive. Retrieved on 18 April 2022.
