The return of Windows

Thursday, January 3rd, I finally got around to re-installing Windows on my work laptop (yes, this post has taken a while to complete). I decided on Vista over XP, because I know that I will have at least one virtual machine running Windows XP with our "base" software configuration. If I still want to keep playing with Linux, I can also run it in a virtual machine, although I probably won’t be able to utilize fun stuff like compiz. Just like the last time, I had a pain in the ass trying to find the drivers for my laptop’s hardware. Specifically, I had trouble finding the Bluetooth drivers and the updated drivers for several devices. Read on to find out more about my continuing journey to setup my work laptop, starting with my trouble activating Vista.

After I installed Vista, I was prompted to activate it, despite having the Ultimate version (no activation-free versions like with Windows XP). Unfortunately, because I had to replace my motherboard and processor due to heat issues, Vista assumed I was using my product key to activate a second computer. In order to complete my activation, I had to spend almost ten minutes on the phone talking to someone with a heavy accent that even I had trouble understanding. I had to explain that my motherboard was replaced under warranty, and that I was not, in fact, trying to activate a second computer. I promised that the key would only be in use on a single computer, and then we exchanged 54-digit codes to activate my copy of Vista Ultimate. It was not a difficult task, but it was definitely a huge pain in the ass. I wonder how much MS has to shell out for these overseas call centers versus the estimated loss in profits due to casual misinterpretation of the meaning of the terms of the EULA. With Windows activated, I felt I could continue my journey with hardware drivers.

It took me a few hours to pinpoint all of my updated drivers. For some reason, Vista did not recognize my Bluetooth adapter, despite it being a common chipset from Broadcom. Ironically enough, once I located a Bluetooth driver, I decided to ditch my Microsoft Desktop Elite for Bluetooth in favor of my old Logitech Cordless Desktop Comfort Laser. The Microsoft set was continually plagued with disconnects, as well as a glitch where the keyboard would act as if a key were stuck pressed down. This had resulted in the deletion of written text and many messages from my inbox. Luckily, I was able to undo the damage most of the time. My main use for Bluetooth has been to transfer files to mobile devices anyway, and with that capability restored, I am fine not dealing with the Bluetooth input devices and their problems.

With the OS and drivers installed, I moved on to installing applications. So far, this has included MS Office 2007, cygwin, Firefox, Thunderbird with Lightning and the Provider for Google Calendar, Lotus Notes on a USB drive, Virtual PC 2007 and VMware Server Console. I have plenty more to install. Hopefully I will be back to a great setup soon.

3 Responses to “The return of Windows”


  1. 1 Grant

    Does the Provider for Google Calendar work well for you?

  2. 2 Mark

    @Grant: So far it has worked out pretty well for me. I have been able to attach to all of my Google calendars. I can update or create a calendar entry in Lightning, and it will post to Google calendar almost immediately. The one caveat is that I believe that I do have to be online to view the calendar. I do not know if there is a synchronizing feature that will sync with my local calendar. It hasn’t been a problem because I am rarely looking at my calendar without an internet connection.

  3. 3 Scott

    @Invisible Guy: Dude I cant see you.

Leave a Reply

Note: This post is over 5 months old. You may want to check later in this blog to see if there is new information relevant to your comment.