I ordered me a new hotsync cable for my Palm this morning. I wanted an extra so I could have one at work and one at home. The new one is a “BoxWave miniSync”:http://tinyurl.com/39a4t. There is a similar product called a “JavoSync”:http://tinyurl.com/yvhrb by JavoEdge. Both include a built-in changer (I’m pretty sure BoxWave’s picture is inaccurate).

The cables look exactly the same other than the logo emblazened on them, which leads me to believe they are outsourcing from the same as yet un-named company. They are both the same price, and I like green more than I like orange, so I went with BoxWave.

I’ll do a full review when it arrives in the mail. Stay tuned.

I just had an “Arby’s”:http://www.arbys.com/arb01.html Beef ‘n’ Cheddar with homestyle fries. Holy cow. Could anything be better? I’m having trouble thinking of anything off the top of my head. Arby’s beats Burger King and McDonald’s hands down. Their fries are the best, and roast beef is so much more refined than hamburger. Did I mention they have awesome shakes?

Man, I gotta get me some more o’ that.

I hesitate to write this review. I’m quite afraid that someone reading what I’m about to say might not want to try Firefox. Please don’t get the wrong impression. I absolutely love Firefox, and I whole-heartedly recommend it to _everyone_. The story below is simply what happened to me during an upgrade, and is not intended to reflect negatively on Firefox or the Mozilla Foundation in any way.

“Mozilla Firefox 0.9”:http://www.mozilla.org/products/firefox was released to the general public yesterday morning. I was so excited I could’ve wet my pants and not noticed. As soon as I knew it was available, I immediately went and downloaded it, taking care to check the release notes so I could avoid having a bad experience upgrading. Little did I know what was in store for me.

The “release notes”:http://www.mozilla.org/products/firefox/releases/0.9.html specify the following:

bq. *NOTE* – Do not install Firefox over the top of another Firefox installation. If you want to install Firefox 0.9 into the same folder that you had Firefox 0.8 in, uninstall Firefox 0.8 first. Upgrading will be fixed in a future release.

The release notes also specify that profile settings are now stored in the @Application Data/Mozilla/Firefox@ directory, rather than the @Application Data/Phoenix@ directory. In addition:

bq. If you were using Firefox 0.8 as your default browser prior to upgrading to Firefox 0.9, data from your profile will be copied into the new location. You can remove the old “Phoenix” folder at your leisure.

I followed all the noted precautions, but something must’ve gone wrong for me, because my profile settings certainly were not moved. I started using Firefox around version 0.6, so I’ve been through a couple of upgrades without any problems. My profile settings have always come through before. I figured it should be an easy matter to move (in retrospect, I should’ve copied) my profile settings from the old folder to the new and edit my @profiles.ini@ file, afterall, the release notes mentioned doing that (though now I realize that note was meant for people with a different, more specific problem).

All that seemed to accomplish was to break the display of certain key components of the browser, prompting me to believe that a few things have changed in the @chrome@ directory.

So, on the off chance that something had gone wrong during the install, I decided to move my profile settings back to the @Phoenix@ folder and reinstall Firefox 0.8. It took me a while to find the 0.8 install file, but upon installing it, my profile settings didn’t come back! It seems something in 0.9 had corrupted (upgraded) the settings so that 0.8 couldn’t read them.

Needless to say, I was quite ticked about the whole thing, since I have a number of bookmarks I need in order to perform my job functions.

I finally decided to start over with Firefox 0.9 (I had a co-worker send me many of the bookmarks I needed). I deleted all the leftover profile files, installed, and created a new profile from scratch.

The next step was to import the “Qute theme”:http://quadrone.org/projects/mozilla/browser/, since the new one is ugly as sin. The import simply didn’t work. “Qute” would flash up in the “Themes” window for a few seconds and then dissappear.

So I moved on to downloading my favorite extensions. I was able to download most of them, but upon downloading “Tabbrowser Extensions”:http://white.sakura.ne.jp/~piro/xul/_tabextensions.html.en and restarting my browser, I started getting XML parsing errors. Turns out there isn’t a version of Tabbrowser Extensions for Firefox 0.9, yet.

At that point, I was steaming, but I uninstalled and reinstalled, then downloaded the rest of the extensions I use (being careful to check if they were compatible with 0.9 first). Everything seems to be working fine.

Things have improved markedly since yesterday. This morning I was able to successfully install the Qute theme, and they’ve made changes to the extension download website. Now it only shows extensions that are compatible with the version you are currently using, which should prevent people from downloading incompatible extensions and getting the same errors I experienced.

Though it would’ve been nice for these things to have been in place before releasing 0.9, it is wonderful to see how fast the Mozilla team has fixed them. It’s great to use a free (open source) browser that is updated often. If you are still using Internet Explorer, get your head out of the sand! Do you realize your browser is three years old and only getting older? Firefox is the way of the future.

For a list of updates in version 0.9, check out The Burning Edge’s “Bigger Picture”:http://www.squarefree.com/burningedge/bigger-picture.html. I’m especially tickled about the new extension and theme managers, update notifications, CSS3 opacity, the smaller download size (4.7 MB), and the 3% speed increase.

I’ve realized that my philosophy has been a little skewed of late. I’ve been sacrificing content to style, and it should be the other way around.

Therefore, exactly three months after tearing my site down to do this redesign (boy am I lazy), I’m going to start posting new entries — even though my site looks like crap in a brown paper sack. Perhaps having the new entries will motivate me to make this place look less hideous?

ContentWatch updated their website today (it’s been in the works for several months) and released version 1.8 of it’s content filtering products.

The website redesign looks pretty spiffy. I like the way they’ve organized things, but I’m a little dissappointed that it’s not coded to current W3C standards (they don’t even declare a doctype!). During the redesign they gave demo links to employees so we could test the new site. I pointed out that the pages weren’t validating, but they must not be worried about that because they haven’t made any changes (other than some bug fixes and minor cosmetic stuff).

The newest version of ContentProtect is wonderful. I’ve been using the beta on my computer for a while and I’m very happy with the changes they’ve made. There are now time controls, so you can fine tune when each family member is allowed to be online down to half hour blocks of time. If you want to restrict your kids to one or two hours of surfing after school, but let them surf most of the day Saturday, feel free.

With the new version comes a new pricing scheme. We’ve switched to a subscription basis for updates and technical support. The update also fixes the recategorization of URLs (which has been broken for a while) and several bugs and incompatibility issues. This is the most stable release so far (they’ve all been pretty stable since 1.4).

For more information, visit ContentWatch on the web. Be sure to check out the most recent press release.