Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!rmr
From: rmr@ccwf.cc.utexas.edu (Randy M. Roberts)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: VLT and FIFOBBS.REXX
Message-ID: <44016@ut-emx.uucp>
Date: 11 Feb 91 19:45:58 GMT
References: <1991Feb10.235516.3828@bronze.ucs.indiana.edu>
Sender: news@ut-emx.uucp
Reply-To: rmr@ccwf.cc.utexas.edu (Randy M. Roberts)
Distribution: na
Organization: The University of Texas at Austin
Lines: 89
Originator: rmr@sleepy.cc.utexas.edu

In article <1991Feb10.235516.3828@bronze.ucs.indiana.edu> graham@venus.iucf.indiana.edu writes:

[... stuff deleted ...]

|
|More specifically,  what is the sequence of events that I must go
|through in order to make fifobbs.rexx work in remote?
|
|The docs aren't clear here.
|
|Here's what I've tried....
|
|1.) RUN VLT.
|2.) Turn fifo pipe ON.
|3.) Turn serial.device off.
|4.) Open up the AREXX Scripts requestor and
|    a.) Select fifobbs.rexx.
|    b.) append the parameter "remote" to the end of it.
|    c.) Press return.
|

[... more stuff deleted ...]

|
|This leads me to more questions about modem setup.
|
|1.) How does fifobbs.rexx ANSWER an incoming call?
|    Must I set the modem myself for auto-answer?
|
|Would someone help?

Well I'm not trying to help, I'm in a similar quandary.

Here's what I did with "limited" success.

First try:

1) run VLT  (I did not close the serial port!)
2) issued ATS0=1 to my modem, which puts in AUTO-ANSWER MODE
2a) pressed the ANS/ORG button to ANS
3) run fifobbs remote
4) in VLT I open fifopipes (needless to say I already mounted FIFO:)
5) Then I typed a <cr> in VLT  (big mistake)

Here's what happened.  VLT and FifoBBS (FB) began getting in an infinite loop
with each other.  FB would send something to VLT which would send it right
bact to FB.  FB thought that this was a new response and would send (usually
bad) responses back to VLT, ad infinitum.

Repair attempt:  (Insert into above sequence)

2b) issued ATE0 to modem, This tells the modem not to echo what has
    been typed.

That seemed to correct the problem, but now the only way I could monitor
incomming sessions was to open a "REMCLI VLTR" (make sure the VLTR is in caps).

Now I am left with what I believe is a more difficult problem.  My friend's
computer (not an Amiga) cannot convert <LF>'s to <CR><LF>'s for display,
so my running FB is just about useless to him.

I still have problems when somebody logs off.  I get a bunch of "ERROR"'s
from my modem, which FB interprets as attempts to logon.  Another
set of infinite loops.

Questions: (finally :)

1) Is it necessary to press the ANS/ORG button to ANS?  Shouldn't the
   modem do that automatically?  (My friend's been to busy to continue
   experimentation.)

2) Should I modify FB to use a different FIFO: device and write a
   small C program "filter" to change all <LF>'s to <CR><LF> and then
   pass it to VLTR, or is there an easy way to just modify FB to automatically
   stick the <CR> in it?  (Sticking <CR>'s after "say"'s doesn't help the
   "address commmand 'type' filename"'s)

3) At the risk of getting an RTFM, can you turn on the "fifopipes" menu
   item from a VLT-REXX (.scp ?) or .vlt script?  I know I can issue
   the "ATE0" and the "ATS0=1" command from a script.

4) Should I modify FB to recognise the "ERROR" from my modem, just like
   it recognizes "NO CARRIER"?

ADVthanksANCE,
Randy
-- 
Randy M. Roberts
rmr@ccwf.cc.utexas.edu