-=> Quoting Mike Ruskai to William Mastop <=-
 WM> I've been using os/2 warp 4, the ftp.exe program, to grab mail and
 WM> files and such from hubs, with a script.  I start it up as follows:
 
 WM> === Begin ===
 WM> ftp -i -n <"f:\fiftp\l920360
 WM> The problem that I have is that if something hangs, like the net, a
 WM> glitch with a file, what have you, it just sits there.  It also doesn't
 WM> let go of the comm port.  I use ppp.exe to dial, and have it set to
 WM> timeout if there's no activity.  It does so just great, and then exits.
 WM> Unfortuneately, it doesn't take ftp.exe with it.  Any suggestions
 WM> would be greatly appreciated. William
 MR> You could run a looping REXX script (with a delay, of course) that
 MR> checks  for PPP.EXE in the process list, and if not found, kills any
 MR> instances of  FTP.EXE that are running.  You would need a process
 MR> viewer/killer such as  GO.EXE for this.
        Or you could use a different ping.exe (available at Hobbes)
that returns a different error code when there is and there is not
an internet connection.  This simplifies greatly the script you
proposed.  It could go something like:
/* Rexx script */
'ping.exe -c 1 -s 1 -n -q www.ibm.com >nul 2>nul'
if rc == 0 then
        say "connected"
else
        say "not connected"
        Stephane [TEAM OS/2]
--- Blue Wave/OS2 v2.30
---------------