ReadMe File For
WINROBOT(C) Shareware Version 2.0
Copyright Bill Buckels 1996-1999
All Rights Reserved.

WINROBOT.EXE is a Script Driven Program Launcher For Windows. It was
created to join a number of Windows and Dos tasks in a linear process
and was later expanded to support linear conditional branching.

WINROBOT.EXE launches applications named in command line scripts. Each
Line In The Script Can Contain An Application Name and its Command Line
or a KEYWORD to modify the next line.  WINROBOT executes each launch
consecutively.

  Usage is : WINROBOT [script.txt] [optional - user.ini]

The WINROBOT Execution Script is an ascii text file listing a sequence
of programs and child processes that will be launched by WINROBOT.
WINROBOT waits until each executable process in the script is finished
before launching the next. A Timer Interval is used to check if each
application has finished and if it has, the next application in the list
is launched, or if an EXIT KEYWORD is reached, the list is terminated
and the Windows session is ended.

WINROBOT will allow sequential execution of up to 128 Applications (the
maximum number of lines in a script).

Although the WINROBOT script is not a replacement for the MS-DOS batch
file, WINROBOT supports a number of internal command options that expand
the functionality of WINROBOT scripts beyond the launching of
applications.

WINROBOT features a number of user definable options which it supports
using user profiles (.INI files). WINROBOT also allows time scheduled
startup and optionally logs activity and errors in the log file listed
in the profile.

Since WinRobot was developed in Windows 3.1, and not in Windows 95 and
beyond, it will work in both environments, and some of the documentation
is written from the Windows 3.1 perspective.

Shareware Registration is $10.00 per installed copy.

Table of Contents
-----------------

  Chapter 1 - Licencing and Registration
  Chapter 2 - What is WINROBOT?
  Chapter 3 - How Is WINROBOT Used?
  Chapter 4 - How WINROBOT Works in Windows
  Chapter 5 - How WINROBOT Works in DOS
  Chapter 6 - How WINROBOT Commands Work
  Chapter 7 - How WINROBOT Support Files Work
  Chapter 8 - How WINROBOT WILDCARDS Work
  Chapter 9 - Limitations - What and Why?
  Chapter 10- What is WAIT.EXE?

Chapter 1 - Licence Agreement
-----------------------------

This program is the exclusive property of the author, Bill Buckels.

If you continue to use this program you must register with Bill Buckels.

Shareware Registration is $10.00 per installed copy. Payment by Cheque
or Money Order only to the address below.

  Bill Buckels
  589 Oxford Street
  Winnipeg, Mb, Cdn R3M 3J2

  Email: bbuckels@escape.ca
  Website: http://www.escape.ca/~bbuckels

Warranty and Liability
----------------------

This program and its files are thought to be free of defects.
Regardless, Bill Buckels assumes no liability whatsoever for the fitness
of use of WINROBOT, or any loss or damage resulting from its use.

If you cannot abide by these conditions and the conditions stated in the
Licence Agreement, do not use this program.

We apologize for errors or omissions. They were not intentional. If you
are a registered user, and you encounter a program bug, we will provide
you with support. If you aren't registered we won't.

Distribution
------------

You may distribute this program and its source code freely. You may not
charge any fee for this distribution, except for a reasonable
duplication fee, as in the case of Shareware Distributors.

If you obtained this program from a Shareware bundle (like a CD) you
must still register with the author.

Trial Period
------------

If you do Batch-Type processing in the Windows Environment, WINROBOT is
an excellent value at only $10.00 for the Registration Fee. If it fits
some of your needs, and you continue to use this program, we expect you
to register.

WINROBOT comes with a 30 day free trial period. This gives you enough
time to see if it fits your needs. If you have not registered in 30 days
you should not use WINROBOT.

Try It Out! We encourage you to try all the features that are described
in the Windows Help for WINROBOT.

Many sample scripts are shown in WINROBOT Help. Just copy the HELP file
text to the Windows Clipboard and paste it into notepad. Then change
what you need to change to use the examples on your own system.

And PRESTO!!! You will have an EASY WAY of trying-out the feature used
in the WINROBOT HELP example.

But you will only have 30 days to try WINROBOT. If you don't register
within this time, WINROBOT will still work but nag you until you do.
Sorry about that, but we feel that the 30 day period is plenty of time
for an evaluation. And you won't care if WINROBOT nags you if you don't
use it anyway, so no harm done!

