see more Lolcats and funny pictures

One of my favorite Firefox add-ons is FireFTP. I use it all the time because it’s very convenient to FTP from my browser rather than firing up a separate application. That and FireFTP just works really well for me.

I went to transfer some files last evening and as soon as the transfer started, Firefox crashed. This isn’t something that happens on a regular basis, but I figured it was a glitch and restarted Firefox. Started FireFTP, connected to the web site, initiated the transfer and…another shower of sparks and the dreaded “Firefox has crashed” dialog.

Everything had worked fine last week, so I started taking inventory of what had changed since then. After a bit of thought, I realized I had installed an application called Surfboard Technologies Tracking Application on my system as part of a survey I was taking.

Step 1: get rid of the Tracking Application! I like my system setup the way it is and won’t go back to using a separate FTP application in order to accomodate badly behaved software. So, I brought up Control Panel, clicked on Programs and Features (yes, this system runs Vista ) and looked for “Surfboard”. I found the entry, clicked on it and clicked Uninstall.

Some 30 minutes later, the dialog was still there saying “Please wait while Windows configures Surfboard…blah, blah, blah”. The hard drive activity light was showing a lot of activity, so I started to wonder what the uninstall process was actually doing. I clicked the Cancel button. The dialog sat there pretty much as before.

I decided to find the process and kill it, so I ran SysInternals’ very handy Process Explorer and searched for “Surfboard” among the running processes. I found a number of entries which told me that the actual executable name is PanelApp.exe. I also got the process ID so with that I went back to Task Manager and found the ID matched up with msiexec.exe. I killed the process and the dialog went away.

The Surfboard app was still showing in Programs and Features, so I knew it hadn’t completed the uninstall process. To keep it from starting up again, I found the directory where PanelApp.exe lived (c:\users\name\AppData\Local\ of all places!) and renamed it to PanelApp.old. I also started up msconfig, found PanelApp in the list of startup programs and disabled it there. I then rebooted the machine.

Now that the Surfboard Tracking Application wasn’t running any more, I tried Firefox again and it crashed again when FireFTP started a file transfer. Firefox immediately crashed. I ran Process Explorer again to see if there was something running that I’d missed. Sure enough, I found that Surfboard had added an add-on to Firefox called PanelApp BHO. I clicked the add-on and was given the option to Disable, but the Uninstall button was greyed out. I clicked Disable, restarted Firefox and tried FireFTP again.

This time I was able to get a clean file transfer so the problem obviously was the PanelApp BHO add-on. So, with that out of the way, I tried the uninstall again from the Control Panel.

I started the uninstall and let it run while I did some other things. Finally, I went to bed and left the system running. The dialog was still there in the morning “configuring…”! I went into Task Manager, killed the process and noticed that the dialog flashed a message of some kind just before it closed.

I checked Programs and Features and the Surfboard entry is gone, so the uninstall process at least got that far. The add-on still shows up in the Firefox add-on list, but I’ll get rid of that, too.

Needless to say, I’m not a big fan of Surfboard Technologies right about now. Just a word of warning if you’re presented with the opportunity to install it on your machine. My advice is don’t!

John The Geek

You may have heard by now that the Microsofties have installed a Firefox add-on along with the .Net 3.5 update distributed some time ago. I was not aware of it until I checked this weekend and found that all my machines have the Microsoft .Net Framework Assistant 1.0 listed in the Add-ons in Firefox.

I’m not quite as bent out of shape about it as others are, but it is annoying that Microsoft took it upon themselves to add something to Firefox that I didn’t request. Even more obnoxious is that the Uninstall button is grayed out and not usable. Worst of all, installing this add-on opens up Firefox and my PC to security vulnerabilities of the .Net framework! See the latest edition of Windows Secrets newsletter for more details on that little bonus.

I keep wondering when Microsoft is going to learn. If you go ahead and do something without giving the user the option, it simply pisses people off. If you give them the option to install and the option to uninstall, many people will be okay with it. The whole key is to allow users to retain control of their PCs, or at least the illusion of control.

I’m not going to add to the general ranting about the arrogance of Microsoft. That’s already well documented. The good news is that there is an update to the .Net update that enables the Uninstall button and allows the Microsoft .Net Framework Assistant to be uninstalled. You can download the fix from Microsoft’s web site.

