Rasport allows NT communications programs to share an NT serial port with RAS.
The Rasport setup dialog lists all the serial COM ports that are available on the NT system.
When you specify that Rasport should use a COM port, Rasport will provide two different names for that COM port ...
1/. The original COM port name (e.g. COM2)
2/. The extra COM port name (e.g. RASPORT2, or perhaps COM3)
After Rasport has been started, both of these COM port names will be visible to NT communications programs (like RAS, FAXPORT3, and TERMINAL) ...
1/. The original COM port name (e.g. COM2) should only be used by RAS.
2/. The extra COM port name (e.g. RASPORT2, or perhaps COM3) can be used by any non-RAS communications program (e.g. FAXPORT3, and TERMINAL) even while RAS has opened the original COM port name and is listening for an incoming call.
Handling Inbound And Outbound Calls
-----------------------------------
a) The current version of Rasport supports RAS dial-in, but not RAS dial-out (so do not dial an outbound RAS connection on a COM port that is being shared by Rasport).
b) Rasport monitors I/O activity on each COM port, to determine when the port is idle (where 'idle' means that the application has open the port, but is merely sitting there waiting for an incoming call) ...
i/. If a program (e.g. FAXPORT or TERMINAL) tries to open the extra COM port name, while RAS is actively handling an incoming call through the original COM port name, then the attempt to open the extra COM port will be failed (and the RAS connection will not be interrupted). If this happens, simply wait until the RAS connection has finished: as soon as RAS is idling, waiting for an incoming call, then the attempt to open the extra COM port name will succeed.
ii/. The current version of Rasport supports adaptive dial-in connections on the extra COM port, only if that extra COM port is being used by FAXPORT (not by any other application); whenever an application other than FAXPORT is using the extra COM port, then RAS will not be able to receive incoming calls.
If FAXPORT is using the extra COM port but has allowed the line to idle (because it has no outbound faxes to send, and is merely listening for an incoming fax), then RASPORT will use the modem's adaptive answer to route any incoming call to the correct program: incoming data calls are passed to RAS, and incoming fax calls are passed to FAXPORT.
iii/. Only one application at a time can be using the extra COM port. For example, if the extra COM port is being used by FAXPORT, then you will not be able to open that COM port using TERMINAL.
iv/. Rasport watches the modem initialization strings that are sent by RAS, so that whenever an application finishes using the extra COM port, Rasport can reinitialize the modem into the state expected by RAS. Rasport will be confused by the multitude of strings that RAS sends to the modem, when RAS is trying to detect the type of modem (when you use Control Panel/Network to install RAS, or to configure it for a new COM port or new type of modem). Control Panel will tell you to restart the system, whenever you change the RAS settings: you should do this (Rasport will not be able to properly reinitialize the modem until after the system is restarted; you will see the folllowing Rasport message in the NT system Event Log "The last modem initialization string captured from RAS did not contain the expected 'Answer On' (i.e. SO=)").
Choosing Extra COM Port Names
-----------------------------
The default 'extra' COM port names that are created by RASPORT are something like "RASPORTCOM1". However, some applications (e.g. TERMINAL) are unable to 'see' COM ports that are called anything other than COMx (e.g. COM3). If you will want to use one of these applications to open the extra COM port, use the '&Name...' button on the Rasport Setup dialog to override the default name.
Rasport Error Reporting
-----------------------
When Rasport is used (or abused), Rasport cannot display messages on the Windows desktop (because Rasport is an NT kernel-mode device driver). Instead, information messages (for example, which say that Rasport is loaded successfully), and any error messages, can be displayed using the NT system Event Log.
Supported Modems And Serial Ports
---------------------------------
Rasport has been tested only with SERIAL.SYS (the standard NT serial port driver). Rasport should work with other serial drivers, e.g. the drivers from Digiboard, however this has not been tested.
See the latest NT Hardware Compatability List for a list of modems supported by RAS.
Faxport will work with any Class 1, Class 2, or Class 2.0 fax or fax data modem (there are too many of these modems to list). However, the current version of Rasport can provide adaptive answer only for Class 2.0 modems. The following are Class 2.0 modems which have been tested with RASPORT:
* USR Courier
Rasport Demo Version
--------------------
If the title bar of your Rasport installation program (IRASPORT.EXE) says "Rasport Installer (Demo)", then the serial port speed of all communications through the extra COM port will be limited to 9600 baud maximum (unless the application that is using the extra COM port is FAXPORT).
Some applications (e.g. Fax programs) will not function properly at lower baud rates; other applications (e.g. TERMINAL) may display a cryptic error message if you try to select an unsupported baud rate.
For a 'non-demo' version of Rasport without this limitation, please contact the sales department here at LANSource.
Optional Windows based On-Line Documentation (RASPORT.HLP)
An optional Windows based On-Line Documentation program is provided with the installation disk.
It contains information on the installation and setup of the RASport program in a standard Windows 'Hyper-text' format.
To use this documentation you may 'Run' the program by launching with the RUN function of
Windows from the A: drive, or place it into a sub-directory of your choice on the hard drive of the Windows NT Server and do the same.
You may also create a Windows Program Manager Icon associated with the documentation. This is done by first hightlighting a program group under Windows Program Manager where you want the icon to reside. You then create the icon by clicking on 'file' on the pull down menu line of the Windows Program Manager, and then choose 'New'.
You will next need 'browse' either the A: drive or the sub-directory on the hard drive where you placed the file in order to select it. Due to the fact that the on-line documentation has an 'HLP' extension, you will also need delete the default extensions shown in the 'FILE NAME' dialog box in order to see the file.
Once the file has been chosen you may click on 'OK' and the icon will be created. When you double click on it, it will 'run' and you will be able to use the information provided.
If you have any futher question consult your Windows Setup Guide for instructions on using HLP extension files.
Trademarks
----------
FAXPORT, RASPORT, and WINPORT are trademarks of LANSource Technologies Inc.
