Advantech PCM-3618, Руководство пользователя

Страница: 20 / 28

PCM-3618 User Manual 12
3.1 Operating Environment Selection
Set jumper 8 (JP8) to correspond with your desired software operating environment.
Connect the left two pins of JP8 to operate in DOS or Windows 3.1 mode, as shown
below. Connect the right two pins to operate in Windows 95/98/NT mode.
3.1.1 Driver Installation for DOS Users
Make a duplicate copy of the driver diskette in case the original disk becomes lost or
damaged. Copy the files to a sub directory on your hard disk if you wish.
3.2 Card Setup
The PCM-3618's driver determines the configuration of the installed cards by reading
a data file, GEN-DRV.CNF. When you first install the PCM-3618, and each time you
change the card's address and IRQ, you will need to run the card setup program to
save the settings to the configuration file. Program files should be installed to the
HDD. Insert the driver disk in your computer, type DOSINST from the A: (or
B:)prompt and press enter. Once the files have been installed, type SETUP from the
\COMLIB\BIN prompt and press ENTER. After the screen shows up, move the cursor
bar (using the arrow keys or the mouse) to the general serial board field and press
ENTER. When you finish setting up the ports, press the ESC key to return to the pre-
vious windows. Press F10 to save the new configuration or ESC to quit without sav-
ing. The setup program will then create a new configuration data file GEN-DRV.CNF.
Its a simple example program capable of sending and receiving data after each port
is opened with selected communication parameters. As Windows 3.x features multi-
tasking, multiple windows for the ports can appear simultaneously under TTY. How-
ever, Terminal, the application provided by Windows is limited to COM1~COM4.
After completing the installation, restart Windows. And additional line "comm.drv =
sercomm.drv", will appear for the PCM-3618 in the [boot] section of the Windows
SYSTEM.INI file. In addition, a Windows group "PC-ComLIB Standard COMM Driver"
will be generated for reconfiguration, driver removal, etc. At this point, you are ready
to execute applications that support Windows COMM API calls.