Is it possible there has been a regression of this in the 2.6.20-16 update that was just released? I'm experiencing nearly identical problems as reported in this thread.
Is it possible there has been a regression of this in the 2.6.20-16 update that was just released? I'm experiencing nearly identical problems as reported in this thread.