Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. ianb16

    Workaround Error 21 - Batch File

    Once I put in the "yield", everything worked fine. I will be doing a complete "stress" test overnight tonight. Thanks.
  2. ianb16

    Workaround Error 21 - Batch File

    I have set up a loop while dialing: while $DIALING endwhile but the program exits from the while loop, before the dialing is complete. Why would this happen? I stored the value of $DIALING to a variable and set a breakpoint to check on this value, which was 1 after exiting the loop.
  3. ianb16

    Workaround Error 21 - Batch File

    Thanks for the reply. Would this mean that I would need to have the script execute right away as opposed to when the connection is made? Secondly, should there be a delay factor waiting for the carrier befor I test for the $CARRIER to be true? Thanks. Ian
  4. ianb16

    Workaround Error 21 - Batch File

    I have created a workaround the error 121 I was previously running into. The solution was to create a batch file running the 31 entries I had in 4 call groups. Therefore I dial into one company at a time capturing data then exiting Procomm. Problem: The problem I have is that the script for...
  5. ianb16

    Run Time Error 121

    The code I posted included the "include" files: captset.inc, genfunc.inc, adpfunc.inc etc. I will try your suggestion, but here is some additional info: - Instead of error 121 I get the message PW5.EXE application error. The instruction at 0x77fcbee8 referenced at 0x0000000d. The...
  6. ianb16

    Run Time Error 121

    Hi Knob, Version 4.8 I have been trying other system settings etc to bypass this error, but it seems to be consistent within that dialing group. I will post the code for one entry in that group (they are all basically the same): ;ABC.WAS ;Script for Downloading data from ABC Company ; string...
  7. ianb16

    Run Time Error 121

    I received the same error with the windows scheduler. I do not receive this for other Groups I dial into. Any suggestions. Further Info: The one group with the error is a different type a script because of a different system.
  8. ianb16

    Run Time Error 121

    It happened on another workstation once. On this workstation it seems to be happening everytime. I am testing it right now with the windows scheduler. Will update with results later.
  9. ianb16

    Run Time Error 121

    I have run the scripts individually and as a group within procomm. So far this message has only appeared when running the Group through procomm scheduler.
  10. ianb16

    Run Time Error 121

    Could someone help with the following error message: Error 121: Fatal exception during script execution. The instruction at "0x004f181b" referenced memory at "0x0214f6ef". The memory could not be written. I am running procomm 4.8 on a Windows 2000 computer. Through the...
  11. ianb16

    Waitfor not "firing"

    Just to finish off... I found if I used a string of letters that is not interrupted by escape characters the waitfor was successful. In this case I used: waitfor "OPIES" Thanks for your assistance in the last few days. Ian
  12. ianb16

    Waitfor not "firing"

    The system I am dialing into is an ADP Auto Dealer System. I am not sure if it is a bug or the way the sytem paints the screen. For example the monitor recording of: mESC[?25hESC[23; May position the cursor at the 25th position and 23 rd line. If so, then the recording would only pick up...
  13. ianb16

    Waitfor not "firing"

    That is correct. The recorded string only starts after the escape sequences before the "R". Is there a limit to the number of characters in a waitfor? or in the recording "conversion" to a waitfor? I counted approx. 94 characters in the recorded waitfor.
  14. ianb16

    Waitfor not "firing"

    Just to elaborate a bit more, I will show what is displayed on the screen versus recorded versus the monitor.cap. On the Screen: ENTER COMMAND (1,2,3,4,5,6,RUN,SAVE,DELETE,EXIT,VIEW,COPIES,?) where this all appears on one line and where 1, 2, 3, 4, 5, 6, R, S, D, E, V, C and ? are...
  15. ianb16

    Waitfor not "firing"

    I have noticed that what was recorded in the recorder script as "^[[" shows up as "left arrow and [" (hex 1B 5B) in the monitor window. Does this give you any clues?
  16. ianb16

    Waitfor not "firing"

    Thanks for the replies but neither suggestion would work. I have recorded the sessions to ensure that I was waiting for the proper characters. Is it possible that there are hidden characters? or that the characters are not what they seem to be?
  17. ianb16

    Waitfor not "firing"

    Hi, I have a problem with waitfor not firing with a system I am dialing into. My settings are a VT-220 terminal 8-N-1 and stripping the 8th bit. I have tried both STRIP and RAW, and escape characters and no escape charaters in the waitfor. Here is the prompt I am looking for with and...

Part and Inventory Search

Back
Top