> No need to make up silly new requirement or other arguments to put my > advice aside.
sorry joep, I am not putting your suggestion asside. I was just stating why I used decimal. I just think that either using decimal or hex is fine since they are just numbers and can be equal. It may be easier in this case to use hex. I am also waiting for an answer to the question, what about other clock rates with your calculation? I was able to get rid of those large numbers, and now use a dword for counting. I think the new code would be quite easy to understand. The number 10000000, which I now use for one second is a decimal number. It is impossible for us to truly test timing. Although my oscillator may not be correct, does my code appear to be ok? Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
