14 Nov 16 23:48, you wrote to me:

 ml>> my type 2+ stuff uses both of the named documents

 MK> I see that but have yet to take a looksee at either.  Thanks for the
 MK> heads up.

welcome :)

 ml>> it may have been the document that Stephen Hurd (Deuce) was working
 ml>> on

 MK> I am wondering if that is the same one I saw and now looks to be
 MK> missing in action.  If so it was a well written doc as per all three
 MK> pkt types.

very... i was glad to offer some input on it, as well...

 MK> Speaking of a difference I see in your READPKT.PAS that proddata in
 MK> type 2.2 is defined as "array[0..3] of char" whereas in the posted
 MK> type 2.2 I have it as a 32 bit integer.  FSC-0045 doesn't define it
 MK> but does have it's width specified as 4 bytes which doesn't help
 MK> matters any.  Personally either/or is fine with me but I was hoping to
 MK> get it right and a 32 bit integer is not the same as a 4 byte
 MK> character string/array/whatever other than they are both 4 bytes at
 MK> the same offset.

yep... i wasn't sure how to define it to just used a 4 byte array as the data
format was unspecified... seeing as it is "product specific data" it could be
any four byte data or even one or two bytes of something with another oine or
two for the rest... chars or some four byte numerical format... the main goal,
at that time (1995) was to get the proper byte count for the header... i'm not
certain but i'm fairly sure that i've run some 2.2 PKTs through the reader...
never really saw anything that would indicate the type of data stored there,
though... it seems pretty well open ended as far as those bytes are
concerned...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Coming Up: French chef Jacques Cousteau's blackened whale recipe.
---