Hey everybody,
unfortunately here the same problem.
But as far as it concerns me, it only appeared after I upgraded to v1.08. Under 1.05 or lower this error never occured!!!
I always thought it is a problem caused by the new patch.
Can anyone confirm this?
regards
Pempel