Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!tahoe!jimi!arrakis!blake From: blake@nevada.edu (RAWLIN BLAKE) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Configuration of PCIP Message-ID: <1991Apr30.174308.18229@nevada.edu> Date: 30 Apr 91 17:43:08 GMT References: <1991Apr30.151747.14671@grape.ecs.clarkson.edu> Sender: news@nevada.edu (News Administrator) Organization: University of Nevada, System Computing Services Lines: 20 In article <1991Apr30.151747.14671@grape.ecs.clarkson.edu> nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET) writes: >Boy, it'd sure be nice to have a version of PCIP that took its parameters >from NCSA Telnet's CONFIG.TEL. There's really no reason, other than >historical, to continue to use netdev.sys. I'd do it myself, but >I don't have Microsoft C 5.1, and I don't have the time to port PCIP to >Turbo C. > >--russ YES, YES, YES I'd do it myself, but I don't know how :-) -------- Rawlin Blake Internet: blake@nevada.edu BITnet: blake@unsvax #include