This is fantastic support for the teams - thank you very much!
I believe that the error was initially tracked down and verified by Team 1726. See
this thread for the original discussion of their description of the problem and recommended solution.
-dave
.