GalleryRemote on Windows 7 64-bit

February 4th, 2012

The default install of GalleryRemote on Windows 7 64-bit works, but the client image resizing does not. This is a pain, especially these days with digital pictures that are sometimes over 10 MB. The problem was the ImageMagick library. I found this to work for me:

Install Imagamagick

Pick the Q16-windows-x64-static.exe version of Imagemagick, latest version, from http://www.imagemagick.org/download/binaries/.

Configure convert.exe path

Edit the file imagemagick/im.properties in the GalleryRemote directory, and set the im.convertPath to the DOS 8.3 compatible name of the convert binary, using a forward slash as directory separator (Hint: use dir /x to list the 8.3 names. The result may vary for different versions of ImageMagick; in my case it looked like:

im.convertPath=C:/progra~1/imagem~1.5-q/convert.exe

At this stage the resize did work again.

Update 2012-03-21. Secunia PSI notified me that 6.7.5-1 was vulnerable. I uninstalled that and installed the newer version 6.7.6-1. This means you have to update the configuration to reflect this as well. In my case the path changed to:

im.convertPath=C:/progra~1/imagem~1.6-q/convert.exe

Google Maps upload – work around

October 16th, 2011

For a while I’ve been unable to upload any GPS track into my Google Maps account.
I use GPS Trackmaker to reduce the track that comes out of my Garmin GPS62S so that it has fewer than 400 data points.
But since last September, I always get this error when I try to upload it:


We could not finish uploading your file.
No changes have been made to the map.

This had worked fine in the past.
I tried some more and found out a work around.
You can import the map if you place the map file on a web server, and then select the “enter the url of map data on the web” option instead of uploading a local file.
Another gotcha: the map file name should NOT contain spaces.

Don’t ask me why, but this is how it works ;-)

Jiskefet’s Kamphuijs nieuwe DNB president

May 25th, 2011

Het heeft even geduurd, maar Kamphuijs (een van de Jiskefet lullo’s) heeft het toch nog tot president van De Nederlandse Bank geschopt ;-)

Ziggo zakelijk – amateurs

December 10th, 2010

Al eens goed geluisterd naar de Ziggo Zakelijk radio commercial?

He victor, kan ik die video mailen naar m’n klant?
No problem, we hebben Internet Plus, van Ziggo Zakelijk

He victor, ik wil een vast IP adres, zodat ik ook thuis kan werken.
No problem, we hebben Internet Plus, van Ziggo Zakelijk

Als je in 2010 nog video’s gaat mailen ben je super lame. Leuk voor je klant ook, een 20MB bestand in de mail. Handig bekijken (not). De way to go is natuurlijk op YouTube/ViMeo zetten.

Vast IP adres om thuis te kunnen werken? Vaste IP adressen zijn alleen bedoeld voor diensten, niet voor eindgebruikers. Thuiswerkers zetten een VPN op. Ben je ook van het FireSheep probleem af.

Looking for: “java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener”

August 28th, 2010

When trying to put together a jar file on Ubuntu Lucid with gant, I got this:

java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
        at java.lang.Class.getMethod0(Class.java:2670)
        at java.lang.Class.getMethod(Class.java:1603)
        at org.codehaus.groovy.tools.GroovyStarter.rootLoader(GroovyStarter.java                  :99)
        at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:130)
Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.BuildListener
        at org.codehaus.groovy.tools.RootLoader.findClass(RootLoader.java:156)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at org.codehaus.groovy.tools.RootLoader.loadClass(RootLoader.java:128)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        ... 6 more

After also installing the ant package everything worked fine…

Canon Err 01 – fixed itself

August 16th, 2010

Last week I went out and took my 550D with me to take some pictures. Unfortunately when I switched it on and tried to taka a pic it gave me this:

Err 01: Communications between camera and lens is faulty. Clean the lens contacts.

Just to be sure I had a look but as clean as it can be – I only have the 15-85 EF-S so I never fiddle with lenses.

A colleague of mine brought his 450D with 50 EF lens to the office. After putting on the 50 mm lens my 550D would still give me the Err 01. So it was clearly an issue with the camera and not the 15-85. After putting the 15-85 back on, everything started worked again like nothing had happened.

This behaviour demonstrates that the Err 01 issue is likely to be caused by some software problem, static electricity or something similar.

The camera had been working fine for a whole month in the US, however this was the first time after I was there that I used it again. I’m guessing the electronics might have had a glitch either on the airport during X-ray scanning, or during transatlantic flight…

Anyway, problem solved (for now) ;-)

Make iscsitarget listen on specific address

August 13th, 2010

I set up iscsitarget on one of my Ubuntu Lucid boxes and it seemed to work. I let one of my VMware ESX hosts scan it, and it sure enough found my LUN, but via two paths.

