Have not tried that yet. I still don't understand why this only started after updating from 1.03 to 2.0B7&11. Also it only happens on occasion. Very weird. Is there anyway to log what is happening? Thanks! Steve