═══ 1. ScreenSaver Installation Program ═══

Use the Source directory entry field to set the directory from which 
ScreenSaver is to be installed. Default is the current directory and there 
should be no need to change this. 

Use the Destination directory entry field to set the directory into which 
ScreenSaver is to be installed. Default is the current directory (except when 
this is on a diskette). You can change this to any drive and directory you 
want. 

Use the Destination directory for DLLs entry field to set the directory into 
which the EMX runtime DLLs (i.e. the files which contain the runtime library 
for the EMX/GCC compiler, with which ScreenSaver was compiled) are to be 
installed. These DLLs are required by many OS/2 programs and therefore should 
be installed to a directory in your LIBPATH where they are found by these 
programs. Default is the \OS2\DLL directory on your boot drive. Change this to 
any directory you want, but make sure this directory can be found in the 
LIBPATH statement in your CONFIG.SYS file. 
It is possible that there is more than one set of these DLLs installed on your 
computer. Only one set of the DLLs is required system wide. You can delete all 
but the newest set. 

Attention! If there are any programs running that use existing EMX DLLs on your 
hard disk, you have to stop them or installation will fail. Alternatively 
choose another DLL destination directory. 
If you have an older version of ScreenSaver running, shut it down before trying 
to install. It may even be necessary to reboot your computer, because OS/2 may 
have locked the ScreenSaver file SSDLL.DLL (this can happen even if ScreenSaver 
has been stopped). 

If the Create WPS object box is checked, a program object is created. If the 
Create in startup folder box is checked, too, this object is created in the 
OS/2 System Startup folder, so ScreenSaver will be started automatically at 
system startup. 

Use the Install Win-OS/2 fullscreen support check box to choose if you want 
ScreenSaver to be activated from Win-OS/2 fullscreen sessions. If you choose to 
install this option, a Windows screen saver is installed in your Win-OS/2 
directory. Use the Win-OS/2 "Control Panel" to set its timeout. Please set the 
directory where Win-OS/2 is installed in the Win-OS/2 directory entry field. 

Use the Install DOS fullscreen support check box to choose if you want 
ScreenSaver to be activated from DOS fullscreen sessions. If you choose to 
install this option, a DOS screen saver is installed in your OS/2 DOS directory 
(\OS2\MDOS). It is invoked from the AUTOEXEC.BAT file of your OS/2 boot drive. 
Set the timeout parameter in the AUTOEXEC.BAT file; for example "SSDKICK 10" 
sets the timeout for DOS fullscreen sessions to 10 minutes. The default timeout 
is 5 minutes. To disable the DOS saver, set timeout to 0. 


═══ 2. ScreenSaver Installation Notes ═══

IMPORTANT INFORMATION. PLEASE READ! 

     If DPMS switching hangs your computer, try changing the BIOS power 
      management settings; see ScreenSaver online help topic "Green monitor 
      support". 

     ScreenSaver is Shareware. Some functions are available only to registered 
      users. See online help or the file REGISTER.DOC for how to register. 

     ScreenSaver provides password protection. For the pre-set password, see 
      online help. Please note that this password is case sensitive! If you 
      have the impression that the system is not unlocked although you typed in 
      the correct password, please check if Caps Lock is active. 

     There is support for DPMS ("Green") monitors now. See online help. 

     If you use OS/2 2.x, make sure there is a dot (".") in the LIBPATH 
      statement in your CONFIG.SYS file (this is default in Warp). 

     There exists a little utility called SSKICK which starts a module when 
      executed. You can add this utility to the Desktop menu (see online help). 

     For available command line switches, see online help. 

     In this distribution, I have included foreign modules. For copyright 
      information see the README file. 

     A few users have reported problems with some Deskpic modules. If a 
      Deskpic module crashes on your system, delete the corresponding *.DSS 
      file. 

     Please read the online help topic on "low priority" if saver animation is 
      not smooth enough.