If you’re a Firefox user, my recommendation is to check your Add-on list to determine whether the Microsoft .Net Framework Assistant is installed. If it is and the Uninstall button works, uninstall it. If the Uninstall button is greyed out, download the update and run it, then Uninstall the add-on.

John The Geek

As I mentioned about 8 months ago, I purchased an HP MediaSmart Server with the intention of making it the hub of my home network. It’s been a bit of an interesting ride, so I thought I’d bring you up to date on that project.

The box came with 512MB of RAM and a 500 GB hard drive. I knew 500GB wasn’t going to be enough to backup my existing computers, much less provide any additional storage, so I bought a 1TB internal drive along with the machine and installed that right after the initial setup, giving me a total of 1.5TB of storage.

I moved my music files and some other archives to the home server to free up some space on my main desktop machine, but otherwise, just set up that machine, my laptop, netbook, and my wife’s laptop to be backed up to the home server nightly. I’ve since replaced the desktop machine, but not before copying its data to the home server.

As a storage platform and automatic backup system, the home server works pretty well. I created shares on the server for music, photos, software installs, and user data then mapped drives on each of the machines to those shares. Windows Explorer simply sees them as drives and file transfers are quick and easy via the network.

I’ve learned a few things along the way, some of which were surprising. The big surprise was learning that if you let Windows automatically update on the home server it will spontaneously reboot itself when the update calls for it. I’ve since told it to download the updates and let me know they’re ready. I had hoped to be able to work on documents directly on the server, but this little “feature” makes it necessary to have a copy on the local machine and update the server as changes are made.

The first time I encountered this one I was, of course, in the middle of editing a document that was stored on the server. I was able to recover without a major data loss, but it was not one of the fonder memories I have of the home server! I had thought perhaps setting the Windows updates to notify instead of automatic would eliminate the problem, but no such luck. It still reboots occasionally, although it’s always around midnight so if I’m paying attention I can anticipate it.

Another thing I learned was that the server is a real worry wart! There are three status levels: normal/healthy (green), needs attention (yellow) and “Omigod the sky is falling!” (red). The latter is accompanied by dire messages like “your network health is critical!” Not only that, the normally blue status LED on the front of the box (which stays blue in “condition yellow”, go figure) changes to red, apparently to get your attention.

There are all kinds of things that trigger a yellow alert. If a machine known to the server hasn’t been backed up in 7 days or more, warning messages begin displaying saying “[name of machine] hasn’t been backed up since [date of last backup]. Your network health is at risk!” Since my machines aren’t all turned on and connected to the network 24/7, this happens a lot.

When this situation occurs, I have three choices: ignore the incessant warning messages, connect the designated machine to the network and back it up, or go into the Home Server Console and tell it to ignore the situation. If a machine isn’t likely to be used for a while, I’ll do the latter just to shut the server up and hopefully turn the yellow tray status icon back to green, at least for a while.

It becomes a sort of game to see how long you can keep the status icon green. You have to become resigned to the fact that it will be yellow quite often. There’s almost always something the thing isn’t happy about!

There’s apparently something a little flakey about my 1TB server hard drive. The past couple of months I’ve been getting “File conflicts” messages. These are yellow alerts, too. File conflicts are not a good thing, and in my case have been indicating that there’s an error on the hard drive. Maybe it’s a bad sector, maybe something else, I’m not sure and I haven’t had the time to dig into it and diagnose it properly.

I’ll occasionally get a red alert that the drive is “unhealthy” which tells me to “repair” it. Back to the Windows Home Server Console to run the Repair function on the drive. This is very likely good old CHKDSK, but it does seem to repair the problems which warning about possible data loss. A successful repair will turn the status icon green…until it discovers that the file conflicts are still there.

This last time, it was a set of four files which apparently were listed in the directory but didn’t really exist. I went in to the share on a connected machine and deleted them. That wasn’t good enough, the file conflict messages continue. The drive reports healthy, however, so there’s no option to run Repair again. –sigh–

I’ve mentioned the Windows Home Server Console. This bit of software until recently took performance to a new low. I’ve seen glaciers move faster!

Seriously, the login nearly always failed the first time (“Cannot connect to your server”). Clicking the OK button generally logged in, but it took several minutes for that to happen. Once in, clicking on any of the toolbar buttons required waiting another few minutes (not seconds, mind you, minutes!). Eventually, something would happen as a result of the mouse click, then the cycle would start over again if another mouse click was needed.

