SM> I checked, and got IC16063 - the site wouldn't let me have 
SM> IC17443, altho it apparently was there.
SM> 
Interesting - since that one fixes some things left out of IC16063. 
Other references to the TCP/IP fixes all refer to IC17443, then
reference IC16063 as a  pre-req for it.  If you can't locate it, I could
make it available or email it to you.
SM> I did find a 03/25/97 dated PPP.EXE, but it appears what I need to
SM> fix the  'invalid protocol' error is a newer SLATTACH, which I 
SM> didn't find. The file I have is dated 26 Oct 95 within the  file.
SM> The actual datestamp on the file is different, tho. 
My SLATTACH,EXE has the same date internally (version 2.0, rev 1.6 26
Oct. 95. PPP.EXE version 2.00, revsion 1.29, with a ref of 1.18b 27 Feb
97 also in the code.)  As far as I know, SLATTACH only does the
internal binding of PPPx to COMy and PPP.EXE handles to protocol
interface.  At least that would be what appears to happen from the logs
(PPPx.LOG, SLATTCH.LOG).  Also indicating that is that PPP.EXE was
supplied to enable PPP connects a while back - Warp 3 days I think. 
And there is a SLIP.EXE.  If you get the Feb '97 PPP that should do you.
--- Maximus/2 3.01
1:128/166)
---------------