Longhorn build 3683 is the earliest 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 often missed/forgotten features present in this build.
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 history. If you came here looking for information about Aurora, please see my post about Aurora & Aero.
In this tutorial you will find everything you need to enable desktop compositing on the Longhorn builds that support it.
The original leak of Longhorn build 4093 from within Microsoft was broken and uninstallable. Prior to leaking the release to the public, the C0d3rz release group had attempted to repair the ISO and at least make it installable. While they loosely succeeded in this goal, the resulting product introduced a number of additional bugs and no effort had been expended to keep it as original as possible.
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 Milestone 3 builds. The tricks may not always work on later builds. That’s it for the intro.
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 components. 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.
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. What is that precisely?
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.
Multiple patents were filed by Microsoft for this sensational effect. One of the patents shows some detailed screens of what Phodeo is supposed to look like. These images closely resemble some concepts shown by Hillel Cooperman at PDC ‘03, but are, in fact, not the same. Where the user in Hillel’s demo was Jim, the user in this concept is called Steven. Also note that in the image below the window frame is visible, clearly identifying this as a mock-up created in Macromedia Director with the title “timeline demo”.
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:
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.
The RMA test tile already caused some discussion in the past and nobody has since figured out what it’s purpose is. This hidden tile for the sidebar in builds 4008 and up has no obvious functionality other than taking up space. In this article we will dive into the real meaning and function of the RMA test tile.