home *** CD-ROM | disk | FTP | other *** search
-
- HAPNDRSI Device Driver for the DRSI PC-Packet Adapter
-
- by Jack Botner, VE3LNY August 15, 1990
-
- (C) Copyright HAPN Hamilton and Area Packet Network 1990
-
- Jack Botner H. A. P. N.
- 222 Divadale Drive Box 4466, Station D
- Toronto, Ontario Hamilton, Ontario
- Canada M4G 2P7 Canada L8V 4S7
-
- Compuserve: 73327,176 (private mail only, please)
-
-
- Introduction
- ------------
-
- This device driver allows the DRSI PC-Packet Adapter to operate with
- the HAPN-1 software. The software developed to support the HAPN-1
- adapter is very user-friendly and provides a high level of function.
- In the HAPN implementation, all Level-1 (hardware) support functions
- are done by the DOS device driver, making it possible to support
- different adapters by changing only the device driver. Higher-level
- functions (AX.25, KISS, etc.) are provided by separate modules that
- are independent of the hardware that is being used.
-
- This driver is installed as a DOS device driver by placing an entry in
- CONFIG.SYS. It takes over all the hardware functions related to the
- adapter and provides an application program interface for accessing
- the packet queues and other adapter functions.
-
- To use this device driver with MSYS, a module named HAPNKISS.COM is
- required to provide the KISS interface between MSYS and the device
- driver. Alternatively, the HAPN AX.25 Program Library (available from
- HAPN) may be used to provide the usual AX.25 communications support.
-
-
- Installing HAPNDRSI.SYS
- -----------------------
-
- HAPNDRSI.SYS is installed by placing a device entry in your boot disk
- CONFIG.SYS file. For floppy disk only systems, a copy of HAPNDRSI.SYS must
- be placed on the boot diskette. The CONFIG.SYS entry appears as follows.
- All command line parameters appear within square brackets, which means
- that they are optional. The default values are satisfactory for most
- installations. If the parameters are coded, they must not contain any
- blanks between the parameters.
-
- device=[d:\path\]hapndrsi.sys [base=bbb][,irq=i][,ttsiz=z][,cts0=xx]
- [,duplex0=yyy][,cts1=xx][,duplex1=yyy]
- [,rxbuffers=rr][,txbuffers=tt]
- [,baud0=nnnn][,baud1=nnnn][,pri=y]
- [,tim=alt]
-
- where bbb is the adapter 8530 base address (in hex). The default
- value is 300. This value must match the setting of sw1-1.
- i is the IRQ (interrupt) level. Values may be 0 through 7, and
- the default value is 2. This value must match the setting
- of sw1-3 through 8.
- rr is the number of Rx buffers to allocate. Minimum
- number is 5, maximum number is 25, default number is 10.
- tt is the number of Tx buffers to allocate. Minimum
- number is 5, maximum number is 30, default number is 15.
- xx is the clear-to-send delay for each port in timer ticks (55 ms).
- Values are 0 to 99, with default value 0.
- yyy is hdx or fdx (only 1st letter scanned). Default is hdx.
- z is the size of the trace table in kbytes. May be between
- 1 and 9. The default value is 4. Set it smaller to conserve
- memory and larger to do datastream debugging.
- nnnn to specify the baud rate when the driver is used with an
- application that is unable to set up the baudrate. The
- default value is 1200.
- pri=y tells the driver to change the priority on the 8259 interrupt
- controller so that the irq level specified for this adapter
- has the highest priority. Don't use this unless you understand
- what you're doing. Mainly used when interrupt overruns and
- underruns are a problem.
- tim=alt tells the driver to use int 1c (hex) for the timer tick
- interrupt instead of int 8. Int 8 is generally more reliable
- when programs are run that use the timer tick interrupt but
- do not share it properly; however in some cases it may be
- desired to use int 1c instead.
-
- In its default configuration, HAPNDRSI.SYS uses 25K of memory. The amount
- of memory depends on the number of Rx and Tx buffers allocated, and the
- size of the trace table. For example, if you specify 8 Rx and 10 Tx
- buffers, and a 1K trace table, 20K of memory will be taken. If you're
- short of memory try using the minimum buffers but performance may suffer
- badly at high packet volumes.
-
- Example of CONFIG.SYS entry with no command line parameters:
-
- device=hapndrsi.sys
-
- or
-
- device=c:\msys\hapndrsi.sys
-
- Example of CONFIG.SYS entry with command line parameters to minimize
- memory requirements and use different irq interrupt:
-
- device=hapndrsi.sys irq=7,rxbuf=5,txbuf=5,ttsiz=1
-
-
- Caution
- -------
-
- This software is currently at BETA test level. It probably contains
- some bugs. If you experience a problem with it, try to describe the
- environment and symptoms as thoroughly as possible and let me know about
- it. I'll try to fix it if I can.
-
-