01 Oct 16 21:01, you wrote to Maurice Kinal:

 MK>> Having said that, I am curious if the c code produces the 'correct'
 MK>> output as far as fidonet tic people are concerned.  Let us call it
 MK>> needed closure.  :-)

 AI> It does output a crc32 value. Always E4D9C11A. ./crc32, crc32
 AI> , and crc32 --help all return that value.

did you notice that it always fills the buffer with random bytes in main()? ;)

it is funny, though, that the same CRC value is generated on separate machine
and multiple runs... something must be wrong with the selection of the random
bytes...

 AI> I don't know if I compiled it right.. I simply did gcc crc32.c.

there's no much to compiling it... maybe specifying an output name... mine
defaulted to a.out...

one thing i do note is that it feeds the entire buffer to the update_crc
routine in one shot instead of feeding it one byte at the time... that will
make a difference in the results... especially if there's any pre- and/or
post- processing and where it is being performed...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... The local diner doesn't give out doggie bags. The SPCA won't let 'em.
---
 * Origin:  (1:3634/12.73)