Set PORT xxx doesn't work

[bon...@my-dejanews.com]

I am having a great deal of trouble getting my scripts to run automatically,
and would appreciate any help I can get. Here is my problem: I have a user who
needs to call up 26 different BBSs every morning, and they do not all have the
same port settings. I.e., several have 7-E-1, several have 8-N-1, and one even
has 7-E-2. Two of them want half duplex instead of full duplex. Sigh.

In any case, to avoid maintenance problems in the future, I *really* want to
keep all of the work in a script - I would prefer not to have different
connection directory entries, or option settings, etc. It will also ease
installation if there are fewer files of fewer types to distribute. The
*only* good part is that the user is my building, so I can walk over there
and work on problems in person and not over the phone.

I have tried the following lines of code (I am using Procomm Plus v4.7):

set port databits 7
set port parity EVEN
set port stopbits 1
set port baudrate 2400

and they just aren't working. I tried pausing after these lines and before
dialing the phone on the theory that they are talking to hardware, and maybe
it wasn't done setting them before I dialed. That didn't work.

Does anybody have any ideas???? If I can't solve this it is going to have to
get messy, and I really despise messy.

Please tell me I'm just being stupid and it's really easy...
Gratefully accepting all suggestions...
-- Bonnie

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[BFZ]

Hi Bonnie,

why dont you create a new directory and create one connection directories each
group of your users who use the same port - you wont have unlimited port number,
will you?

cheers

Benjamin

[bon...@my-dejanews.com]

In article <37303045...@fisci.com>,

BFZ <zh...@fisci.com> wrote:
> why dont you create a new directory and create one connection directories each
> group of your users who use the same port - you wont have unlimited port
number,
> will you?

Well, I want to avoid doing that if I can. My user is currently accessing 26
different BBSs, and it could go up from there. It *should* go down, but there
is no guarantee when, or indeed if, it will.

Just a gripe, not related to this - I really, really, REALLY wish I could pass
arrays as parameters to my procedures!!!! (Are you listening, Symantec?)
Getting around this limitation has made for some *very* messy code.

Sorry, just had to get that off my chest.

Thanks anyhow - keep the ideas coming!

[John Schultz]

In article <7gqcuj$a37$1...@nnrp1.deja.com>,

bon...@my-dejanews.com wrote:
> Just a gripe, not related to this - I really, really, REALLY wish I could pass
> arrays as parameters to my procedures!!!! (Are you listening, Symantec?)

Good luck, I doubt Symantec will do anything with Procomm in the near future,
other than rake in whatever cash they can get. I wouldn't be surprised to
see them release a new version without RapidRemote (a remote control app that
conflicts with many newer video cards and made redudant since Symantec has
PCAnywhere). However, it would probably just be an unannounced change to the
install program, and not include any new features or bug fixes. A pity,
really.

[John Schultz]

In article <7gnvqf$5mt$1...@nnrp1.dejanews.com>,

bon...@my-dejanews.com wrote:
> I have tried the following lines of code (I am using Procomm Plus v4.7):
>
> set port databits 7
> set port parity EVEN
> set port stopbits 1
> set port baudrate 2400
>
> and they just aren't working. I tried pausing after these lines and before
> dialing the phone on the theory that they are talking to hardware, and maybe
> it wasn't done setting them before I dialed. That didn't work.

The commands above will fail if you are not in what is called "modem command
mode" (which can be turned on and off via the Data | Modem Command Mode menu
item). With TAPI, Procomm does not talk directly to the modem like it did in
Windows 3.1 days. You can force Procomm to talk to the modem, rather than
going through TAPI, by using the above menu item. I saw the same problems you
were experiencing until I turned on modem command mode before running the
script. I couldn't find a way to directly turn modem command mode on and off
in ASPECT, but the following code snippet will toggle the state of the menu
item:

#include "pw4menu.inc"
proc main
menuselect PWMENU _4MODEM_ATMODE
endproc

One thing to keep in mind about modem command mode is that other applications
(including Procomm) can no longer access the modem until modem command modem
is turned off. For this reason and also for simplicity, I would recommend
using the Connection Directory to store the information about the different
systems that your user is calling.

[BFZ]

Following is the commad section from our application for your reference.

set xmodem relaxed ON ;this makes it less picky before shutdown your file
transfer
commandmode on
transmit "atdt"

; your code here .....

commandmode off
HANGUP
set xmodem relaxed off

Good luck !