George White,
  In a message on 1 March, to Dave Kelly, wrote :
GW> Yes, but as you are only storeing 8 bits in each int, and for most of
GW> us an int is either 16 or 32 bits long you need to make that:
GW> 
GW>   SigRecieved.e = ( (s) >> 24 ) & 0xff;
GW>   SigRecieved.f = ( (s) >> 16 ) & 0xff;
GW>   SigRecieved.g = ( (s) >>  8 ) & 0xff;
GW>   SigRecieved.h = ( (s) ) & 0xff;
GW> 
GW> otherwise you may find SigRecieved.h contains a copy of the input data,
GW> which may or may not be a problem depending on how the code uses it.
My int is also 16 bits. You are the third person to say that I need to
add the '0xff'. Exactly what does it do?
You might see a previous post on this. As of yet the results seem to 
be the same with or with out it.
Thanks for the feed back.
  
...
 * ATP/OSK 1.40 * The longer the title, the less important the job.
--- T.A.G. 2.7d Standard
---------------