In trying to troubleshoot that phenomenon, I learned that you can access the server via Remote Desktop just like a “real” Windows machine! Doing so, however, is less productive than you might think. For one thing, when you log in, Internet Explorer pops up and delivers a dire warning that bypassing the WHS Console can have dire consequences (you could screw something up royally) and you really shouldn’t be doing this. Suffice to say that working directly in the server is not for the faint of heart and you’d better know what you’re doing to avoid catastrophe.

Within the past several weeks, the WHS Console has magically become fairly usable. Gone are the multi-minute reaction times. While performance is nowhere near snappy, it’s at least tolerable. You know that when you click something, you’ll see a response in this lifetime. The login even works the first time…usually. Whoever fixed this has my undying gratitude!

The MediaSmart Server isn’t really designed to be what I had in mind, but I’m adapting to it. If nothing else, the automatic backups are a major plus. Now I just have to implement a plan to backup the server itself!

John The Geek

As some of you may already know, the Conficker worm is due to begin contacting its “home base” for instructions on April 1, 2009. It is estimated that this worm has infected millions of PCs worldwide.

Windows Secrets has published an in-depth article on how to secure your PC from the Conficker worm and what to do if you already have it. I strongly suggest reading this article and taking the recommended steps to avoid having your PC contribute to the problem:

http://windowssecrets.com/2009/03/30/01-Run-a-Conficker-removal-tool-before-April-1

John The Geek

The latest paid version of the Windows Secrets newsletter contains an article by editor Gizmo Richards touting the superiority of Windows Vista over Windows XP. Sorry, gang, but I couldn’t resist. Below is the email I just sent to the Windows Secrets crew:

Hi, guys,

First, let me say that I have the utmost respect for Gizmo Richards and have been a subscriber to his TechSupportAlert newsletter for some time. In general, his reviews are helpful and accurate.

So, after reading the latest column under Gizmo’s byline regarding the alleged superiority of Vista over XP, I’ve gotta ask: who is that guy and what’s he done with Gizmo?

I’ve owned a Vista laptop for almost a year and been through the initial version as well as SP1. While I will admit there are a few things about the Vista interface that are actually improvements, in general, I’ll take XP over Vista any time. The big reason: it actually works! Things do what they’re supposed to do, even if they don’t look quite as cool.

Vista’s Wi-Fi management is terrible. XP’s Wi-Fi management is simple and straightforward. Vista wants to connect to whatever network it can find despite being told innumerable times to remove offending networks from its list. Sometimes it actually connects to my own network on the occasions when the random-order generator puts it at the head of the list. In these days when virtually every Internet user has a Wi-Fi network broadcasting all over the neighborhood, the list of networks Vista finds gets pretty long and there’s no way I can find to tell it to ignore all but mine and any others I’ve approved. At least XP only connects automatically to those networks to which I’ve specifically connected in the past AND in the order I specified.

Vista’s Windows Explorer apparently has a random view generator, as well. When I create a new directory, it’s a real adventure to see which view configuration it will decide is appropriate. The defaults have the file name…period. No date/time stamp, no size, no file type, all the things XP users take for granted. I carefully set the directory view the way I want it, go into the Tools | Folder Options menu and tell it to set that view for All Folders and the little folder gnomes inside must bust a gut laughing. The next time I go into a directory it’s decided to Group things!

What genius decided that it’s necessary to group my file listings by 0-9, A-H, etc? Alphabetical order is sufficient, thankyouverymuch.

Exploring in Vista is more exciting than ever because I can attempt to access certain directories and be told that I don’t have access to them. Excuse me? This is my machine and I’m the administrator thereof. By definition I have access to whatever I want access to!

Before you ask, of course I’ve turned off UAC, another stroke of genius by the Microsofties. Apparently, there were numerous meetings of the design team to find ways to make Vista as annoying as possible for users who have a clue. If I want a machine that insulates itself from me, I’ll buy a Mac.

I could go on, but suffice to say that I beg to differ with Gizmo on this one. The only reason I haven’t downgraded my laptop to XP Pro is a lack of the required time to do so. The real improvements in Vista are so few and so far outweighed by its stupidities as to be meaningless.

All the above notwithstanding, thanks for Windows Secrets and the work you guys do.

John The Geek