try a "cvs log" on the offending files. Binary files should have
been added with a "cvs add -kb" to suppress keyword expansion (and CR/CRLF translation). if they keyword expansion mode isn't "b", then the problem is as you suspect. This just bit me on one of my own CVS
repositories today
cvs maintainers, you can do a "cvs admin -kb <offending file>" to fix.
Apologies if this isn't the problem.