Best Web Browser

[mechy]

Hey everyone,

I've begun the process of resurrecting my Amiga 500, and was wondering if there were any decent web browsers for the Amiga?  I've heard of one, but I think it can only render in 16 colors.  You I stick to browsing on my windows based system.  Additionally, can a 25/50mhz Amiga handle a DSL connection?

-Miked

Not sure if these run on 68000 but they might be of interest to all amigas, its from Biggun,his aweb Max version of aweb:

http://www.greyhound-data.com/gunnar/aweb/

[Starglider]

http://amigan.1emu.net/releases/AWeb-m68000-05.07.2011.lha

Thanks but are you sure this 8MB file is for Amiga 500+?

[Starglider]

What do you mean no installable files? You just unpack the archive and run AWEB icon. That's it

What happens when you do it? Do you get any errors?
Do you have ClassAct in your system?
http://aminet.net/package/dev/gui/ClassAct2Demo

There were no icons that were executable. If you look inside the lha (http://aminet.net/package/comm/www/AWeb-3.5.09-68000#contents) there aren't any .info files/

I installed ClassAct, but that made no difference to that.

[Minuous]

Thanks but are you sure this 8MB file is for Amiga 500+?

Yes, that includes various catalogs, etc.; not all parts are loaded into memory simultaneously.

there aren't any .info files

I can email you a suitable icon if you like. In the meantime it can be run directly from CLI.

[Sir_Lucas]

There were no icons that were executable. If you look inside the lha (http://aminet.net/package/comm/www/AWeb-3.5.09-68000#contents) there aren't any .info files/

I installed ClassAct, but that made no difference to that.

Check this video
It shows AWEB 68000 downloaded from Aminet and working.

Downloaded with IBrowse 2.4 - A1200 030 + Roadshow + WIFI CARD. AmigaOS 3.1 + ClassAct.

[sim085]

Do not want to hijack the thread but does 68000 mean it runs on 68000? I downloaded AWeb provided here and tried it on WinUAE. When I set the CPU to 68000 I get an error (AWeb, Program failed (error #80000003), Wait for disk activity to finish).

When I try it with CPU 68020 it works. So is this usable on a real A500?

[Ross_Geller]

I've got AWeb running.

After installing Classact, I did this:

1. Download the 68020 version: http://aminet.net/package/comm/www/aweb3.5.09_68k_20070721
2. Download the 68000 version: http://aminet.net/package/comm/www/AWeb-3.5.09-68000
3. Unpack the two versions, and copy the 68000 files over the 68020 versions.
4. Don't run the installer, it complains that it wants at least a 68020 to run.  Instead, just click on the AWeb icon and it runs (for me at least!).

At the moment all I can do is look at the AWeb docs, but it's a start!

[Starglider]

I found an AWeb demo that has all the icons for launching. Thanks for the guidance.

[sim085]

Thanks, I'll try those steps out.

I've got AWeb running.

[sim085]

Still does not work for me

I am trying on Workbench 3.1 (With BetterWB)
The ROM is 3.1
CPU is set to 68000 (Fastest Possible)
Chipset is Full ECS
RAM 2MB Chip and 8MB Z2 Fast

The WinUAE version I am using is 3.1.0

I get the same error as before. However if I use 68020 CPU it works.

Thanks, I'll try those steps out.

[Ross_Geller]

Still does not work for me

I am trying on Workbench 3.1 (With BetterWB)
The ROM is 3.1
CPU is set to 68000 (Fastest Possible)
Chipset is Full ECS
RAM 2MB Chip and 8MB Z2 Fast

The WinUAE version I am using is 3.1.0

I get the same error as before. However if I use 68020 CPU it works.

I was going to post a long instruction guide for setting up AWeb on a fresh install of 3.1 with your WinUAE setting.  

But, I then then installed BetterWB and got the AWeb crashes you got.  Sometimes AWeb would run for ages, sometimes it would crash when I was changing website.  The crash would usually turn the screen to garbage, and then it'd Guru with 80000003, 80000000, and even one 8000000F.

I don't know what the conflict is, but I hope someone can suggest a fix, because BetterWB looks interesting.

And give Aweb on a fresh, stock 3.1 install another chance.

P.S.  Why on why do we have to get the Installer command from the root of the Install disk, rather than it being automatically copied into the C directory?  Such a weird choice...