The README.TXT file contains all text files that were distributed separately with new releases of the BitSURFR Pro.
In addition to the flash software (".sl" file), included with this upgrade are:
mot1116f.inf - Win95 & Win NT4.0 inf file for the BitSURFR Pro
Softload.exe - DOS utility for softloading
***********************************************************************************
Topics covered in this file are:
Installation of Win95 INF files (driver.txt)
Explanation of the operation of PPP (ppp.txt)
Instructions on upgrading the flash memory of the BitSURFR Pro
from previous releases. (flash.txt)
Instructions on the operation of the DOS utility SOFTLOAD.EXE (softload.txt)
Release notes for current and prior releases (release.txt)
***********************************************************************************
Installing the new INF file, MOT1116f.inf:
1) Removing the Bitsurfr Pro From Win 95 Go to the control panel and go into Modems
Highlight the BitSurfr PRO and click on Properties. Click on the Connection tab.
Click on the Advanced button.
Write down the Extra Settings string.
Then OK all of the Properties windows for the Bitsurfr PRO.
Then with the Bitsurfr Pro still highlighted hit the Remove button.
2) Removing the old Driver from Win 95
Go to the Windows Explorer and open up the Windows folder.
( Set explorer to "View All Files")
In the Windows folder open the INF folder.
In the INF folder look for any files named OEM0.INF or OEM1.INF etc.
Double click on the OEM file and a Notepad should open showing the contents of the
OEM file.
In the text of the OEM file, If the word MOTOROLA is listed for the manufacturer.
close the Notepad and delete that OEM file.
Open and view all OEM files and view them.
Delete only the ones that reference Motorola.
Note: In release 2 of Win 95 there is a folder named "Other" in the INF folder.
There are no OEM.INF files. Just open the "Other" folder and delete the MOT1116C.INF
file.
3) Reinstalling the Bitsurfr Pro.
Reboot the PC and let Win 95 detect the Bitsurfr Pro.
Use the MOT1116F.INF file when Win 95 asks for a driver change using the Browse button.
4) Bitsurfr Pro Properties
Go to the control panel and go into modems Highlight the BitSurfr PRO and click on
Properties.
Click on the Connection tab.
Click on the Advanced button.
Type in the Extra Settings string from step 1.
Then OK all of the Properties windows for the Bitsurfr PRO.
Close the Control Panel.
***********************************************************************************
Explanation of the operation of PPP
The BitSURFR Pro supports most authentication methods in conjunction with single-link
PPP by "passing through" all authentication messages.
The BitSURFR Pro supports the following three authentication methods in conjunction
with the multi-link PPP: Password Authentication Protocol (PAP), Challenge-Handshake
Authentication Protocol (CHAP) and Shiva Password Authentication Protocol (SPAP).
CHAP supports multiple authentication algorithms, and the BitSURFR Pro supports two
of these algorithms: CHAP-MD5 and CHAP-MS.
The CHAP feature supports two message modes: Pass-through and Respond. In
Pass-through mode the BitSURFR Pro passes all challenge messages to the DTE. In
Respond mode the BitSURFR Pro responds to all challenge messages by using the
provided password and the built-in algorithm. You must use Respond mode for
proper operation of Windows 95 Dial-up Networking when used with MD5-CHAP.
Your BitSURFR Pro defaults to the Pass-through mode. Respond mode is invoked either
by entering the AT command AT@M20="password" or the dial-string modifier
>P="password". The password in the dial-string modifier takes precedence over the
password stored by the AT@M20 command.
SPAP offers encryption of PAP passwords and is commonly used by Shiva Remote Access
Servers.
The AT command "AT@M2" is no longer needed to enable PAP or CHAP.
-------------------------------------------------
New AT Command:
The command "AT@B2=n", where "n" is a value 0-255, may be used to limit the number
of times the BitSURFR Pro will attempt to connect the second channel of a Multi-link
PPP call, if the first attempt fails. The default limit is 5. If you set the limit
to 0, then the BitSURFR Pro will continuously try to connect the second channel until
the first channel is dropped.
***********************************************************************************
Explanation of the process of softloading the BitSURFR Pro Flash memory
IF YOU ARE A WINDOWS USER (WIN3.X, WIN95, WIN NT):
IT IS RECOMMENDED THAT YOU SOFTLOAD USING THE SURFR SETUP UTILITY PROVIDED WITH YOUR
BITSURFR PRODUCT! SOFTLOAD.EXE AND MANUAL SOFTLOADING USING YMODEM-G CAN BE DONE,
BUT ARE NOT THE PREFERRED METHOD.
BitSURFR Pro Softload
The Motorola BitSURFR Pro utilizes flash memory to store the operating system
software. This memory can be upgraded or "reflashed" when necessary to
provide enhancements to the product. The softload process is accomplished by
uploading a new softload file from the PC or Mac attached to BitSURFR Pro
using Y-Modem G file transfer protocol found in most popular async
communications packages. The instructions below describe the steps necessary
to perform softloading. You may use the softload program for DOS which is
included in the softload directory. The readme.txt file describes exactly
how to use it. SURFR SETUP and SOFTLOAD.EXE are the least error prone methods
to softload the BitSURFR PRO.
------------------------------------------------------------------------------
WARNING: Once a file transfer has begun, the BSPro will lose all
functionality except the ability to softload. If the transfer is canceled
for any reason, the BSPro will re-enter the YModem-G receive mode and will
accept another softload attempt. The BSPro will not function otherwise until
a valid softload is completed.
If power is removed from the BSPro during a softload, when power is restored
the BSPro will immediately re-enter the YModem-G receive mode. Another
softload may proceed normally, except the file must be uploaded at 19200 bps,
regardless of the speed of the first softload. See the Softload Failure
section at the end of this chapter for further instructions.
------------------------------------------------------------------------------
* If there is a readme file accompanying the softload file, read it for a
description of the software contained in the softload file.
* For best results, the softload file should be uploaded from the PC or Mac's
hard disk instead of the floppy drive.
The following steps demonstrate a typical MANUAL softload session from a PC or Mac,
using async communications software such as HyperACCESS for PCs or
MicroPhone LT for Macs.
1. Configure the PC or Mac's communications software for 38400 or 19200 bps,
full-duplex asynchronous operation, 8-bit characters, no parity, one stop bit, and
RTS/CTS flow control.
Softloading can be done at any DTE speed supported by the BSPro. However,
no increase in softload throughput is achieved with DTE speeds past
38400bps.
2. Using the terminal emulation on the PC or Mac, send an AT command to the
BSPro. The BSPro will respond with OK.
3. Configure the BSPro for RTS/CTS flow control. This may be done using
either LocalMenu or the AT\Q3 command.
4. Verify the current operating system software of the BSPro using the ATI8
command. Note the current "Software Revision" and "Freshest File Stamp"
date.
5. Set a softload password using the AT%P1=x where x is a 1-8 character word.
A password is required to later initiate softloading. The current password
can be verified using the AT%P1? command.
6. Initiate softload using the command AT$Y=x (where x is the softload
password). The TA responds with either ERROR (if the password is invalid)
or the softload method banner (SOFTLOAD YGMS-1). This banner identifies
the download method and file format. The BSPro will send the message
READY to indicate that it is ready for softload, and will begin sending
the YModem-G initiation character (G).
7. Initiate the YModem-G file upload from the PC or Mac. Upload only the .SL
file to the BSPro. Do not attempt to send any other type file. The
transfer will take approximately 2.5 minutes at 38400 bps, or
approximately 4 minutes at 19200 bps. During the softload the TD
(Transmit Data) LED on the BSPro will blink green as the file is being
sent to the BSPro.
------------------------------------------------------------------------------
If any errors are encountered during the file transfer, the BSPro will
display an error code and the message "Softload failed! Restarting softload".
The BSPro will re-enter YModem-G receive mode and begin sending the YModem-G
initiation character (G). At this point a new file transfer may be started.
If a softload failure occurs, see the section at the end entitled Softload
Failure for instructions.
------------------------------------------------------------------------------
8. When the file transfer upload is complete, the BSPro will pause for several
seconds. Do not remove power from the BSPro during this pause! It will
then display the message "Softload successful, restarting TA". The BSPro
will reset itself and return to AT command mode. A D-channel
reinitialization will also be done. It is now operating with the software
upgrade.
9. Verify the new operating software using the ATI8 command as used in step 4.
Softload Failure
The BSPro can contain only one set of software at a time. During a softload,
the BSPro is replacing its existing software with the new software contained
in the softload file. For this reason, if the file transfer is interrupted
for any reason, then the software in the BSPro will be incomplete, and the
BSPro will be unable to function. In most cases, it will retain enough
functionality to perform another softload. A successful softload must be
performed before the BSPro will be able to operate normally.
* Canceling softload before a file transfer has been started.
When the AT$Y=x command is issued, the BSPro responds with the softload method
banner and the message READY. It will begin sending the YModem-G initiation
character (G). At this point it is possible to cancel the sofload, by
removing and reapplying power to the BSPro, as long as a file transfer has not
been started. Do not remove power from the BSPro if a file transfer has been
started. After a file transfer begins, it is impossible to return to the old
software.
* Interrupted file transfer
Do not cancel a file transfer, since this will render the BSPro unable to
function except to perform another softload. If a file transfer is
accidentally interrupted, then the BSPro will display an error code and the
message "Softload Failed! Restarting softload". The BSPro will then re-enter
the YModem-G receive mode and will send the YModem-G initiation character (G).
At this point a new file transfer may be started.
* Loss of power during a softload
If power to the BSPro is removed at any point during a softload after the file
transfer begins, then the BSPro will be unable to function, except to perform
another softload. When power is reapplied to the BSPro, it will immediately
enter the YModem-G receive mode, and the softload may proceed normally as
described above, with the following exception: the communications software
must be set to 19200 bps, 8-bit characters, no parity before sending the file.
The softload will be invalid at any other setting. If this softload is
successful, then the TA will restart itself and will be fully operational with
the new software upgrade.
* If the BSPro does not respond after a softload attempt
After a successful softload, the BSPro should respond to AT commands. If the
softload failed for any reason, then the BSPro should re-enter the YModem-G
receive mode. It will not respond to AT commands while it is in YModem-G
receive mode. In this mode the BSPro should be sending the YModem-G
initiation character (G) to the terminal continuously, indicating that the
BSPro is ready for softload.
If power has been removed from the BSPro during a softload attempt or after a
softload failure, make sure the communications package is set to 19200 bps
before another softload is attempted. If power has not been removed, then the
communications package settings should not be changed.
If the BSPro will not respond to AT commands, and the YModem-G initiation
character (G) is not being sent to the terminal, then the software in the
BSPro may have been corrupted. Contact Motorola ISG technical support for
assistance.
***********************************************************************************
SOFTLOAD
Version 1.5
Terminal Adapter Firmware Update Utility
This utility makes it easy to update your ISDN terminal adapter with a new
firmware revision.
1. Connect the terminal adapter to a COM port on your PC. Power on the
terminal adapter.
2. Obtain the firmware update file. This will usually be a data file with
a ".SL" file name extension (for SoftLoad). Read any text file provided
with the firmware file for notes and instructions.
3. From the DOS command line, run the SOFTLOAD utility. Specify the COM
port where your terminal adapter is connected, and the name of the
SoftLoad file to download.
For example, the command line
SOFTLOAD /c2 sample.sl
downloads SAMPLE.SL to the terminal adapter connected to COM2. Use
/C1, /C3 or /C4 for COM1, COM3, or COM4. For a reminder, use
SOFTLOAD /?
For best results, DO NOT run this program under Windows. If you are running
Windows 3.1 or 3.11, please exit Windows before running this application.
If you are running Windows 95, please shut down Windows and choose to restart
your computer in MS-DOS mode.
As an alternative, you may perform a manual SoftLoad using a terminal
emulation software package that supports the YModem-G file transfer protocol.
Follow the instructions given in your terminal adapter operations guide under
SoftLoad.
Copyright (C) 1993, 1995 Motorola. All rights reserved.
***********************************************************************************
Release notes for current and prior releases
Motorola BitSURFR Pro
Software Release Advisory Notice
Board No. : 4574262
New Revision Code: 3M
Replaced Revision Code: 3L
Revision Date: 12/08/97
Revision Summary
----------------
This release is for implementation of bug fixes and features for the BitSURFR PRO.
Documentation Changes
---------------------
None
Release Notes
-------------
New Features and Modifications:
AT@B2 Command - The AT @B2 command was added to allow the user to set the number of times the 2nd channel of a MLPPP call will try and connect.
Extended the time that line voltage drops on a voice port from 100ms to 400ms when a remote caller goes on-hook.
Bug Fixes
---------
The unit would reset when running MLPPP and taking a POTS port off hook a second time when DCA is about to re-establish the MLPPP call on the port.
Xon/Xoff flow control would not work when running V.120.
The unit would reset when trying to enter Internet Explorer with a MLPPP call established.
The BitSURFR PRO would reset when running MLPPP and browsing the web or doing FTP.
The BitSURFR PRO did not recognize the Incoming Additional Call Tone, Signal Information Element. This prevented BitSURFR PRO from ringing a phone for an incoming call when running MLPPP.
The BitSURFR PRO would intermittently fail to pass data on a AIMux connection.
Upgrade Requirements
--------------------
This upgrade is softload compatible
********************************************************************************
Software Release Advisory Notice
Board Number: 4574262
New Revision Code: 3L
Replaced Revision Code: 3K
Revision Date: 08/12/97
Revision Summary
---------------
This is a maintenance "bug fix" release to correct problems that existed
in 1K code and to add the PPP Passthrough Feature and support for
Enhanced Caller ID (Name Delivery)
Documentation Changes
---------------------
* In the 1L code, the &F1 profile has been changed to a V.120 profile. Also, the
default for DTR Setting has been changed to &D2 (hangup) and the default for
DCD Setting has been changed to &C1 (normal) for all factory profiles.
* When placing a Multi-Link PPP call where the two telephone numbers are the
same, you should now enter the number only once. If the two telephone numbers
are different, you must still enter both numbers connected by an ampersand (&).
* You may now disable Call Waiting on the BitSURFR Pro's voice ports. This can
be done in LocalMenu, under the Voice Ports menu. You can also disable Call
Waiting using AT commands: the command to disable Call Waiting on Voice Port 1
is "AT*%A78=0", for Voice Port 2 it is "AT*2%A78=0". To re-enable Call Waiting,
the command is "AT*%A78=1" for Voice Port 1 and "AT*2%A78=1" for Voice Port 2.
* See PPP.txt for documentation on PPP Passthrough
New Features:
_____________
* PPP Passthrough
* Support for Enhanced Caller ID (Name delivery)
Bug Fixes:
* The &F1 default profile has been changed from PPP to V.120. For all
profiles the defaults have been changed to &D2 and &C1
* Corrects POTS compatibility problem with the Zoom V.34 modem
* Corrects a resets problem associated with using the AT@P2 command to
use 230.4 Kbps
* Corrects a problem with CHAP challenges greater than 40 chars is received
* The AT&H Help screen information is reduced
* New AT command added to allow Call Waiting to be disabled on the POTS ports
* Corrected problem with 3-way calling during a Multi-link PPP call
* New AT command to allow the user to set the number of times the 2nd channel
of a MLPPP call will try to connect
* When placing a Multi-Link PPP call where the two telephone numbers are the
same, it is no longer required to enter the number twice.
Upgrade Requirements:
This upgrade is softload compatible.
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.