Artisoft			Technical Document


Title:		Using Third Party Software and Accessories with Artisoft 
ModemShare(TM)
Updated:	01/97
Description:	Explains basic configurations and setups for commonly used 
applications.
FileName:	mshare.txt
FaxReturn#:	4111
Pages:		14


MULTI-PORT SERIAL CARDS

 ModemShare should work with any third party non-intelligent multi-port 
serial card. Up to 16 ports in one communication server are supported.

Artisoft manufacturers its own high performance multi-port serial cards. 
For more information on the line of multi-port serial cards from Artisoft 
call our Sales Consultation Center at 800-846-9726.

The following is a partial listing of other vendors of multi-port serial 
cards that have been used with ModemShare:
 
 DigiBoard
 Quatech
 Arnet


INT14 , NASI, OR WINDOWS COMPATIBLE SOFTWARE

INT14 compatibility is the key aspect of any communication package for 
operation with ModemShare in a DOS enviroment.  As long as the software is 
INT 14, NASI or uses a Windows Comm port and does not try to access the 
modem through hardware, then ModemShare should be fully compatible with 
the application. 

If you have software that does not support INT14, NASI or Windows and the 
manufacturer is interested in providing this support, download the INT14 
programming API file INT14API.TXT from the Arti-Facts BBS at 520 
884-8648.  This is for information only and is not supported through 
Artisoft Technical support.



SETUP INFORMATION FOR 3RD PARTY INT14 AND NASI SOFTWARE

Most INT14 and NASI communication packages have the setup for INT14 or 
NASI under the port parameter settings. You should find that INT14 or NASI 
will be listed among the other standard COM1, COM2, COM3 port list. For 
correct operation the software must be changed from a COM1, 2, 3, et 
cetera setting to INT14 or NASI.

Provided below are specific reference notes for the following third party 
INT14 or NASI products:
 
 Crosstalk Mark 4 Version 1.1
 Reflection 1+ Version 3.3
 Lexis/Nexis Version 2.5
 Westmate Version 3.20
 pcANYWHERE IV (Outbound)
 pcANYWHERE IV (Inbound)
 pcANYWHERE/Lan (Outbound with the NASI Option)
 pcANYWHERE 5.0 (Outbound with the NASI Option)
 pcANYWHERE 5.0 (Inbound)
 pcANYWHERE for Windows 1.0 & 2.0 (Inbound)
 Proconsul Plus Network Version
 ReachOut Modem And Network Versions (DOS)
 ReachOut Modem And Network Versions (Inhost Windows)
 
For all third party INT14 communication applications ensure that the 
CLIENT.CON file has been set to Xon/Xoff (if the application requires 
Software 
Flow Control) or RTS/CTS (if the application requires Hardware Flow 
Control). 
Use the PAREDIT program to edit the CLIENT.CON file to the appropriate 
setting.

Crosstalk Mark 4 v1.1
 1. DCA's Crosstalk package should be installed following DCA's 
recommended  installation procedures and set the flow control to Xon/Xoff 
(software  flow control).
 2. Run MSERVER on the workstation where the modem physically resides to  
share it with other network users and MCLIENT on workstations using  
CROSSTALK Mark 4 to access the shared modem.
 3. To use Crosstalk with the MCLIENT program you will need to set 
specific  configuration options. The following steps outline the procedure 
for  adding a Phone Book Entry Card which describes the Device and 
Terminal  Drivers to use. The INT14 driver will always be used, the 
default BLANK card can be modified with the desired drivers.
 4. Load Crosstalk and select the Offline Menu. Select Change 
Configuration  or Phone Book and enter the information for a new card (you 
may also  choose Change Information on an old card if you are modifying 
the default  record, Blank).
 5. Enter the phone number and description for the entry you are 
creating,  then press Ctrl+Enter to end the editing of the record.
 6. When prompted for a name during the Save Operation, enter a new name 
for  the Phone Book Card (unless editing a card you have previously 
configured  for use with MCLIENT) and press Enter. Press Esc several times 
until you  return to the Crosstalk command line and type DEVICE INT14, 
then press  Enter. 
 7. Press Alt+D to access Device Setup Editing. Select the appropriate  
