home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.apps
- Path: sparky!uunet!rei2!fox
- From: fox@rei.com (Fuzzy Fox)
- Subject: Re: Windows and NCSA telnet....
- Message-ID: <1992Dec21.180809.1850@rei.com>
- Date: Mon, 21 Dec 1992 18:08:09 GMT
- References: <BzDHwz.230@news.cso.uiuc.edu> <BzDv2A.H52@news.iastate.edu> <BzEs7J.3u0@m2.dseg.ti.com> <BzEvtH.Dwz@news.iastate.edu> <mcdonald.614@aries.scs.uiuc.edu>
- Organization: Recognition Equipment, Inc.
- Lines: 22
-
- mcdonald@aries.scs.uiuc.edu (J. D. McDonald) writes:
-
- >The proper ways are three:
-
- >1) use the internal driver inside Telnet for your card
-
- >2) first load the packet driver, then telnet, then after exiting Telnet
- > unload the packet driver. Don't use the -w switch.
-
- >3) The best way, and the only reliable way if you want to run the
- > packet driver from DOS once and for all, is to load the packet driver
- > there (no -w switch), then outside Windows, load Pktmux, the packet
- > multiplexor.
-
- 4) use the WINPKT packet driver shim, which specifically understands the
- Windows context-switching problem and solves it.
-
- --
- #ifdef TRUE | Fuzzy Fox (a.k.a. David DeSimone) fuzzy@netcom.com
- #define TRUE 0 |
- #define FALSE 1 | "You have been recruited by the Star League to defend
- #endif | the Frontier against Xur and the Kodan Armada."
-