Compiled ASPECT script cause error

[fechen]

I am using a procomm script to telnet to a network device and then chain to another script.

The problem is when I call the script from command line using .wax (compiled file), sometimes it works perfect, sometimes give weird error, such as:
"winsocket Error(0)"
script not running
bad script version (can't remember the exact word)
The fail:success ratio is about 1:1 to 3:1. I even precompiled the script on the PC which I will run the script. Doesn't help.

After I start to use .was (source file), things are working perfect. I don't see the problme any more.
I am using Procomm Plus 4.70.

Does anybody see the same thing? Any idea? Thanks

 

[knob]

What does your command line look like? Is the original script (the one of the command line) failing, or is it the chained script? When you say you start to use the .was file, do you mean you are using the .was file instead of the .wax file in the command line?

 

[fechen]

The command line looks like:
pw4.exe TELNET CONNECT MANUAL serverName logon.was (or logon.wax)

Script looks like:

proc main
waitfor "login: "
transmit "mylogin" ;fake login
transmit "^M"
waitfor "Password: "
transmit "mypassword" ;fake password
waitfor "=> "

transmit "^M"
pause 2
endproc

As you said, initially I use logon.wax (manually compiled)to speed up a little bit. After I saw the problem, I use logon.was. It works perfect.

I believe most of time when I saw the error, the script is not executed at all, since I didnt see "login:".

 

[knob]

Do you have more than one copy of logon.wax on the system? I would think if the script was compiled and ran fine from within Procomm but had problems when run from the command line, that the problem would be in the way the command line was specified. Or possibly the problem was that login.wax existed but login.was was a newer file, which would cause Procomm to display an error message asking if you wanted to compile the newer script file. Is that possibly the error message you were seeing?