AWeb Logo

AWeb 3.6   Beta 8

The Amiga Web Browser

A web, suddenly
Forty years meditation
Minds awaken, free

This is AWeb 3.6, a new version of the classic Amiga web browser, developed by amigazen project. This release is AWeb 3.6 Beta 8, a preview build intended for testing and feedback. Following from the previous AWeb 3.6 Alpha 7 snapshot, Beta 8 adds major improvements to networking (especially HTTPS keep-alive), disk caching, memory management, font rendering (AWeb can now use TTEngine) and CSS support. The full source code of this release is available at https://github.com/amigazen/aweb3/

amigazen project uses modern software development tools and methods to update and rerelease classic Amiga open source software. This new version 3.6 updates AWeb to build against NDK3.2, replacing ClassAct with ReAction, updating networking code for RoadShow and AmiSSL, and ensuring it builds against the amigazen project ToolKit standard for Amiga SDK configuration.

Read this first

New features in AWeb 3.6 include:

What's New in AWeb 3.6 Beta 8?

This first beta release of AWeb 3.6 marks the transition from work in progress alpha releases, to a functionally complete and relatively stable release ready for wider distribution and testing. At this point no major new features will be added for AWeb 3.6, and the focus will be on bug fixes, optimisations and compatibility with Amiga-centric web sites.

AWeb 3.6 beta 8 brings many new features and refactored core components including:

Running AWeb

AWeb no longer requires an installer script. It can run from anywhere. Just run it from the folder it's in. Do note however that if the assign "AWeb:" does not already exist it will temporarily assign it to its current directory until it exits. On the other hand if you have assigned AWeb: to a different location then it won't find its plugins.

Saved AWeb prefs configs from earlier releases are not guaranteed to be compatible to AWeb 3.6, as AWeb 3.4 had several major defects in its prefs management and AWeb 3.5 changed the prefs file format. It is recommended to start with a fresh config for AWeb 3.6. You can use the CONFIG argument/ToolType if you wish to keep your AWeb 3.6 config separate from your earlier releases. In any case, AWeb 3.6 is much smarter about choosing default settings and for most users the defaults will be appropriate.

This beta build supports a DEBUG/S command line option which will output a LOT of debugging output to the console. If you use this, redirect the output to a file on a safe disk like the RAM: disk or, if running under emulation, a mounted host folder, just in case it causes filesystem corruption.

The requirements for AWeb 3.6 remain the same as the original 3.4 release, however most websites, even those that only use HTML 3 and 4 features, require significant amounts of RAM - 8MB Fast RAM is probably a sensible minimum. Some of the new default settings assume a more powerful Amiga than would have been common in the 1990s. It will of course fail to correctly load most modern websites requiring HTML5, CSS3, video content, heavy JavaScript, etc.

What's New in 3.6 Alpha 7?

What's New in 3.6 Alpha 6?

What's New in 3.6 Alpha 5?

What's New in 3.6 Alpha 4?

What's New in 3.6 Alpha 3?

What's New in 3.6 Alpha 2?

Known Issues in 3.6 Beta 8

Contact