Tech support has a posting a few weeks ago that the problem has been identified and fixed for the 6.2.0 release, due "soon."


David Grauman MD, FACP
Flagstaff, Arizona