I leaving shortly for Den Haag for the first installment of the Longhorn Developer Preview Tour throughout Europe as part of the Dutch Developer Days 2004. We start tomorrow and I am quite excited since this is the first time I will speak about Indigo in any detail to a larger audience. I've witnessed Indigo "forming" from a distance when the team was still in "stealth mode" and it's great to see how it comes along.

But be forewarned: In my talk there will be no live demos. I have 75 minutes for the talk and I had to decide whether I concentrate on explaining the "M5" milestone that is currently in development in Redmond and which implements the (likely) final programming model or whether I allocate more time to the M4 model found in the PDC build. The decision that I made was that M4 is so different from M5 that unless you want to get a major degree in Longhorn development history or have way too much time on your hands, learning and therefore showing M4 code is almost pointless. I will show code, but it won't run.

If you want to check out how this first run of my talk goes (as usual, I don't really rehearse talks so this is as spontaneous, "fresh" and probably embarrassing as it gets on this tour), Microsoft Netherlands will have a live webcast tomorrow that you can log into at http://www.microsoft.com/netherlands/msdn/devdays/webcast.asp.

I am getting ready for the Longhorn Developer Preview tour. Now that the whole notebook ordeal is hopefully over, I have been and still am polishing slides and we'll have an online rehearsal today during the day. Furthermore, we're working with Microsoft EMEA on a two day workshop about writing service oriented applications that consolidates all the thinking that I've been blogging about in the past year. The "sample" around which the workshop will center is, not very surprisingly, the FABRIQ.

I really need to get back into a "blogging mood".

To expect that the newest hardware works with a pre-Alpha version of the newest Microsoft operating system may be expecting a bit much. My Alienware Area51-m just wouldn't boot past the logo screen just 3 seconds after booting from the install disk. It just hung. Bummer.

To expect that a hardware vendor, especially one that's comparatively small and which is specialized in gaming machines and therefore very consumer focused, would even consider providing support on that issue is hopeless.

Is it? Well, usually it probably would be, but not with Alienware. Their tech support simply rocks. And with their help and help from the Longhorn Evangelism team in Redmond, Longhorn is now finally running on my new notebook.

The problem of the Area51-m not booting Longhorn is an unfortunate combination of a more BIOS-sensitive bootloader in Longhorn compared to XP/Win03 and a bug in current production AMIBIOS (AMIBIOS8, 1.09) that Alienware puts on their machines. Once we had that identified and I got the same fix that the Longhorn Evangelism team got for their Alienware machines (they have them too), flashed the BIOS and Longhorn booted.

Done? Unfortunately not. What I found was that this particular "special fix" BIOS version (1.08.01) would work stably with Longhorn and Win03 only when the machine is on AC power. Once you unplug and run on batteries, both OSses bluescreen after about 10-15 seconds.

Because this is my primary machine, I must have the machine running on batteries and therefore I re-flashed the BIOS back to the production version (1.09) so that at least Win03 would work and for Longhorn demos I'd just re-flash down to the other BIOS. Once done, I rebooted the machine and it happened to boot into Longhorn. And worked. Why would the installer hang so early on this BIOS version but the OS just boots fine once installed?  Puzzling.

So after all this had been sorted out, I figured that Longhorn isn't a good idea to have on the D: drive, after all. It does work, but I'd have to adjust a lot of demos and that's just too much work. So I am installing Win03 and Longhorn once more right now in the following sequence: BIOS 1.09 > Win03 to D: > "special fix" BIOS 1.08.1 > Longhorn to C: > BIOS 1.09. Now that we've got this sorted out, Alienware will hopefully have a permanent fix for the production BIOS soon so that this step becomes unnecessary and so that others can get Longhorn installed on their Area51s as well.

On the Longhorn tour, we'll have two of these boxes as our demo machines. Although they are absolutely swamped right now, Alienware made it possible to provide a system for Microsoft on very short notice, so that we don't have to carry a rather massive desktop PC around on "this 13 cities in 13 consecutive work days" tour as was initially planned.

Now I need to work on my backlog.

So my new notebook is an Alienware Area-51m. It's really, really fast, and looks great, but as of now, it doesn't get past the boot screen when I try to install Longhorn. The Longhorn boot screen starts fading in and the machine locks up. Win03 and XP work just fine ("great!" I should say). So I am sitting here, fiddling around with the install options and I am suspecting that something in the BIOS isn't quite like Longhorn expects it to be. To be continued ...

Blah, Blah ... "...if someone is using it who doesn't have a clue. Just like us."  Dismissing vulnerabilities in any operating system like that just to turn around and bash Microsoft while they're at it is just idiotic.