README.TXT Driver File Contents (NT4_W2K_XP_W2K3_502_503_508_514.zip)

BSCV2 SUPPORT FOR WINDOWS UTILITY SET
-----------------------------------------------
Sangoma Technologies Inc. does not assume any liability for damages as
a result of the use or misuse of these programs, and disclaims all
warranties, either express or implied, with regard to this software.
Use these programs at your own risk.

IF YOU HAVE NOT YET INSTALLED THIS PACKAGE, READ INSTALL.TXT FIRST!
It explains the installation process.

UTILITY SET CONTENTS
--------------------
The following programs are utilities to aid the NAPI application developer:

NTEST.EXE (NTESTer)
NRX.EXE (Receive Function Tester)
NMON.EXE (NMONitor)
NCARDS.EXE (NCARDS)
NCONFIG.EXE (NCONFIGurator)
Ncnfg508.exe (S508 configurator)
Ncnfg514.exe (S514 configurator)
WINNLOAD.EXE (WINNLOADer)
Bsldr508.exe (S508 loader)
Bsldr514.exe (S514 loader)

They are described individually below.


NCONFIG
-------
This program is used to set the configuration parameters for the BSC code
running on the SDLA card, and the NAPI library.  It will create new logical
card configuration entries, or edit current ones.
Use Ncnfg508.exe to configure S508, Ncnfg514.exe to configure S514.

The card and code configuration parameters are explained in the BSC Support
for MS-DOS Operations Manual.

Any changes made to the card configuration will not take effect until the 
card is reloaded using WINNLOAD.  The driver interface options will take
effect only when the DLL is (re)loaded by a first-time calling application.

The concept of a logical card is explained in DEVELOP.TXT and in the NAPI
On-Line Function Reference (NAPI(32).HLP) for the functions NAPIRegisterCard()
and NAPIUnregisterCard().  Since it is likely that not all 16 entries will
be used for separate cards, it is possible to use these extra "configuration
entries" to store different card configurations that may be used at different
times for the same physical card.  A logical card number can thus be thought
of as an index within a database of configuration records.  If the application
program does not have the capability of reconfiguring the SDLA card, the
WINNLOAD utility could be run using a different logical card number that
indexes this new configuration as set earlier by NCONFIG.

This program does not have the option to delete a logical card configuration.
In order to do this, the SDLA.INI file needs to be edited such that the
entire [sdla<card_number_to_delete>] section is deleted.  You may also wish
to delete the configuration data file, normally called bsc_cfg.<card #>.
In addition, for Windows NT/2000, the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SDLA\Parameters\sdla<#>
should be deleted as well using REGEDT32.

The default logical card number for these utilities is usually 0, and it is
assumed that this number is used to reference a physical card.  When NCONFIG
is loaded for the first time, an entry for logical card 0 is created using
predefined default values for the configuration.

In addition, for Windows NT/2000, the service key is created in the registry
along with the required service values as shown below:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SDLA:
ErrorControl: REG_DWORD: 0x1
Start: REG_DWORD: 0x2 (automatic loading - set to 0x3 for manual)
Type: REG_DWORD: 0x1 (kernel driver)

The startup mode may be changed in Control Panel/Devices, or by using
REGEDT32 to edit the value manually.  If the sdla.sys driver is moved, or
if the system is having difficulty finding it, you may set the value
ImagePath: REG_EXPAND_SZ: \SystemRoot\System32\Drivers\sdla.sys,
for example.

Once the service name is created in the registry, the operating system must
be rebooted for the service manager to recognize it.

Note that the SDLA device driver must be restarted if new logical cards are
added or if cards are deleted.  This may be done using Control Panel/Devices
or by using the command shell: NET STOP SDLA, then NET START SDLA.


WINNLOAD
--------
This loader is designed only to load the BSC code bsc.502 and bscmp.502,
although the names could be different as specified using NCONFIG.  It should
also be able to handle any upgrades to this code; if not, a newer version of
WINNLOAD will be released as well.  It will not load code other than BSC.
Use the bsc.502 code for point-to-point operation, and bscmp.502 for multi-
point operation.
Use Bsldr508.exe to load S508, Bsldr514.exe to load S514.

