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.181140.1923@rei.com>
- Date: Mon, 21 Dec 1992 18:11:40 GMT
- References: <BzDHwz.230@news.cso.uiuc.edu> <BzDv2A.H52@news.iastate.edu> <BzEs7J.3u0@m2.dseg.ti.com> <BzEvtH.Dwz@news.iastate.edu>
- Organization: Recognition Equipment, Inc.
- Lines: 30
-
- rjhoffma@iastate.edu (Richard J. Hoffmann) writes:
-
- >wd8003e -w 0x60 10 0x280 0xd800
-
- >Until I did that, I could only execute Telnet under Windows if I set the
- >*.pif so that Execution: was exclusive. I seem to recall that there is
- >another driver that you could load right after the packet driver that
- >will accomplish the same thing as the -w switch, which was described as
- >a "hack." Unfortunately, I can't remember what it is, but I think it
- >comes with the Clarkson packet driver collection.
-
- The "hack" that you're thinking of is WINPKT, a pseudo-packet driver
- which accepts hardware packet interrupts and delivers them to Windows in
- the proper context. It's not too easy to set up, but then, neither are
- packet drivers, but it works flawlessly for me.
-
- Some folks feel that PKTMUX is a better solution, but after reading the
- documentation for it, I determined that it was even more of a gross hack
- than WINPKT, so I decided to stick with WINPKT. Since NCSA telnet
- contains all the FTP and Telnet services that I need, I do not require
- multiple programs accessing the network card.
-
- Actually, I don't use NCSA telnet, but instead use CUTCP, which is based
- on NCSA but is more stable and has some nicer features, in my opinion.
-
- --
- #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."
-