============================================================================ THE DIGI_OS2.SYS DRIVER (PCI CARDS ONLY) ============================================================================ The digi_os2.sys driver is used with the pci/xem,xr,cx & epc/x con16. For the pci/4r,8r and xem card the device statement would look like this. device=c:\digi\digi_os2.sys /cn=3(The cn= parameter is used for naming the ports) For the pci cx/con16 and the epcx/c/con16 you need to run the digidevf.exe file which gives you the pci ID for the card. The two card type require the /t:96:10 the 96 is the pci ID and the 10 means that there is one c/con16 or epc/con16 on line sync line one and none on sync line 2. There are only 2 parameters used with driver. /cn=3 which names the port. /t:96:10 which is used for the cx & epc/x There are a couple of errors that you may see. Both errors are fixed with the beta driver. 1. Error (board1) couldn't reset board. 2. Error internal error 003. ============================================================================ BASIC TROUBLE SHOOTING FOR ALL DRIVERS ============================================================================ To verify that the digi is working after the driver is loaded. 1. Use dmode to see if os2 sees the ports. Example: dmode com3 The result should look something like this. Maximimum Baud for this device=115200 com3 38400 N,8,1 TO=OFF,XON=OFF,IDSR=OFF,ODSR=OFF,OCTS=OFF,RTS=ON,DTR=ON,ALT=OFF,QW=ON 2. Next type (dir>com3) a terminal or printer will display the directory. When using a modem you would see the rxd & txd lights flash. When using a modem you can also type(echo atdt phone#>com3 and the modem will dail the number.. 3. Included with the driver is a os2 diags called dgos2ud.exe, it requires a loopback on the port to run. The options for the diags are very simple. SELECT PORT SHORT TEST CONTINUOUS TEST DISPLAY ERROR LOG LOG FILE (disabled) EXIT