Source Code Agreement
---------------------

WINROBOT is distributed with Source Code.

The source code is provided as-is and where-is.

We understand how important it is for some sites to have source code. It
allows a programmer to modify and add to the WINROBOT program if special
requirements exist.

But remember that you may not produce any commercial package from the
WINROBOT source code that competes with WINROBOT in any way. And We do
not support modified versions. You will have to take care of this
yourself.

Installation Instructions
-------------------------

Just add WINROBOT.EXE anywhere you please in your WINDOWS program
manager. Add WINROBOT.HLP as well. These 2 files must be in the same
directory. Make this your start-up directory for WINROBOT for now. You
can get fancy later.

If Installing from WINROB20.ZIP, unzip complete with pathnames. A
directory called \WINROBOT will be created for you.

A Tip About ShortCuts: During your actual use of WINROBOT as a TASK LIST
LAUNCHER you will need to use a script file with WINROBOT containing
each TASK LIST. So WINROBOT needs to be installed as one or several
program items (ShortCuts), since text scripts (similar to DOS batch
files) are required for its use.

Since a script file name is required, you must include the script name
on the command line in your program group item.

Use Windows Help to read the WINROBOT.HLP HELP file for more info.

Program History
---------------

The WINROBOT program is the prototype that I used for a commercial
application launcher for a special purpose application that required the
use of linear launching of mixed dos and windows applications.

It is not really a prototype at all, but a pretty good and functional
straight-line task launcher for Windows.

The program that was based on WINROBOT and eventually distributed was
tweaked somehwat from this prototype. It is not called WINROBOT. The
recipient paid for the tweaking of the prototype and in fairness, the
paid-for additional functionality is not present in WINROBOT in respect
of their special interest.

I wrote this application during many long evenings and weekends of very
tedious programming and testing. In restrospect I should have probably
been doing something of a more recreational nature since I was paid
zero.

Sadly, the product that was based on WINROBOT sees very little use.

I made the decision to distribute the WINROBOT prototype as Shareware in
the hope of salvaging some of its remaining potential. It is really too
good an effort to throw away.

I hope you find WINROBOT a useful and effective system tool for your
particular TASK LIST launching requirements.

Chapter 2 - What Is WINROBOT?
-----------------------------

WINROBOT.EXE is a Script Driven Multiple Application Chain Launcher For
Windows. It was created to join a number of Windows and Dos tasks in a
linear process and was later expanded to support linear conditional
branching.

WINROBOT is not a meant to be used as a replacement for DOS batch file
processing. It is primarily an automatic program launcher.

WINROBOT will launch Dos Batch and Dos Program applications as well as
Windows Applications as named in a WINROBOT Session Script.

Some DOS-like internal commands also provide limited File Management and
Interface Response in the Windows Environment.

WINROBOT is written in Microsoft C for Windows and was produced from the
Microsoft Software Developer's Kit (SDK) for Windows 3.1.

WINROBOT was designed, programmed, and tested in its entirety by Bill
Buckels. The process took place during many sleepless nights and
weekends.

Additional Credits
------------------

During the design phase, Bill's friend Grant Rondeau provided
suggestions and encouragement, and was WINROBOT's first ALPHA SITE.

Chapter 3 - How Is WINROBOT Used?
---------------------------------

  Usage is : WINROBOT [script.txt] [optional - user.ini]

The WINROBOT Execution Script is an ascii text file listing a sequence
of programs and child processes that will be launched by WINROBOT.

WINROBOT waits until each executable process in the script is finished
before launching the next.

WINROBOT will allow sequential execution of up to 128 Applications (the
maximum number of lines in a script) and can optionally automatically
exit Windows when the script is finished processing.

One significant feature of WINROBOT is the support for the FOXPRO style
of RunTime application. Since WINROBOT launches the RunTime and the
RunTime in turn launches the runtime application, Windows reports that
the task has ended prematurely. WINROBOT has a feature which overcomes
this problem.

WINROBOT features a number of user definable options which it supports
using user profiles (.INI files).

WINROBOT also allows time scheduled startup and optionally logs activity
and errors in the log file listed in the profile.

SAMPLE DOS START-UP BATCHFILE
-----------------------------

