> >Hmm...if I were in your situation, my thinking would be along the lines of: "I > >need to generate a CRC-16 value for communicating with Poser. In order for Poser > >to support this, it must be able to calculate a CRC-16 value. Since the source > >code to Poser is available, then I can just snag *its* routine and use it." And > >sure enough, there's a Crc.c file that comes with Poser that has the function > >you want. I bow to your superiority oh master of the secrets ;-> I apologize for the stupidity on my part. I didn't realize I had access to the source. I will keep that in mind for the next question. I will look at the source when I get the chance. > >On the other hand, you could probably just skip all that, since I don't think > >Poser validates the checksum right now. So set that field to zero and see what > >happens. Eventually I may get around to validating the checksum, but for now I > >don't want to make things too difficult for developers in your situation. But > >set the checksum to zero! If I later add checksum support, then I'll only do it > >when the checksum field is non-zero. Now, there's an engineer after my own heart !!! > > > >-- Keith Rollin > >-- Palm OS Emulator engineer
