Is Microsoft deliberately trying to kill Vista?

As I twittered about a week ago, I’m upgrading from Vista to XP. Vista has become very unstable over the last year that I’ve been using it, and all the beta drivers and programs that I had to install to support 64 bit probably did their share of damage. Not to mention the WOW64 addition to the registry – what a pain in the behind that is. Service Pack 1 was a case of “too little, too late”: hardly any perceivable improvements. I don’t care if a lot of the improvements were “under the hood”: if I don’t benefit from it, directly or indirectly, it’s next to useless to me.

We (the company I work for, and probably everybody else that looked at Vista) installed Vista on the machines we got around this time last year, under the impression that XP was quickly going to be replaced by Vista. Dismissing the reports that Vista wasn’t all it was supposed to be, we installed it on 6 machines in our IT department. I actually was so bold as to install the 64-bit version, assuming that within a year, 64-bit would be the norm instead of the exception. Yeah right.

Not in Windows land. Apparently things move slower there than anywhere else on this planet. And that’s coming from someone born and raised in the Netherlands, that used to have the title that everything happened 25 years later there than in the rest of the world. I’ll ask the city of Redmond to come by and pick up that trophy. After a year, most programs I used to use are available in 32-bit versions (oh, Symantec: having a 32-bit application doesn’t do any good if the installer is frakking 16-bit!). Most programs. And the ones that are in 32-bit, don’t all support 64-bit Windows (as I found out when we were rolling out our ShoreTel phone system with accompanying clients).

One of the “improvements” of Vista would be its increased security. Much to my surprise I read an article a week or two ago, in which a product unit manager at Microsoft, David Cross, is quoted as saying that one of the security features in Vista was deliberately designed to “annoy users”, to put pressure on third-party software makers to make their applications more secure. I’m still wondering if amongst those applications were such gems as Microsoft Office, and not to forget Vista itself.

Then of course in the beginning of April was the commotion about a Windows 7 product announcement for 2009. Regardless of whether or not this announcement is viable or not (as is David Cross’ comment), if I run a company with 500 PC’s, and am faced with either upgrading to Vista now, or waiting another year or so and skip the Vista upgrade, I know what I’d choose.

On top of that, two analysts from Gartner describe Windows as “collapsing”, and claim that Microsoft must make radical changes to the OS or risk becoming irrelevant. Is this foreshadowing that Windows 7 will be better, or that Windows will be replaced by one of the competing operating systems (Apple OSX, Linux, etc)?

I’m with Dvorak on this one…

Blackberry Desktop crashes when reading Outlook calendar

For the past two days, my Blackberry Desktop software has crashed when it was trying to read the Outlook calendar entries. Rebooting didn’t help, and I really didn’t want to reinstall software and go through the pain of resynchronizing.

Luckily, the solutions was relatively simple. After Googling around for a bit, I came across this post on BlackberryForums.com, describing an easy and effective way to make my Blackberry’s calendar match my Outlook calendar (again).

The KB entry referenced (KB 11703 on the BlackBerry Technical Solution Center) describes the procedure for Windows 2000/XP. The procedure is similar on Windows Vista, the only difference is that the Intellisync folder is located at C:\Users\<user name>\AppData\Roaming\Research In Motion\BlackBerry\Intellisync. You don’t even have to reconfigure the synchronization settings – after deleting the Intellisync directory, start the Desktop Manager and synchronize your Blackberry.

But I have to agree with the post directly below the solution: I wonder what got it messed up to begin with…

Technorati Tags: , , , ,

100 Things people are really saying about Windows Vista

Microsplot has an interesting article contradicting Microsoft’s slogan “100 Reasons You’ll Be Speechless“. Au contrair, MS. People are talking more than ever about Vista, and not all of it is Wow.

Some of the items are not entirely Microsoft’s fault, such as not supplying disks with a new computer, but the majority of the issues are directly to be blamed on Microsoft. You can see a number of quotes from articles around the web for each of the points brought forward in the article.

The 100 things in a nutshell:

  1. Vista is a flop. A disaster. Dead.
  2. Vista is one of the 10 worst tech products of 2007!
  3. Vista is the most disappointing tech product of 2007!
  4. This took five years?
  5. What happened to all the promised features in Vista?
  6. Vista isn’t ready for release!
  7. Vista? Yawn.
  8. Vista? Why?
  9. Vista: The end of the Microsoft empire?
  10. Abandon Vista, Microsoft! [Read more...]

Don’t give up on Vista?

After all the Mac guy vs. PC guy videos, you might think they’re running out of ideas. Not so. This one is too funny (especially since I’m struggling with Vista every day…):

Kensington Bluetooth 2.0 under Windows Vista 64-bit

I finally got my Bluetooth adapter (a Kensington Bluetooth USB Adapter 2.0) working. Initially when I bought it, trying to install the factory supplied driver wouldn’t work. After a tiresome exchange with support, where they informed me that there was no Vista driver available, and they didn’t have any information about whether or not the driver would be developed.

Well, apparently they developed one (yay Kensington), but failed to inform people who had filed a request for it (Booh! Hiss!). However, when I tried to install it, everything seemed to work fine until a message box popped up informing me that the installation had failed. Digging through the Vista Temp directory, I found the installation log, with one Error message (the rest was fine): “ERROR Device plugged in, no MS stack”.

After trying to run the installation program with Administrative rights, and with UAC turned on and off, I was ready to give up. The funny thing was that the installation program just seemed to download the actual installation program, explode it, run the setup program in there, and delete it when it finished or failed. So, during a new attempt, I grabbed the directory that the installation program created. It has the platform specific files (in my case 64-bit), a setup program and some other stuff. Of course, the installation failed again, but at least I had the files now.
Update:The files are located in \Users\[you]\AppData\Local\Temp\BTW_6.0.1.6200.

When I pulled up the Device Manager in Vista, it showed the Bluetooth EDR dongle listed. I tried several different things (which I won’t mention, because they didn’t work), until I decided to Update the driver for the dongle. When Vista asked me for the driver, I pointed it to the driver directory within the exploded installation directory, and Vista was happier than a clam to install a bunch of devices (Kensington Bluetooth EDR Dongle with trace filter, Microsoft Bluetooth Enumerator, and two Bluetooth devices in the Network adapters group). Yay!

The next (and last) step in setting up the adapter with my Motorola RAZR was the easiest: go to Control Panel, Bluetooth Devices, and Add a new device. Make sure your phone is discoverable, and set up a passkey. Voila! The phone should now be connected.

Next thing on the list is trying to grab floAt’s Mobile Agent. I have an older version installed, and have already figured out that the only way floAt can talk to my phone seems to be to use the COM port (when you pull up Bluetooth Devices, click your phone, select Properties, and go to the Services tab, it will tell you which COM port the phone uses).