🚀 go-pugleaf

In article <19951001.000933.17@oaknet.demon.co.uk>,
Jim Gilligan <Jim@oaknet.demon.co.uk> said:

> I have just installed SlipSwitch 0.03 (or is it SwitchSlip...oh well...:) It
> works *very* well now I have reconfigured the file names to match those on my
> RiscPC properly.....

Eh?  Everything works through xxx$Dir and xxx$Path variables, so there
shouldn't be any changes to file names needed, provided all applications
have been 'seen' by the Filer before running SlipDial.

> Couple of questions:
> 
> 1. On start up the Slipdial status flashes up a 'Waiting for a while -
> Timeout 2 secs' Then a 'Timeout' message - before successfully running
> !TCPIP. What is this....please?

Don't quote me on this (I just copied that bit of code from the old
scripts!), but I *think* the delay is needed to make the centred message
box work properly.

> 2. More to the point... The line dropped after 3 minutes inactivity tonight,
> which was a little annoying as I was editing a file locally to send and
> didn't want the line to drop in the meantime. Was this a Demon 'failure' or
> is there a tcp timeout at work. I found a tcp 60 3 exit in a configuration
> file dropped into !TCPIPUser. Is this the culprit? 

Yes and no.  *A* "tcp hangup" command probably was the culprit.  As
mentioned in !!ReadMe, this is the usual way to ensure that unattended
automatic operation does time out.  The command "tcp hangup 60 3 exit" is
included in ConfigA to drop the line after 3 minutes of inactivity
_during_an_automatic_session_only_.  However, if you start the session
manually with the mouse, the normal Config file is used - which probably
won't have a timeout setting at all unless you've put one there yourself. 
Or were you up at 6am (or whatever) doing your editing during the
automatic session?  :)

-- 
 /  Richard Birkett   <><    ><>    <><   |   Cambridge, UK   \
 \  Email: richard@musicbox.demon.co.uk   |                   /