@echo off
echo Now Booting Windows!
WIN WINROBOT SCRIPT.TXT
if errorlevel 2 goto abort
if errorlevel 1 goto success
rem Trap Error Level Returned From Exit Command In Script
rem Windows Allows Us To Use The Following exit codes
rem To Control The Windows System Action On Exit
rem make the last line in your script one of the following if
rem you want windows to take over and either reboot or restart
rem these are handy for installations and things of that nature.
rem EW_RESTARTWINDOWS 66
rem EW_REBOOTSYSTEM   67
:abort
echo Done! WINROBOT was aborted before processing was complete!
goto end
:success
echo Done! WINROBOT completed processing script.txt!
:end
echo Now Back In Dos!

SAMPLE WINROBOT SCRIPT
----------------------

rem A WINROBOT Script with an EXIT command
rem comments and blank lines are ignored.
if exist C:\WINDOWS\WRITE.EXE goto SKIPIT
WRITE.EXE
:NOTEPAD
NOTEPAD.EXE C:\WINDOWS\WIN.INI
goto END
:SKIPIT
PBRUSH.EXE
if not exist FOOBAR.TXT goto NOTEPAD
:END
EXIT 1

Chapter 4 - How WinRobot Works In Windows
-----------------------------------------

The WINDOWS LAUNCH OPTION
-------------------------

Usage is: WINROBOT [script.txt] [.ini file-optional]

Purpose : The same as listed in the DOS LAUNCH OPTION except that
WINROBOT is executed from a windows program group using the script that
is desired listed on the command line of the program item properties.

How WINROBOT Works and How User Profiles Are Supported
------------------------------------------------------

Format 1: Normal Execution - 1 line required
--------------------------------------------

Each Line In The Script Contains An Application Path Name and its
Command Line or a KEYWORD Line that Modifies the Behaviour of the Next
Line in the execution script.

During normal execution, WINROBOT waits for the successful launch of the
Pathname and then records the number of tasks that are associated with
that Pathname's module. When the number of tasks associated with the
pathname's module fall below the recorded amount, WINROBOT assumes that
processing has completed and executes the next line in the script.

Format 2: CHILD Runtime Execution - 2 Lines required
----------------------------------------------------

Some Child processes (notably Microsoft FOXPRO RunTime) will launch
processes of their own, and do not register as a successful launch since
they in turn launch a child application which becomes the "NEXT WINDOW".

To support this runtime type of execution, WINROBOT requires the KEYWORD
phrase of the form "CHILD=Window Text" be placed on the line preceding a
normally formatted application path entry.

To implement CHILD Keyword execution, WINROBOT launches the the
application by the path entry then waits until the "Window Text" in the
script is displayed in the title bar of the "NEXT WINDOW". WINROBOT does
not wait forever for this to occurr, and by default retries 3 times at 5
second intervals before giving-up.

If a CHILD launch is successful WINROBOT then waits until the text in
the "NEXT WINDOW" no longer matches the "Window Text" before processing
the next line in the script.

Format 3 - EXIT Windows Option
------------------------------

If The Line In The Script says "EXIT" Windows is exited and the Windows
Session Ends. An optional exit code of the form "EXIT 1" Can be used to
return an exit code to DOS or to reboot the computer or restart windows.

GENERAL
-------

If an Application Fails To Execute, WINROBOT aborts the execution script
and does not exit Windows

A Timer Interval is used to check if the application that WINROBOT has
launched has finished and if it has, the next application in the list is
launched, or if an exit command is reached, the list is terminated and
the Windows session is ended.

Chapter 5 - How WinRobot Works In DOS
-------------------------------------

The DOS LAUNCH OPTION (Windows 3.1 Specific)
--------------------------------------------

  Usage is: WIN WINROBOT [script.txt] [.ini file - optional]

Purpose is: Start Windows, consecutively execute the Windows Apps listed
in the script, and (optionally) exit windows when done.

If the last command in the script is the word "EXIT" windows will be
exited if safe to do so.

Exiting can be done with an exit code defined in the script. The exit
code can be trapped in a dos batch or be used to restart windows or
reboot the computer. By trapping WINROBOT's exit code a batch file can
tell if WINROBOT was terminated before completing.

Windows exit is disabled until WINROBOT's apps are finished processing
unless WINROBOT itself is terminated.

When WINROBOT encounters an error (in the script etc.) it posts the
error and then aborts the process after the user has acknowledged the
error.

