> Actually, unsigned integers cause the problem, as seen below. That's why no one, ever, used unsigned integers. The assembly source was clear in using ">" (signed) and the C pseudo-code used "> 0" which pretty much implies the value compared is signed. <removed 120 line "there's only one unsigned integer > 0" proof> Philipp Rumpf