Search results for query: *

You have been so very helpful in the past I'm sure this is something simple I'm just overlooking.. This script will not recognize the feof 0? and goto the else programming. What have I missed? string listmbxfile = " " PROC main string f_line string DREFF clear capture off...

Humm... well I took out the forever command after the waitfor "." and the script stopped in the same place, and unfortunatlly the "." that I'm waitting for is the only thing returned from the remote system at the end of that particular command. Any idea's... I'm going to try...

Hi, well I like the changes you made, however the script is still not waiting for the run reports to complete?? by watching the statmsg at the bottom of Procomm the script will start over... The other thing is now the number being dialed is not displayed when the call is placed.. not a big...

...if that's what you think is the cause of this script not waiting, it can just be removed. Thanks again for you time. ;DIAL-REPORTS1.WAS v1.0 ;***************************************************************************** ;* DIAL-REPORTS1.WAS...

Ok Knob... I did try this script you suggested but it still just runs over itself... I tried a waitfor "." forever at the end of the main but that didn't work.. Help this does everything I need it to do but it won't wait before dialing the next number.... what else can I try????

...;loops while dialing if $CARRIER == 0 Set Capture Path "C:\ReportFialures" Set Capture Overwrite OFF ;* Don't Overwrite Set Capture Query OFF ;* Don't Prompt for Capture Query else if not ddeinit LinkVar...

Ok I have found something interesting, although I have the command waitfor "." forever I can see the statmsg and after about 5 min. the script will start over, start going through all the modules again and there has been no "." issued by the system I'm connected to. any idea's??

This is the line it stops at everytime. Transmit "L all^M" Waitfor "." Forever These are in the middle of the run reports module. it's almostlike Procomm has a timer on and time is up for this entry. I've looked all through Procomm for timers and can't find any. Help...

Ok I added usermsg at the start of each module and the script apears to be working correctly through each one, however during the last secsion run reports it seems to time out after about 5min. something drops the line.... any sugestion? is this a Procomm issue? I can't find anything in Procomm...

...min.?? I can't see anything in the script that would be causeing this is this something in Procomm? and if so what?? ;DIAL-REPORTS1.WAS v1.0 ;***************************************************************************** ;* DIAL-REPORTS1.WAS...

What's odd is that just because the running man has stopped the script is still running in the back ground I started this script and the running man stopped after about 20min or so however the script continued to run for another 8 hours?? Is there a buffer to Procomm that fills?? or is it the...

I'm running a very simple script however after about 8 hours it seems to have lost the path to the csv file. Is there a way to determine why this script seems to have stopped? The icon in the toolbar that indicates the script is running stops after about 20 min. it is very confusing for the...

Thanks I have done that so that each of these systems I'm logging onto already has it's own script. I'd like to be able to write a script that will go through the dialling directory and call each member of a group in the ProCom dialling directory and each of those contain thier own script, that...

Knob, thanks for your input. Am I doing this all wrong will Aspect dial from the directory of ProCom which in turn would run another script? instead of trying to pull this information from an Excel file and haveing to maintain both the Excel spreadsheet as well as the directory in ProCom?

Your right again the script will only change modem settings if your directly connected the system. Thanks

I have written a script that dials several systems and runs and captures reports. Is there a way that the script can capture any of the systems that ProCom was not able to log onto, or is that something in ProCom??

Thank you very much that did the trick.

I'm running a script and have almost all the bugs out however the piece I'm missing is to make sure that the script at it's end dissconts from the system it's on. Any ideas?

Thanks for the tip I read the help file and your right it will not allow me to change the modem /port settings on anything but a direct connection. Thanks for your time.

Help I can't seem to get this to set the modem to 7,e,1 The terminal type is set to VT100 correctly, should I be setting this proc. in the main? it is currently the third proc. in the main. Any suggestions would be great. proc SetModem ; test Set terminal type...