The command line arguments are as follows, and may be changed by selecting 
the File/Properties option in Program Manager:
        WINNLOAD.EXE [-<lcn1> ][-<lcn2> ]...
where lcnN is the logical card number N to quick-load.  For example, the most
likely command-line for quick-loading would be WINNLOAD.EXE -0, to load card
number 0.  Quick-loading is non-interactive in the sense that no user input
is required unless an error occurs.  If no command-line parameter is
provided, the program starts interactively where the user may then choose
a card to load and observe the details of the loading procedure, obtaining
information such as the determined CPU speed of the SDLA card and the version
of the BSC code that has been downloaded.  

Non-interactive mode may be used once it is anticipated that loading will run 
smoothly.  In this mode, a window will appear for the duration of the loading
procedure to report the progress made, and the program will terminate once
all cards specified on the command-line have been loaded.  It may be very
useful to have a dedicated program item set for non-interactive mode placed
in the STARTUP group so that the required card(s) may be loaded during
Windows startup.  The INSTALL program will place such a program item in the
dedicated BSC program group for this purpose and to serve as an example for
loading card 0.

Windows 3.1 and NT/2000 only:
Note that the loader will refuse to load a card if it is currently being
used (i.e. it is registered for use by an application).  It will also prevent
applications from registering while the card is being loaded, which will
likely not occur in Windows 3.1 (by not being pre-emptive).


NCARDS
------
This is a small program that continually checks the logical card existence
and registration status.  

Windows 3.1 and 95:
The card "exists" if a registration section is present for it in SDLA.INI
since the last time the driver was loaded by a first-time calling
application.  Existence is indicated by a filled circle next to the card
number.

Windows NT/2000:
The card "exists" if the corresponding key in the registry was present when
the SDLA device driver was started.  The addition or removal of logical
card configurations are not reflected by this program (or any other NAPI
application) until the driver is restarted, either manually or by a system
reboot, assuming its startup mode is automatic.  Existence is indicated by a 
filled circle next to the card number.

The card is registered for use by an application if the corresponding circle
is filled as well.


NTEST
-----
This program provides some of the BSC functions to test the link and to serve
as an example application.  The source code is provided as well.

Command Line: NTEST.EXE [-<lcn>]
Example: NTEST.EXE -6
The command line may be modified by selecting the icon in the program group
and choosing File | Properties... (You may wish to copy the program item
first.)
Specifying the logical card number on the command line bypasses the option
of asking for the card on startup, as well as the default card number.


NRX
---
This program provides receive-only functionality for the point-to-point
code. It is primarily used for passive receive mode.

Command Line: NRX.EXE [-<lcn>]
Example: NRX.EXE -6
The command line may be modified by selecting the icon in the program group
and choosing File | Properties... (You may wish to copy the program item
first.)
Specifying the logical card number on the command line bypasses the option
of asking for the card on startup, as well as the default card number.


NMON
----
This is a statistics monitoring program.

Command Line: NMON.EXE [-<lcn>]
Example: NMON.EXE -6
The command line may be modified by selecting the icon in the program group
and choosing File | Properties... (You may wish to copy the program item
first.)
Specifying the logical card number on the command line bypasses the option
of asking for the card on startup, as well as the default card number.


Documentation:
--------------

The documentation on the operation of the NAPI32 in the 'NAPI32 User Function Reference' 
Help file is supplemented by the document titled 'BSC Support for Sangoma Cards Hardware
Interface Manual' in the file BiSynch.pdf in the directory 
'Manuals_for_communications_APIs' on the CD.

The BSC Hardware manual includes general, information on Sangoma's BSC implementation that
is not specific to Windows or any other operating system. These include notes on all the 
return codes generated by the on-board microcode.

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web5, load: 0.45