LAP - AWeb

The final package I am going to install in the main build is a web browser for the Amiga. For the avoidance of doubt in the heads of imbeciles, there is no point in doing this if you did not or could not install the network drivers for your system.

Much like e-uae itself, the AWeb browser needs a toolkit to display stuff like buttons, menus and so on. Actually the toolkits we are going to install are used by a number of other applications, so they are useful in and of themselves. One thing which uses them is a replacement icon set, so we will install that as well just now. In addition, the makers of the web browser AWeb no longer supply copies of their software, so I had to resort to archive.org. Seems to work fine though.

umount -v /media/amiga
sudo mkdir /media/lfs 
sudo mount -v -t ext3 /dev/disk/by-label/amiga /media/lfs 
cd /media/lfs/sources/amiga

wget http://aminet.net/util/libs/mui38usr.lha
wget http://aminet.net/dev/gui/ClassAct2Demo.lha
wget http://aminet.net/util/wb/NewIcons46.lha
wget http://web.archive.org/web/20070102173257/http://aweb.sunsite.dk/files/full/AWeb_APL34_full_020.lha

Again, when you have booted to the Amiga you then want to move, or copy, the files from /sources/amiga to ~/amiga/shared/ so that the files are available to the emulated Amiga. Then boot your A1200HD machine.

The first bit of the toolkit we install is Mui, which sounds halfway been a pretentious Moi and a Hawaiian island. In actual fact it sounds like it is GTK for Workbench.

lha x Shared:mui38usr.lha ram:

Open this up in the same way as Picasso. In other words you double click on the ramdisk, then double click on the MUI directory, and finally double click on the icon called "Install-MUI". When asked to select a place to install MUI, click on show drives and select dh0: Installing to the root of dh0: is fine. You should choose to install all image sets. The example programs are not required.
Once it is installed, reboot the Amiga, and navigate to the system->mui folder and run the Mui program located there. When the program opens, hold down the right mouse button and go to the menu at the top of the screen – not the Mui program, but the very top of the desktop. There, select project, choose open, and select Stuntzi.prefs. Save your selection.

ClassAct is another toolkitty type thing which works alongside MUI. It may even be a rival to MUI in some areas of operation.

lha x Shared:classact2demo.lha ram:

Double click on the ram disk and then on "ClassAct" and then on "Install_Classes". The classes should be installed to the default location, which should be SYS:Classes. All other options are OK by default as well, so just 'Yes' and 'Proceed' your way through the install. If you select Novice instead of Intermediate user it will just fire straight through without asking you anything.

The two toolkits are actually the dependencies for a new icon set, so since we have installed the toolkit packages, we may as well now install a new icon set. We want to do this because the Workbench icons are designed to be viewed on an interlaced display. The result is that when you view them through the uaegfx: card they lose half their height and look a bit stupid.

lha x Shared:newicons46.lha ram: 

You then, again, double click on the ram disk, and then double click on "NewIconsV4". Then double click on "Install" and finally on "Install_NewIcons". We are not given the chance to install these as a novice, so go for intermediate. Select all check boxes that appear. You should get the opportunity to install a high end library. Take it.
The first install location should be System:Utilities. You should then be given the chance to update a disk or partition image. It should auto choose dh0:, but if not click on show drives and select dh0: and then proceed. Do the same for dh1:. I think this affects the drawer images IN that device as opposed to its icon on the desktop. I mostly think this because the next thing the install does is offer you the chance to change the desktop icons. Do this in the same way. It offers you different icons this time.
The next install options should be SYS:Storage - Proceed, then Help: - Proceed. When it gets to "include:" you need to step in. Change the install path to System:Utilities, by clicking on dh0:System, then scrolling down the list and choosing Utilities. The "Selected Drawer" box should now show "System:Utilities", and if it does click on Proceed. Next it should ask about the example source code and suggest installing it to Work:. You have not defined work: so choose to install it to System:Storage as a fallback, and then do exactly the same for the Autodoc material.
Then, after a reboot, go to System->Prefs->newiconsprefs, and check the boxes next to RTG Mode, no borders, and transparent.

Finally we come to Aweb which is a web browser for Amiga OS. It is, when compared with today's browsers, basic.

lha x Shared:AWeb_APL34_full_020.lha ram:

Start the install in exactly the same way as before. When you start the install it will suggest installing to the ram disk. This is a stupid idea. Instead, install to System:. When asked, you can confirm that you have more than 2Mb of ram. About 254Mb more in fact.
You then get a message telling you that plugins should be installed to AWeb_APL:, and not AWeb3:. Hmm, OK.
So, plugins then. From the open AWeb_APL_020 folder, double click on plugins. From there you should see three folders, which correspond to the jpeg, gif and png plugins. The procedure is really the same for each one. Avoid using the built in scripts. They are a pain in the arse, and only half work. Do it manually instead. Drop to a Shell and run:

copy ram:AWeb_APL_020/Plugins/awebjfif68020/awebjfif.awebplugin AWeb_APL:Storage
copy ram:AWeb_APL_020/Plugins/awebgif/awebgif.awebplugin AWeb_APL:Storage
copy ram:AWeb_APL_020/Plugins/awebpng/awebpng.awebplugin AWeb_APL:Storage

You should then double click the AWeb icon in the AWeb_APL folder. When the program loads, hold down the right mouse button to bring up the menu, and then go to Settings, and then Browser Settings. From the window that comes up (called AWeb browser settings) click on the IMAGE/GIF line under the 'Type' column. The click on the box at the bottom called 'Action', which brings up a drop down menu from which you choose "AWeb Plugin". Then click the icon next to the "Name" box (just under the arrows next to the box now showing "AWeb Plugin"). From the dialogue box that pops up select storage, select awebgif.awebplugin and hit OK. Now do the same for JPEG and PNG (which are just under GIF). Hey presto, your AWeb browser can now display images!