Flying Whatever
                         Version 1.0
                        April 22, 1993


------------
Introduction
------------

The program FlYING.EXE makes a modified copy of the Windows 3.1
screen saver "Flying Windows", aka SSFLYWIN.SCR.  The original
file is not changed.  The program has been tested with the
versions of SSFLYWIN.SCR that come with Windows 3.1 and
Windows for Workgroups 3.1.  Correct operation with other
versions cannot be guarenteed.

When making the new sver you can choose three things:

  The new flying character (chosen from the Wingdings font)

  A new name for the Saver DLL (defaults to SSFLYXXX.SCR)

  A new description for whatever's flying (defaults to XXXXXXX)

For example, you can have the Wingding Bell symbol fly, change
the description to "Bells" (so the setup screen, for example,
refers to "Flying Bells"), and call the new saver SSFLYBEL.SCR.


------------
Installation
------------

You've already unzipped the distribution file (since you're
reading this README.TXT file).  So now the question is, "What
do I do with all these files I found".  Here are the answers:

FLYING.EXE - put it anywhere you like.  Make a Program Manager icon
for it (File|New|Program Item), or run it from ProgMan's File|Run
menu choice.

MSMASKED.VBX and THREED.VBX - These are extensions to Visual Basic
(in which FLYING.EXE is written), and should be placed in your
WINDOWS\SYSTEM directory (if you have one).  Otherwise, put them
in your WINDOWS directory.

VBRUN200.DLL - This file is not in the ZIP file.  You'll need to
get a copy if you don't have one already, and place it in 
WINDOWS\SYSTEM or WINDOWS.  It should be available from wherever
you got your copy of FLYING.ZIP, and may be in a ZIP file named
something like VBRUN200.ZIP.


----------
Conclusion
----------

"Flying Whatever" was written by Karen Kenworthy (karenk on BIX,
karenk@bix.com on the Internet).  It's freeware and can be freely
distributed and used.  The author makes no warranty or other claims.
So, although the program is designed to not modify SSFLYWIN.SCR,
if you're the least bit litigious, back up SSFLYWIN.SCR before 
running FLYING.EXE.  :)