hm, i've got your latest. I did some more debugging today and this was a
red herring: it turns out that it was not your patch causing this
problem, it triggered with your patch only because of a subtle .config
difference that i overlooked. Sorry!
Ingo
-