|| Friday, 30 September 2005
Not only is Standby not possible since initial installation, now even Hibernate balks at my sincere request for cooperation:
Not that it worked great before - the last hibernation took almost three minutes for 1GB of memory. The XP installation on the same box still works fine... I have the sinking feeling I am in for more "surprises".
Application note: Forgot to mention that Daemon Tools wouldn't install, but that I almost expected.
Update Longhorn experiment terminated. It hung with not even Ctrl+Alt+Del reacting any more. Looks like something went awfully wrong with my installation.
|| Wednesday, 28 September 2005
I arrived late yesterday in Seattle after a total flight time of 14 hours. If only Lufthansa were offering a direct connection from Munich. Well. At least another MVP had to endure the same route with me: Christian Wenz.
Learned another lesson about Longhorn yesterday in the hotel: if you have installed ISA client, and are not connected to the network it was configured for, it will balk at being disabled! Only way to straighten this out was uninstalling the firewall software. Guess I will be having some more fun in the next weeks of self-imposed Longhorn testing.
|| Monday, 26 September 2005
Seems that I found another application that more or less breaks entirely on Windows Server Codename Longhorn: SharpReader. It does load the feeds and cache correctly, however, one thing does not work at all - refreshing the feeds. I'd say that this pretty much renders a RSS reader useless. Darn. Especially now that I got everything else up and running, including #develop 2.0 Codename Corsavy Build 510.
Update PEBKAC. I didn't install SP1 for .NET Framework v1.1. Now SharpReader works as expected. Note to self: having a WSUS server up and running for your other boxes really can spoil your Beta experience.
In preparing my laptop for Seattle, I had to copy my SharpReader configuration, which lives in Documents and Settings\<username>\Application Data\SharpReader on my XP box. I did that many times before, however, this was the first time for Longhorn. Again, I was in for a surprise - first, it is now AppData, second, there are two renditions: Local and and Roaming.
I picked the correct one by chance (Roaming, although Administrator is a local account). Seems I have to learn a lot more about Longhorn than I previously thought.
For those of you also going to Seattle, you should read UF's The Lord of the Rings.
|| Sunday, 25 September 2005
I already have one box (the Shuttle XPC) that is running Windows Server Codename Longhorn Build 5219. Because it wasn't all that much of a hassle when compared to Beta 1 of Windows Vista, I decided to set up Longhorn on my laptop - and try to work with that installation for a week, while I am in Seattle for the MVP & AspInsiders summits. Boy did I end up with an installation marathon...
Lessons learned in this Sunday's "don't try this at home kids" department:
- Don't assume that ATI drivers for your IBM X31 will install on Longhorn. They refuse, making for rather crappy UI performance. By the way, on failing, setup suggests to install a VGA driver first.
- None of the network adapters were found - neither the onboard LAN, nor the onboard WLAN. When you peek into Computer Mangement, it is your guess which of the two "Ethernet Controller" is which.
- Don't only update the driver for one, even if it is the LAN one. Your ISA 2004 client installation will mysteriously fail. After installing drivers for all LAN equipement, it just works.
- Minor annoyance: the OS-provided sound driver produces hisses et al. Not too bad, but annoying if you plan to watch loads of Channel 9 movies. Your guess is correct: the vendor-provided driver refuses to install.
- No standby. That sucks royally.
- You learned about that in my previous post - no .NET 1.1 for you by default.
- Installing VS can be so much fun, especially if MSXML 6.0 refuses to install as part of the default install. Doing it separately works so much better. And the "Locate File" dialog for the VM driver irritated me only for the better part of a minute...
- Before installing the Atlas VSIs, you better start VS at least once. Otherwise the Atlas installation will fail. Only mildly interesting.
- Do I need to mention that Virtual PC networking doesn't work? That one didn't change for the better, which will make me dual boot into XP.
On a different note: default installs of 5219 have a blank password for Administrator. And IIS 7 is installed by default, which really baffled me. I'm so trained to enable features after install that at first I was thinking it was not part of the bits I got...
Seen today on Windows Server Codename Longhorn, Build 5219 (the PDC build). At first, I thought Paint.NET was kidding me, but once I checked with Windows Explorer, I knew this was for real. Doh!
|| Wednesday, 21 September 2005
Before PDC, I decided I'd need a new PC for testing purposes - Team System (Beta 3 coming soon), IIS 7.0 on Longhorn Server as well as Windows Vista definitely do run a lot faster when not in VirtualPC. That's what I got myself:
That's a Shuttle XPC SB81P, a Pentium P4 630 (3Ghz, 2MB Cache, FSB800), 2GB of RAM, a 250GB WD SATA HDD and one of my old DVD-RAM drives. Nice setup, and not too expensive either.
|| Tuesday, 20 September 2005
Before heading to PDC, I got my new cell phone - the Sony Ericsson W800i. Hence I didn't have time to put it through the paces, which I then did the past couple of days (how shocking: I never bring my cell phone to the USA). What a difference from the SPV C500! It has great battery lifetime, it starts up really fast compared to the C500, and important functionality is easy to reach.
There are a couple of smart technical choices that I love: for one, the wired headset comes in two parts - one connects to the cellphone and has the mike, the second part connects to the former using a standard stereo jack. Read: I can use my excellent Etymotic ER 6 with it! For phone calls, listening to music (it is after all an MP3 player shipped with a 512MB card in the box) as well as listening to the radio (yep, can do that too, nice touch).
It comes with a USB cable, and it connects to your PC by default as a mass storage device. No need for special software if you want to transfer files - how cool is that? (I already thought about abusing it as a "toolbox" instead of a USB memory stick) If you want to sync with Outlook et al, that is still possible - but you then need software (included). And of course the phone is being charged when connected to USB. Having to install ActiveSync so my C500 would charge annoyed me royally.
The only snag so far: you can use WAV files for ring tones, however, when trying to assign them to individual contacts they are not shown - they are filtered out. For the general ringtone it works fine. Definitely a bug, but not a real issue: Audacity to the rescue I converted the WAV files to MP3.
Finally, the design. My brother's opinion: "schwul" (faggy). I have to agree - white seems to be a real bane since Apple entered the scene of digital lifestyle accessories.
demonstrated it last week at the PDC, now he released the new version of the Web Development Helper
to the public. Read more about the exciting new features here
|| Sunday, 18 September 2005
The Seattle Post Intelligencer has the by far best analysis on the "Mono BOF" at the PDC - read it here (Builder UK article for contrast). From the marketing aspect of the BOF refusal to the impact Mono will have to shops that bought into Windows (zilch, that is), those two articles cover all bases.
Especially the one I also like to point out: Mono will always play catch up with .NET (unless the development pace at MS slows down, but there was no such sign at this year's PDC). I had to laugh out loud when the Seattle PI quoted Somasegar as saying that "it's [Mono] a good science experiment that is happening there". And a warning that if it eats into their revenue, they will reconsider their current position. Given that Mono not only implements the ECMA standard, this certainly is an option. Taking further into consideration that MS sure as hell won't risk a class action suit from shareholders growling about lost money because of Mono, this is a threat scenario the Mono project better prepares for.
Before you flame me for the previous paragraph: I am project manager on the open source #develop project, so spare me the FUD blames. Especially if you are IANAL.
© Copyright 2017 Christoph Wille
newtelligence dasBlog 2.3.9074.18820