The best way to do that is to have a script running in two separate Procomm windows, one for the connection on COM1 and another for the COM2 connection. You can use the set modem connection command in your script to assign the connection for each script (i.e. you will need one separate script for each open window).
As you told me, a script A run for open window connected to COM1; a script B run for open window connected to COM2,at the same time; even A.wax and B.wax are the same content.
A.wax and B.wax would have the same content, except you would have a different set modem connection command in each script to make sure that Procomm was using the correct connection in each window. Another way to do this would be to have two launcher scripts that each set the correct connection, then they could each execute the same main script (via the chain command) after the environment had been properly set. This could be a little cleaner since you would have to do maintenance on the main script (and likely none ever on the launcher scripts) instead of two separate scripts with mostly identical contents.
If you need to have data from both sessions used in one script there are basically two options:
Have the scripts communicate through Text files which may
have obvious hand-shaking problems.
or
Use DDE to communicate from one session of procomm to the
other.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.