========================================================================
AWeb-II_3.1_README            AmiTrix Development           Jan 13, 1998
========================================================================

Thank you for purchasing AWeb-II v3.1, we hope you will enjoy using it.

This file contains some instructions on the installation process and any
last minute information that did not make it into the manual or online
docs.  It will be copied to the AWeb3 Extras drawer for reference.

The Greek catalog is provided and Copyright © 1996 by AC Software, and
should only be used with the Greek Workbench package by AC Software.

The Polish catalog is provided and Copyright © 1997 by Marcin Orlowski
WFMH, and can only be used if you own the WFMH LocalePL v2! package.


Installing the 3.1 version of AWeb-II
=====================================

A couple of notes about our Installer script:

All installations are started from the icons on AWeb3.1_Disk1.

The 'Install-AWeb3' script is used not only to install AWeb-II v3.1, but
also to install utilities, plugins, and datatypes associated directly
with AWeb-II.

The 'Install-HTMLHeaven' script is used to install HTMLHeaven only.

After clicking on the "Install-AWeb3" icon, simply follow the on screen
instructions.  You will be prompted to insert the 2nd and 3rd disks as
required.  We have attempted to keep disk swapping to a minimum.

It is OK to run the install script more than once to install parts of
AWeb-II you did not select on the initial install.  You should not repeat
the installation of any specific part unless you are sure it needs to be
replaced, settings created on the initial install may be changed.

Run the script from its Workbench icon, not from a shell.  Use the
Installer script to install AWeb-II, do not do it manually.  Some
necessary files are not contained in any archive but are built by the
installer script.

If you have version 2.1 of AWeb-II installed, your hotlist, authorizations,
and many of your settings will be used for the new AWeb v3.1 installation.
Your older AWeb-II installation will not be disturbed.  Older versions of
the AWeb-II cache are not compatible with AWeb v3.1.


Note: On some systems the "FixFonts" and/or "AddDataTypes" operations run
====  by the install script may fail.

These utilities are part of the normal Workbench, and should work if they
are in their correct locations.  However, on a few systems there seems to
be interference due to some other installed software.

The FixFonts utility can be run from Workbench by clicking on the icon
which should be found in the System drawer.

The AddDatatypes command can be issued from a shell or should be run
automatically when the system is rebooted.

If the installation hangs or aborts at these points, the Fonts and/or
Datatypes have already been put in place, so you can run the install
again and skip those steps to complete the remaining processes, if
necessary.


Upgrading from AWeb-II v2.x , v3.0 to v3.1
------------------------------------------

If you have an existing copy of AWeb-II installed, the install script will
find it and import many of your custom settings.  The new version will be
installed in a new location (AWeb3) with a new set of configuration
files (ENV:AWeb3 & ENVARC:AWeb3) and assignment.  You will still be able 
to use your existing AWeb 2.1 version if necessary.  Later you may choose 
to delete the old version and only use AWeb-II v3.1.

Once the upgrade installation has finished, start the new version of AWeb 
and entered your registration information.  After the AWeb screen opens, 
do a "save all settings".  This will allow the config program to cleanup 
the newly created prefs files.  Now you should manually check two of your
configuration settings.

1. MENU-Settings/GUI/ARexx

Remove any old ARexx menu settings that conflict with the newer versions.
The newer versions are at the end of the menu item list.  Some examples 
are "HTTX", "AWebNews" and "AWebMail".

2. Menu-Settings/Browser/Viewers

AWeb 3.1 no longer requires "X-" mine types.  Mime types such as "X-WAV" 
are now handled by the standard "WAV" setting.  You should remove any 
"X-" mime types inherited from your AWeb 2.1 installation.

Your new installation is now complete.

You can stop the installation program from finding your previous v2.1
settings by renaming the ENVARC:AWeb drawer.  Unless you have difficulty 
with the installation process you should NOT do this.

If you have updated your akJFIF datatype since installing AWeb-II v2.x, you
should not install the one included with v3.1, yours may be newer.  If not,
you should get the newest version available from Aminet or our web page
next time you are online.

A note on the ClassAct prefs; you can compact the AWeb GUI and gain more
page display window space by changing the Layout spacing in the Misc.
section from the default 4 pixels to 1.  You must do this while AWeb is 
not running to see the results next time the program is started.


Still Missing!
--------------

We regret that the new Widget external plugin for displaying GIF images and
anims is not yet completed, and is therefore not included with the initial
release.  Once it is finished, we will put it up on our AWeb home page for
download by all v3.1 customers.  Sorry!

The main AWeb documentation is only available in english at this time.
Translations for several other languages are in progress. When they
are complete they will be posted on our AWeb web page.


===========================================================================

         Watch our AWeb page for new info & plugin updates!

===========================================================================
