Opps, meant to include that infomation in my last post. Well I was using driver version 1.05b when I first noticed the problem, and then I updated it to 1.07 and it didn't fix it. I looked at the source myself last night, and the national semiconductors datasheets and can't find anything wrong with it myself, though the datasheet didn't give the crc routines they where using.