home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!darwin.sura.net!blaze.cs.jhu.edu!newton.cs.jhu.edu!silano
- From: silano@newton.cs.jhu.edu (Mike Silano)
- Subject: Re: DV/X and NCSA Telnet WORKS!
- Message-ID: <1992Jul24.010637.11132@blaze.cs.jhu.edu>
- Sender: news@blaze.cs.jhu.edu (Usenet news system)
- Organization: Johns Hopkins Computer Science Department, Baltimore, MD
- X-Newsreader: Tin 1.1 PL4
- References: <1992Jul23.204306.27235@usenet.ins.cwru.edu>
- Date: Fri, 24 Jul 1992 01:06:37 GMT
- Lines: 54
-
- trier@slc6.INS.CWRU.Edu (Stephen C. Trier) writes:
- : In article <1992Jul23.175757.1607@blaze.cs.jhu.edu> silano@newton.cs.jhu.edu (Mike Silano) writes:
- : >The reasons for this are clear - when the task is swapped out,
- : >the ISR(Interrupt Service Routine) is swapped as well. ...
- :
- : >The solution to this is pktmux - the packet driver multiplexor.
- :
- : What?? No, pktmux is a solution to a different problem. The -w option
- : to the Crynwr packet drivers is a solution to the problem you describe.
- :
- : Pktmux is designed to solve the problem of running more than one TCP/IP
- : protocol implementation simultaneously. It gets it *almost* right, too.
- : There are many potential problems with using it, enough that most (all?)
- : TCP/IP vendors won't provide tech support for a problem that occurs
- : while pktmux is loaded.
- :
- : It's possible that pktmux also solves the first problem you describe,
- : even though that is definitely not its raison d'etre. If you are running
- : only one TCP/IP stack at a time, try using the -w flag on your packet
- : driver instead of running pktmux.
-
- :r
-
- From the documentation of pktmux 1.1:
-
- A second requirement was to allow MOS2 to run under a control
- program such as Windows 3 or DESQview. This is an instance of a
- more general problem in running an application which uses a Packet
- Driver under a control program. It arises because the Packet
- Driver, which is loaded before Windows, calls the application when
- it has received a packet. This is quite satisfactory under DOS but
- under Windows there is no certainty that the application is
- currently running and there is therefore the risk of jumping into
- the middle of another program with dire consequences. A Packet
- Driver option -w gets over this by checking that part of the
- application program code is present and throwing away the packet if
- not. This leads to a rather slow data rate as the protocol timeout
- and retry mechanisms have to be brought into play to recover from
- the situation. A better solution is provided by the free software
- WINPKT which only works under Windows 3 Enhanced mode and uses
- Windows 3 facilities to make sure the application is running. A
- copy of WINPKT is provided in this package. WINPKT has the
- drawback that it does not work with other control programs such as
- DESQview and also with certain ethernet cards such as the BICC 16
- bit varient. PKTMUX meets this requirement and gives the
- additional feature of being able to run communications applications
- in more than one window.
-
- The -w option on the packet drivers has never worked for me
- (wd8003 driver on an SMC (WD) Elite 16 card.
-
- -Mike
-
- Replies, comments, suggestions or other to silano@cs.jhu.edu
-