several ways to run scripts.. from the normal blue screen term mode in procomm.. alt a, the pick new.. alt a is scripts edit.. then paste in the posted script.. do a save as and give it a name.. one of the icons is for complie.. click that (or not) and close the script edit screen..
back in the program mode. logi ld 90.. for the posted script, note the 1st waitfor is waitfor "NPA " so the script will not start until it sees that.. new, cust 0, ac1. npa... start the script.. if your view is setup default you'll have a drop down window with each complied script.. if not you can go back to the script edit, (alt a) pick the script and click complie and run or just run..
script starts, it's waiting for npa so when you hit return the switch sends npa and the script starts.
here's a simple starting point as well.. press alt ]. login go to ld 20 then hit alt ].. you'll be prompted for a file name.. name and save it.. now go edit and compile it. or log out and run it.. the edit mode will look like this.
proc main
tranmit "name^M "
waitfor "Password "
transmit "secret^M "
waitfor "> "
transmit "ld 20^M"
endproc
the alt ] is script start/stop record.. the ^M is a return. we've posted 100's of proven scripts.. some as simple as the logi and others run for pages.. with scripts i have programed a full 61 with 1000 sets, bars names, never needed the copy command.. 2 very long days.. maybe 30+ hours. an opt 11 with 100 sets and a couple of pris is not even a long days work.. scripts enter data at 9.6, without breaks and without errors.. not a bad tool.. i started writing scripts almost 20 years.. 16/18 years back when procomm came out as shareware via a bbs.. i'm old school, but back then as well as now, i'm to lazy to do anything without a shortcut
john poole
bellsouth business
columbia,sc