...
 
Commits (13)
......@@ -3,6 +3,7 @@ image: registry.gitlab.com/pages/hugo:latest
variables:
GIT_SUBMODULE_STRATEGY: recursive
HUGO_ENV: production
before_script:
- apk add --update --no-cache git
......
......@@ -9,8 +9,9 @@ enableRobotsTXT = true
[params]
description = "A look at a defining Microsoft project"
gitlab = "https://gitlab.com/hounsell/longhorn-ms"
gitlab = "https://gitlab.com/experience-longhorn/longhorn-ms"
featured_image = "/images/header-01.jpg"
custom_css = [ "dist/custom.css" ]
[taxonomies]
category = "categories"
......
---
title: "Experience Longhorn"
title: "Microsoft Longhorn"
---
# "Long what?"
......@@ -12,4 +12,4 @@ The goal of the Experience Longhorn project is to comprehensively document the L
In the [Builds](/builds/) section you will find BIOS dates, product keys and installation notes to help you install Longhorn today. Moreover, you will also find fixes and interesting facts about each build. In the [Articles](/articles/) section you can find post ranging from elaborate tutorials to technical description of Longhorn features. For the ones less interested in all technical hodgepodge there is the development category completely focused on how Longhorn was being developed at Microsoft.
Longhorn.ms is currently maintained by Thomas Hounsell. You can submit changes via pull requests on [our GitLab repository](https://gitlab.com/hounsell/longhorn-ms).
Longhorn.ms is currently maintained by Thomas Hounsell. You can submit changes via pull requests on [our GitLab repository](https://gitlab.com/experience-longhorn/longhorn-ms).
......@@ -3,21 +3,22 @@ title: Avalon Display Panel
author: Melcher
type: post
date: 2014-10-25T19:33:31+00:00
url: /avalon-display-panel
url: /avalon-display-panel/
featured_image: display-panel-3683.png
categories:
- Research
- Features
---
Only two builds, build 3683 and build 4093 have a working, accessible Display Properties control panel, out of the box. These two Avalon display panels are extremely different in construction, and it is entirely possible that the two are the result of two entirely different development efforts, baring no connection beyond their function and underlying technology. Later Milestone 3 builds can have the 3683-style enabled through the use of a registry key, as detailed below.
There are two distinct "new" display control panels developed prior to the Longhorn reset. The first appeared in Milestone 3, and was removed in early Milestone 4. The second was present only in [build 4093](/builds/4093/). Though both are created in the Avalon UI framework, it seems almost certain that the two efforts were not connected beyond their functionality and underlying technology.
#### Milestone 3
In build 3683, it is accessible by right-clicking on the desktop and selecting Properties from the right click menu, as one would with any previous version of Windows. The Avalon display panel in 3683 has a number of bugs however. Later builds have even further bugs, caused by a lack of further development to ensure that it kept pace with the rapidly changing framework. The last confirmed build to contain the Milestone 3 Avalon display panel is 4001.
In [build 3683](/builds/3683/), it is accessible out-of-the-box by right-clicking on the desktop and selecting Properties from the right click menu, as one would with any previous version of Windows. The Avalon display panel in 3683 has a number of bugs however. Later builds do not have this new panel enabled out of the box. Once enabled though, they have even further bugs, caused by a lack of further development to ensure that it remained compatible with the rapidly changing Avalon framework. The last confirmed build to contain the Milestone 3 Avalon display panel is [4001](/builds/4001/).
![](display-panel-3683.png)
It was first activated in one of the other Milestone 3 builds as part of the protoPlex Project in early 2008 as depicted in the screenshot below. It was achieved by simply copying in the 3683 desk.cpl, and executing that rather than the version native to that build. This step was then forgotten about and was not investigated further. In 2012, this screenshot was rediscovered, prompting further investigation. This investigation has revealed that it can be enabled in other 3xxx builds by simply using the registry file below:
It was first activated in one of the other Milestone 3 builds as part of the protoPlex Project in early 2008. It was achieved by simply copying in the 3683 desk.cpl, and executing that rather than the version native to that build. This step was then forgotten about and was not investigated further. In 2012, this screenshot was rediscovered, prompting further investigation. This investigation has revealed that it can be enabled in other Milestone 3 builds by simply using the registry file below:
{{< highlight reg >}}
Windows Registry Editor Version 5.00
......@@ -26,7 +27,7 @@ Windows Registry Editor Version 5.00
"ClassicDisplayCPL"=dword:00000000
{{< / highlight >}}
This works because 3683 assumes that if this registry key doesn’t exist, then the user has indicated that they want to use the new display panel. In later builds, this behaviour was changed so that it required the registry key to be present and explicitly set to 0 before displaying the new panel.
This value is checked in all builds with the display panel present. However, there is a difference between the check in 3683 and later builds which explains why it works out of the box in 3683, but requires the value set in later builds. In 3683, the display panel is shown if the `SHRegGetValueW` call fails or the returned value is not 1. In later builds, this has been fixed so that the display panel is only shown if the `SHRegGetValueW` call succeeds or the value returned is 1. Logically, the latter behaviour is correct, so it makes sense to reason that this was a bug fix by Microsoft. With the original check, the `SHRegGetValueW` call could fail for any number of reasons, and not just because the registry key is not present, potentially causing unintended side-effects.
![](display-panel-3718.png)
......
......@@ -3,10 +3,10 @@ title: Diskpart
author: Melcher
type: post
date: 2014-10-25T16:33:28+00:00
url: /diskpart
url: /diskpart/
featured_image: longhorn-setup.png
categories:
- Tutorials
- User Guides
---
Diskpart is a command line tool that'll let you manage disks in Windows. Diskpart comes in more than handy when installing Longhorn since numerous Longhorn WinPEs have trouble formatting disks themselves. On this page you will find a brief description on how to use this tool to partition a disk for installing Longhorn and a little extra.
......
......@@ -3,10 +3,10 @@ title: My TV and Movies
author: Melcher
type: post
date: 2014-10-25T20:17:03+00:00
url: /my-tv-and-movies
url: /my-tv-and-movies/
featured_image: mytv-guide.png
categories:
- Research
- Features
---
The My TV and Movies _library_ becomes visible when using the Media Center Edition (_Freestyle_) variant of some Longhorn builds. The My TV and Movies library is a media application for recording and watching TV. The application is an Avalon container and is opened in Internet Explorer by the Avalon Shell Handler. The container itself includes a couple of dll and BAML files as well as a manifest.
......
......@@ -3,13 +3,13 @@ title: Startpage
author: Melcher
type: post
date: 2014-10-25T15:48:28+00:00
url: /startpage
url: /startpage/
featured_image: startpage-3718.png
categories:
- Research
- Features
---
The Longhorn Startpage is a feature present in Milestone 3 builds. The startpage appears to be an early attempt at replacing the [OOBE (Out-Of-Box Experience)](/oobe) that these builds carry over from Windows XP.
The Longhorn Startpage is a feature present in Milestone 3 builds. The startpage appears to be an early attempt at replacing the [OOBE (Out-Of-Box Experience)](/oobe/) that these builds carry over from Windows XP.
Already in build 3683 we can catch a glimpse of the startpage, be it in a very early stage. The code for the startpage can be found in the assemblies _Microsoft.Windows.Client.dll_ and _ShellInterop.dll_ It's interesting to note that one assembly holds both the CAML and XAML for the startpage (which differ a tiny bit from each other) and the other assembly holds the code back-end of the whole thing. A "PromotionsTile' that is loaded just shows up as a solid black color.
......
......@@ -3,10 +3,10 @@ title: 64-bit Windows
author: Melcher
type: post
date: 2014-10-31T19:47:10+00:00
url: /64-bit-windows
url: /64-bit-windows/
featured_image: amd64.jpg
categories:
- Research
- History
---
If you ever bothered to take a look at one of the 64-bit Longhorn compiles, you may have noticed that these builds are extremely empty and lack, for example, the sidebar. There's a good reason why these compiles lack lots of features the x86 Longhorn compiles did have.
......
......@@ -3,11 +3,11 @@ title: Componentising
author: Melcher
type: post
date: 2014-11-01T14:35:28+00:00
url: /componentising
url: /componentising/
featured_image: targetdesigner.png
categories:
- Development
- Research
- Features
- History
---
At WinHEC 2003 Microsoft revealed that Longhorn would be build from the ground up from a list of components. Already before this time various people at Microsoft had stated that Longhorn would be the first "modular" operating system. But what does this all mean? I'll try my best to get clear what componentising really is.
......
......@@ -3,10 +3,11 @@ title: Activation cracks
author: Melcher
type: post
date: 2014-11-06T19:23:48+00:00
url: /activation-cracks
url: /activation-cracks/
featured_image: null
categories:
- 'Tips & tricks'
- User Guides
- Downloads
---
Run Microsoft's Windows "Longhorn" today using these activation cracks for each build. Simply replace the "winlogon.exe" in your System32 folder with the copies contained in the ZIP below.
......
......@@ -3,10 +3,10 @@ title: .NET framework
author: Melcher
type: post
date: 2014-11-06T20:17:10+00:00
url: /net-framework
url: /net-framework/
featured_image: null
categories:
- Research
- History
---
A significant part of Longhorn is written in managed C#. Taskbar, sidebar, preview pane&#8230; it's all .NET. I thought it would be interesting to know the mechanics behind this framework, so here we go: an article solely about .NET.
......
......@@ -3,13 +3,13 @@ title: Out-of-box experience
author: Melcher
type: post
date: 2014-11-06T13:06:36+00:00
url: /oobe
url: /oobe/
featured_image: 1.png
categories:
- Research
- Features
---
With the new image-based installation introduced in Milestone 4 it was also time for a revamped out-of-box experience (OOBE) wizard. The first build to feature the image-based install and new OOBE wizard is [build 4001](/guide/b4001).
With the new image-based installation introduced in Milestone 4 it was also time for a revamped out-of-box experience (OOBE) wizard. The first build to feature the image-based install and new OOBE wizard is [build 4001](/guide/4001/).
After a brief time loading at the "Please wait&#8230;' page you will find yourself at the _WelcomePage_ where you will be welcomed to the wizard. On the next page, _aacnamepage_, you can add as many users as you like. After doing this, you will find yourself at _FinishPage_. Even though this really is the end of the setup, the text on the page suggests that the setup continous after this page:
......
......@@ -3,13 +3,14 @@ title: 'Aurora & Aero'
author: Melcher
type: post
date: 2015-01-11T10:56:59+00:00
url: /aurora-aero
url: /aurora-aero/
featured_image: aurora-5219.png
categories:
- Tutorials
- Features
- User Guides
---
Aurora is one of the eye-candy features which is best represented in Milestone 7 builds. Using the powerful Avalon presentation engine, Longhorn was able to draw fancy animations, like Aurora, without any significant performance hit on the processor. Aurora in the preview panel was first shown at the PDC 2003 conference when a [private build was showcased](/guide/4050-xx). At first sight many people thought the demo was just a flash mock-up, but Hillel Cooperman was fast to debunk this. The particular demo shows us working WinFS, content-based thumbnails, Aero Glass and an animated aurora effect in the preview panel. Most of these features wouldn't be seen again until the next year at WinHEC 2004. Although the "WinHEC build", 4074, does have a working DWM engine, at first it looked like it didn't have any aurora at all.
Aurora is one of the eye-candy features which is best represented in Milestone 7 builds. Using the powerful Avalon presentation engine, Longhorn was able to draw fancy animations, like Aurora, without any significant performance hit on the processor. Aurora in the preview panel was first shown at the PDC 2003 conference when a [private build was showcased](/guide/4050-xx/). At first sight many people thought the demo was just a flash mock-up, but Hillel Cooperman was fast to debunk this. The particular demo shows us working WinFS, content-based thumbnails, Aero Glass and an animated aurora effect in the preview panel. Most of these features wouldn't be seen again until the next year at WinHEC 2004. Although the "WinHEC build", 4074, does have a working DWM engine, at first it looked like it didn't have any aurora at all.
But it did. The effect was found and applications were made to show what it would look like when working. Only some years ago a modded 4074 image was released under the name _The Way It Was Meant To Be_ (TWIWMTB) which added the fully working aurora effect to explorer. In the remainder of this article I will explain more about Aero and why the aurora which is available in build 4066 and 4074 doesn't work in the first place and how it works at all. Moreover, I will go one the steps needed to manually enable the Animated Preview Panel Aurora (APPA) in build 4074.
......@@ -27,7 +28,7 @@ To convert Jade to Aero you need to rename the theme files and edit the .theme f
Applying the Aero theme will result in a completely new style. If you don't see the new task and sidebar, you might need to restart explorer.exe. Note that even though the new style task and sidebar are only enabled when the Aero theme is applied, they aren't part of the Aero theme itself, but a system library. They will only show once a "theme name check' has been passed.
Build 4066 is the first build where above described "Jade to Aero conversion" works. Aero is not exclusive to Milestone 7 builds though, the theme was already [referenced in much earlier builds such as 4033 and 4039](/4039-tips-tricks).
Build 4066 is the first build where above described "Jade to Aero conversion" works. Aero is not exclusive to Milestone 7 builds though, the theme was already [referenced in much earlier builds such as 4033 and 4039](/4039-tips-tricks/).
Note that converting Jade to Aero will not enable the transparent Aero Glass theme, but will show up using greenish borders. For 4074 and 4066 patched files exist to enable transparent window borders.
......@@ -59,7 +60,7 @@ This package includes the transparent DWM theme by BOFH patched so that it has w
![](desktop-aurora.png)
Aurora in the preview panel isn't the only kind of aurora we know. In build 4066 and up a BAML file for desktop aurora can be found. Desktop aurora is what its name suggests; aurora as a desktop wallpaper. This implementation of aurora was probably introduced in build [4050 with build tag private/lab06_demo.031013-1849](/guide/4050-13) since this build's tag is included in the BAML file. One class for loading the desktop aurora can be found in Longhorn's system files. Sadly, while loading the BAML file Avalon will throw an error.
Aurora in the preview panel isn't the only kind of aurora we know. In build 4066 and up a BAML file for desktop aurora can be found. Desktop aurora is what its name suggests; aurora as a desktop wallpaper. This implementation of aurora was probably introduced in build [4050 with build tag private/lab06_demo.031013-1849](/guide/4050-13/) since this build's tag is included in the BAML file. One class for loading the desktop aurora can be found in Longhorn's system files. Sadly, while loading the BAML file Avalon will throw an error.
4066 is also the first build to have aurora as background when the 3D view option is enabled in explorer. The files that make up this aurora effect had been in Longhorn since the start of Milestone 4 and therefore this aurora is often called "Milestone 4 aurora'. It's noticable that this aurora is not rendered using the managed Avalon API, but consists of a set of PNG images rendered using DirectX. Below you see renders made using the original files found in build 4028 created with AssimpView.
......
......@@ -3,10 +3,10 @@ title: onghornLay
author: Melcher
type: post
date: 2015-03-09T21:24:14+00:00
url: /pig-latin
url: /pig-latin/
featured_image: build-4029-piglatin.png
categories:
- Development
- History
---
While exploring Longhorn builds you might have noticed these weird spelling mistakes in the Windows branding like; "onghornLay rofessionalPay" and wondered whether one of the developers had a breakdown while typing this. In this article I will elaborate on the exact purpose of the "onghornLay" branding.
......
......@@ -3,11 +3,10 @@ title: Virtual development
author: Melcher
type: post
date: 2015-04-17T15:19:42+00:00
url: /vbl
url: /vbl/
featured_image: null
categories:
- Development
- Research
- History
---
Ever looked at a Windows build list and wondered what all those different tags mean? Or did you ever wonder about the production process of Windows? If yes, you've just clicked the correct article. This article will elaborate on the Windows build process as used during the pre-reset Longhorn development. Please note that even though I've conducted rigorous research, not all information in this article may be accurate.
......
......@@ -3,10 +3,10 @@ title: Hexadecimal notation
author: Melcher
type: post
date: 2015-05-14T14:07:38+00:00
url: /hexadecimal-system
url: /hexadecimal-system/
featured_image: hex-field.png
categories:
- Research
- History
---
This quick introduction to hex was originally to be part of another article, but became quite long and therefore I decided to separate it. Even though it doesn't have anything to do with Longhorn in particular I believe it will be worth the read.
......
......@@ -3,16 +3,17 @@ title: '4039 Tips & tricks'
author: Melcher
type: post
date: 2015-08-10T11:53:14+00:00
url: /4039-tips-tricks
url: /4039-tips-tricks/
categories:
- 'Tips & tricks'
- Features
- User Guides
---
This is the very first page in its kind; a tips 'n tricks page. More of these pages will follow for other interesting builds, showing you the ins and outs and providing easy tutorials to activate hidden features. Pages like this will be updated every so often to include the latest finds. But for now, 4039.
#### Enable Aero glass {#aero-glass}
This build contains some super sleek Aero glass resources in desksrv.dll for the theming service to use. By default, the opaque resources will be used, but a simple patch of desksrv.dll enables the glass borders on windows when DCE is running. For a tutorial on how to enable DCE please see [this page](/desktop-compositing). The desksrv patch involves simply replacing the opaque PNG files with the transparent ones. While this is neat and all, it's not a very original way of doing things. Luckily there is a much more convenient and original trick to enable transparent borders.
This build contains some super sleek Aero glass resources in desksrv.dll for the theming service to use. By default, the opaque resources will be used, but a simple patch of desksrv.dll enables the glass borders on windows when DCE is running. For a tutorial on how to enable DCE please see [this page](/desktop-compositing/). The desksrv patch involves simply replacing the opaque PNG files with the transparent ones. While this is neat and all, it's not a very original way of doing things. Luckily there is a much more convenient and original trick to enable transparent borders.
1. Browse to the themes folder, C:\Windows\Resources\Themes\
2. Copy the Plex folder and rename it to Aero.
......
......@@ -3,15 +3,15 @@ title: Self-hosting
author: Melcher
type: post
date: 2015-08-14T14:12:22+00:00
url: /self-hosting
url: /self-hosting/
featured_image: 4042votenow.png
categories:
- Development
- Research
- Features
- History
---
At Microsoft it's common practice to use products still under development to continue development of that very product. Once a stable version of a product is available, developers are encouraged to install it on their workstations and use it for every day use. Developers using the product can directly provide feedback and report bugs to teams working on certain features. This process is internally called _self-hosting_. Often times the process is also referred to as "eating your own dog food" or _doogfooding_: when the product is no good and tastes nothing better than dog food, developers will still need to _eat_ it.
At Microsoft, it is common practice to use products still under development to continue development of that very product. Once a stable version of a product is available, developers are encouraged to install it on their workstations and use it for every day use. Developers using the product can directly provide feedback and report bugs to teams working on certain features. This process is internally called _self-hosting_. Often times the process is also referred to as "eating your own dog food" or _doogfooding_: when the product is no good and tastes nothing better than dog food, developers will still need to _eat_ it.
The idea of self-hosting is to quickly get feedback and bug reports as mentioned earlier. Another reason to do this is also to keep in touch with the product. Since developers actually have to use their product, they see and experience what end users of the final product will see.
......
......@@ -3,10 +3,11 @@ title: Exposing a spy
author: Melcher
type: post
date: 2016-01-11T10:39:45+00:00
url: /exposing-a-spy
url: /exposing-a-spy/
featured_image: phodeo-top.png
categories:
- Research
- Features
- History
---
Most of you will probably be aware of some of the hidden view options available throughout the Longhorn builds. These views are commonly known as "Carousel" and "Panorama". The latter is often also called "Phodeo". Enabling the 3D view-mode as well as one of these hidden views causes a DirectX rendered view to appear instead of the familiar plain 2D view. The DirectX powered view features all sorts of animation to spice up the browsing experience.
......
......@@ -3,13 +3,13 @@ title: Hillel demoes Longhorn (Extended cut)
author: Melcher
type: post
date: 2016-01-27T08:37:16+00:00
url: /hillel-demoes-longhorn-extended-cut
url: /hillel-demoes-longhorn-extended-cut/
featured_image: hilleldemopdc.png
categories:
- Concept spotlight
- History
---
Here it is. 6 minutes of Hillel Cooperman introducing Longhorn to the public during Bill Gates' keynote on 27 October 2003 at PDC '03 in Los Angeles. Originally this demo was cut from the footage from Bill Gates' keynote that was published online at Channel9. I found bits and bops of the footage scattered over the web and decided to put them together in one large video. I complemented some of the original footage with videos by Paul Thurrott. The build shown is known to be [4050.private/lab06_demo](/builds/4050-pdc).
Here it is. 6 minutes of Hillel Cooperman introducing Longhorn to the public during Bill Gates' keynote on 27 October 2003 at PDC '03 in Los Angeles. Originally this demo was cut from the footage from Bill Gates' keynote that was published online at Channel9. I found bits and bops of the footage scattered over the web and decided to put them together in one large video. I complemented some of the original footage with videos by Paul Thurrott. The build shown is known to be [4050.private/lab06_demo](/builds/4050-pdc/).
Check it out
......
......@@ -4,10 +4,10 @@ author: Melcher
type: post
date: 2016-01-28T14:25:46+00:00
draft: true
url: /?p=1369
url: /longhorn-4074-vm/
featured_image: vm.png
categories:
- Special Download
- Downloads
---
For your convenience, I uploaded a pre-configured Longhorn VM for you to download!
......@@ -22,7 +22,7 @@ The VM contains a vanilla 4074 installation with the following bits changed:
* enabled MILExplorer in registry
* removed 180 day evaluation restriction
Note that the VM was created in VMware Workstation 7.1.4 and should also be used with that version of VMware. **When restarting the VM it probably wants to active right away. Be sure to start into some WinPE environment so you can apply the [winlogon crack](/activation-cracks).**
Note that the VM was created in VMware Workstation 7.1.4 and should also be used with that version of VMware. **When restarting the VM it probably wants to active right away. Be sure to start into some WinPE environment so you can apply the [winlogon crack](/activation-cracks/).**
Once unpacked, the VM is 5.59 gigabytes in size. Note that the VM was created on a computer with a 4th generation core i5. Processors with feature-set vastly different from this may not work well with this VM.
......
......@@ -3,10 +3,11 @@ title: 'Hacking Avalon – 1: Disable it'
author: Melcher
type: post
date: 2016-03-14T22:01:47+00:00
url: /disable-avalon
url: /disable-avalon/
featured_image: hackingavalon.png
categories:
- Hacking Avalon
- History
- Features
---
This is the first post in a series that I'll be doing. Hacking Avalon will be all about interesting stuff in Avalon. Furthermore, I hope to provide some background on how early variants of Avalon work together with the shell in Longhorn. Keep in mind, this series will mainly discuss the earliest revisions of Avalon found in the 3xxx range of builds. The tricks may not always work on later builds. That's it for the intro. Now onto the subject of this post; disabling Avalon in explorer.
......
......@@ -3,10 +3,11 @@ title: 'Hacking Avalon – 2: Port it'
author: Melcher
type: post
date: 2016-04-08T13:25:55+00:00
url: /installing-avalon-nt
url: /installing-avalon-nt/
featured_image: avalon-on-xp.png
categories:
- Hacking Avalon
- History
- User Guides
---
Always wanted to experiment with Avalon on Windows XP? In this second part of the "Hacking Avalon" series we're going to install not only Avalon but also some other Longhorn component. In this post I will take Windows XP as example, but the installer is also compatible with Server 2003. Below is a description of the included components and their use.
......
......@@ -3,10 +3,10 @@ title: Proper 4093 release
author: Melcher
type: post
date: 2016-04-20T18:08:50+00:00
url: /fixed-version-4093
url: /fixed-version-4093/
featured_image: 4093-fixed-1.png
categories:
- Special Download
- Downloads
---
_This used to be hosted on the initial website two years ago (whoa, time flies). I completely forgot about re-uploading it until now. Enjoy!_
......@@ -22,7 +22,7 @@ Install notes:
We would like to thank Hounsell for hosting our website and letting us host the download of the fixed copy.
[Download](/images/4093fixed.zip)
[Download](https://mega.nz/#!xVxUyKDZ!bO9nwg54iy6qGYDNRlcz4FBpcQn5xExxjuZsi9YT4oI)
(please do not directly link to the download. Link to this page instead)
......
......@@ -3,10 +3,11 @@ title: Installing drivers
author: Melcher
type: post
date: 2016-04-22T15:01:27+00:00
url: /installing-drivers
url: /installing-drivers/
featured_image: hard-wiz-err-3.png
categories:
- Tutorials
- User Guides
- Downloads
---
When using Longhorn it's a must to known how to manually install drivers in Windows. The process is basically the same in all versions of Windows, but I thought it couldn't hurt if I would write up a short tutorial for those people new to installing drivers.
......
......@@ -3,10 +3,10 @@ title: The very beginning
author: Melcher
type: post
date: 2016-05-07T15:00:57+00:00
url: /early-development
url: /early-development/
featured_image: timeline.svg
categories:
- Development
- History
---
Often times people are confused to hear Longhorn was based off of Windows Server 2003. To the newcomer it seems more plausible that it was instead based off of Windows XP because early builds look so much like it. In this post we will have an in-depth look at the early beginning of the Longhorn project. Along the way we will discover how Longhorn emerged from the Server 2003 code base.
......@@ -15,7 +15,7 @@ Often times people are confused to hear Longhorn was based off of Windows Server
#### Trunk based development
Before we begin, it's good to know something about how Windows is developed. When developing a large software application there are various ways to separate the developmental code from the release code. One of these ways is trunk based development. Using trunk based development there is one clearly distinguishable shared branch all developers commit their code changes to. This one branch is called the "trunk". For Windows this trunk is better known as the [_main_ branch](/builds/branch/main). The trunk is in continuous development and over time Windows versions are released from the trunk's code base.
Before we begin, it's good to know something about how Windows is developed. When developing a large software application there are various ways to separate the developmental code from the release code. One of these ways is trunk based development. Using trunk based development there is one clearly distinguishable shared branch all developers commit their code changes to. This one branch is called the "trunk". For Windows this trunk is better known as the [_main_ branch](/builds/branch/main/). The trunk is in continuous development and over time Windows versions are released from the trunk's code base.
Whenever a product is due to be released a _release branch_ is forked from the trunk. A release branch is maintained as long as the product is supported. When critical updates are available for the trunk usually these will also be released in some form for release branches affected by the same problems. This way the release branches will more or less stay in synch with the trunk. Eventually, when the product is being phased out and reaches the end-of-life (EOL) status, the branch will be abandoned.
......@@ -36,7 +36,7 @@ In 2001, somewhere between 17 and 23 July the main branch was forked to the _xpc
![](timeline.svg)
The first Longhorn build confirmed to exist is [3663](/builds/3663) compiled by [_lab06\_n_](/builds/branch/lab06/lab06_n). There are, however, indications that Longhorn builds were already being compiled as early as 2001.
The first Longhorn build confirmed to exist is [3663](/builds/3663/) compiled by [_lab06\_n_](/builds/branch/lab06/lab06_n/). There are, however, indications that Longhorn builds were already being compiled as early as 2001.
Exhibits from the Microsoft v.s. Comes case give a unique insight in some of the earliest development and planning of Longhorn. According to document _[PX06977](PX06977.pdf)_, planning for Longhorn was supposed to start in either July or August 2001. The passage below originates from internal Microsoft correspondence dating back to December 2001.
......
......@@ -2,11 +2,10 @@
title: 'Phodeo in detail'
author: Melcher
date: 2016-05-09T10:00:00+00:00
url: /phodeo-in-detail
url: /phodeo-in-detail/
featured_image: phodeo-close-up.png
categories:
- Concept spotlight
- Feature review
- History
---
......
......@@ -3,10 +3,10 @@ title: 'Hacking Avalon – 3: Compiling xaml'
author: Melcher
type: post
date: 2016-05-14T12:56:07+00:00
url: /avalon-compiling-it
url: /avalon-compiling-it/
featured_image: xaml-direct.png
categories:
- Hacking Avalon
- History
---
In this third part of the Hacking Avalon series we are taking a closer look at the process of making an Avalon application. To do this, we will be using a special tool only available in early Longhorn builds. This tool is called the Avalon Compiler or simply "ac'. This tool does what its name suggests; compile Avalon. But what is that precisely?
......
......@@ -3,10 +3,11 @@ title: '3683 Tips & tricks'
author: Melcher
type: post
date: 2016-08-12T19:40:50+00:00
url: /3683-tips-tricks
url: /3683-tips-tricks/
featured_image: 3683.png
categories:
- 'Tips & tricks'
- Features
- User Guides
---
Longhorn build 3683 is the "youngest' of all Longhorn builds we have access to, dating back to September 2002. As such you might expect it to be very similar to XP and Server 2003 versions of Windows. When looking superficially at this build this may seem to be correct, but for those that care to take a closer look there are plenty of new features to be found throughout this build. Moreover, when taking a look under the hood, it becomes apparent that technologies like desktop compositing and WinFS had already largely been implemented by this time. On this page I'll point out some of the often missed/forgotten features present in this build.
......@@ -17,7 +18,7 @@ WinFS, in contrast to later builds, indexes the complete root drive of the compu
### StartUp Applications Monitor
Even though this feature was already available through another tool -_msconfig_ - this is a more user friendly way of presenting applications that automatically start with Windows. This tab is found in Performance settings in System Properties.
Even though this feature was already available through another tool - _msconfig_ - this is a more user friendly way of presenting applications that automatically start with Windows. This tab is found in Performance settings in System Properties.
![](StartUp-Application-Monitor.png)
......
......@@ -3,10 +3,11 @@ title: True meaning of RMA
author: Melcher
type: post
date: 2016-08-17T09:15:54+00:00
url: /true-meaning-of-rma
url: /true-meaning-of-rma/
featured_image: 4008-rma-tile.png
categories:
- Research
- History
- Features
---
......
......@@ -3,11 +3,11 @@ title: Desktop Compositing
author: Melcher
type: post
date: 2016-09-18T11:48:55+00:00
url: /desktop-compositing
url: /desktop-compositing/
featured_image: aero-flip.png
categories:
- Research
- Tutorials
- Features
- User Guides
---
......@@ -142,7 +142,7 @@ C:\Windows\i386\sbctl start
C:\Windows\i386\sbctl stop
```
In most cases a restart of explorer is required to make the task- and sidebar visible again. Build 4033 has a bug in DCE which causes it to automatically fall-back to CPU processing instead of hardware processing. Therefore, running DCE in this build will not unlock the special borders. By default builds 4039 and 4042 have an opaque theme. You can, however, perform the trick [described here](/4039-tips-tricks) to enable Aero glass.
In most cases a restart of explorer is required to make the task- and sidebar visible again. Build 4033 has a bug in DCE which causes it to automatically fall-back to CPU processing instead of hardware processing. Therefore, running DCE in this build will not unlock the special borders. By default builds 4039 and 4042 have an opaque theme. You can, however, perform the trick [described here](/4039-tips-tricks/) to enable Aero glass.
### 4066
{{< figure src="4066-dwm.png" title="DWM on 4066, resulting in some blurry green borders." >}}
......
......@@ -3,14 +3,14 @@ title: Aero done right
author: Melcher
type: post
date: 2016-12-17T13:49:43+00:00
url: /aero-done-right
url: /aero-done-right/
featured_image: 4074-dwm-jade.png
categories:
- Feature review
- Tutorials
- Features
- User Guides
---
A lot of people have been struggling to get Aero to work in build 4074. In this post I want to show you how Aero can be enabled along with a little bit of its history. If you came here looking for information about Aurora, please see my post about [Aurora & Aero](/aurora-aero).
A lot of people have been struggling to get Aero to work in build 4074. In this post I want to show you how Aero can be enabled along with a little bit of its history. If you came here looking for information about Aurora, please see my post about [Aurora & Aero](/aurora-aero/).
#### A theme with two faces
......@@ -20,7 +20,7 @@ According to internal documentation, personal authorization by Scott Hanggie was
{{< figure src="aero-pat.png" title="Note that only the border is transparent. Probably, MILExplorer has not been set in the registry." >}}
Although there is no way to tell when this screenshot was taken and on which build, I tend to think it was taken on one of the many 4050 [lab06_demo](/builds/branch/lab06/lab06_demo) builds compiled during 2003 leading up to the [PDC 2003 demo build](/builds/4050-pdc). By default the build from the lab06_demo branch had an appearance similar (if not identical) to the publicly released build at PDC 2003, [4051](/builds/4051). In contrast to the public build these builds, however, did have full support for Aero. The sad news that the public build would not yet feature Aero was brought by [Paul Thurrott](http://web.archive.org/web/20060310222543/http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=40367%26DisplayTab=Article "Windows IT Pro - Exclusive: PDC Attendees to Get Aero Demo Only") in September:
Although there is no way to tell when this screenshot was taken and on which build, I tend to think it was taken on one of the many 4050 [lab06_demo](/builds/branch/lab06/lab06_demo/) builds compiled during 2003 leading up to the [PDC 2003 demo build](/builds/4050-pdc/). By default the build from the lab06_demo branch had an appearance similar (if not identical) to the publicly released build at PDC 2003, [4051](/builds/4051/). In contrast to the public build these builds, however, did have full support for Aero. The sad news that the public build would not yet feature Aero was brought by [Paul Thurrott](http://web.archive.org/web/20060310222543/http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=40367%26DisplayTab=Article "Windows IT Pro - Exclusive: PDC Attendees to Get Aero Demo Only") in September:
> For the past several weeks, Microsoft has forked the Longhorn code to develop a special PDC build that's separate and distinct from the main code fork. This build will include virtually every Longhorn technology except Aero(&#8230;)
......@@ -40,7 +40,7 @@ Although Microsoft employees denied any claims of Aero and DWM being present and
#### Getting ourselves some Aero
Before trying to enable Aero be sure to have a look at this post I wrote earlier: [Destkop Compositing](/desktop-compositing). On that page I explain everything you need to know to get DWM working on your (virtual) machine. So, go have a look there - I'll wait.
Before trying to enable Aero be sure to have a look at this post I wrote earlier: [Destkop Compositing](/desktop-compositing/). On that page I explain everything you need to know to get DWM working on your (virtual) machine. So, go have a look there - I'll wait.
Okay, done that? Now that you have installed the proper drivers, it’s probably a good thing to reboot the computer for the changes to take affect (if you haven't do so already).
......@@ -84,6 +84,6 @@ tskill explorer
#### Results
If everything went corrent you should end up with something like the picture below. Note that the screenshot also shows the Animated Aurora Preview Pane. More information on how to patch the theme can be found in [another post](/aurora-aero#fix). You might have also noticed that the borders on all windows are still actually opaque and not the Aero translucent kind. Unfortunately, the original resources are not available in any build. There are, however, a few very good patched theme files with transparency available on the internet as well as a build of 4074 (TWIWMTB) that has a pre-patched theme file.
If everything went corrent you should end up with something like the picture below. Note that the screenshot also shows the Animated Aurora Preview Pane. More information on how to patch the theme can be found in [another post](/aurora-aero/#fix). You might have also noticed that the borders on all windows are still actually opaque and not the Aero translucent kind. Unfortunately, the original resources are not available in any build. There are, however, a few very good patched theme files with transparency available on the internet as well as a build of 4074 (TWIWMTB) that has a pre-patched theme file.
{{< figure src="4074-dwm-jade.png" title="Aero taskbar and sidebar show up when using an altered version of the Jade theme" >}}
\ No newline at end of file
......@@ -3,11 +3,10 @@ title: Revisiting the Online Photo Print Wizard
author: Melcher
type: post
date: 2017-05-14T14:09:12+00:00
url: /revisiting-the-online-photo-print-wizard
url: /revisiting-the-online-photo-print-wizard/
featured_image: 4042-2017-05-14-13-53-05.png
categories:
- Feature review
- Tutorials
- Features
---
In this post I will have a look at how one can unlock the "full potential' of the wizard - to lift a corner of the veil: it doesn't have a lot of potential. If you can vaguely remember me writing about exactly this subject a few years back.. you are right, but with the switch to the WordPress powered website I totally forgot to place the original article back so here I am revisiting the subject C:
......
......@@ -3,10 +3,10 @@ title: Some build
author: Melcher
type: post
date: 2017-05-17T17:47:17+00:00
url: /some-build
url: /some-build/
featured_image: 408x-2.png
categories:
- Research
- History
---
I'm on some sort of "write down all the things" spree, [documenting things](https://www.betaarchive.com/forum/viewtopic.php?f=62&t=33865 "BetaArchive - Longhorn for everyday use (back then)") I've found in the past, but never properly have written down here on longhorn.ms. Today I'd like to have a brief look at this unidentified build.
......@@ -19,7 +19,7 @@ The image below is the only overview shot of this build we get to see in this vi
![](408xoverview.png)
The explorer style does indeed suggest we're dealing with a late Longhorn build: no plus sign in front of the "Storage favourites' item and no folder image in the preview pane behind the "X item in this folder' text both of which were still present in build 4074. Moreover, the iconic tree wallpaper seen in builds [4084](/builds/4084), [4088](/builds/4088) and [4093](/builds/4093) is present.
The explorer style does indeed suggest we're dealing with a late Longhorn build: no plus sign in front of the "Storage favourites' item and no folder image in the preview pane behind the "X item in this folder' text both of which were still present in build 4074. Moreover, the iconic tree wallpaper seen in builds [4084](/builds/4084/), [4088](/builds/4088/) and [4093](/builds/4093/) is present.
![](408x-2.png)
......
......@@ -3,10 +3,10 @@ title: Behind the wallpapers
author: Melcher
type: post
date: 2018-06-26T22:17:33+00:00
url: /behind-the-wallpapers
url: /behind-the-wallpapers/
featured_image: ws_Vista_grass_1600x1200.jpg
categories:
- Research
- History
---
Here's just a funny tidbit I found some time ago to keep you guys entertained. In [an interview on Channel9](https://channel9.msdn.com/Shows/WM_IN/Jenny-Lam-Designing-Experiences-at-Microsoft "Jenny Lam - Designing Experiences at Microsoft"), Robert Scoble asks a designer on the Windows team, Jenny Lam some questions about Vista and how its coming up Channel9. During the interview the following comes up on the subject of wallpapers:
......
......@@ -3,16 +3,15 @@ title: The reset
author: Melcher
type: post
date: 2018-06-26T22:25:14+00:00
url: /the-reset
url: /the-reset/
featured_image: 4042-2014-11-17-14-34-01.png
categories:
- Development
- Research
- History
---
The piece of text you read below was originally part of the "[Guide](/builds)" section present on the very first iteration of the "Experience Longhorn" site. Since the switch to WordPress as a CMS and all changes to the theme there has been no more place to have it on what is now called the [Builds list](/builds). I really didn't want to throw the story on the reset away though, so here you have it: a short an concise explanation about the infamous Longhorn reset.
The piece of text you read below was originally part of the "[Guide](/builds/)" section present on the very first iteration of the "Experience Longhorn" site. Since the switch to WordPress as a CMS and all changes to the theme there has been no more place to have it on what is now called the [Builds list](/builds/). I really didn't want to throw the story on the reset away though, so here you have it: a short an concise explanation about the infamous Longhorn reset.
The newest Windows product at the time of the reset in late 2004 was Windows Server 2003 sp1 RC, which was used as a base after the reset. The new codebase was first componentised before any new features were added to it. Work on componentising the Server 2003 codebase had already begun weeks before build 4093 was compiled. The post-reset range started at build 5000. The first post-reset builds were compiled by the [vbl_core](/builds/branch/base/vbl_core) lab. The last pre-reset build compiled probably is 4094.private/Lab06\_dev\_tech(skatari).
The newest Windows product at the time of the reset in late 2004 was Windows Server 2003 sp1 RC, which was used as a base after the reset. The new codebase was first componentised before any new features were added to it. Work on componentising the Server 2003 codebase had already begun weeks before build 4093 was compiled. The post-reset range started at build 5000. The first post-reset builds were compiled by the [vbl_core](/builds/branch/base/vbl_core/) lab. The last pre-reset build compiled probably is 4094.private/Lab06\_dev\_tech(skatari).
### When did this happen?
......
......@@ -3,11 +3,11 @@ title: 'Guide: WinFS and tasks in build 4042'
author: Melcher
type: post
date: 2018-07-08T15:23:15+00:00
url: /guide-winfs-and-tasks-in-build-4042
url: /guide-winfs-and-tasks-in-build-4042/
featured_image: 4042-2017-05-13-13-00-16.png
categories:
- 'Tips & tricks'
- Tutorials
- Features
- User Guides
---
A big new thing in Longhorn were the tasks and help topics integrated into Explorer. Many builds show an empty space where these tasks would go in Explorer's task pane, but no tasks are showing. In this post I'll describe a the step-by-step process of getting these tasks to work on build 4042. The idea is that we go from an empty pane to a nice and completely filled pane like in the image below.
......@@ -18,7 +18,7 @@ A big new thing in Longhorn were the tasks and help topics integrated into Explo
Tasks are stored on the system as `*.help` files. These files can be found in `C:\Windows\HELP`. These files are compiled by combining multiple other files such as MAML. The Micorsoft Assistance Markup-Language (MAML) was a new addition to define help topic and tasks in Longhorn. The files defining tasks for explorer are not in MAML format, but rather contain serialized .NET objects defined search and task behavior. A good resource on [how to create your own help files can be found here](https://www.help-info.de/en/Help_Info_AP_Help/longhorn_4051_first_steps.htm).
It is interesting to note that the <em>NuiAnnotations.help</em> file contains a sample snippet of a task definition which was generated using `XMLSpy v4.4`. The root element contains a `snapshotDate` which tells us this sample was created as early as 17 December 2001 at 9:30 AM. This substantiates the claims I made earlier in my article about [the very beginning of Longhorn](/early-development).
It is interesting to note that the <em>NuiAnnotations.help</em> file contains a sample snippet of a task definition which was generated using `XMLSpy v4.4`. The root element contains a `snapshotDate` which tells us this sample was created as early as 17 December 2001 at 9:30 AM. This substantiates the claims I made earlier in my article about [the very beginning of Longhorn](/early-development/).
### Setting up WinFS
......
---
title: 'Managed C++: Clearing the C# myth'
author: Thomas Hounsell
type: post
date: 2019-07-15T09:00:00+00:00
url: /managed-cpp-in-longhorn
categories:
- Research
- Development
---
Reading up on Longhorn's development process, and you'll read a lot about how the shell or user interface was redeveloped using the .NET Framework, and many people infer that this meant using C#, including a number of Microsoft employees. This has then been blamed for the terrible performance of Longhorn and in particular, the rampant memory leaks it had.
It's time for a back to basics lesson on how the Longhorn shell was developed, to help dispell some of those common myths and get to the core of what went wrong in Longhorn's shell.
### Architecture
Let's take a step back for a moment and consider the shell improvements from a wider view. We know that the traditional `explorer.exe` shell has been steadily developed using native Windows APIs and C++ right from its inception. A cursory inspection of any Longhorn build will reveal that this remains largely unchanged. This is how builds for other architectures, such as AMD64, work and feel much like XP, with Windows Explorer working in very much the same way.
At this early stage, .NET was only supported on the 32-bit x86 platform. .NET Framework v2.0 would eventually add support for both IA-64 and AMD64, but this did not arrive ahead of Longhorn's development reset. While Longhorn for IA-64 and AMD64 both included _WoW64_ (Windows on Windows 64), which allowed 32-bit applications such as .NET to run, their `explorer.exe` shell was 64-bit, and you cannot mix architectures within the same process.
This betrays a little of how the "new" shell was implemented - it was not an independent new shell, but rather a (rather complex) plugin for Windows Explorer. The .NET Framework allows for the creation of COM components within managed libraries and so this is how it was implemented. Indeed, this is how many such changes had also been implemented in Whistler / Windows XP, albeit they were exclusively native C++ rather than using the .NET Framework. This is also how Longhorn can fallback gracefully to an XP-style experience - it attempts to load the new Longhorn extension via COM first, and if that fails, falls back to the XP-style COM experience. In the unusual event even that fails, you would end up with something akin to the "Classic" view, or Windows 2000 style.
### The Language?
So then, if they're using .NET, it's got to be C# right? It's _the_ .NET language. First-class support and the hot new thing Microsoft were pushing to developers at every opportunity. They even already had some experience of shipping a Windows component written in C# - Windows XP's Media Center was a purely managed C# affair for the most part, with only a small number of components written in C++.
For reasons we can only speculate, the Shell team did not use C# much, if at all, within the Longhorn shell. Instead, they used Microsoft's variant of C++ called *Managed C++*. This is related, but not quite the same as the more modern *C++/CLI*, which is Microsoft's second attempt at a C++ dialect for the .NET Framework, and probably one that was very much influenced by the painful experience of the Longhorn Shell.
There are a few probable reasons for this decision. One is that the C# language was very much in it's infancy. It is important to recall that at this early stage, C# was not the proven, mature language it is today. There was no support for generics, to take one example.
Furthermore, developers who had extensive experience with the language were few and mostly associated with the .NET team itself. Instead, what the Shell team did have an overabundance of was developers trained and highly experienced with C++. It would have likely seemed the wiser decision to limit the amount of on-the-job training by going with something that very much bridged the gap.
A third factor was likely the ease of interoperability with existing native code with Managed C++. The story in C# for interoperability is not horrible per se, but it was and still is from a developers point of view, more rigid and more work. In C#, you're required to use a Platform Invoke, or P/Invoke, that requires you to redefine the export in C#. For example, this export from the Windows SDK headers...
{{<highlight cpp>}}
INT ShellAboutW(HWND hWnd, LPCWSTR szApp, LPCWSTR szOtherStuff, HICON hIcon);
{{</highlight>}}
...would become this P/Invoke definition in C#:
{{<highlight csharp>}}
[DllImport("shell32.dll")]
static extern int ShellAbout(IntPtr hWnd, string szApp, string szOtherStuff, IntPtr hIcon);
{{</highlight>}}
Rather than go through and create all these redefinitions - which may also expose information that was limited before to private internal-only header files - using Managed C++ allowed MS to simply reference native functions in much the same way as they would in native C++, for example in this toy program (this is C++/CLI rather than MC++, which doesn't have the gcnew keyword):
{{<highlight cpp>}}
#include <string>
#include "windows.h"
#include "shellapi.h"
#pragma comment(lib, "shell32.lib")
using namespace System;
const char* show_shell_about()
{
return ShellAbout(NULL, L"C++/CLI Sandbox", L"Hi from the Experience Longhorn project", NULL) == TRUE
? "True"
: "False";
}
int main()
{
auto result = show_shell_about();
System::Console::Write("Result: ");
System::Console::WriteLine(gcnew System::String(result));
return 0;
}
{{</highlight>}}
This would have likely been considered a huge benefit to the Shell team which, with strict performance goals, were likely to be passing across the native / managed boundary quite frequently. Unlike C#, this also allows you to have a "mixed-mode" library or executable, which contains both unmanaged and managed code.
If you were to decompile the compiled version of the toy program above, you'd note some key differences from typical .NET executables. Using an IL decompiler, such as dnSpy, you'd notice that a lot of placeholder classes and structs that represent various structures defined in the Windows SDK headers. In a <Module> class, you'd find the methods that were in the global namespace, such as the `main()` and `show_shell_about()` from the toy program above. In here is our ShellAboutW() import stub, that dnSpy decompiles to the following C#:
{{<highlight csharp>}}
[SuppressUnmanagedCodeSecurity]
[DllImport("", CallingConvention = CallingConvention.StdCall, SetLastError = true)]
[MethodImpl(MethodImplOptions.Unmanaged)]
internal unsafe static extern int ShellAboutW(HWND__*, char*, char*, HICON__*);
{{</highlight>}}
The `show_shell_about()` method decompiles as so:
{{<highlight csharp>}}
internal unsafe static sbyte* show_shell_about()
{
return ref (<Module>.ShellAboutW(null, (char*)(&<Module>.?A0x37975f1f.unnamed-global-1), (char*)(&<Module>.?A0x37975f1f.unnamed-global-0), null) != 1)
? ref <Module>.?A0x37975f1f.unnamed-global-3
: ref <Module>.?A0x37975f1f.unnamed-global-2;
}
{{</highlight>}}
You can see that the strings have been pulled out into the executables' `.rdata` (read-only data) section and that .NET refers to them simply using automatically generated fields.
If you were to open this executable in a more typical decompiler, such as IDA Pro in PE mode, you'd see that unlike typical P/Invokes, a MC++ reference is also included in the imports table of the executable.
### Okay, but what does it all mean?
Well, Managed C++ came with some issues that Microsoft tried to rectify with C++/CLI. In particular, their overloading of the `new` keyword made it more difficult as to which objects would be collected by the managed garbage collector, and which objects had to be cleaned up manually by the developer. The potential outcome of such confusion would be that some objects never got collected or cleaned up, introducing a memory leak. Certainly, it is quite possible to introduce memory leaks in purely managed code, though not in the same way, but it does strike me that this is possibly a major contributing factor to Longhorn's well documented problems in this area. It's also noteworthy that they made the C++/CLI changes in line with the .NET 2.0 / Visual Studio 2005 release, after the Longhorn reset.
\ No newline at end of file
---
title: "3683.Lab06_N"
type: build
url: /builds/3683
url: /builds/3683/
build_tag: "6.0.3683.0.Lab06_N.020923-1821"
build_arch: [ "x86" ]
build_m: 3
......@@ -10,12 +10,21 @@ install_key: "CKY24-Q8QRH-X3KMR-C6BCY-T847Y"
featured_image: overview.png
---
Build 3683 was the first Codename "Longhorn" build to leak publicly on the internet when it leaked on 20th October 2002 as an x86 Professional compile by the xBetas release group. The publicly leaked version is a modified reduced-size ISO, some private collectors have the unmodified x86 Professional compile.
3683.Lab06_N was the first Codename "Longhorn" build to leak publicly on the internet. It was leaked on 20th October 2002 by the xBetas release group. The publicly leaked version is a modified Professional x86 release, featuring xBetas branding. Some private collectors have an untouched copy of the release.
Though an early build, it has a number of unique features. It is the only Milestone 3 build to feature an Avalon-based display properties control panel, out of the box. The display panel has a number of bugs however, and though present in later Milestone 3 builds, few bugs were fixed (indeed, a cursory examination suggests that it might not have been updated enough to ensure compatibility with the rapidly-changing runtime). As such, this build provides a unique opportunity to examine some early working Avalon code. DCE is partially implemented in this build.
Despite being the earliest build available, it debuts a number of features new to Longhorn and even includes a few that do not exist in later builds. The "Avalon" extension to the .NET Framework makes its first appearance within this build, and uniquely is built on top of a released .NET version (v1.0) instead of the in-development versions found in later builds (either v1.2 or v2.0 pre-release). This quirk allows you to [transplant the version of Avalon](/installing-avalon-nt/) in 3683 onto Windows XP.
[Tips and tricks for this build](/3683-tips-tricks)
It is one of only two builds to include a new [display display panel](/avalon-display-panel/) enabled out of the box - the other is [4093](/builds/4093/), which featured an entirely redeveloped display control panel. Other Milestone 3 builds included the same display control panel as 3683, but it is locked behind a registry key and is progressively more and more broken with each passing build up to its removal shortly after the start of Milestone 4.
Under the hood, the system is also being moved over to a [new branding API](/pig-latin/) that would consolidate branding from different components all over the system into one single, common API. There's also a small amount of early prototype code for the [Start page](/startpage/), though this is not exposed out of the box.
Lastly, the build contains the [Desktop Compositing Engine](/desktop-compositing/), though there is no UI to control it yet. It also does not work under virtual machines due to a compatibility issue with the emulated GPUs that they use.
### Gallery
{{< gallery 25 "desktop.png" "explorer.png" "overview.png" "contacts-browser.png" >}}
\ No newline at end of file
{{< gallery 25 "desktop.png" "explorer.png" "overview.png" "contacts-browser.png" >}}
### Related Articles
* [Tips and tricks for this build](/3683-tips-tricks/)
* [Compiling XAML in 3683](/avalon-compiling-it/)
\ No newline at end of file
---
title: "3706.Lab06_N"
type: build
url: /builds/3706
url: /builds/3706/
build_tag: "6.0.3706.0.Lab06_N.021029-1731"
build_arch: [ "x86" ]
build_m: 3
......@@ -10,7 +10,7 @@ install_key: "CKY24-Q8QRH-X3KMR-C6BCY-T847Y"
featured_image: sidebar-start-menu-glitch.png
---
Build 3706 was leaked on 22nd May 2006 as an x86 Professional compile. It is one of only a few builds that are confirmed to contain a working start page. The Desktop Composition Engine (DCE) is partially implemented in this build.
Build 3706 was leaked on 22nd May 2006 as an x86 Professional compile. It is one of only a few builds that are confirmed to contain a working [start page](/startpage/). The Desktop Composition Engine (DCE) is partially implemented in this build.
This build is the first to include the _new taskbar_. However, the taskbar is not a separate panel in this build yet, and therefore when enabled, shows the taskbar acting like a tile on the sidebar. Also included in this build is the all new My TV and Movies library.
......
---
title: "3713.Lab06_N"
type: build
url: /builds/3713
url: /builds/3713/
build_tag: "6.0.3713.0.Lab06_N.021113-1841"
build_arch: [ "x86" ]
build_m: 3
......
---
title: "3718.Lab06_N"
type: build
url: /builds/3718
url: /builds/3718/
build_tag: "6.0.3718.0.Lab06_N.021119-1730"
build_arch: [ "x86" ]
build_m: 3
......@@ -9,8 +9,8 @@ install_date: "2002-11-20"
install_key: "CKY24-Q8QRH-X3KMR-C6BCY-T847Y"
---
Longhorn build 3718 was leaked as an x86 Professional compile on April 30, 2004.
Longhorn build 3718 was leaked as an x86 Professional compile on April 30, 2004. A second CD image containing the Media Center and Tablet PC components has also been leaked.
The build features a Desktop Composition Engine, much more workable than the one found in earlier builds. This feature would later be renamed Desktop Window Composition, and remains present in Windows today. It provides hardware-accelerated window effects, such as alpha transparency and transitions, though both are quite different to what is found in later examples. The alpha transparency effect is present on the entire window, rather than simply the frame. Likewise, the transitions, though only present on minimising and restoring, are slower and more deliberate than found on later builds, flipping the window horizontally and vertically several times.
The build features a Desktop Composition Engine, much more easily used than the one found in earlier builds. This feature would later be renamed Desktop Window Composition, and remains present in Windows today. It provides hardware-accelerated window effects, such as alpha transparency and transitions, though both are quite different to what is found in later examples. The alpha transparency effect is present on the entire window, rather than simply the frame. Likewise, the transitions, though only present on minimising and restoring, are slower and more deliberate than found on later builds, flipping the window horizontally and vertically several times.
This build was the basis for the greenPlex, later known as protoPlex, project.
\ No newline at end of file
---
title: "3790.winmain"
type: build
url: /builds/3790
url: /builds/3790/
build_tag: "5.2.3790.1232.winmain.040819-1629"
build_arch: [ "x86" ]
build_m: "Omega-13"
......@@ -9,6 +9,6 @@ install_date: "2004-08-20"
install_key: "CKY24-Q8QRH-X3KMR-C6BCY-T847Y"
---
Built only hours after [build 4093](/builds/4093), this is the first build form the main branch after the reset. Note that the main branch has been renamed to winmain. This build identifies itself as being Longhorn in the _End User License Agreement_. General consensus is, however, that 3790 isn't a Longhorn build at all. It rather is a main branch compilation of the Server 2003 sp1 RC codebase. This build was presumably compiled only to pave the road for the coming real Longhorn (and eventually Vista) builds which jumped to the 5000-range after the reset took place.
Built only hours after [build 4093](/builds/4093), this is the first build form the main branch after the reset. Note that the main branch has been renamed to winmain. This build identifies itself as being Longhorn in the _End User License Agreement_. General consensus is, however, that 3790 isn't a Longhorn build at all. It rather is a main branch compilation of the Server 2003 SP1 RC codebase. This build was likely only compiled as a known-good baseline with which to test the new build systems that had been put in place after the reset. Actual development had already begun in a [virtual build lab](/vbl/), compiling a series of builds with the number 5000, from which development continued.
During setup you will be asked to locate some missing files. All of the missing files are in the i386 directory on the installation media. Because of the nature of this build, setup doesn't know where to look for the files itself. After installation this build requires you to activate Windows immediately. To bypass activation boot into safe-mode an apply your favourite activation crack.
\ No newline at end of file
---
title: "4001.main"
type: build
url: /builds/4001
url: /builds/4001/
build_tag: "6.0.4001.0.main.021204-1515"
build_arch: [ "x86" ]
build_m: 4
......
---
title: "4002.Lab06_N(ntvbl06)"
type: build
url: /builds/4002
url: /builds/4002/
build_tag: "6.0.4002.0.Lab06_N(ntvbl06).030108-1926"
build_arch: [ "x86" ]
build_m: 4
......
---
title: "4005.main"
type: build
url: /builds/4005
url: /builds/4005/
build_tag: "6.0.4005.0.main.030128-1920"
build_arch: [ "x86" ]
build_m: 4
......
---
title: "4008.main"
type: build
url: /builds/4008
url: /builds/4008/
build_tag: "6.0.4008.0.main.030219-1933"
build_arch: [ "x86" ]
build_m: 4
......
---
title: "4011.main"
type: build
url: /builds/4011
url: /builds/4011/
build_tag: "6.0.4011.main.030305-2045"
build_arch: [ "x86" ]
build_m: 4
......@@ -10,7 +10,7 @@ install_key: "CKY24-Q8QRH-X3KMR-C6BCY-T847Y"
featured_image: dce.png
---
This build’s installer throws a debug assertion error. It's recommended to [start setup from another build's WinPE](/diskpart). There used to be two different ISOs floating around the web. One had a corrupted Install.wim making the installation of the build impossible, the other installs fine. This build contains a Bar Settings Panel which seems to be an extension of the earlier seen [Avalon Display Panel](/avalon-display-panel).
This build’s installer throws a debug assertion error. It's recommended to [start setup from another build's WinPE](/diskpart/). There used to be two different ISOs floating around the web. One had a corrupted Install.wim making the installation of the build impossible, the other installs fine. This build contains a Bar Settings Panel which seems to be an extension of the earlier seen [Avalon Display Panel](/avalon-display-panel/).
### Gallery
......
......@@ -10,7 +10,7 @@ featured_image: high-res.jpg
This build was used at the Desktop Composition Demonstration booth at the [third day of WinHEC 2003](https://web.archive.org/web/20031217090239/http://www.microsoft.com/whdc/winhec/eyeonwinhec/QT3.mspx). At this booth exaggerated desktop animations were shown to emphasize the power of Longhorn’s new graphics subsystem. Effects include wobbly and rotating windows. The animations seen in this build are most likely enabled by installing additional "demo tools" written solely for this occasion. This would mean the animations shown are not unique to the actual build, but are created by invoking the right API functions from the DCE batch file instead. Notice the files visible on the desktop besides the batch file are a controls text document and ep2 video. The video shown is the [Star Wars episode 2 trailer](https://www.youtube.com/watch?v=gYbW1F_c9eM).
The hardware configuration used for this demonstration was [fairly modest](https://www.itprotoday.com/windows-78/winhec-2003-first-look-longhorn-graphics) for its time: a Pentium 4 (1.5GHz) processor with 384 MB main memory topped off with an ATI Radeon 9700 3D graphics card. The same system was also present at PDC 2003 where it was [photographed by xBetas](https://web.archive.org/web/20031202161327/http://pdc.xbetas.com/content.php?page=aerodcedemo) together with another system running build [4018.lab06_n](/builds/4018).
The hardware configuration used for this demonstration was [fairly modest](https://www.itprotoday.com/windows-78/winhec-2003-first-look-longhorn-graphics) for its time: a Pentium 4 (1.5GHz) processor with 384 MB main memory topped off with an ATI Radeon 9700 3D graphics card. The same system was also present at PDC 2003 where it was [photographed by xBetas](https://web.archive.org/web/20031202161327/http://pdc.xbetas.com/content.php?page=aerodcedemo) together with another system running build [4018.lab06_n](/builds/4018/).
According to the members of xBetas that spotted this machine at PDC 2003, the animations were painfully slow. The graphics card couldn’t keep up because of the insane screen resolution of 3840 x 2400 pixels used this time.
......
---
title: "4015.main"
type: build
url: /builds/4015-main
url: /builds/4015-main/
build_tag: "6.0.4015.0.main.030328-1500"
build_arch: [ "x86" ]
build_m: 5
......
---
title: "4018.Lab06_n"
type: build
url: /builds/4018
url: /builds/4018/
build_tag: "6.0.4018.Lab06_n.030417-1721"
build_arch: [ "x86" ]
build_m: 5
......
---
title: "4020.idx02"
type: build
url: /builds/4020
url: /builds/4020/
build_tag: "6.0.4020.0.idx02.030507-1155"
build_arch: [ "x86" ]
build_m: 5
......
---
title: "4032.lab06_n"
type: build
url: /builds/4032
url: /builds/4032/
build_tag: "6.0.4032.0.lab06_n.030710-1709"
build_arch: [ "x86" ]
build_m: 6
......
---
title: "4033.main"
type: build
url: /builds/4033-main
url: /builds/4033-main/
build_tag: "6.0.4033.0.main.030717-1555"
build_arch: [ "x86" ]
build_m: 6
......
---
title: "4039.Lab06_n"
type: build
url: /builds/4039-lab06_n
url: /builds/4039-lab06_n/
build_tag: "6.0.4039.0.Lab06_n.030827-1717"
build_arch: [ "x86" ]
build_m: 6
......@@ -10,7 +10,7 @@ install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
featured_image: transparent-dce.png
---
This is the fist leaked image to use a system in which the complete setup is contained inside the install.wim file. This is also the reason why the image is not bootable: setupldr.bin tries to load the WinPE from a non-exsisting index in the install.wim. A simple workaround is to [start the setup from another build's WinPE](/diskpart).
This is the fist leaked image to use a system in which the complete setup is contained inside the install.wim file. This is also the reason why the image is not bootable: setupldr.bin tries to load the WinPE from a non-exsisting index in the install.wim. A simple workaround is to [start the setup from another build's WinPE](/diskpart/).
Build 4039 is one of only a handful of builds that have the 3D view option in the view menu. Both Panorama and Carousel can be unlocked by adding registry keys, however when Carousel view-mode is chosen no icons will be displayed. Also, this build includes DWM and, when started successfully, adds nice window borders. Explorer tends to render windows very slowly.
......
---
title: "4040.Lab04_N"
type: build
url: /builds/4040
url: /builds/4040/
build_tag: "6.0.4040.0.Lab04_N.030828-1910"
build_arch: [ "x86" ]
build_m: 6
......
---
title: "4042.Lab06_n"
type: build
url: /builds/4042
url: /builds/4042/
build_tag: "6.0.4042.Lab06_n.030909-1709"
build_arch: [ "x86" ]
build_m: 7
......
---
title: "4044.Lab06_n"
type: build
url: /builds/4044
url: /builds/4044/
build_tag: "6.0.4044.0.Lab06_n.030915-1925"
build_arch: [ "x86" ]
build_m: 7
......
---
title: "4051.idx02"
type: build
url: /builds/4051
url: /builds/4051/
build_tag: "6.0.4051.0.idx02.031001-1340"
build_arch: [ "x86", "amd64", "ia64" ]
build_m: 7
......@@ -10,7 +10,7 @@ install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
featured_image: hd.png
---
This build was given out to attendees of the _Professional Developers Conference_ (PDC) 2003 and is the very first version of Longhorn to be released by Microsoft publicly. Build 4051 was lacked most, if not all, interesting bits shown by [Hillel Cooperman using a 4050 compile](/guide/4050-xx). As such it lacked Aero Glass and Aurora in the preview pane. Slate was introduced as temporary substitute for the Aero theme. Microsoft representatives commented on this fact that the Aero look was still in development and under heavy security. Only a select group of developers had access to the true Aero theme. Note that this build is an _idx02_ branch compile which means it has sub-beta quality. This build is infamous for its memory leaks.
This build was given out to attendees of the _Professional Developers Conference_ (PDC) 2003 and is the very first version of Longhorn to be released by Microsoft publicly. Build 4051 was lacked most, if not all, interesting bits shown by [Hillel Cooperman using a 4050 compile](/guide/4050-xx/). As such it lacked Aero Glass and Aurora in the preview pane. Slate was introduced as temporary substitute for the Aero theme. Microsoft representatives commented on this fact that the Aero look was still in development and under heavy security. Only a select group of developers had access to the true Aero theme. Note that this build is an _idx02_ branch compile which means it has sub-beta quality. This build is infamous for its memory leaks.
### Gallery
......
---
title: "4066.main"
type: build
url: /builds/4066
url: /builds/4066/
build_tag: "6.0.4066.0.main.040226-1010"
build_arch: [ "x86" ]
build_m: 7
......
---
title: "4067.lddm_dev_tech"
type: build
url: /builds/4067
url: /builds/4067/
build_tag: "6.0.4067.0.private/lddm_dev_tech(davidmo).040212-1646"
build_arch: [ "x86" ]
build_m: 7
......
---
title: "4074.idx02"
type: build
url: /builds/4074
url: /builds/4074/
build_tag: "6.0.4074.0.idx02.040425-1535"
build_arch: [ "x86", "amd64", "ia64" ]
build_m: 7
......@@ -10,7 +10,7 @@ install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
featured_image: window-overview.png
---
This is the best known Longhorn build, it is generally known as the 'WinHEC 2004' build as it was given out there. It is from the Milestone 7 stage, still features the Slate theme, but with an updated wallpaper known as <i>Leaves.</i> It also contains a new theme called Jade and retains Windows XP's Luna as well as Windows Classic. This build also had a few cosmetic changes, like new icons in the Start Menu and Explorer. Windows Media Player has not been updated, however, Windows Messenger did get upgraded to 6.1 which changes the look. Creating new folders has been 'disabled' in this build. Applying the registry key below will enable folder creation.
This is the best known Longhorn build, it is generally known as the 'WinHEC 2004' build as it was given out there. It is from the Milestone 7 stage, still features the Slate theme, but with an updated wallpaper known as _Leaves_. It also contains a new theme called Jade and retains Windows XP's Luna as well as Windows Classic. This build also had a few cosmetic changes, like new icons in the Start Menu and Explorer. Windows Media Player has not been updated, however, Windows Messenger did get upgraded to 6.1 which changes the look. Creating new folders has been 'disabled' in this build. Applying the registry key below will enable folder creation.
{{< highlight reg >}}
Windows Registry Editor Version 5.00
......@@ -19,7 +19,7 @@ Windows Registry Editor Version 5.00
@="Folder"
{{< / highlight >}}
A modified ISO has been released by Savoury and PandaX on BetaArchive in November 2011. This repack is known as TWIWMTB, short for _The Way It Was Meant To Be_. This repack includes a fully working Aurora Preview Panel Animation (APPA) and some minor fixes. TWIWMTB also has a DWM theme with transparency pre-installed. You can add APPA and Aero Glass to your vanilla Longhorn 4074 installation by [following this tutorial](/aurora-aero).
A modified ISO has been released by Savoury and PandaX on BetaArchive in November 2011. This repack is known as TWIWMTB, short for _The Way It Was Meant To Be_. This repack includes a fully working Aurora Preview Panel Animation (APPA) and some minor fixes. TWIWMTB also has a DWM theme with transparency pre-installed. You can add APPA and Aero Glass to your vanilla Longhorn 4074 installation by [following this tutorial](/aurora-aero/).
#### 64-bit
A 64-bit compile of this build is also available. As with the 4051 one, it still uses the i386 installation method but the basic VGA Driver has been updated so it works better after installation. As with the previous version, desktop applications and some Explorer dialogs are not included as well as the Sidebar.
......
---
title: "4083.main"
type: build
url: /builds/4083
url: /builds/4083/
build_tag: "6.0.4083.0.main.040516-1537"
build_arch: [ "amd64" ]
build_m: 8
......
---
title: "4084.main"
type: build
url: /builds/4084
url: /builds/4084/
build_tag: "6.0.4084.0.main.040527-0915"
build_arch: [ "x86" ]
build_m: 8
......@@ -12,7 +12,7 @@ install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
Very empty build, most interesting features had been removed by this time to implement them again one by one over time. WinFS has been cut in this build. None of the required services is present after installation, even the libraries are gone from Computer.
### Fixes
The setup fails to format the disc before copying files which always results in a "An error occurred while preparing the install drive" exception. This error is causd by a missing dll in the WinPE sector of the install.wim, _vssapi.dll_. An easy workaround is to [partition and format the drive from another build's WinPE](/diskpart).
The setup fails to format the disc before copying files which always results in a "An error occurred while preparing the install drive" exception. This error is causd by a missing dll in the WinPE sector of the install.wim, _vssapi.dll_. An easy workaround is to [partition and format the drive from another build's WinPE](/diskpart/).
After the first stage you will need to edit `C:\Windows\System32\onlinesetup.cmd`. Remove the lines listed beneath.
......
---
title: "4088.lab02_n"
type: build
url: /builds/4088
url: /builds/4088/
build_tag: "6.0.4088.0.Lab02_N.040706-1655"
build_arch: [ "amd64" ]
build_m: 8
......@@ -11,4 +11,4 @@ install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
Leaked 13 January 2015, this is the most recent public Longhorn leak. Although similar to neighbouring builds, it show some minor changes. Before this time only a WinPE build with the same version number was publicly available lacking the install.wim which made installing impossible.
In contrast to [build 4084](/builds/4084), WinFS is present again. Even though the WinFS services are actually installed there is no way of starting them. You will either get "Error 107:5: The dependency service does not exist or has been marked for deletion" or "Error 1067: The process terminated unexpectedly". Searching will result in a crash of explorer.exe.
\ No newline at end of file
In contrast to [build 4084](/builds/4084/), WinFS is present again. Even though the WinFS services are actually installed there is no way of starting them. You will either get "Error 107:5: The dependency service does not exist or has been marked for deletion" or "Error 1067: The process terminated unexpectedly". Searching will result in a crash of explorer.exe.
\ No newline at end of file
---
title: "4067.lab06_dev_ux"
type: build
url: /builds/4089
url: /builds/4089/
build_tag: "6.0.4089.0.private_lab06_dev_ux.040721-1800"
build_arch: [ "x86" ]
build_m: 8
---
A single screenshot of this build was leaked as a _Christmas gift_ at AeroXP. The screenshot shows us a Movie Maker 3 prototype which is much the same as the prototype found in [build 4093](/builds/4093). Note that this is a privately built build.
\ No newline at end of file
A single screenshot of this build was leaked as a _Christmas gift_ at AeroXP. The screenshot shows us a Movie Maker 3 prototype which is much the same as the prototype found in [build 4093](/builds/4093/). Note that this is a privately built build.
\ No newline at end of file
---
title: "4093.main"
type: build
url: /builds/4093
url: /builds/4093/
build_tag: "6.0.4093.0.main.040819-1215"
build_arch: [ "x86" ]
build_m: 8
......@@ -9,4 +9,4 @@ install_date: "2004-08-20"
install_key: "TCP8W-T8PQJ-WWRRH-QH76C-99FBW"
---
Often labelled as the most unstable pre-reset build this build is actually surprisingly usable and even features like WinFS are present and working. This build can be seen as a last salute of the developers to Longhorn in its pre-reset state. Presumably, this is also why this build is packed with features. Only hours after 4093's compilation the main branch refreshed its source tree with the much stabler code from the _dnsrv_ branch ([read 3790.1232](/builds/3790)). The original leaked image of this build was heavily modified. We released a proper image since which can be found [here](/fixed-version-4093).
\ No newline at end of file
Often labelled as the most unstable pre-reset build this build is actually surprisingly usable and even features like WinFS are present and working. This build can be seen as a last salute of the developers to Longhorn in its pre-reset state. Presumably, this is also why this build is packed with features. Only hours after 4093's compilation the main branch refreshed its source tree with the much stabler code from the _dnsrv_ branch ([read 3790.1232](/builds/3790/)). The original leaked image of this build was heavily modified. We released a proper image since which can be found [here](/fixed-version-4093/).
\ No newline at end of file
---
title: "5000.vbl_core"
type: build
url: /builds/5000
url: /builds/5000/
build_tag: "6.0.5000.0.vbl_core.040803-2000"
build_arch: [ "x86" ]
build_m: "Omega-13"
......
User-agent: *
Disallow:
\ No newline at end of file
.avenir, .athelas
{
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
}
.nested-img img
{
width: auto;
max-width: 100%;
margin: 0 auto;
}
\ No newline at end of file
static/images/header-01.jpg

291 KB | W: | H:

static/images/header-01.jpg

98.9 KB | W: | H:

static/images/header-01.jpg
static/images/header-01.jpg
static/images/header-01.jpg
static/images/header-01.jpg
  • 2-up
  • Swipe
  • Onion skin
Subproject commit bcaa83b7ad58ab539cf52a8e4786d55bdf1ac543
Subproject commit 11246e470dedf8e563af4e215f388ce2bcc4685a