Turned out that because the host running iscsitarget has two NICs, the ESX host sees two paths. Not exactly what I wanted, because one NIC sits on the internet, the other on the dedicated iSCSI network.

Unfortunately it is not possible to configure ietd to listen to a specific address by editing any of the configuration files (/etc/default/iscsitarget and /etc/ietd.conf), you have to hack the init script to be able to do this…

Edit /etc/init.d/iscsitarget and go to the function ietd_start(), then change this line:

start-stop-daemon --start --exec $DAEMON --quiet --oknodo

to:

start-stop-daemon --start --exec $DAEMON --quiet --oknodo -- --address 10.10.1.1

(or whatever IP you want to have it listen to).

Dell Latitude 2110 running Windows 7 64 bit

June 5th, 2010

Dell Latitude 2110
Last week I received a shiny new Dell Latitude 2100 netbook.
I picked this laptop to replace our old D610s, which cannot run Windows 7.
As soon as I deployed my Windows 7 64 bit image onto it, I saw that a lot of devices were missing a driver.
Unfortunately the Dell support site does only lists 32 bit Windows 7 drivers when you select Latitude 2110 as your model :( However, some of the installers you download actually include both 32 and 64 bit drivers. Eventually I managed to get everything going:

Dell wireless 375 Bluetooth Module

Driver from 32 bit Windows 7 list also contains 64 bit driver.

Dell WLAN card

Driver from 32 bit Windows 7 list (for 1397, 1501, 1520, 15xx WLAN half minicard) also contains 64 bit driver.

Onboard gigabit NIC

Drivers on Dell site are only 32 bit. You will have to download a driver directly from the Broadcom site.

Graphics card

The listed Dell driver for the Intel GMA3150 video card is only 32 bit, so you will have to download that directly from the Intel site.

Free fall sensor

This is one of the unknown devices. The listed Dell driver (ST Microelectronics DE351DL) contains 64 bit drivers as well.
Strange to have this in a laptop with SSD, but I guess it just comes with the motherboard or something.

Card reader

This is the SD card reader on the front. The listed Dell driver (Realtek RTS5208) contains 64 bit drivers as well.

The 64 GB SSD disk is a Samsung and luckily this disk has firmware VBM24D1Q, which is known to support the TRIM command.

Google Apps IMAP migration

May 22nd, 2010

I have recently moved to Google Apps.
One of the nice things is that you can have IMAP access so you can keep using the MUA of your choice.

If you have the paid version (Premier Edition), IMAP migration can be done smoothly using the migration tools, which suck messages from your old IMAP account and transfer them into your Google Apps account. This has some interesting benefits, such as de-duplication of messages. I used to copy all incoming mail (after spam etc filtering, just before it hit my INBOX) to an ‘All’ mailbox in my old IMAP account. I could then keep my INBOX clean by just deleting messages, which were still available in the ‘all’ box. This was of course not very efficient, and in the end it contained about 100.000 messages which were well over 2 GB. After migration to Google Apps, all double message were removed, and instead they just received an extra tag ‘All’. Very cool.

If you have the free edition, you will have to do the transfer yourself. There are command line tools such as imapsync, which work most of the times.
You can also configure two IMAP account in your MUA, and then copy folders over. Whatever method you use, there are a few things that can screw up the migration, and that should be fixed prior to any migration attempt. If you don’t, you migration will fail somewhere half way, and your MUA might or might not inform you what actually went wrong.

Messages greater than 20 MB cannot be stored

The easiest way to fix this is to remove those messages from your mailbox and copy the attachment to your computer. Sending such huge message is highly questionable at all, and the good thing is that once you are in Google Apps, you are not allowed to such ridiculous stuff any more.

IMAP folder names cannot exceed 40 characters

This is an implication of the fact that IMAP folders are merely a representation of labels, which cannot exceed 40 characters.
Hence the total IMAP folder name cannot exceed 40 characters. Also, each level counts as a character, because it is represented by a separator (/) in the label.
This can seriously impact your migration. I am amazed at the IMAP folder structures people have build-up over the years, this can get really insane.

Update As of April 2011 this limit has been raised to 225 characters :-)

The extreme on one side is a single folder of 40 characters, the extreme on the other side is a nested structure of 20 one character folders:

No more than 1800 IMAP folders are migrated

You are not likely to run into this limit, but hey, don’t underestimate the average user ;-)

H.264 Encoding for Android

January 8th, 2010

After some experimenting it turned out that H.264 video needs to be encoded using the Baseline Profile for the HTC Hero (running Android 1.5) to be able to play it.
High Profile will not play at all on the phone. Main Profile will play, but gives an entirely green video – unusable.