Using a Windows Batch file to run several simultaneous ProComm dial-up

[jend]

I am attempting to use a Windows Batch file to run two simultaneous ProComm sessions (one dial-up and one telnet).
However when I run the batch file it will not execute the second session until after the first session has completed. I've listed the content of my batch file below.

"D:\PROGRAM FILES\PROCOMM PLUS\programs\PW4.EXE" TelMultiSwAud.wax WVSwitchDirtel.DIR
"D:\PROGRAM FILES\PROCOMM PLUS\programs\PW4.EXE" DCMultiSwAud.wax WVSwitchDirtel.DIR

Can anyone help me out with the proper commands I need? Thanks in advance.

 

[knob]

I did not have a problem with this on my Win98 machine (what version of Windows are you running)? My batch file was identical to yours except I had the order of the .wax and .dir files flipped (the proper .dir file did not seem to load otherwise). Try switching the order of the .dir and .wax files and see if that helps for some strange reason.
aspect@aspectscripting.com

http://www.aspectscripting.com

 

[jend]

I am running Windows NT 4.0. I tried switching the order of the .dir and .wax files, but it did not make a difference. The Dial-up ProComm session will not start until the telnet ProComm session has completed.

Does anyone have any other suggestions?

Thanks.

 

[knob]

I tried loading just two copies of Procomm (no scripts, no Connection Directories) on NT and see the problem on that platform, so I can only presume this is due to the way NT processes batch files. I'll have to think on this a little bit to see if I can think of a workaround.

aspect@aspectscripting.com

http://www.aspectscripting.com

 

[jend]

Knob -

I'm still stumped. Any further assistance you or anyone can provide would be super.

Thanks.

 

[knob]

Sorry about that, it dropped right off my radar. Will try to have something for you by the end of the day (ghosting my test machine to NT now).
aspect@aspectscripting.com

http://www.aspectscripting.com

 

[knob]

Here's something I was able to get working, hopefully it will fit the bill for you. What I did was create one script (call it launch.was) that itself launches other copies of Procomm via the run command. Each run command includes a specific script that is run when the new Procomm window comes up. Here is what it looks like:

proc main
run "c:\program files\symantec\procomm plus\programs\pw5.exe script1.wax"
pause 1
run "c:\program files\symantec\procomm plus\programs\pw5.exe script2.wax"

When launch.wax is run, it creates two other Procomm windows with the associated script running. Does that fit the bill.
aspect@aspectscripting.com

http://www.aspectscripting.com