INSTALL.TXT Driver File Contents (NT4_W2K_XP_W2K3_502_503_508_514.zip)

SDLA PROTOCOL SUPPORT FOR WINDOWS INSTALLATION
----------------------------------------------
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.

INSTALLATION
============
To install both the utility set and the development kit, run the INSTALL.EXE
program that comes with these files, either by launching it from File
Manager (Windows Explorer), selecting File/Run from Program Manager(on NT3.5),
or by some other means.

The INSTALL program is Windows 95/NT4/Windows 2000 compatible.
The installation script assumes you have Program Manager running (on NT3.5),
as opposed to some other desktop manager, within which new program groups and
items may be placed. 

You may install from a temporary directory on a hard disk, or from a floppy.
Once the installation is complete, the temporary directory may be removed
so long as you still keep a complete copy of all files with the original 
distribution.  It is highly recommended that you do not install any of the 
files to the same directory as the source!  In other words, if you are 
running INSTALL from C:\WINABC, do NOT specify C:\WINABC as any of the 
destination directories.  Nothing fatal will occur, except that the files
will be inconveniently intermixed.

If all goes well, you will be asked to enter the name of the Windows System
directory (if different than the one detected), the drivers directory (for
Windows NT/2000) and the names of the directories to which these files will be
copied.  It will automatically create the directories if they do not exist.
If they do exist, the files will be copied to them without warning, unless an
overwrite attempt occurs.  Some .INI files will be created (or updated) in the
Windows directory, and the appropriate system and driver files will be copied
into the specified directories, and will also be placed in the development
directory to keep the file groups together.  A program manager group will be
created (unless it exists already) and various program items will be added.

The INSTALL program is an independent utility that uses a specific script
to perform the required installation functions.  It is NOT the same type of
script used by Microsoft Setup.  You are free to experiment with the script
if you want to set up custom installations, but we (Sangoma Technologies)
remind you that we are not responsible for what you do with this Sangoma
Installer program, and for the havoc that may be caused from your misuse of 
it.

Once installation is complete, you must run the Configurator appropriate for
the hardware type (S502/S503, S508 or S514) to set up the
hardware and protocol options of logical card 0, and for any other logical
cards that may be used.  For more information on the Configurator and on
logical cards, read the README.TXT file.

None of the installation-related files will be copied (INSTALL.EXE,
INSTALL.INS, and INSTALL.TXT).


INSTALLING WINDOWS NT SUPPORT TO NON-WINDOWS NT PLATFORM
--------------------------------------------------------
If your development platform is on Windows 3.1, install the Windows NT
development kit, but specify an alternate directory for the driver, and later
delete the driver file.  Also, do not run the Configurator, as it will
attempt to install the driver as a service in the registry.  None of the
other utility programs can be run either.

If your development platform is on Windows 95, you should be installing the
Windows 95 development kit.  Any applications built using the Windows 95
kit will also run unaltered on Windows NT.  It is not necessary to run
the Configurator if no card is installed.


INSTALLING WINDOWS 95 SUPPORT TO NON-WINDOWS 95 PLATFORM
--------------------------------------------------------
If your development platform is on Windows 3.1, install the Windows 95
development kit.  Do not run the Configurator or any other utility.

If your development platform is on Windows NT, you should be installing the
Windows NT development kit.  Any applications built using the Windows NT
kit will also run unaltered on Windows 95.  You do not have to run the
Configurator if no card is installed.

Note for S514 PCI card under Windows 2000 only:
===============================================
If you want to prevent the "Hardware Wizard" from starting each time system boots:
after you have installed and configured SDLA software run "Hardware Wizard"
from "Control Pannel\Syste\Hardware". When the wizard starts and finds the new device (S514)
click on "Next", choose "Display a list of the known drivers for this device...",
click "Next", in "Hardware Types:" choose "Network adapters", click "Next" then "Have Disk..." 
and browse to the directory where SDLA.inf and SDLA.SYS files are found, click OK.
If "Update Driver Warning" or "Digital Signature Not Found" appears click on "Yes".


UNINSTALLING ENTIRE SOFTWARE PACKAGE
====================================
If you will be upgrading this package, it is advisable that you completely
uninstall it first.

To completely remove this software from the system, do the following:

1. Make sure all ?API applications are closed.

2. Windows NT/2000:
   At the DOS prompt, type 'net stop sdla'.
   Then run Regedt32, the registry editor, and delete the following key:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SDLA

   Windows 3.1:
   Go to Control Panel - Drivers, and remove the S502 series driver.

3. Delete the following files:
        Windows NT:
        \winnt35\system32\?api32mc.dll
        \winnt35\system32\drivers\sdla.sys
        \winnt35\sdla.ini

        Windows 95:
        \windows\system\?api32mc.dll
        \windows\sdla.ini

        Windows 3.1:
        \windows\system\?api.dll
        \windows\system\sdla.drv
        \windows\sdla.ini

   ** Substitute the appropriate character where ? appears above, depending
      on the protocol. DO NOT TYPE 'DEL ?API.DLL' as this will also delete
      the windows MAPI.DLL file.

4. Delete the development kit files at the location specified during
   installation.

5. Remove the program group from \WINNT\Profiles\All Users\Start Menu\Programs.

6. S514 card on Windows 2000 only: in "Device Manager" right click on 
   "Sangoma S514 PCI Adapter" choose "uninstall".

If you wish to upgrade while preserving your configuration, simply copy
or rename sdla.ini to mysdla.ini, install the new package on top of the
old one while responding YES to overwrite confirmations, and then copy
mysdla.ini back on top of sdla.ini (make sure you do this before running
the Configurator).  It would be wise to reboot at this point. If you cannot,
and wish to use the new package under Windows NT/2000, at the DOS prompt type
'net start sdla'.
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