**********************************************************
* *
* INSTALLATION OF BUS-TECH PBSA FIRMWARE *
* *
**********************************************************
SECTION 1
*******************************
* Minimum System Requirements *
*******************************
1.1 The following are the minimum levels of Bus-Tech Channel
Drivers required to operate with this firmware release:
* Novell NetWare: NetWare Channel Drivers Version 5.4.2
* Windows NT: Windows NT Channel Drivers Version 5.4.2
1.2 ***CAUTION*** If your Channel Drivers are not at the above
version level or higher make sure that this new firmware is
installed ***before*** you upgrade to Channel Drivers
Version 5.4.2 or higher.
1.3 If your current Channel Drivers are version 5.1.2 or less:
NetWare users should use the procedure in Section 2.
Windows NT users should use the procedure in Section 4.
After the firmware upgrade is complete, upgrade to the latest
version of Channel Drivers. See the readme file that comes with
the Channel Drivers for installation information.
1.4 If your current Channel Drivers are version 5.4.2 or above:
NetWare users should use the procedure in Section 3.
Windows NT users should use the procedure in Section 5.
SECTION 2
*************************************************
* Installing new firmware on NetWare Servers *
* using Channel Drivers version 5.1.2 and below *
*************************************************
2.1 If you are running any Netware NLM's that use the Bus-Tech
Channel Board, please unload them first before proceeding.
(i.e. for NetWare for SAA, type CSDOWN, for TCP/IP Passthrough
type UNLOAD BTIDLBR or for DataBlaster2 type UNLOAD BTIBLAST).
2.2 At the Netware Console prompt (:) type LOAD BTITOOL <ENTER>.
The BTITOOL NLM will be loaded.
2.3 At the Netware Console prompt (:) type BTITOOL <ENTER>.
The screen will clear and the BTITOOL> prompt will appear.
2.4 Insert a floppy disk that contains the firmware file named
"PBSA.HEX" that was provided with this release into the A:
drive on the server.
2.5 At the BTITOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the PBSA Card you wish to load.
(Note: the SLOT=x parameter is only required if more than one
Channel Board is installed in the server. If you are not sure
what slot number to use, invoke the SHOW ALL command to determine
the correct slot number.)
When loading completes, the console will display the BTITOOL
command prompt.
2.6 If there is a 2nd PBSA Card installed in your server, perform
the next step. If not, GO TO STEP 2.8
2.7 At the BTITOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x) = the Slot Number of the 2nd PBSA Card.
When loading completes the console will display the BTITOOL
command prompt.
2.8 Type EXIT <ENTER> to exit BTITOOL.
2.9 You must now DOWN the server and EXIT to the DOS prompt.
2.10 Perform a hardware REBOOT on the server for the changes to
take effect.
SECTION 3
*************************************************
* Installing new firmware on NetWare Servers *
* using Channel Drivers version 5.4.2 and above *
*************************************************
3.1 If you are running any Netware NLM's that use the Channel Board,
please unload them first before proceeding.
(i.e. for NetWare for SAA, type CSDOWN, for TCP/IP Passthrough
type UNLOAD BTIDLBR or for DataBlaster2 type UNLOAD BTIBLAST).
3.2 At the Netware Console prompt (:) type LOAD CHLTOOL <ENTER>.
The CHLTOOL NLM will be loaded.
3.3 At the Netware Console prompt (:) type CHLTOOL <ENTER>.
The screen will clear and the CHLTOOL> prompt will appear.
3.4 Insert a floppy disk that contains the firmware file named
"PBSA.HEX" that was provided with this release into the A:
drive on the server.
3.5 At the CHLTOOL prompt (>), type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the PBSA Card you wish to load.
(Note: the SLOT=x parameter is only required if more than one
Channel Board is installed in the server. If you are not sure
what slot number to use, invoke the SHOW ALL command to determine
the correct slot number.)
When loading completes, the console will display the CHLTOOL
command prompt.
3.6 If there is a 2nd PBSA Card installed in your server, perform
the next step. If not, GO TO STEP 3.8
3.7 At the CHLTOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x) = the Slot Number of the 2nd PBSA Card.
When loading completes the console will display the CHLTOOL
command prompt.
3.8 Type EXIT <ENTER> to exit CHLTOOL.
3.9 You must now DOWN the server and EXIT to the DOS prompt.
3.10 Perform a hardware REBOOT on the server for the changes to
take effect.
SECTION 4
******************************************************
* Installation of new firmware on Windows NT Servers *
* using Channel Drivers version 5.1.2 and below *
******************************************************
4.1 If you are running Microsoft SNA Server, stop the SNA Service.
4.2 Start an MS-DOS CMD Prompt session.
4.3 At the MS-DOS CMD prompt, change to directory C:\BTI.
4.4 At the MS-DOS CMD prompt, type: BTITOOL <ENTER>.
The screen will clear and the BTITOOL> prompt will appear.
4.5 Insert a floppy disk that contains the firmware file named
"PBSA.HEX" that was provided with this release into the A:
drive on the server.
4.6 At the BTITOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the PBSA Card you wish to load.
(Note: the SLOT=x parameter is only required if more than one
Channel Board is installed in the server. If you are not sure
what slot number to use, invoke the SHOW ALL command to determine
the correct slot number.)
When loading is complete the console will display the BTITOOL
command prompt.
4.7 If there is a 2nd PBSA Card installed in your server, perform
the next step. If not, GO TO STEP 4.9
4.8 At the BTITOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the 2nd PBSA Card.
When loading is complete the console will display the BTITOOL
command prompt.
4.9 Type EXIT <ENTER> to exit BTITOOL.
4.10 You must now SHUTDOWN the server.
4.11 Perform a hardware REBOOT on the server for the changes to
take effect.
SECTION 5
******************************************************
* Installation of new firmware on Windows NT Servers *
* using Channel Drivers version 5.4.2 and above *
******************************************************
5.1 If you are running Microsoft SNA Server, stop the SNA Service.
5.2 Start an MS-DOS CMD Prompt session.
5.3 At the MS-DOS CMD prompt, change to directory C:\CHANNEL.
5.4 At the MS-DOS CMD prompt, type: CHLTOOL <ENTER>.
The screen will clear and the CHLTOOL> prompt will appear.
5.5 Insert a floppy disk that contains the firmware file named
"PBSA.HEX" that was provided with this release into the A:
drive on the server.
5.6 At the CHLTOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the PBSA Card you wish to load.
(Note: the SLOT=x parameter is only required if more than one
Channel Board is installed in the server. If you are not sure
what slot number to use, invoke the SHOW ALL command to determine
the correct slot number.)
When loading is complete the console will display the CHLTOOL
command prompt.
5.7 If there is a 2nd PBSA Card installed in your server, perform
the next step. If not, GO TO STEP 5.9
5.8 At the CHLTOOL prompt (>) type the following line:
LOAD FIRMWARE A:PBSA.HEX SLOT=x <ENTER>
where (x)=the Slot Number of the 2nd PBSA Card.
When loading is complete the console will display the CHLTOOL
command prompt.
5.9 Type EXIT <ENTER> to exit CHLTOOL.
5.10 You must now SHUTDOWN the server.
5.11 Perform a hardware REBOOT on the server for the changes to
take effect.
SECTION 6
******************************************************
* PBSA Diagnostic Utilities *
* (used under the direction of Product Support only) *
******************************************************
6.1 PBSAUP.EXE - Used to gather traces and memory contents from the
PBSA, and save it to a DOS file.
Execute this file on a DOS PC that is connected, through a Null
Modem Cable to the DB9 connector on the PBSA Board.
Type PBSAUP for help on this utility.
6.2 PBSADOWN.EXE - Used to transfer data from a DOS file to the PBSA.
Normally used for download of new Emulation Firmware.
Execute this file on a DOS PC that is connected, through a Null
Modem Cable to the DB9 connector on the PBSA Board.
Type PBSADOWN for help on this utility.
6.3 FIRMWARE TRACES - Occasionally you may be directed by Bus-Tech
Product Support to retrieve an internal trace of activities in
the Channel Board. Traces are retrieved via a PC connected to the
DB9 connector on the PBSA Board using a null modem cable.
The syntax of the MS-DOS command to upload the trace table is:
PBSAUP filename 1000088c 10000
:where filename is the name of the target file to be created on the
connected PC. (i.e. PBSATRC1.TRB)
The Trace File that is uploaded is a binary trace file. It must be
formatted using the MS-DOS Utility BTIFMT.EXE which is supplied
with this release.
6.4 BOARD DUMP - You may be directed by Bus-Tech Product Support to
retrieve all of the internal structures needed to diagnose a problem.
This information is retrieved via a PC connected to the DB9 connector
on the PBSA Board using a null modem cable. The syntax of the MS-DOS
command to upload the trace table is:
PBSAUP DMPPBSA.LIS
:where DMPPBSA.LIS is a data file supplied with this release. It contains
a list of files that will be created as a result of running this command
(all files will have a .MEM extension). The file also contains the start
address of each memory region, and the number of bytes to dump.
All of the .MEM files created should be passed to Bus-Tech Product Support
for analysis.
For NT system users, there is a batch file that can be run on the NT
server which uses CHLTOOL to obtain this same information. This does not
require a separate PC or a serial port connection. The batch file requires
2 command line parameters when run. The first parameter is the path of
where to place the files created. The second parameter is the slot number
of the board. The batch file can be run from an MS-DOS prompt window
and the syntax is:
DMP_PBSA directory slot_number
An example using this to dump the data to a floppy in drive A, for a
board in slot number 196619 would be:
DMP_PBSA a: 196619
This will create several .MEM files, and save a firmware trace to a .TRB
file. All of these files should be passed to Bus-Tech Product Support
for analysis.
********************
* Additional Notes *
********************
For optimum performance, you should always ensure that the Bus-Tech
Channel Drivers running on your Server are at the most current
revision level.
Please visit our WEB site at www.support.bustech.com for details on
obtaining the latest version of Channel Drivers.
***End of README.TXT***
Download Driver Pack
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.