Hi, I just noticed I can't reproduce this bug after rebooting, so it was likely caused by bad RAM or something. If you can't reproduce it, too, we can just close it. Falk