-=> Alan Ianson 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.   
      
   Ahh, I think you tried the first one that Maurice posted.  I had a quick glance   
   at that source and noticed there was no file handling in it, and you've   
   confirmed my suspicions.   
      
   Try the second link Maurice posted.  For me, that one produces the same result   
   as the DOS CRC32.COM utility.  Now just have to tweak the output a bit, then   
   try hatching a file with that CRC value.  Running crc32 --help simply produces   
   an error message saying it can't find a file called "--help".    
      
    AI> I don't know if I compiled it right.. I simply did gcc crc32.c.   
      
   I did:   
      
   gcc -o crc32 crc32.c   
      
   Just to make sure I generated the binary with the name I wanted.   
      
   Anyway, next step is to tweak the source to produce the output I want (i.e.   
   easy to stuff into a .tic file without extra string manipulation), then try   
   hatching a file with a CRC value specified.   
      
   Stay tuned! :)   
   ... Doesanyoneknowhowmuchitcoststogetaspacebarrepaired?   
   --- MultiMail/Win32 v0.49   
    * Origin: Freeway BBS - freeway.apana.org.au (3:633/410)