I'm glad you sorted it out. :)

Any chance you could tell us what the fix was, in case anyone else runs 
into something similar?  Or is that unlikely to happen?

Also, while you're there, I have a favour to ask:  could you tell me
what the result of doing 

>>> 1e16 + 2.99999

is on that platform?  It's not often I get to find out much about Python 
on m68k, and I'm curious to know whether it has the same double rounding 
problems as x86.

Thanks!