>>/31361/
there was a fix for that a thread or two ago I think