WINROBOT does use some system resources and checks the process at user
definable intervals to see if the application that it has launched is
finished. If the application that WINROBOT has launched is done it
simply launches the next in the list, or ends if the list is complete.

WINROBOT is always minimized, but can be closed at any time if it is
desirable to do so.

The script is an ascii text file and can contain either program names or
program names with command line options or can contain KEYWORDS (127
character max per line).

If WINROBOT is not provided with a script, a usage message is posted.

Chapter 6 - How WINROBOT Commands Work
--------------------------------------

Display Commands (KEYWORDS)
--------------------------

The following display commands apply only to Windows applications. The
initial display mode of a DOS application launched under Windows is
controlled by the .PIF file for the application.

SHOW = MAXIMIZE
SHOW = MINIMIZE
SHOW = NORMAL

Controls the initial display mode of the launched application

FORCE

Initially opens the application maximized and then Forces the
application (next window) to display in maximized mode by making an api
call to ShowWindow.

A Limited Number of DOS-Like internal commands are supported by WINROBOT.
-------------------------------------------------------------------------

Conditional Branching
---------------------

i.e. GOTO, IF EXIST and NOT EXIST

The syntax and label convention used in WINROBOT is basically the same
as that used in a DOS batch file. By providing this feature internally
in WINROBOT, intervention can be performed directly in the WINROBOT
script.

File Commands
-------------

WINROBOT does not support its internal DOS-like commands in exactly the
same way that DOS does. Wildcards are not fully supported nor are
implied Pathnames. However the COPY and DEL commands offer Wildcard
support.

Conversely, directories as well as files can be renamed, and the
WINROBOT copy command expands files that have been compressed using
Microsoft's COMPRESS utility when the files are copied.

The following is a list of WINROBOT's internal file commands:
-------------------------------------------------------------

MKDIR [directory name]
RMDIR [directory name]
DEL [filename]
RENAME [source] [destination]
COPY [source] [destination]

If full DOS file command support is required as part of a WINROBOT
session, use WINROBOT to launch a DOS batch file.

User Messages
-------------

The WINROBOT ECHO Command works differently from the DOS ECHO Command,
although the principle is basically the same.

When the Echo command is used in the WINROBOT script, WINROBOT saves
each line of text following the echo command in a an internal buffer.
When the next WINROBOT command that is not an ECHO command is reached,
the echoed text is displayed in an OK style message box before
continuing.

The WINROBOT PAUSE Command has the additional effect of displaying the
Pause message from the WINROBOT.Ini file. By default this message says
"Press OK to continue..."

The WINROBOT echo command provides a simple method for user messages to
be displayed in Windows during WINROBOT script execution.

Sample WINROBOT Script: The Echo Command
----------------------------------------

rem The Following Illustrates The Use Of
rem The Echo And Pause Commands
echo Hello There Yogi Bear.
echo No Big Deal...
pause
echo Hello There BooBoo Bear.
echo Ok Boob...
echo No Big Deal...
mkdir garp
rmdir garp

Comments
--------

If the first letter of a script line in a WINROBOT script begins with a
character below ascii 48, the script line is considered a comment.

The exception to this is whitespace. Leading blanks are stripped.

The DOS REM statement can also be used to designate a comment line in a
WINROBOT script.

Chapter 7 - How WINROBOT Support Files Work
-------------------------------------------

WINROBOT.INI and USER PROFILES
------------------------------

An .INI File is used by WINROBOT to supplement the execution script in
order to support user options and events. The .INI file controls how
WINROBOT will process a child execution script.

If a WINROBOT.INI file does not exist in the Directory that WINROBOT is
currently being run from, a default WINROBOT.INI is created. The user
can edit this file to create a custom version.

The .INI file that is created contains example sections that explain
each profile used in the live sections.

Multiple .INI files can be used with WINROBOT, just as Multiple Scripts
can be used with WINROBOT. The optional second command line parameter
for WINROBOT is the name of the INI file that WINROBOT will use to
modify the current session.

The following optional parameters are supported by WINROBOT. These are
stored as profile strings in the [Options] section of WINROBOT.INI.

They are shown with the default values. If a Value is not in a valid
range, the default is used.

Delay=10

Delay time in seconds between checks for Executable Process Termination
and StopFile Events. The Value must be in the range of 5-60 seconds.

Retries=3

Number of retries to check for start of Child Runtime Event in the Next
Window. A Value of 0 is invalid.

Wait=5

Time in seconds to wait between Retries. The Value must be in the range
of 5-60 seconds.

PurgeLog=Y

Purge the Log File each Session (Yes or No). WINROBOT provides Logged
Activity. It may Not Be desirable to maintain a large activity log. If
this profile is set to N the log continues to grow in size.

UseLog =Y

The LOG is turned on by default. If it is not desirable to have this
feature enabled then the profile can be set to N. (NO)

Note: Additionally, the Use and Purge profile strings apply to the other
support files used by WINROBOT. Please refer to the WINROBOT.INI file
that is created when WINROBOT is first run for a complete listing of
these profiles.

The following files are supported by WINROBOT. These are stored in the
[Files] section of WINROBOT.INI

LogFile=Drive:\Directory\Filename.Ext

WINROBOT uses the .INI file format as the format for the log. Windows
itself is used to update the log rather than doing so directly. (This is
a precaution to avoid DISK I/O Conflicts).

The WINROBOT log file is organized into DATE sections. Each entry in the
log is preceded by the TIME and a sequence of execution for the script
starting with number 1. The LOG is treated as a keyed file by Windows
and the sequence number ensures that each log entry has a unique key.
The sequence number also links a session. Each session (script) starts
with number 1 (as indicated).

The Log Format...
-----------------

Uses Today's Date for The Log Section - [Month-Day-Year]
Uses The Current Time For The Section Key - Hr:Min:Sec Sequence
Uses The Log File Path Name That is Specified In The .INI File
Purges the Log Each Session unless this is over-ridden in the .INI file.
Always Logs activity unless this is over-ridden in the .INI file.
Each Log Entry is of the Form "Key=Event".

The LOG is good for debugging purposes and it is for this reason that it
is turned on by default. Since entries in the log are made at the
beginning of a launch and at the end, the log process does not use
excessive resources.

StartFile=Drive:\Directory\FileName.Ext

Do Not Process WINROBOT Script until the specified file is found.

The following files are used to send and receive an OK or a YES-NO
response between launching of applications

StopFile=Drive:\Directory\FileName.Ext
QuestionFile=Drive:\Directory\FileName.Ext

Pause or Terminate WINROBOT if the specified file is found. Get user
response before terminating or resuming. Return user response in the
Answer File.

The Stop File and the Question File Are of the Following Format

Line 1 - Style (Must Say OK or YESNO). Default is YESNO.
Line 2 - Message Box Title
Lines 3 to EOF - Message Text

AnswerFile=Drive:\Directory\FileName.Ext

The Answer File Is Returned In The Formats:

set winanswer=Y (for Yes or OK)
set winanswer=N

The answer file can either be parsed for a response or called from a DOS
batch file as a supplementary batch to set the winanswer environment
string. If the environment string is to be used in this manner it is a
good idea to set the winanswer environment variable in dos prior to
starting windows so that an out of environment error does not occurr. It
is up to the launched process to remove the unused response file after
it is finished with it.

The StopFile Event - A Semaphore File Technique
-----------------------------------------------

If the file named in the StopFile Event in WINROBOT.Ini exists then
WINROBOT suspends processing and requests process instructions from the
Windows User. If a formatted Message Block is found in the StopFile,
this is used for the message box prompt.

The options available are to either abort WINROBOT or to resume.

Additionally, the file is removed after processing, and the answer File
that results contains the user response.

The StopFile Event can be used by a Child Application to Signal WINROBOT
that processing should be stopped or paused by creating the textfile
named in the corresponding StopFile profile string in the .INI file.

The application creating the StopFile can place a message into the file
if a reason for the stop is desired, and this will be displayed in
WINROBOT's message box.

The StopFile event will not be checked by WINROBOT until the child
application is no longer detected as being active. This is done to avoid
prematurely opening the StopFile if it is in the process of being
created.

This event can be used from a Dos Child Application to post a user
message to WINROBOT's Message Box upon completion of or failure of a
given task.

The Question and Answer File are a variation of the StopFile with the
difference that Processing is only paused and not stopped.

The following event parameters are supported by WINROBOT. These are
stored in the [Events] section of WINROBOT.INI

StartTime=HH:MM

Begin Processing WINROBOT Script at this time. If the current time is
after the start time WINROBOT terminates without processing.

Chapter 8 - How WinRobot WildCards Work
---------------------------------------

The Limited Use Of WildCards In WINROBOT
----------------------------------------

When WINROBOT was designed, it was not meant to replace DOS batch file
processing. It was intended as a simple sequential JOB CONTROL MANAGER
for Windows Apps.

After adding limited DOS Commands, we found that we needed Wild Card
capabilities for the COPY and DEL commands.

Of the many Wildcard conventions that are used in DOS, we support most
including the use of either ASTERISK or QUESTION MARK.

We do not support renaming during the COPY process. There may be also be
some other conventions that we have overlooked. Examples of WINROBOT's
use of Wildcards are shown below.

The Following Formats of the COPY Command can be used in a WINROBOT
script:

Example 1 - Combined Implicit and Explicit Path Components
----------------------------------------------------------

copy c:\dos\*.com *.*
copy c:\dos\f*.exe g:\winapps\WINROBOT\*.*
copy c:\dos\c*.* g:\winapps\WINROBOT

Example 2 - Combined Implicit and Explicit Path Components
----------------------------------------------------------

copy *.exe g:\winapps\*.*
copy *.* g:\winapps\*.*
copy *.* \winapps\*.*
copy *.* \winapps

Chapter 9 - Limitations - What and Why?
---------------------------------------

Like any application, WINROBOT has its limitations. The Reason that
WINROBOT's limitations exist is generally derived from what is necessary
to achieve a reasonable level of support for launching programs from
within Windows. No plans have been made to expand WINROBOT's
functionality beyong these limitations.

WildCards - Only for COPY or DEL WINROBOT does not fully accept
WildCards or implied Path Names. Unless you use the WINROBOT internal
file commands COPY or DEL you must do so EXPLICITLY.

WINDOWS itself does not use or expand WildCards and WINROBOT maps its
file commands to WINDOWS internal commands. The internal commands
provided in WINROBOT are provided as a convenience only and are not
intended to replace those of the operating system.

ABORTED Applications - WINROBOT does not detect an aborted application
i.e. one that has been halted using the [CTRL-ALT-DEL] key combination.

If an unrecoverable error occurrs and the user is forced to manually
terminate the application the user is on their own. WINROBOT has no
knowledge of this intervention and continues to process the task list.

WINROBOT also does not validate .PIF files to determine that the
application named in the .PIF exists.

Chapter 10 - What is WAIT.EXE?
------------------------------

ReadMe File for
WAIT(C) Version 2.0 CopyLeft Bill Buckels 1999
All Rights Reversed.
Distributed As Freeware.

OverView
--------

The windows program WAIT.EXE is a FreeWare Program included for use in
WINROBOT scripts.

This is a dummy program which is can be called by WINROBOT prior to
launching the next application.

It provides a method to allow Windows to regain control of system
resources which may still be in use when the previous application ends.

WAIT.EXE can also be used as a task scheduler.

Description
-----------

Wait... A command line Windows Program that will Wait from 1-60 seconds
or until a scheduled time. Can be called from a WIN95/98 DOS Batchfile
or a WinRobot Script To pause for a specified period of time.

Usage is:

  "Wait"                  - Waits a minute.
  "Wait [1-60 seconds]"   - Waits a number of seconds.
  "Wait Until HH"         - Waits until the hour.
  "Wait Until HH:MM"      - Waits until hour:minute
  "Wait Until HH PM"      - Waits until AM or PM
  "Wait Until HH:MM AM"
  "Wait Before HH"         - Waits Before the hour.
  "Wait Before HH:MM"      - Waits Before hour:minute
  "Wait Before HH PM"      - Waits Before AM or PM
  "Wait Before HH:MM AM"
  "Wait After HH"         - Waits After the hour.
  "Wait After HH:MM"      - Waits After hour:minute
  "Wait After HH PM"      - Waits After AM or PM
  "Wait After HH:MM AM"

Licence Agreement
-----------------

You have a royalty-free right to use, modify, reproduce and distribute
this program and its source code in any way you find useful, provided
that you agree that Bill Buckels has no warranty obligations or
liability resulting from said distribution in any way whatsoever. If you
don't agree, remove this source code from your computer now.

  Bill Buckels
  589 Oxford Street
  Winnipeg, Manitoba, Canada R3M 3J2

  Email: bbuckels@escape.ca
  WebSite: http://www.escape.ca/~bbuckels

End Of Wait ReadMe

End of ReadMe