speed, parity, data bits, and stop bits. For the 'Flow' option, press  the 
space bar until the 'None' selection is chosen. For the 'Local'  option, 
press the space bar until the 'Off' selection is displayed if you prefer 
automatic dialing, or choose the 'On' selection if you prefer to  manually 
enter the modem commands you will use. 
 8. When you have finished making these changes, press Ctrl+Enter then 
enter  a new name for the Phone Book Card (unless you are editing a card 
you  have previously configured for use with MCLIENT) and press Enter. 
 9. As you are setting up other Phone Book Cards for use with MCLIENT, 
you  should start by selecting cards already set up for use with INT 14  
drivers and enter or change the information pertaining to the new  phone 
number. This can be done by selecting the 'Make a call from the  phone 
book' option from the menu, selecting the appropriate card, then press Esc 
to cancel the call. The card chosen becomes the 'current' card  in the 
view window and you may now perform any edit operations required.
10. If you will be making multiple outbound calls you may need to set 
Result  Codes On (reference the Crosstalk users manual for instructions 
on  setting this parameter.

Reflection 1+ v3.3
 1. The Reflection 1+ package should be installed following DCA's 
recommended  installation procedures and set the flow control to Xon/Xoff 
(software  flow control).
 2. Run MSERVER on the workstation where the modem physically resides to  
share it with other network users and MCLIENT on workstations using  
Reflection 1+ to access the shared modem.
 3. Load the Reflection program you are using; R1.EXE for use with 
Digital  Equipment Corporation equipment, or R1V.EXE for use with 
Hewlett-Packard  equipment.
 4. The first time Reflection loaded the Basic Configuration Menu will  
appear. You may also press Alt+C to bring up the Configuration Menu.  The 
Configuration Menu options are accessed through the function keys  listed 
at the bottom of the screen.
 5. Press F1 to access the Datacomm Configuration Menu and at the 
Datacomm  Port Entry select INT14. You should also set the Baud Rate, 
Parity, Data  Bits, and Stop Bits to the values you will use with your 
host link or  modem.
 6. Select the Session # (LAN) field and enter the number 1 to select the  
serial port, port one. When you have selected the correct values, press  
F6 to save the changes and F5 to activate the changes.
 7. Select the Global Configuration Menu and confirm that the top line is  
correctly configured for the terminal type you will be emulating. All 
other defaults settings should be sufficient. Once you have confirmed  the 
correct settings, press F6 to save the changes and F5 to activate the  
changes.
 8. To use Reflection with ModemShare, press F8 to return to terminal 
mode.  You may now start a Revelation host session or send modem commands 
to a  shared modem.
 9. Reflection operates as a direct terminal communications interface to 
host  computers, therefore all modem commands must be entered manually 
when  using a ModemShare shared modem. Refer to your modem manual for the  
command syntax instructions for your modem.

Lexis/Nexis v2.5
 1. The Lexis/Nexis package should be installed following the recommended  
installation procedures and Xon/Xoff (software flow control) selected.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on the workstation using 
Lexis/Nexis to access the shared modem.
 3. Run the Config program from the Lexis subdirectory and select the 
Primary  Connection Option then the Primary Connection Method. Select 
INT14  (Polling) and save changes.

Westmate v3.20
 1. The Westmate package should be installed following the recommended 
installation procedures and Xon/Xoff (software flow control) selected.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on the workstation using 
Westmate to access the shared modem.
 3. Load the Westmate program and when the Off-line screen appears with 
the  '-=>' prompt, type the command VPRINT then press Enter.
 4. A series of settings for Westmate's variables will be displayed on 
the  screen. For ModemShare to function correctly, you will need to 
change  the "@modport" variable setting. Type the following commands in 
lower  case and exactly as they appear below: 
 
 @modport=com1 <Enter>
 init <Enter>
 write <Enter>

 Refer to your Westmate software manual for specific instructions on 
setting up your Westlaw access parameters such as your user ID and 
password.

pcANYWHERE IV (Outbound)
 1. Install pcANYWHERE IV following the recommended installation 
procedures  and be sure that RTS/CTS (hardware flow control) is selected 
in the  hardware configuration.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE IV to access the shared modem.
 3. Load the remote portion of pcANYWHERE IV by typing AWREMOTE <Enter>.
 4. Select Hardware Configurations from the Main Menu.
 5. Edit the "Device/Port: " field by pressing Return and selecting INT14  
from the list provided. You will be asked to define a COM port of COM1  or 
higher. This parameter does not effect communication with MCLIENT.
 6. Set a maximum baud rate of 9600. Setting a higher baud rate when using 
INT14 will result in an error.
 7. Adjust all other fields according to your Modem Type then save your 
changes under the default configuration. You can now dial out using 
pcANYWHERE IV.

pcANYWHERE IV (Inbound)
1. Install pcANYWHERE IV following the recommended installation 
procedures  and set RTS/CTS (hardware flow control).
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE IV (Host) to receive a call from the shared modem.
 3. Load the host portion of pcANYWHERE IV by typing AWHOST <Enter> and 
select Hardware Configuration from the Main Menu.
 4. Edit the "Device/Port:" field by pressing Return and selecting INT14 
from  the list provided. You will be asked to define the COM port of COM1 
or  higher. This parameter does not effect communication with MCLIENT.
 5. Edit the Modem type and select None.
 6. Make sure that Connection Started By is set to "Always Connected" and  
Connection Ended By is set to "DCD".
 7. Set DTR and RTS state to "Always On". Confirm that flow control has 
been set to RTS/CTS.
 8. Set the modem baud rate to the same value specified in the SERVER.CON  
file. All other parameters are to be set based on the modem attached to 
the MSERVER station and personal preference. Save all default settings and 
exit AWHOST.
 9. From the command line, type "INHOST AWHOST.EXE, -M=A" <Enter>. This 
will  load the Inhost program with the default service name in the 
CLIENT.CON  and will execute the program AWHOST.EXE with the parameters 
-M=A (mode =  automatic).

The following steps will allow a workstation that has been taken over as a 
host to reset itself and be prepared for an inbound call again without 
rebooting. Create a batch file called LOGOFF.BAT that contains the 
following commands:
 
 AWLOGOFF C:
 rem This cancels pcANYWHERE
 MCLIENT RELEASE
 rem This releases your current modem connection immediately)
 INHOST AWHOST.EXE, -M=A
 rem This reloads INHOST and waits for an inbound call without tying up a 
 rem modem.

