Driver & Board Installation

How to check if a Synway voice board and the driver are successfully installed?

The following 3 conditions are indicators that the hardware and driver are properly installed:

1) In ‘Device Manager’ of Windows operating system, under ‘Sound, video and game controllers’, check that all models of boards installed on the computer are present and without the ‘!’ mark before their names.

2) Run shconfig.exe under the installation directory (usually ‘/ShCti/’). Click on ‘Default’. The number of boards and their models in the list should correspond with those actually installed. Click on ‘Apply’. A message should appear on the top-left corner or a dialog should pop up to indicate that the current configuration is verified.

3) The test program – test.exe – can be started; the number and type of channels in the list should fit well with the actual situation.

Which operating systems does the driver support?

The driver supports Windows 2012, Windows 8, Windows 7, Windows vista, Windows 2000, Windows XP, and Linux operating systems.

Board interrupt cannot be detected at board initialization, Why?

Possible causes: A. Poor connection due to board not being properly inserted into the slot. B. Incompatibility with the host (or mainboard) C. Llinux system restart after the sleep mode as the driver will release the source during the sleep time.

Certain types of board cannot be found at initialization. Why?

Possible causes:

A. If the error message states a model that is different from the one installed, it could be that the ShConfig.ini file is not properly configured or the incorrect driver was installed. B. If the error message states a model that is in fact already installed, it could be that: ① The voice board is not positioned properly in the slot. ② The slot is damaged. ③ The voice board itself could be faulty (check if obvious physical damages are present).

The board cannot be found in the manage device after you insert and install it. Why?

Possible causes: A. The voice board is not positioned properly in the slot or the slot is damaged. B. Incompatibility with the host (or mainboard) C. The voice board itself could be faulty (check if obvious physical damages are present). D. The power supply is not appropriate for the board (See Q10 in Chapter 1 for the table ‘Power Supply for Each Board Model’).