But, on the next Byte received (or in the Test IOC); I do not see where the  
STATE is cleared in the INT version.  
 
I do see your foreground remnant does clear the STATE though.
 
 
 
In a message dated 5/13/2008 10:18:11 P.M. Central Daylight Time,  
namiller2@naxs.net writes:

On Tue,  May 13, 2008 at 10:54:55PM -0400, DavidCOU@aol.com wrote:
> It appears  that perhaps the STATE variable is not being reset to 0 when  
>  receiving (or interactions of STATE with the Tx and Rx Ints).
>   
> Keep me in the loop.  It is probably something very  simple.

Oh, I'm sorry that I didn't mention that the implementation is  to be
half-duplex. This is why the state variable is reused.

I agree  that the problem is likely simple. It's just that I've over looked
the  problem many dozens of times. :(

Oh, and the state variable is set to  zero in the IOC handler during
reception.

Thanks. Matt

--  
The idea that every single thing in the universe should be usable  by
the untrained, the uncaring and the uninterested is a fallacy.   There
is nothing wrong with having something that works well when used by  the
expert.

- John W. M. Stevens posting in comp.os.linux.advocacy,  June 15 1998
-- 
http://www.piclist.com PIC/SX FAQ & list  archive
View/change your membership options  at
http://mailman.mit.edu/mailman/listinfo/piclist





**************Wondering what's for Dinner Tonight? Get new twists on family 
favorites at AOL Food.      
(http://food.aol.com/dinner-tonight?NCID=aolfod00030000000001)
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist