G4WPT password support for WinPack
----------------------------------
This ZIP contains the files needed to enable support for G4WPT style
passwords in WinPack V5 or later. It does not support any other
password system.

Installation
------------
Put G4WPTPWD.EXE in the WINPACK\SCRIPTS\PROGRAMS directory. Edit BBS.TXT
and make sure that it is capable of connecting to your local BBS. Unless
you connect via a node or a digi, it should not need altering. Put it in
WINPACK\SCRIPTS, replacing the original file. (You may like to keep a
copy of the original).

If you can get a copy of <CALLSIGN>.USR (where <CALLSIGN> is your
callsign, e.g. G4IDE.USR) from your sysop, put it in
WINPACK\SCRIPTS\PROGRAMS. The first time the password program runs, it
will find the file and convert it into <CALLSIGN>.LST in the same
directory. If you have only got your passwords on a printed page, you
must create the .LST file and key in the passwords one per line:-

abcde
QWERT
cFvGb
etc.

At this point you are allowed to curse the fact that the system uses
both upper and lower case!   :-)

If you haven't got your passwords on a printed page, stop at this point
because this program is not for you!

That's it! You should now be able to run WinPack, press F2 and get a
conection to the BBS, with the password being correctly sent. If that
works then the Auto BBS sessions will also work.

Problems
--------
If it doesn't work, some things to check:-

1. Make sure that the WAITFOR in BBS.TXT is correct. Sysops using the
G4WPT system are able to change the prompt that it sends. If your sysop
has done this, then you need to change the WAITFOR text.

2. If '1' above is correct, then you should see the password program
briefly appear on the screen in the form of a small box in the bottom
left hand corner of the screen, when the first password prompt is
received from the BBS. If it doesn't appear, you've either put it in the
wrong directory, or messed up the spelling of G4WPTPWD in BBS.TXT.

2. Make sure that whatever you have put for the BBS prompt in
Personal/BBS Info in WinPack is correct. It doesn't have to be the whole
prompt, but it must be some text that occurs in the prompt. Preferably
something more than just the BBS callsign.

4. Have a look in WINPACK\SCRIPTS\PROGRAMS - if you had a USR file ,it
should have disappeared and been replaced by <CALLSIGN>.TXT. If it hasn't
then you have got a different callsign in the Personal/BBS Info to the
one for which the USR file was supplied!

Refinements
-----------
In its default state, the password program takes you through to the
first proper BBS prompt. The way the system works is that the program is
actually run once for each line of incoming text. If your local BBS
sends a lot of text between the password input and the first proper
prompt, the program will be run a lot of times which may cause the
screen to flicker a bit.

If you find this is happening, try the following:-

1. Edit BBS.TXT and remove the ';' from the start of the WAITLINE line.

2. In WINPACK\SCRIPTS\PROGRAMS create a file called G4WPTPWD.CFG and put
in it a single line that contains some text that occurs immediately
after a correct password is received. The word OK should be enough.

This will cause the password system to stop processing text as soon as
the OK is received. However, if you find that the script now hangs at
the WAITLINE line, you will have to delete the CFG file and put the ';'
back.

Roger Barker, G4IDE
December 1995
