Peter Soetens writes:
I reported this before too. *everyone* (on 64bit?) is seeing this, and
the fix is trivial.
Can you explain why the issue occur? It seems I'll not be able to get to this
hardware till next weekend, but any input is appreciated.
Gennadiy
