If you think that things are going (relatively) well, they come right back at ya....
This time it's my laptop from work. I used to enjoy my HP NX8220 widescreen laptop. It served its purpose well over the last 3 years. Since it was out of warranty (and noisy), it had to be replaced by a Fujitsu Siemens Lifebook E8310.
Personally, I never liked the Fujitsu Lifebooks. They feel like cheap plastic laptops that might fall apart with every keystroke. Apart from the physical look and feel, there's the 'need' to use hardware which can only be used by installing a gazzilion Fujitsu installers/drivers (on the HP I only needed half the drivers to get a functioning laptop).
The quality of these drivers are questionable. On a default Windows XP Pro SP2 OS with ALL the tools/drivers recommended by Fujitsu the hardware and Windows OS don't seem to get along. Without any reason, the OS seems to hang every once in a while. And lately things have gotten worse....
As you might have noticed, the server was down the last 24 hours. When I got home last night I found my server dead. The green power LED on the mainboard was still on, but apart from that... nothing. So I tried to switch the server on and off a couple of times. After a few tries, the entire room lit up for about a nanosecond followed by absolute silence, and darkness.....
The power supply had short-circuited and took the entire house with it. Byebye power supply.
The initial thought was; 'Well, it's gonna be a nice weekend reinstalling the server from scratch', but thankfully, it was only the power supply that had died on me.
After replacing it, the server ran as before. This got me thinking about the life-expectancy of computer hardware. Frequent visitors may have read
a similar post on my blog last year. So
the power supply that died isn't even a year old. I still might have had some warranty on it (if I hadn't pried it open to see
the internal damage :) ). If I would like to use the warranty, I'm looking at at least a couple of days downtime, and since a new power supply is relatively inexpensive, I couldn't be bothered.
The life expectancy of hardware is obviously shorter than the
Mean Time Between Failure (MTBF) given by the manufacturer. The new supply has a (theoretical) MTBF of >100.000 hours, This means >4000 days. Well, mine lasted <365 days.
A while ago I started a
search for a GPS Data Logger which I can use for adding GPS coordinates to my photo's. The current status is that most of those devices are Windows only. The
few that might be OSX compatible aren't sold in the Netherlands (yet).
So I had to find an alternative. There is a sourceforge project called '
MTK GPS Data Logger Device Control' which facilitates certain GPS (chipset) devices to function on multiple platforms. So my best guess would be to buy one of those 'supported' GPS Data Loggers. Due to availability, I bought the
Qstarz BT-1000. It's a GPS mouse with navigation and logging capabilities.
First I had to make sure that the device was actually working properly, so I installed the driver and software in a Windows XP Virtual Machine. This was quite easy, and the unit seemed to work properly.
Next thing was to install the opensource program to allow communication between the GPS unit and OSX Leopard.
To get it to work on OSX you need to follow a installation manual. Something I'm not used to :). Needless to say that it took a bit longer than expected.
First of all, you'll need the
software from the sourceforge website. Second,
you need SuperWaba files (free registration is required) [these files seemed to be present in the download package from sourceforge], and the
USB driver. After that you need to follow the instructions in the README.txt provided in the sourceforge package. Note that the script information on the
forum has been superseded by the README.txt in the downloadfile (use the provided
bt747_macosX.command from the sourceforge download package instead).
Eventually, you'll end up with a directory structure whick looks something like this:

Run the
bt747_macosX.command file to start the application.
One thing I must mention is that somewhere along the lines is the mention of using TextEdit to alter (script)files. Do NOT forget to remove the formatting on the files before saving. You might end up with scriptsfiles containing some markup stuff.... And this means that you might be getting some weird error messages.

Anyway, the interface is still very simple, but you have access to lots of features. The actual manual for the application is available on
Google Docs.
I've been looking for a GPS logger for a couple of months. A GPS logger can be used for attaching GPS information to your digital photos. This way, you can display your photos on publicly accessible maps in Flickr or Google Earth.
More and more of those GPS loggers are surfacing on the market [
Sony GPS-CS1 /
GPS-CS1KA,
Globalsat DG-100,
Qstarz BT Q-1000,
GiSTEQ PhotoTrackr,
WBT-201]. But they all have one problem; None of them seem to work (natively) with an Intel Mac running Leopard (
source). Some of them require open-source drivers to function. The downside of that is that an update from Apple or an updated firmware in the GPS logger might cripple the functionality.
Why is it that GPS manufacturers won't create a GPS (logger) device that simply works on both platforms. It couldn't be that hard. Just create a GPS device that is also recognized as a external drive, containing the raw GPS data in the most common format (e.g.
NMEA). This way even the Linux users are not left out.