To bad it's the new one. I still recall the Win3.1 (or possibly 3.11 WFW) calc.exe returning 0 when calculating 2.11 - 2.1 .
I've always been curious to know what could have triggered that error since it was too big to remain unnoticed for so much time.