Monthly Archives: September 2006

Lightroom beta 4

According to the Adobe Labs blog, Photoshop Lightroom beta 4 is out (note the name change, the addition of “Photoshop” to the title). I’ll have to give it a try over the next couple of days – stay tuned.

Technorati: , ,

More on the TomTom 910 – it gets better

Since getting my TomTom, I’ve experienced intermittent connection problems with the windscreen dock… basically it would not always keep a good connection, so I’d have to press it down whilst driving. It was irritating. One of the firmware updates stopped it from powering off when it lost the connection (the worst part about the problem at first), so it hadn’t affected me hugely, but it was an annoyance.

I just read on that if your TT x10 came from one of the early batches, you can now order a replacement dock for free. Just type in your serial number and they will ship it out. I just registered for mine. I think this is excellent, and a good move by TomTom.

In other news (also via, there has been another firmware update which adds support for the soon-to-be-released Car Connect (Bluetooth car kit) and the RDS-TMC receiver, both of which I’m eagerly awaiting…

Technorati: , , ,

El Reg picks up on our Second Life adventures

A great write-up on The Register about some of the stuff we’ve been doing in Second Life.

Technorati: ,

Apps vs. IBM Java 1.5

I have IBM’s Java Runtime Environment version 5.0 installed on my laptop.

Unfortunately, it seems that some applications don’t like this very much. The issue appears to be that they look into the Windows registry to work out where the JVM is installed. The apps concerned are looking for the HKLM\SOFTWARE\JavaSoft key. If they can’t find it, they tend to become distressed and assume that no JVM is available.

Solution #1

Previously, I’d only needed to edit a batch file to fix this. Remove the calls like this:

REG QUERY "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment" /v CurrentVersion

Replace with code to set JAVA_HOME to the location of your IBM JVM.

Solution #2

Today, I had a situation where an installer built using IzPack complained that it could not find Java 1.5. Not only that, but when it couldn’t find Java it tried to start Internet Explorer (not the default web browser on my system) and go off to to get it for me. Not the most well-behaved application I’d ever come across.

Well, the JAVA_HOME environment variable is set. At this point, there’s nothing for it but to provide what the application is looking for. So, I created a registry entry that would point at my IBM JRE installation.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Runtime Environment]

[HKEY_LOCAL_MACHINE\\SOFTWARE\\JavaSoft\\Java Runtime Environment\\1.5.0]

Job done (naturally, you’ll want to edit the value of the JavaHome entry to match your IBM Java installation…)

Disclaimer: I take no responsibility for this trashing your Windows installation. It worked for me.

Technorati: , , ,

Another broker usability snippet

Whilst creating some test questions last night, I was using the autocompletion function in the ESQL editor, and came across the following item in the drop-down list:

So, you can now get autocompletion for MQ constants from the toolkit. I didn’t know about this – perhaps it was available before fixpack 2 came along? Either way, it is a handy feature.

Technorati: , , , , , , ,