Wasn’t “ComputerWeek” once a publication full of hardware deals and stuff like that? Seems like it was, but we’re reaching back into the 1990s with that one.
Regardless, I’ve certainly spent a lot of time around computers this week. Not that I don’t normally; after all, I work with them for my job, which has me sitting in front of one for at least 8-10 hours a day. But this week I’ve been engaged in a lot of fussing around with hardware and software, researching compatibility, coming up with contingency plans and even overclocking my own workstation here at home (something I haven’t dabbled with in some years). It’s to the point where today feels more like a Thursday or Friday than a mere Wednesday.
Since this past Sunday, I’ve put most of my efforts toward setting up my dad’s new notebook computer. It’s a Toshiba Satellite A505, if I recall correctly, which he will be using as his main workstation during his upcoming work-from-home efforts. This is actually a really nice machine — 16-inch ultrawide screen, backlit keyboard with full numeric keypad, excellent sound (for a notebook, especially), slot-loading DVD burner and a number of other cool things. There’s a lot of attention to detail evident in the design of this machine, the kind of attention I never saw Dell put into anything. The form factor and weight are a little unwieldy if you want to carry it around a lot, but as a desktop replacement it’s a good size.
The problems I’ve been having, though, aren’t related to the Toshiba, really, but to the Palm Treo that my dad uses as his phone, master organizer and PDA. This Treo runs Palm OS, and I’ve since come to learn that Palm completely dropped the ball with their Palm OS-based product line. The new laptop shipped with Windows Vista 64-bit, so as to take advantage of the preinstalled 4GB of RAM. Unfortunately, Palm’s support for 64-bit operating systems (and Vista in general) is woeful, to the point where you cannot even plug your Palm Treo into the computer via USB. There are no drivers for the USB cable.
All this means you have to sync via Bluetooth, but the Toshiba Satellite A505 doesn’t have Bluetooth. So we had to make an emergency run to Best Buy to pick up a micro Bluetooth adapter. (For reference, the Rocketfish RF-BCDM4 works right out of the box with Vista x64, using Microsoft’s own built-in drivers — and as a bonus, it’s ridiculously tiny.) Despite having to travel to the neighboring city to find a Best Buy that had the thing in stock, we finally got one, loaded it up and it worked great. So I thought our Palm problems were over.
I was wrong. While HotSyncing my dad’s Treo via Bluetooth worked perfectly, the Palm Desktop software did not. The issue is that Palm Desktop version 4, which he’s been using for some time now, doesn’t work in our configuration. Palm claims it doesn’t work under Windows Vista at all, a claim I seemed to refute by installing it successfully on my own Vista-based machine. The problem, though, is that Palm Desktop 4 doesn’t support Bluetooth syncing, and Vista prevents you from using USB syncing. In other words, I can’t see any way to friggin’ sync the phone under Desktop 4. So, Palm advises that you upgrade to Palm Desktop 6.2 instead. OK, fine. I downloaded it. It’s two versions newer, so it must be better anyway.
Boy, was that an asinine assumption. Palm Desktop 6.2 is way worse than Palm Desktop 4. This is perhaps the first time I’ve ever experienced a full-on software regression. The biggest problem is that version 6 completely drops the color-coded categories feature in an astounding display of poor judgment. It’s also missing the Expenses and Notepad apps. Tasks no longer have the “Repeat” function. Birthdays are no longer supported in Calendar. And there’s also a superfluous pmTraceDatabase failure message on every sync (which at least Palm has issued a fix for). This is unconscionably bad. Horrible, actually.
Continue Reading…
Nuke Plant Gets SQL Slammed
By Chief Oddball on August 20th, 2003 at 6:12 pm
Filed under Commentary ··· Comments Off
In light of the big northeastern blackout last week, I’ve heard some jokes spread around that maybe the infamous LoveSan computer virus took out the grid. Not bloody likely—or so we thought. According to SecurityFocus, the SQL Slammer worm of a few weeks ago nearly did just that…at Ohio’s Davis-Besse nuclear power plant.
Continue Reading…
Commenting Disabled