AWeb 3.6 does not use an installer script. Unpack the archive to any drawer you like and run AWeb from that folder.
If the assign AWeb: does not already exist, AWeb will create a
temporary assign pointing at the directory you started it from, and
remove that assign when it exits. That way the program can find its own
Docs, aweblib, and awebplugin drawers next to the executable.
If you have permanently assigned AWeb: elsewhere, AWeb will use that
location instead.
For distribution-specific notes (default CONFIG profile, disk cache location, AmiSSL, and debugging options), see the release ReadMe.html in this archive and System requirements.
Saved preferences from older AWeb releases are not guaranteed to be compatible
with AWeb 3.6. A fresh configuration is recommended. You can keep a separate
prefs profile using the CONFIG ToolType or Shell argument (see
ReadMe.html for the default profile name used with
this build).
AWeb 3.6 is built for the ReAction GUI framework. Legacy ClassAct-only setups from the original AWeb 3.4 installer are no longer the supported path; see ClassAct and ReAction and System requirements for details.
If you use the JFIF datatype (by Christoph Feck, TowerSystems), then please read this:
The JFIF datatype doesn't seem to handle shareable pens on public screens correctly under all circumstances. You must register AWeb in the datatype preferences or AWeb will not be able to show inline JPEG images.
In the JFIF preference editor, you must add an application named
AWebIP (AWeb Image Processing), and then select
Single-Pass Quantization (in the GadTools version of the
preference editor) or One-pass (in the MUI version).
AWeb includes three image format plugins that are shipped with the distribution but must be enabled and configured for their MIME types if you want to use them instead of (or in addition to) DataTypes:
These plugins live in the awebplugins drawer next to the main AWeb
binary (under the same root as this Docs folder once unpacked).
Configure them from AWeb's settings (Viewers page). See each plugin's
documentation for parameters.
Note: These plugins are bundled with AWeb. Patent restrictions on these image formats have long since expired, allowing these plugins to be included in the standard distribution.
To keep the main executable smaller, some less frequently used parts of AWeb are
loaded from separate modules. They are expected in the aweblib
drawer. If you move or delete files out of that drawer the associated
features will stop working.