CompuServe Thread

#MANDELBROT

4 messages in this thread
#50479From: Bela Lubkin/SysopJan 24, 1987 1:37 AM
Kelly, the SIGware provides a function to send a prompt character after each prompt. Go into OPtions and set your prompt character to something, then use that as part of the search string in your script. One possible character is ^H (control-H — you give it to the OP;PC command as ^H). I usually write "Function;" or "Funcxion:"… >Bela<
#50542From: Kelly JordanJan 24, 1987 12:20 PM
Thanks Bela, That appears to be the best alternative yet. It seems to work pretty good. I looked at implementing Larry's idea of including the line feed (or carraige return for this term pgm – VT100 V2.4) but after doing a hex dump of the end of a capture, I found out that CIS is sending me four nulls after every carraige return and I can't get the term pgm to recognize a null in a WAIT command string. I don't know why I get these nulls either. Printer delays in Go Terminal are set to zero. Maybe it is tymnet, since I understand that datapac in the great white north has to connect to Tymnet to get to CIS (I wish CIS would get a direct DATAPAC port, it would be a lot cheaper for us up here). Anyways, I set the promt to a ^G so this way I also hear when the RTN is done. 73, Kelly
#50561From: John DraperJan 24, 1987 1:59 PM
Kelly, You might try setting the Datapac parameters as you would for a download and see if that helps the NULLs after newline. We are lucky here in Vancouver to have a direct CIS node. It is a lot cheaper, and there are no extra parameters to fiddle with. Regards, Larry.
#50593From: Kelly JordanJan 24, 1987 6:23 PM
Larry, I probably would if I knew what the various items meant. How do I found out what each of the items is supposed to be or control? Can I get this information on datapac like you can for datapac phone numbers/ports in various cities? A few hours later after playing at datapac address 92100086,A I finally found the instructions for the datapac parameters. Boy, do they ever hide them! Why don't they put them under documentation instead of Software updates!! That was the only place I had left to look that had any relation to 3101 ports! That does appear to be what the problem is. Doesn't really matter now. I used Bela's suggestion and appears to work fine. 73, Kelly