home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
DIGI_OS2.ZIP
/
INSTALL.DOC
< prev
next >
Wrap
Text File
|
1990-06-11
|
6KB
|
147 lines
5/1/90
DigiBoard Non-Intelligent board OS/2 Device Driver Version 1.4.0
Installation Guide
Files
There are 2 files on the distribution diskette that you will need to
install the MC/X driver:
DGX.SYS - The executable device driver.
INSTALL.DOC - this file.
Additionally, a utility program to assist in establishing communications
settings on the additional serial ports is included.
DMODE.EXE - a 'MODE' work-alike utility
DMODE.DOC - related documentation for above program.
Note that if the driver file (DGX.SYS) is not placed in the root
directory, its full path must be given on the line in the CONFIG.SYS
file.
In order to have the driver load, the following line must be included
in you 'CONFIG.SYS' file.
device=dgx.sys
Without any arguments thus the driver comes up with the following defaults:
[ Port addresses in Hexadecimal ]
1 8-channel PC/8 board
Status Port = 140
Channel I/O port addresses 100, 108, 110, 118, 120, 128, 130, 138
Device names are assigned to COM3 COM4 COM5 COM6 COM7 COM8 COM9 COM10
The default modes for each of the channels follow the MS OS/2 standards of:
1200 Baud, 7 data, 1 stop, Even Parity, RTS control-mode.
GLOBAL Command line arguments:
/n:device_names sets up the naming algorithm to be used to
generate device names. Consists of an
optional new stem followed by the starting
device number. Without the new stem, 'COM'
will be used. Numbering of channels will
continue contiguously from one board to the
next in the order that the boards are
specified on the command line.
/n:"digi"0 DIGI0,DIGI1,DIGI2,....DIGI7
/n:4 COM4,COM5,COM6,....COM11
/b:baud_rate OS/2 by default sets up all serial devices
at 1200 baud at initialization-time. Use this
option to override that value.
/b:9600 [ all channels initialize to 9600 baud ]
/d:data_type OS/2 by default sets up all serial devices
to Even Parity, 7 data bits, 1 stop bit at
initialization-time. Use this option to
override those value. Syntax is
ParityDataStop
[E|O|N] [8|7|6|5|] [1|2]
All three values MUST be provided.
/d:N81 [ all channels initialize to No parity, ]
[ 8 data bits, 1 stop bit ]
PER-CARD arguments to the driver MUST be in complete sets indentifying
Port address range and IRQ number. It is HIGHLY reccomended to
fully specify ALL boards in your system right on the command line
to ensure that current settings are plainly visible.
----------------
PC/16 Exception:
----------------
Since the I/O port settings for the PC/16 are set at the factory and
are NOT configureable by the user, any PC/16 MUST !! be specified
with the following set of arguments:
device=dgx.sys /p:140 /c:16 /i:[interrupt_line]
The '/p:140' and '/c:16' arguments are very important as they tell
the driver that this is a 16-channel board!!
If any of the below arguments ar given, ALL cards in the system must
be thus fully described. In other words, if you are running ANY
other configuration except the default (see above 'Default
Configuration'), then the each card in your system MUST BE FULLY
DESCRIBED by these arguments.
/p:io_port_address set the I/O port address range ceiling.
This argument specifies the top of the
[Hexadecimal] 40-port range of I/O port
addresses that will be used by the PC/X.
This address should correspond to the
dip-switch setting of the Status Port.
Individual channel port addresses should then
begin [hex] 40 BELOW this address, occupying
a congiguous block, each channel a [hex] 8
step from the previous.
/p:280 [ set card to Status port address 280 (hex)]
[ IO Port for Channel 1 = 240 (hex) ]
[ IO Port for Channel 2 = 248 (hex) ]
[ IO Port for Channel 3 = 250 (hex) ]
[ IO Port for Channel 4 = 258 (hex) ]
[ .... etc. ....... ]
/i:IRQ_num set the IRQ line number from among the legal
options for the PC/X.
/i:12 [ set card to IRQ 12 (decimal) ]
/c:channels set the number of channels (4, 8 or 16)
This is required for each card that does NOT
have 8 channels on it.
/c:4 [ assume only 4 channels on card ]
[ NOTE: The driver may crash the System ]
[ if you only have a 4-port PC/X ]
[ and you do not specify this option ]
Trouble-shooting:
If the driver comes up with a problem message please check that your
configuration matches the switch settings on the card. If it still
fails, try actually powering down the system and then back up. If it
STILL fails, give DigiBoard Technical Support a call and talk it
through.
In general, a good way to test the basic functionality of the driver is
to hook up a terminal to one of the ports; (say, for example, COM3)
and set it up for the correct Baud rate, Handshake, and Data type
characteristics; and simply try to re-direct output to it from the
command prompt.
C:\>dir > com3
If the terminal is set up correctly (typically the above defaults) you
should get the directory listing comming out on it. If there is no
output, or if the above commands hangs, then you may need some technical
support. It is possible that the board is not functioning properly.