home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: bit.listserv.banyan-l
- Path: sparky!uunet!think.com!spool.mu.edu!darwin.sura.net!aplcen.apl.jhu.edu!aplcenmp!prm
- From: prm@aplcenmp.apl.jhu.edu (Paul Raymond McMullin)
- Subject: unloading banyan drivers?
- Message-ID: <C02vI7.Ax0@aplcenmp.apl.jhu.edu>
- Keywords: cabletron drivers, mark & release, packet drivers
- Sender: Paul_McMullin@jhuapl.edu
- Organization: Johns Hopkins Continuing Professional Programs
- Date: Wed, 30 Dec 1992 15:10:55 GMT
- Lines: 44
-
-
- We've started using the crynwr packet drivers with the "CSIBAN.COM" interface.
- This appears to work fairly well, and the packet drivers seem to support
- concurrent TCP/IP sessions using FTP software's "NDIS/IFCUST" packet driver
- interface, also without real problems. Now that more and more users are
- getting DOS 5 and Windows, we're starting to "loadhigh" the packet driver and
- the Banyan drivers on some machines, again successfully.
-
- But here's the problem: quite a few of our users used to run MARK or MARKNET
- before starting the Banyan software (esp. running the 3c503ban.com driver) and
- then running RELEASE or RELNET when finished with the network to "unload" the
- Banyan drivers. If they were running TCP/IP they'd run the EBANYAN interface
- that allows the FTP software to pass their packets to the 3c503ban.com driver
- to operate the card. If we "loadhigh" the crynwr packet driver, and MARK and
- RELEASE the Banyan drivers to unload them, when you try to load the Banyan
- drivers a second time they report that the packet driver appears to be busy.
-
- The FTP software's "ETHDRV" and "INET UNLOAD" commands appear to be able to
- clean up after themselves so that a second invocation of the ETHDRV command
- succeeds! Is there anyone who is using the packet drivers with Banyan that
- knows how to unload the Banyan drivers?
-
- (I know that loading the packet driver AFTER the MARK command works, and I
- also know that the packet driver comes with a "termin" program to unload it,
- but in the first place unloading the packet driver defeats the "concurrency"
- that I hope to establish with Windows [suppose Banyan is in one window and
- TCP/IP is in another], and secondly, TERMIN does not seem to work when the
- packet driver is "loadhigh"ed.)
-
- I suspect that someone familiar with the way the packet drivers work could
- "whip up" a simple C-ish program that could be run after the RELEASE that
- dumps the Banyan drivers to tell the packet driver that the session is
- closing would allow the second Banyan invocation to re-subscribe.
-
- (I had hoped that the PKTMUX (packet multiplexing) driver might be applicable
- for this problem, but it appears to be mainly for TCP/IP sessions; in any case
- I still don't think that the RELEASE of the Banyan drivers would allow the
- PKTMUX driver to recognize that the subscriber has departed...)
-
- Thanks.
-
- -prm
- --
- Paul McMullin prm@aplcomm.jhuapl.edu
-