🚀 go-pugleaf

In article <726794367snz@spell.demon.co.uk> spell@spell.demon.co.uk (Martin Glassborow) writes:
>From: spell@spell.demon.co.uk (Martin Glassborow)

>>In article <1993Jan11.150438.2051@newsie.dc.dk> ole@dc.dk writes:
>>Have anybody ever tried WINQVT and SLIP with success ?
>>
>>Thanks in advance.....
>>
>Yes, with limited success using FTp's SLP16550 drivers. 

If you cannot get SLIP8250.COM to work with QVT/net, there is something 
incorrect in your configuration.  I have included below a post that I sent to 
all members the Trumpet beta-testing list.

If you follow these instructions precisely, you should be able to get SLIP to 
work well with Windows, and WinQVT/net.

Ashok

-- Begin forwarded message --
Based on my experiences on setting SLIP on a few PCs, here are my comments
on setting up SLIP on a PC and SLIP with Windows in particular.

Modem:
a) Turn off DTR (AT&D0&W0)
b) Dial and establish the SLIP connection first.  This can be done
   automatically if you use a program like SLIPDIAL (from the University of
   Minnesota) which will dial and establish a SLIP connection then load the
   SLIP packet driver (SLIP8250 is preferred).
   My modem and several others based on the Rockwell RC144AC V.32bis data-
   pump do not work with current versions of SLIPDIAL.  I therefore use a
   DOS program (QMODEM) to dial the SLIP server, and automatically run a
   Qmodem script file that establishes the SLIP link.
   I need to turn off DTR because QMODEM drops DTR when it exits.  This hangs
   up the connection, which is not very desirable.  If you use another comm. 
   program such as CONEX or KERMIT to establish your SLIP connection you do 
   not have to turn off DTR, as these programs give you the option of exiting 
   without hanging up the connection.

SLIP drivers: (SLIP8250.COM is preferred over ETHERSL.COM)
a) Try getting a version 10 SLIP driver.  Philip Burns of Northwestern
   University has a modified SLIP8250.COM driver that is better at hardware
   handshaking.
b) Load the driver AFTER establishing the SLIP connection.  My modem is a
   V.32bis modem on COM1, so here is how I load the driver.
   slip8250 -w 0x62 -h SLIP 4 0x03f8 57600
c) Since I use DOS TCP/IP applications in WIN 3.1 DOS boxes, I also use the
   double-ended packet driver shim WinPKT.COM -- this creates a virtual
   packet driver at 0x60.  DOS applications in native mode, DOS
   applications in Windows 3.1 DOS boxes and Windows applications can all
   use this virtual driver at 0x60.
   winpkt.com 0x60 0x62
d) I use QVT/Net, so I load PKTINT.COM next.  QVT/net is configured in
   QVTNET.INI to use the interrupt at 0x60.
   pktint.com

Windows 3.1
a) Get the Cherry Hill COM Buffer from "ftp.cica.indiana.edu" and install
   as directed in their instructions.  I think that the file is called
   chcomb.zip.  This replaces the Windows 3.1 COM buffer with a more
   robust COM buffer that provides better COM port buffering.
b) Make the following modifications to the SYSTEM.INI file [386Enh]
   section.
   i) List all your COM ports, with their addresses and interrupts.
       COM1Irq=4
       COM1Base=03F8
       COM2Base=02F8
       COM2Irq=3
       COM3Irq=5
       COM3Base=03E8
   ii) Give the port to which your modem is attached a generous COM buffer
       COM1Buffer=10000
   iii) Change the COM port AutoAssign value for the COM port that you wish
       to use for your modem to ZERO.  This is the amount of time that
       Windows waits in seconds before handing control of that COM port to
       another application.  If you use WinQVT/net and then want to switch
       from session to session, and this value is at the default value of
       2 seconds, you are will get a GPF and Windows will crash.
       COM1AutoAssign=0

Additional notes:

PKTMUX will not work on SLIP8250 under Windows.  Perhaps it will work on
Peter's SLIP packet driver under Windows.

If you choose to use ETHERSL.COM instead of SLIP8250.COM, the
instructions are exactly the same with one crucial difference.  You will
have to DELETE the line "device=*vcd" from the [386Enh] section of 
SYSTEM.INI.  This will interfere with running regular Windows Comm 
applications (such asCrosstalk), and you will get lots of dropped characters 
etc.  This is therefore not recommended.

So to summarize:
a) Modify the SYSTEM.INI file in your WINDOWS directory as described above.
b) Establish a SLIP connection
c) Load SLIP8250, WINPKT, and PKTINT in that order
d) Load Windows.

This setup works with every TCP/IP application that I have tossed at it
including NuPOP, POPmail/PC, NCSA Telnet, CUTCP, WinQVT/net, the complete
Trumpet suite of programs.  Please note that if you use WTCPDRV.EXE and
WINTRUMP.EXE, you will have to load WTCPDRV.EXE before starting Windows.

Best wishes to all.

Ashok
-- End forwarded message --
----------------------------------------------------------------------
                              Ashok Aiyar 
                      Department of Biochemistry
                       CWRU School of Medicine
----------------------------------------------------------------------