home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!stanford.edu!agate!spool.mu.edu!mixcom.com!Dean.Roth
- From: Dean.Roth <Dean.Roth@mixcom.mixcom.com>
- Subject: Re: SLIP8250 and SLIPDIAL
- Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
- Distribution: usa
- Date: Thu, 21 Jan 1993 14:24:51 GMT
- Message-ID: <1993Jan21.142451.3523@mixcom.com>
- References: <C164EM.2rD@eis.calstate.edu>
- Sender: xeee02@mixcom.com (Dean A. Roth)
- Lines: 31
-
-
- >My idea is to slightly modify the SLIP8250 packet driver so that it has
- >an ON and OFF mode. It would startup in the OFF mode in the
- >autoexec.bat along with PKTINT.COM. I would write a Windows application
- >(based on the SLIPDIAL source) that would do the dialing and connecting.
- >Once the connection to the SLIP server was established, I would signal
- >the already running SLIP8250 packet driver to switch to ON mode.
-
- >Questions:
- >Does this approach make sense?
-
- I've already been through this problem. You do not need to do what
- you have proposed.
-
- I wrote a dialer program using Greenleaf's comm lib software.
- The Greenleaf software disconnects anything else from the UART while it
- is using the UART, and reconnects what was already there when
- the program quits. THerefore the SLIP driver can already be loaded
- before the dialer program is used.
-
- However, there is one flaw that is easily solved.
-
- The SLIP driver enables a 16550 UART's fifo. The Greenleaf code
- disables the fifo when it quits. This screws up the SLIP driver.
- My solution was to disable the fifo enabling code in the SLIP driver,
- which means the SLIP driver does not use the fifo. This works fine.
- The other solution would be to modify the Greenleaf code so that it
- does not muck with the fifo. (Greenleaf supplies source code, so
- changing it is easy.)
-
- Dean
-