When you are ready to end your communication session type LOGOFF on the 
Host workstation and it will automatically end the remote session and set 
up for a new session.

If a reboot is required, you can set pcANYWHERE to auto reboot the 
workstation at the end of the session then load the INHOST commands in the 
PC's AUTOEXEC.BAT for continuous dial-in capabilities.

pcANYWHERE/LAN (Outbound with the NASI Option)
 1. Install pcANYWHERE following the recommended installation procedures 
and  be sure that RTS/CTS (hardware flow control) is selected in the 
hardware  configuration.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE to call out on the shared modem.
 3. Load pcANYWHERE/LAN by typing "AWLAN" <Enter> then enter your ID code.
 4. Select Hardware Configuration from the Main Menu. Press Insert to 
create  a new configuration or select one that has been previously 
established.
 5. Edit the "Device/Port:" field by pressing Return and select NASI/NCSI  
from the list provided. You will be asked for the server, group and  port, 
based on your selections you will be shown the available modems on  the 
network. For more information on the NASI options refer to your  
pcANYWHERE manual.
 6. Adjust all other fields according to your Modem Type and save your 
changes.
 7. Select Remote Operation, then select View/Modify List of Hosts.
 8. Edit or Create a new Host Entry and be sure to use the Hardware 
Configuration you created with the NASI selection. Save your Host Entry.  
You can now select from "Connect Via List Of Hosts" and dial out through 
ModemShare.

pcANYWHERE/LAN (Inbound)
 1. Install pcANYWHERE/LAN following the recommended installation 
procedures  and set RTS/CTS (Hardware Flow Control).
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE/LAN (Host) to receive a call from the shared modem.
 3. Load pcANYWHERE/LAN by typing "AWLAN" <Enter> 
 4. Select Hardware Configuration from the Main Menu. Press Insert and 
create a new Hardware configuration.
 5. Edit the "Device/Port:" field by pressing Return and select INT14 
from  the list provided. You will be asked to define the COM port of COM1 
or  higher. This parameter does not effect communication with MCLIENT. You 
cannot use the NASI option in this case for Inbound calling. pcANYWHERE 
will try to reset the connection when executed. You must use  the INT14 
Option.
 6. Edit the Modem type and select None.
 7. Confirm that Connection Started By is set to "Always Connected" and 
Connection Ended By is set to "DCD". Set DTR and RTS state to "Always On". 
Confirm that flow control is set to RTS/CTS.
 8. Set a maximum baud rate of 9600. Setting a higher baud rate when 
using  INT14 will result in an error. Confirm that the modem baud rate is 
set to the value specified in the SERVER.CON file. For example, if you 
have  a baud rate set for LINE1 at 9600 in the SERVER.CON file, make sure 
that  the baud rate in pcANYWHERE is set to 9600.
 9. All other parameters are to be set based on the modem attached to the  
MSERVER station and personal preference. Save all default settings and  
exit AWHOST.
10. Save all settings and exit back to main menu.
11. Select Host Operation from Main Menu, select Active Configuration and  
highlight the configuration just created and press Enter.
12. Exit pcANYWHERE/LAN and copy the ModemShare INHOST.EXE file to your 
pcANYWHERE subdirectory.
13. From the command line, type "INHOST AWLAN.EXE, -o=h -i="your user 
code"  -M=A" <Enter>. This will load the Inhost program with the default 
service name from the CLIENT.CON file and will execute the program 
AWLAN.EXE with the additional parameters. You can now receive calls using 
pcANYWHERE/LAN and ModemShare.

The following steps will allow a workstation that has been taken over as a 
host to reset itself and be prepared for an inbound call again without 
rebooting. Create a batch file called LOGOFF.BAT that contains the 
following commands:
 
  AWLOGOFF C:
 rem This cancels pcANYWHERE
 MCLIENT RELEASE
 rem This releases your current modem connection immediately
 INHOST AWLAN.EXE, -o=h -i="your user code" -M=A
 rem This reloads INHOST and waits for an inbound call without tying up a 
 rem modem.

When you are ready to end your communication session type "LOGOFF" <Enter> 
onthe Host workstation and it will automatically end the remote session 
and set up for a new session.

If a reboot is required, you can set pcANYWHERE to auto reboot the 
workstation at the end of the session then load the Inhost commands in the 
PC's AUTOEXEC.BAT for continuous dial-in capabilities.

pcANYWHERE 5.0 (Outbound with the NASI option)
1. Install pcANYWHERE following the recommended installation procedures 
and  be sure that RTS/CTS (hardware flow control) is selected in the 
hardware  configuration.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE to call out on the shared modem.
 3. Load pcANYWHERE 5.0 by typing "AW" <Enter> and enter your ID code (if  
used).
 4. Select Configure from the Main Menu. Select System Hardware and press  
your Insert key to create a new Hardware Configuration or select one that  
has been previously established.
 5. Edit the "Device/Port:" field by pressing Return and select NASI/NCSI 
from the list provided. You will be asked to define the server, group,  
and port. Based on your selections you will be shown the available  modems 
on the network. For more information on the NASI options refer to  your 
pcANYWHERE manual.
 6. Adjust all other fields according to your Modem Type and save changes.
 7. Select Call A Host then select View/Modify List of Hosts.
 8. Edit or Create a new Host entry and be sure to use the Hardware 
Configuration you created with the NASI selection. Save your Host Entry.  
You can now select from "Connect to a Host" and dial out through 
ModemShare.

pcANYWHERE 5.0 (Inbound)
 1. Install pcANYWHERE 5.0 following the recommended installation 
procedures  and set RTS/CTS (hardware flow control).
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using pcANYWHERE 5.0 (Host) to receive a call from the shared modem.
 3. Load pcANYWHERE 5.0 by typing "AW" <Enter> and enter your ID code (if  
used).
 4. Select Configure from the Main Menu. Select System Hardware and press  
Insert to create a new Hardware Configuration.
 5. Edit the "Device/Port:" field by pressing Return and select NASI from 
the  list provided. The Select at a Later Time Option should be set to 
"No".
 6. Edit the Modem Type and select None and adjust the baud rate to match 
the baud rate value set in the SERVER.CON file. For example, if you have 
a  baud rate set for LINE1 at 19200 in the SERVER.CON file, make sure 
that  the baud rate in pcANYWHERE is set to 19200.
 7. Confirm that flow control is set to RTS/CTS. Save all settings and 
exit  back to the Main Menu.
 8. Select Be A Host from the Main Menu then select Active Configuration 
and  highlight the Hardware Configuration you just created. Press Return.
 9. Exit pcANYWHERE 5.0 and copy the ModemShare INHOST.EXE file to your 
pcANYWHERE subdirectory and from the command line type "INHOST AW.EXE, 
/O:H /M:A" <Enter>. This will load the Inhost program with the default 
server name from the CLIENT.CON file and will execute the program AW.EXE  
with the additional parameters. You can now receive calls using pcANYWHERE 
5.0 and ModemShare.

If you are sharing one modem you may receive the message "Initializing 
Modem" and then experience a system failure as you load pcANYWHERE. 
pcANYWHERE is looking for an available port before loading, and because 
the port you are dialing into is busy, it will fail. The following is a 
work-around to this problem until Symantec makes a correction:

 1. Create a new line in the SERVER.CON file called GHOST. Make sure that  
the line has been defined with "No Modem" (MODEM=N if you are looking at  
the SERVER.CON file through a text editor).
 2. Create a new Group in the SERVER.CON file and call it DONOTUSE. Make 
sure that the LINES= statement contains GHOST.
 3. Save the SERVER.CON file and reboot the COM server. You should then 
be  able to dial in without problems.

The following steps will allow a workstation that has been taken over as a 
host to reset itself and be prepared for an inbound call again without 
rebooting. Create a batch file called LOGOFF.BAT that contains the 
following commands:
 
  AWLOGOFF C:
 rem This cancels pcANYWHERE
 MCLIENT RELEASE
 rem This releases your current modem connection immediately.
 INHOST AW.EXE, /O:H/M:A
 rem This reloads INHOST and waits for an inbound call without tying up a 
 rem modem.

When you are ready to end your communication session type "LOGOFF" <Enter> 
onthe Host workstation and it will automatically end the remote session 
and set up for a new session.

If a reboot is required, you can set pcANYWHERE to auto reboot the 
workstation at the end of the session then load the Inhost commands in the 
PC's AUTOEXEC.BAT for continuous dial-in capabilities.

pcANYWHERE for Windows v1.0 and v2.0 (Inbound)Configure ModemShare Inhost:
 1. ModemShare should be installed for Windows support. See the User 
Manual  (Windows Installation). The Inhost icon should be available in 
the  ModemShare group in Program Manager.
 2. Run the Port Status and Setup program and be sure that the COM port 
redirector is installed and note the COM port number that is currently 
being redirected by ModemShare.
 3. Double-click the Inhost Icon in the ModemShare program group to load 
the  Inhost program.
 4. Click the Browse button and select the directory where pcANYWHERE for  
Windows was installed and click the program name WINHOST.EXE.
 5. Enter "pcANYWHERE Host" or some other suitable description in the 
Program  Description field.
 6. Leave the Input Parameters field empty.
 7. You may enter a Service Name in the field provided (this is optional). 
If you do not supply a service name, ModemShare takes the default name  
specified in the CLIENT.CON file. This is the name displayed when you  
call into the server.
 8. Select the "Reset after Connection Termination" box then select the 
"Options" button and be sure that both options are not checked.
 9. Click the OK button. Inhost is now ready to accept an inbound call. 
All  other selections on the main screen are optional. 
 
Configure pcANYWHERE:
 1. Run pcANYWHERE for Windows and click the "Be A Host PC" button.
 2. Under the frame box titled Allow Control Options, click the Settings  
button.
 3. The Edit Caller Entry menu will appear. Click the Advanced button.
 4. Under the frame box titled Caller Rights, select the option Allow 
Caller  To Change Host Mode and click OK twice to return to the main Be A 
Host PC  menu.
 5. From the frame box titled Your Hardware Configuration Name, select 
Direct  Connect from the list box.
 6. Click the Edit button and set the Device to the Windows COM port that 
was  redirected by ModemShare.
 7. Be sure that the No Modem[Direct Connect] radio button is selected.
 8. Set the Data Rate to the same speed as set in the SERVER.CON file for 
the  Inbound line and set the Flow Control to RTS/CTS.
 9. Click the Advanced button and under the Connection box you may find 
it  necessary to change the Started by to the option Receive 2 <CR>s. 
When  you dial into the COM server and select the station, press return 
twice to wake up the pcANYWHERE host. (This may not be necessary on all 
workstations). Click OK until you return to the main Be A Host PC menu.
10. Minimize pcANYWHERE (do not select Wait For Call). You can now call 
in  and select this host by name when the communication server answers.
11. When hanging up from the connection, you will see a check box under 
the End Session prompt. Uncheck the box and then proceed to end session.  
This will ensure that the connection is reset and ready for the next dial  
in.

The following steps will automate the process of setting the workstation 
ready for the next call if you plan on having the PC reboot after 
disconnect:

 1. Adding the WIN command to your AUTOEXEC.BAT file to automatically 
load  Windows.
 2. Add the pcANYWHERE icon (WINAW.EXE) to the Windows Startup Group and 
select "Minimize" under the properties for that icon.
 3. Add the ModemShare Inhost icon (INHOST.EXE) to the Windows Startup 
Group.  Under Properties for the Inhost icon add the command AUTO. For 
example,  Command Line in Properties might read "C:\\MSHARE\INHOST.EXE 
AUTO".

Proconsul Plus Network Version
 1. Install Proconsul following their recommended installation procedures 
and  when prompted select EBIOS INT14 or NASI for the type of network  
communications you will be using.
 2. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on workstations that will be 
using Proconsul to call out on the shared modem.

ReachOut Modem and Network Versions for DOS (Outbound)
 1. Reachout should be installed following the recommended installation 
procedures and set the flow control to RTS/CTS (hardware flow control).
 2. Select Modem Assist Plus when prompted for the COM setting. If Modem 
Assist Plus is not a selection, you will need to contact Stac to obtain a  
new RCHACS and SETUP file. 
 3. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on the workstations using 
ReachOut to access the shared modem.
 4. Load ReachOut by typing "GVM" <Enter>.
 5. When you have completed your ReachOut session you can unload the 
ReachOut  TSRs from memory by typing "UNLOADMH" <Enter>. You can then 
remove the  ModemShare MCLIENT TSR from memory by typing "MCLIENT" <Enter>.

ReachOut Modem and Network Versions for DOS (Inbound)
 1. Reachout should be installed following the recommended installation 
procedures and set the flow control to RTS/CTS (hardware flow control).
 2. Select Modem Assist Plus when prompted for the COM setting. If Modem 
Assist Plus is not a selection, you will need to contact Stac to obtain a  
new RCHACS and SETUP file.
 3. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users and MCLIENT on the workstations using 
ReachOut to access the shared modem.
 4. Copy the following ModemShare files from C:\\MSHARE to your ReachOut 
subdirectory (C:\REACHOUT):  MCLIENT.EXE, CLIENT.CON, INHOST.EXE, and, if 
you are going to run the  client program on the communications server as 
an inbound host, also  copy MLCLIENT.EXE.
 5. Edit the ReachOut GHM.BAT file with the following commands:

 MCLIENT
 SET RCHPATH=C:\REACHOUT (local or network path to the ReachOut files)
 RCHACS NAME=TEST (name is an example only)
 INHOST RCHDOS.EXE,
 DOSGRAPH
 HOSTMDM

 6. Execute the batch file GHM. This will load the ModemShare client and 
install the necessary ReachOut TSRs. The ReachOut RCHDOS TSR will be 
executed by Inhost when an incoming call has been placed. Any other 
optional ReachOut TSRs listed after the Inhost command will be executed.

Disconnecting From An Inbound ReachOut Session:

There are two methods available to end an inbound session, each described 
below.

 1. Setup ReachOut to reboot upon disconnect and add the command CALL 
GHM.BAT  to the end of the workstation's AUTOEXEC.BAT file. All ReachOut 
and  ModemShare program files will need to be accessible on the local hard 
drive or network connection before the CALL GHM.BAT command is executed.  
Once the workstation has rebooted it will take a minute or two for  
ModemShare to reset the connection at the COM server before taking  
another call.

 2. Edit the ReachOut file UNLOADMH.BAT and add the following commands at 
the  end of the file:
 
 MCLIENT -
 GHM
 
 When you run the UNLOADMH.BAT file the ReachOut and MCLIENT TSRs will be  
removed and the GHM.BAT file will be called to reload ReachOut and start  
INHOST.

ReachOut Modem and Network Versions for Windows (Inbound) Configure 
ReachOut:
 1. Reachout should be installed following the recommended installation 
procedures and set the flow control to RTS/CTS (hardware flow control).
 2. Select Modem Assist Plus when prompted for the COM setting. If Modem 
Assist Plus is not a selection, you will need to contact Stac to obtain a 
new RCHACS and SETUP file.
 3. Run the PAREDIT program and edit the CLIENT.CON to reflect the setting 
"NASI=3".
 4. Run MSERVER on the workstation where the modem physically resides to 
share it with other network users, and MCLIENT on the workstations using 
ReachOut to access the shared modem.
 5. Copy the following ModemShare files from C:\\MSHARE to your ReachOut 
subdirectory (C:\REACHOUT): MCLIENT.EXE, CLIENT.CON, and if you are going 
to run the client program on the communications server as an inbound host 
you will also need to copy MLCLIENT.EXE.
 6. Edit the ReachOut WINLDM.BAT file and add/change the following:
 
 MCLIENT
 SET RCHPATH=C:\REACHOUT (local or network path to the ReachOut files)
 RCHACS NAME=TEST (name is an example only)

 7. Execute the batch file WINLDM.BAT to load the ReachOut TSR and the 
ModemShare client then load Windows.

Configure ModemShare Inhost:
 1. ModemShare should be installed for Windows support and the INHOST 
icon  should be available in the ModemShare group in Program Manager.
 2. Double-click the Inhost Icon from the ModemShare program group to 
load  the Inhost program.
 3. Click the Browse button and select the directory where ReachOut was 
installed and click the program name HOSTMENU.EXE.
 4. You may enter "ReachOut" or some other suitable description in the 
"Program Description" field (optional).
 5. Leave the "Input Parameters" field empty.
 6. You may enter a "Service Name" in the field provided (optional). If 
you do not supply a service name, ModemShare takes the default name 
specified in the CLIENT.CON file. This is the name displayed when you call 
into the server.
 7. Select the "Reset after Connection Termination" box then select the 
"Options" button and check the box Terminate Program on Carrier Drop. Do 
not check the other option.
 8. Click OK. All other selections on the main screen are optional. 
 9. Inhost is now ready to accept an inbound call. You can call in and 
select this host by name when the COM server answers.

The following steps will automate the process of setting the workstation 
ready for the next call if you plan on having the PC reboot after 
disconnect:

 1. Add the command CALL WINLDM.BAT to your AUTOEXEC.BAT file to 
automatically load the ReachOut program files.
 2. Add the command WIN to the last line of your AUTOEXEC.BAT file to 
automatically load Windows.
 3. Add the ModemShare Inhost icon (INHOST.EXE) to the Windows Startup 
Group.  Under Properties for the Inhost icon add the command AUTO. For 
example,  Command Line in Properties might read "C:\\MSHARE\INHOST.EXE 
AUTO".


Artisoft, Inc.
2202 N. Forbes Blvd			 
Tucson, AZ  85745		
				
Internet 
  web:				http://www.artisoft.com	
  ftp:				ftp.artisoft.com
FaxReturn: 			520-884-1397
ArtiFacts bbs:			520-884-8648 (8 bits,No parity,1 
stop bit)
Sales Consultation Center:  	(800) 846-9726  
			  FAX (520) 670-7359
Customer Service:	      	(800) 846-9726
Technical Support Information:	(520) 670-7000

ARTISOFT TECHNICAL SUPPORT
Artisoft offers a wide selection of technical support options.  For 
information regarding technical
support services, please refer to our Directory of Support Services, 
available where you obtained 
this Technical Note.
Check Technical Support & Services on our Home Web Page, request FaxReturn 
document 4, or 
download the file DIRLIST.TXT).  You can also obtain this information by 
calling Artisoft at (520) 670-7000.

DISCLAIMER:

THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO ARTISOFT 
AND IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER 
EXPLICIT OR IMPLIED.  ARTISOFT DISCLAIMS ALL WARRANTIES AND 
SHALL NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, 
INDIRECT, OR PUNITIVE DAMAGES, OR LOST PROFITS OR REVENUE, EVEN 
IF IT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  SOME 
STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR 
CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING 
LIMITATION MAY NOT APPLY TO YOU.

Brand names, company names, and product names are trademarks of their 
respective companies.
