  Copyright (c) 1994/June/16 by K.H. Weiss  All rights reserved. 

  Written by:
      K.H. Weiss           Internet: <khweis1@mvmhp.ciw.uni-karlsruhe.de>
      Eulenweg 2           Phone   : (49)-721-608-2418
      76536 Weingarten
      Germany

                              SLIPLOGW
                              --------
SLIPLOGW is an improved version of my SLIPLOG. It replaces sliplog and
the (inofficial) 'sliplogr', which was buggy. First of all, you should 
read the old SLIPLOG.DOC-file!
---
Compared with the old sliplog, you have some new features:

- working with windows now (yes, remotecontrol works in the dosbox !)
- autodial (Dial on Demand)
- monitor incoming calls on the screen
- watchdog (rebooots pc if sliplogw failes for a while)
- some new commandline-options

autodial
--------
Everytime sliplogw 'sees' a packet, addressed to the serial line
and there is no connect, sliplogw dials and connects to a (hopefully installed)
server. The dialstring used, is that one, defined with the first password in
comlog.pwd (sysop-password, see sliplog.doc). After loading sliplog, 
this feature is disbled. There are two ways to enable 'autodial':

switch on Autodial:

sliplogw <packet-INT> -D n   connection closed after n seconds of inactivity

or:
Call the server, login as sysop (the dialstring is NOT part of the
password now!) and after you see the prompt, just type 'autodial'. 
Now the message 'autodial on' should appear. If you type once more
'autodial', then autodial is off again. 

switch off Autodial:

sliplogw <packwet-INT> -D 0    disables dial on demand

or:
Call the slipserver and login as sysop as mentioned
above. If you are still in a session, you may send a break over the line (with
'comtool' for example, see sliplog.doc) and relogin as sysop. Now type 
'autodial' to switch off autodialing. This may be useful, if you 
want to sleep and your slipserver is ringing you on and on ....:-)


Other changes:
--------------
If you programmed a password with callback, (see sliplog.doc) only the first
part of the accessstring (until the '#'-delimter) is the password.

comlog.msg file is no longer needed. Instead of this, you
must give the ip number of slip on the commandline:

sliplogw <comport> <packetvector> \path_to_helpfiles\  <ip_number_of-slip>
or:
sliplogr <portadress> <comirq> .....

After you installed sliplogw (there should be a succes-message), you
can make another call to sliplogw, only giving the packet-IRQ and some
otions:

sliplogw (no parameters)  search all sliplogs and print the status of them

sliplogw Pkt_INT          print status of this sliplog

sliplogw Pkt_INT -W n     Watchdog-Timer set to n *10 Sec. If the program is 
	                  inactive for more then 10 sec, a warning beep occurs.
                          Ater n* 10 sec of inactivity, the pc is rebooted.
 		          -W 0 switches off the watchdog.		

sliplogw Pkt_INT -P n     Sliplog is suspended for up to n * 10 Sec. Incoming
			  calls are not answered. If you don't resume within
                          n*10sec (by calling sliplogw pkt_int -P 0), 
                          the pc is rebooted. If pause is activated, 
                          you are warned be a beep every 10 sec
		
sliplogw Pkt_INT -B n     Switch off (n=0) or On (n=1) the warning-beep

sliplogw Pkt_INT -M n     Switch off (n=0) or On (n=1) monotoring of 
                          incoming calls to the screen

sliplogw Pkt_INT -R       Reboot the pc. Works even with windows, by pulsing                          			
			  the reset-line. Before the reset is executed, all
                          buffers are flushed.

sliplogw Pkt_INT -S n     switch to 'sysopmode', that means: only the sysop
			  is allowed to login. If someone calls, a service-
                          message shows this state to the caller.

sliplogw Pkt_INT -H       Hangup the modem

sliplogw Pkt_INT -U       Unload sliplogw

-----------------------------------------------------------------------------
                          IMPORTANT
------------------------------------------------------------------------------
!!!!!!      ALL FILENAMES CHANGED      !!!!
-------------------------------------------
sliplog.pwd  (the passowrd-file, formerly 'comlog.pwd')
sliplog.msg  (the welcome-message, formerly 'welcome.msg')
sliplog.log  (the logfile, formerly 'comlog.log')
-----------------------------------------------------------------------------

For further informations have a look on 'sliplog.doc'!

Installing SLIPLOGW with WINDOWS:
---------------------------------
Install sliplogw from DOS just after winpkt. If you have a packetmultiplexer:
You should use pktmx12b, winpkt is loaded after calling pktdrv. You
should NOT use pktmx12h (this version doesn't need winpkt), I had problems
with ARP-protocols on new connections over slip. 

Here the relevant part of my autoexec.bat:

lh \win3tcp\wd8003e 0x65 5 0x340 0xcc00
lh \win3tcp\pktmux 3 65 /4
lh \win3tcp\pktdrv 60 65
lh \win3tcp\pktdrv 61 65
lh \win3tcp\pktdrv 62 65
lh \win3tcp\cslipper com2 baud=38400 vec=63 ether
lh \win3tcp\winpkt 0x60
lh \win3tcp\winpkt 0x61
lh \win3tcp\winpkt 0x62
lh \win3tcp\winpkt 0x63
lh \win3tcp\slip 2 63 c:\nos\spool\ 129.13.118.21

I attach 63 sl0 and 62 en0 in nos. 61 is my packetdriver for winsock and
i use 60 for another application, getnews for example.

nos11c (or another compile) is started in windows with a pif-batch.
You should reserve as much memory you have, but not declare the HMA.
priority settings are 100/50. The original version of nos11c was very
slow, when in background. I patched this version (simply removing a 'hlt'
in the 'giveup'-proc), with the result, that fgnd/bgnd settings have an
influence now and a dramatic speed up of the ftp-server when working
in the background.

THE FINAL VERSION OF SLIPLOG WITH A NEW, COMPLETE *.DOC WILL COME IN THE
                          NEAR FUTURE!

      Feel free to correct my english: it's not my native language ;)
  **********************************************************************
  *  This program executable, help file, and related text files may be *
  *  distributed freely and used without fee by any individual for     *
  *  non-commercial use. This version of SLIPLOG may  NOT be           *
  *       distributed as part of any commercial package.               *
  *                                                                    *
  *           USE THIS SOFTWARE AT YOUR OWN RISK                       *
  **********************************************************************

  Thanks to all those people who are working on ka9q/NOS, especially
  Ashok Aiyar. His server <biochemistry.cwru.edu> contains an
  excellent NOS-Version (nos11c.exe), the nntpget-tool, and a lot of
  tips for the installation of nos and winsock-software!

--
  Report bugs and comments to: <khweis1@mvmhp.ciw.uni-karlsruhe.de>
