home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
mdpool.zip
/
Read.Me
< prev
Wrap
Text File
|
1995-03-18
|
6KB
|
131 lines
The MDPOOL.ZIP file contains the following files:
READ.ME - this file
FIRST24.SCR - script to connect via modem pool (try this one first)
FIRST96.SCR - script to connect via modem pool (if FIRST24 doesn't work)
These files can be used to allow CompuServe Information Manager (CIM) for
OS/2 to connect to the CompuServe Information Service (CIS) using a modem in
a modem pool.
Since the prompts from your switch will probably be different than ours,
the literals in the scripts will most likely need to be modified. Follow
this procedure:
1. Use the Terminal Emulation mode of CIM for OS/2 to connect to CIS. Pay
attention to everything you do while you make the connection. For
example, does the first prompt from the switch appear automatically, or
do you have to hit Enter or another key to get it to appear? As you
connect, write down every prompt you receive from your switch and what
your response to the prompt should be. For example:
Prompt from switch Human Response
------------------ --------------
DISCONNECTED press Enter to get ENTER CLASS prompt
ENTER CLASS type in "MODEM" and press Enter
GO now connected to modem
ready to dial telephone number
2. Start with the script in the FIRST24.SCR file. Edit the file.
3. Our data switch waits for you to hit the Enter key before it displays
the first prompt. The scripts include a couple lines to "wake up" the
switch by sending a Carriage Return (Ctrl+M). If your switch displays
the first prompt automatically, delete these lines from the scripts:
! wait 2 seconds for DTR to stabilize then wake up the switch
wait until 20; ! 2 seconds
send "^M";
4. Under "wait" in the "Send_Wait" section of the scripts, put one line
for each of the prompts from the switch (from step 1). Each line looks
like this:
"<prompt>" goto Send_<label>
where <prompt> is the prompt from the switch and <label> is a label
which describes the response which is going to be sent.
For the prompt which indicates you are connected to a modem, use the
following line instead:
"<prompt>" goto Exit_Success
5. Create a "Send_<label>" section for each prompt. Each section looks
like this:
Send_<label>:
wait until 2; ! .2 seconds
send "<resp>^M";
goto Send_Wait;
Change <label> to the label you used in step 4. Change <resp> to the
response which you need to send to the switch. The "^M" sends a
Carriage Return which is used where you have to press the Enter key.
6. Save the file.
7. Go to the \CSERVE\SCRPITS directory. Rename the existing FIRST.SCR to
FIRST.OLD. Copy the script you have modified to the directory and
rename it to FIRST.SCR.
8. Start CIM for OS/2 and select "Session Settings" from the "Special"
menu. Make sure "Dial Type" is "Tone". Enter the CIS access telephone
number in the "Phone" field. Make sure you include a "9," at the
beginning of the telephone number if your PBX needs a "9" to access an
outside line. (Note: Even if you have to dial a "9" for an outside
line on the telephone on your desk, the modem pool might be set up with
direct outside lines and may not need the "9,".)
9. Select "Connect..." from the "File" menu. Press the "Connect" button.
This will run the CONNNECT.SCR script which calls the FIRST.SCR you
have created. If the script has been set up properly, you should be
connected to a modem in the modem pool and CIM will make the connection
to CIS. If CIM hangs at or terminates after "Initializing the modem",
you probably didn't get connected to the modem pool, or the modem is
not responding.
If you are having trouble connecting to the modem pool at 9600 bps or
more, try it at 2400 bps. The script in FIRST24.SCR worked for us at
2400 bps but not 9600 bps. We noticed that "Dial Type" of "Manual"
also worked at 2400 bps but not 9600 bps. With the help of a data
scope, we were able to identify the problem. It turns out that, for
some reason, our switch (which is more than 10 years old but still
runs great and never goes down) can handle a constant stream of data at
9600 bps for the PC-to-modem connection, but not when talking to the
switch itself during the connection process. We had to send a short
delay between each character transmitted. FIRST96.SCR shows how to set
up the response sections to send a response with a delay between
characters. The revised response sections look like this:
Send_<label>:
wait until 2; ! .2 seconds
send "M";
wait until 1; ! .1 second
send "O";
wait until 1; ! .1 second
send "D";
wait until 1; ! .1 second
send "E";
wait until 1; ! .1 second
send "M";
wait until 1; ! .1 second
send "^M";
goto Send_Wait;
This sends the string "MODEM^M" with a one-tenth of a second delay
between characters.
If you have any corrections or questions, please send e-mail to me at
71520,737 or post a message to me in the OS2USER forum.
Best regards.
Robert Simpson
Black Box Corp.