>I understand what he meant, and I respect the general message.
>That's why I put the smiley in there. And, in the future when
>I have a short question I will include the code in the message.
>I like to make it easy for people to give me the info I want.
>I thought I was making it easier by referencing the manual,
>but in retrospect I do see Olin's point.

I did think you had made a reasonable attempt at putting the code in your
original post, and that Olin had then broken it up somewhat. However good to
see you haven't taken umbrage at it.

>I also went out to the Embed Inc site and looked at the code
>there. That is the kind of stuff I want to see, although my
>own needs don't (at present) require that I introduce the
>same level of sophistication that is evident in the code
>that Olin is working with. Lots of study ahead.

You will find it a lot easier to just leap in the deep end, and use Olins
environment, rather than try and relearn later. That way you will get a
better strategy set up straight away, and work around the niggles in the
lower end PICs without realising it. A lot of Olins macro coding also has to
do with having them work with any family of PICs, from the smallest 10F
series to the dsPic family, without the code writer having to set to and use
different macros for different chip families. Just use the macros you need
to get under way, and sort the rest out later. Do not forget to download the
PDF document that Jan-Erik has produced from Olins documentation, as it is
in a nicer format to use as a reference. The link to it is on Olins pages.

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist