morrison@herodotus.cs.uiuc.edu (Vance Morrison) (07/04/90)
Hello, If my understanding of PCIP is correct, PCIP has some sort of TSR (or device driver), that handles most of the TCP/IP protocol and application programs (like Telenet FTP, etc) interface with that driver. (thus the driver is shared, unlike programs like NCSA telnet). Now a while back, I heard that there was a spec for interfacing to the PCIP driver. I am looking for this spec. Any pointers would be appreciated. Thanks Vance Morrison Univ of Il.
romkey@asylum.sf.ca.us (John Romkey) (07/05/90)
PC/IP had no TSR driver. Its TCP and other protocols could be linked into any small memory model application, but that application then had to contend with the tasking package. PC/IP's spiritual successor, FTP Software's PC/TCP, does have a TSR kernel with TCP and other basic network protocols available through a software interrupt interface. That interface is non-proprietary, and is documented in the developer's kit. I believe that Wollongong's WIN/PC should have some kind of TSR interface, and that the UMD code does, but I don't know any details about these. - john romkey USENET/UUCP: romkey@asylum.sf.ca.us Internet: romkey@ftp.com "There is no loyalty except loyalty to the party. There is no love except love of Big Brother. All competing pleasures we will destroy." - 1984 (film)
nelson@sun.soe.clarkson.edu (Russ Nelson) (07/06/90)
In article <1990Jul4.141211.18788@ux1.cso.uiuc.edu> morrison@herodotus.cs.uiuc.edu (Vance Morrison) writes:
If my understanding of PCIP is correct, PCIP has some sort of
TSR (or device driver), that handles most of the TCP/IP protocol
and application programs (like Telenet FTP, etc) interface with
that driver. (thus the driver is shared, unlike programs like
NCSA telnet).
You mean MIT/CMU/Harvard's PCIP. FTP to ftp.com, and look around.
It's called packet_d.txt.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667
In Communism's central planning, citizens are told "you will make widgets".
In Capitalism's advertising, citizens are told "you will buy widgets".jbvb@VAX.FTP.COM ("James B. Van Bokkelen") (07/06/90)
It sounds like you're thinking of our PC/TCP product, which is a commercial DOS TCP/IP developed from a PCIP base. PCIP itself has the protocol stack linked into the application, and no part of it is a TSR. Our versions up to 1.16 worked the same way, but then we did v2.0, which put the stack into a TSR module, and had the applications talking to it via INT instructions. James B. VanBokkelen 26 Princess St., Wakefield, MA 01880 FTP Software Inc. voice: (617) 246-0900 fax: (617) 246-0901
ernie@cwjag.CWRU.EDU (Ernie L. Ellenberger) (07/07/90)
In article <NELSON.90Jul6002954@image.clarkson.edu> nelson@clutx.clarkson.edu writes: >In article <1990Jul4.141211.18788@ux1.cso.uiuc.edu> morrison@herodotus.cs.uiuc.edu (Vance Morrison) writes: > > If my understanding of PCIP is correct, PCIP has some sort of > TSR (or device driver), that handles most of the TCP/IP protocol > and application programs (like Telenet FTP, etc) interface with > that driver. (thus the driver is shared, unlike programs like > NCSA telnet). > >You mean MIT/CMU/Harvard's PCIP. FTP to ftp.com, and look around. >It's called packet_d.txt. In MIT/CMU/Harvard PCIP, "most of the TCP/IP protocol and application programs" are handled by code compiled into each application, as I believe somebody pointed out. There is another version of PCIP which is not freely distributable, Stanford's SU-PC/IP, which does have a TSR TCP/IP kernel. There is indeed an interface spec for this 90K TSR, but it is specific to Stanford's SU-PC/IP. While on the subject of SU-PC/IP, I'll point out that it has a decent implementation of MH using POP, which allows secure mail handling on a PC. It also has FTP and the venerable PCIP Telnet, and BOOTP support. We have added a Packet Driver interface, though this is not part of the standard distribution. I'm not sure what the current distribution policy is, but Stanford previously sold academic site licenses for $100. -Ernie (ernie@cwlim.ins.cwru.edu) Standard Disclaimers Apply. Contents volatile under pressure.