Aros m68k (Kickstart substitute)

[Mequa]

Toni, thanks a lot for your hard work in getting AMOSPro to run under AROS-68k.

In case you are interested, I attach a zipped ADF of Blitz Basic 2 V1.8 from Back To The Roots. I also attach the log files on attempting to run it on AROS-68k (tested on AROS-20110714). It currently reboots shortly after launching.

To launch on AROS-68k/Workbook (tested on AROS-20110714, RTG disabled) on booting the ADF into Workbook, open the AROS-Shell from the pull-down menu and type "Blitz2", and press enter. It will attempt to launch the Blitz2 text editor, "Ted". (I have also noticed that the mouse pointer may also be invisible if it doesn't crash immediately.)

[Toni Wilen]

Originally Posted by Mequa

I was wondering if there are plans to include a replacement "Workbench disk" ADF which will boot into Workbook (not enough space for Wanderer on a floppy), but built from free/AROS-68k code, and perhaps including a few very lightweight applications?

Usual answer: too early. Anything can change, startup-sequence probably breaks every few weeks, size of programs can become too big etc..

P.S. Does there exist an open-source build of the "C:LoadWB" executable to launch Workbook under AROS-68k? (Of course this can be copied from an original Workbench disk, but an open-source build for AROS-68k Workbook might be a good idea too).

Very minimal C:LoadWB implemented today.

int main(void)
{
    struct WorkbenchBase *WorkbenchBase = TaggedOpenLibrary(TAGGEDOPEN_WORKBENCH);
    if (WorkbenchBase) {
    	StartWorkbench(0, NULL);
    	CloseLibrary((struct Library*)WorkbenchBase);
    }
    return 0;
}

EDIT: Always use -seriallog command line parameter when including winuaelog.txt using AROS ROMs. (Built-in enables it automatically, extrernal ROM images won't)

[Mequa]

If anyone is interested, I have made a Win32 installer for easy install of the latest nightly build of AROS-68k (2011-07-31) with WinUAE (2.3.2):

Amiga AROS-68k Emulation Pack.exe (Installer):
http://www.megaupload.com/?d=W8I51DJT

Amiga AROS-68k Emulation Pack.exe (ZIP Archive):
http://www.megaupload.com/?d=0U0MYGHF


I also added a Workbook launcher to the install folder ("Amiga AROS - Workbook.exe"), which will launch Workbook instead of Wanderer with Toni's new C:LoadWB replacement.

[Toni Wilen]

Originally Posted by Toni Wilen

Arghh.. AMOS calls dos.library/LoadSeg() with A6 pointing to ExecBase.. Some stupid workaround needed..

Stupid workaround now done

[Mequa]

Excellent work - I'll test my unpatched AMOS-3D game ADF with the latest nightly.

Question: Are there plans to eventually support booting into AmigaOS 3.5 and 3.9 using the AROS-68k ROM, or is this not a priority at this stage?

[GBAura]

Originally Posted by TheCyberDruid

Changed for now until someone comes up with a better one

Does 'Legal KickStart ROM' make more sense?

[NovaCoder]

Yep I like it, 'Legal KickStart ROM (AROS)'

[Mequa]

You forgot "FREE". Amiga Forever is legal too but not too cheap.

How about "Free and legal Kickstart ROM replacement (AROS-68k)"?

[mihcael]

Originally Posted by Mequa

You forgot "FREE". Amiga Forever is legal too but not too cheap.

How about "Free and legal Kickstart ROM replacement (AROS-68k)"?

Almost back to what it was originally!

[Ezrec]

Originally Posted by Mequa

Excellent work - I'll test my unpatched AMOS-3D game ADF with the latest nightly.

Question: Are there plans to eventually support booting into AmigaOS 3.5 and 3.9 using the AROS-68k ROM, or is this not a priority at this stage?

Somebody send me AmigaOS 3.5 and 3.9 CDs, and I'll work on the compatibility.

- Jason McMullan, AROS m68k developer

[Toni Wilen]

One big reason for AOS crashes: Make sure RTG is not installed (Currently most compatible solution is to remove all monitor drivers in devs:monitors). Any attempt to load AOS RTG causes immediate crash.

[synchro]

Originally Posted by Zetr0

actually guys I dont think that a FreeKick solution wouldn't damage Amiga-Forever at all

I suspect that they can be empowered (as much as the rest of the community) by it.

Amiga Forever is a very good legal product that contains a lot of great games and apps - even a workbench that, although can be improved - does provide a great basis for it.

Agreed....I have created quite a few projects in my time for myself and others that enable me to run any amiga stuff i want ...BUT !!

Even i own a Legal Amiga Forever and a C64 Forever and i would Highly recommend everyone here buying one....IMO a genuine Amiga,C64 etc collector/fan should be willing to pay out as well as collecting stuff for free. Its all Amiga support at the end of the day

[Ezrec]

Originally Posted by Ezrec

Somebody send me AmigaOS 3.5 and 3.9 CDs, and I'll work on the compatibility.

I was surprised.

As of today, AmigaOS 3.9 mostly works out-of-the-box so long as you remove/rename SYS:Libs/workbench.library - there seems to be some incompatibility with AROS's build-in icon.library.

Some math libraries were missing from the AROS ROM, they should be in tomorrow's build (fixes the 'missing resource.library' popup)

[NovaCoder]

Originally Posted by Ezrec

I was surprised.

As of today, AmigaOS 3.9 mostly works out-of-the-box so long as you remove/rename SYS:Libs/workbench.library - there seems to be some incompatibility with AROS's build-in icon.library.

Cool, that's really great news. Sounds like we are not too far from soft kicking a 'free and legal' AROS ROM using our ACA's

[Toni Wilen]

I am totally stuck with real hardware issues that can't happen in emulation. Namely 68060 copyback cache. If it is enabled, Blizzard SCSI hangs during booting, time to hang is random.

MMU tables that set caching modes are correct (same as 68060.library sets). Even 68060 rev5 and older official errata workaround is enabled.

Also 68060 cyberstorm PPC and fastata is reported to have same kinds of hanging issues. It must be AROS bug somewhere. I hope.. (in worst case it is driver bug that is masked by some unknown AOS "feature"..)

Argh.

Other problem is Picasso96 driver compatiblity issues. I really need more RTG cards and an A4000, thanks (or A3000 compatible 68040+ accelerator board). 68030 A3000 + PicassoII is probably too slow and has too small caches..

Other changes:

Lots of other compatibility bugs has been found and fixed.

icon.library problem is fixed but OS3.9 can still crash during booting because of bug in OS 3.9 workbench.library!: Its Open/Close routines are not semaphore protected and can run at the same time = bad things happen.. (Another reason is probably kernel scheduling difference or something else but it still is a AOS workbench.library or c:loadwb bug)

Full shell startup packet support will be coming soon. This should finally fix last remaining WB1.x boot problems. Jason has been examining this very undocumented BCPL "feature". (Ok, whole BCPL Tripos is a so called "feature")

[matthey]

Originally Posted by Toni Wilen

I am totally stuck with real hardware issues that can't happen in emulation. Namely 68060 copyback cache. If it is enabled, Blizzard SCSI hangs during booting, time to hang is random.

MMU tables that set caching modes are correct (same as 68060.library sets). Even 68060 rev5 and older official errata workaround is enabled.

Thomas Richter (ThoR) knows the 68k MMU and caching like the back of his hand and he is still active. You could either post on http://www.Natami.net which he frequents or send him an e-mail (same as always). I bet he can find the problem if you can post links to the source files that are most likely to contain the problems (MMU and cache setup and handling).

Originally Posted by Toni Wilen

Other changes:

Lots of other compatibility bugs has been found and fixed.

icon.library problem is fixed but OS3.9 can still crash during booting because of bug in OS 3.9 workbench.library!: Its Open/Close routines are not semaphore protected and can run at the same time = bad things happen.. (Another reason is probably kernel scheduling difference or something else but it still is a AOS workbench.library or c:loadwb bug)

Does that include the latest workbench.library 45.131 (04/15/06)?

[Toni Wilen]

Originally Posted by matthey

Thomas Richter (ThoR) knows the 68k MMU and caching like the back of his hand and he is still active. You could either post on http://www.Natami.net which he frequents or send him an e-mail (same as always). I bet he can find the problem if you can post links to the source files that are most likely to contain the problems (MMU and cache setup and handling).

I have already contacted him about other MMU issues. But it is not MMU problem, it is "bug somewhere" that is very very difficult to find..

Crash or illegal access (MMU bus error) would be easy to debug. Hang isn't, especially when other tasks keep running normally (floppy keeps clicking etc..)

Does that include the latest workbench.library 45.131 (04/15/06)?

I have only confirmed with version 45.127 (2001-02-21)

Originally Posted by Toni Wilen

Other problem is Picasso96 driver compatiblity issues. I really need more RTG cards and an A4000, thanks (or A3000 compatible 68040+ accelerator board). 68030 A3000 + PicassoII is probably too slow and has too small caches..

Have a3000 w/ a3640(v3.1) + GVP Spectrum Video. What can I do to help?

[Toni Wilen]

Originally Posted by Rodomoc

Have a3000 w/ a3640(v3.1) + GVP Spectrum Video. What can I do to help?

Copy Spectrum.card and CirrusGD542X.chip from your Picasso96 installation to same directory as arosbootstrap and aros.elf.gz.
Boot to aros using arosbootstrap:

arosbootstrap aros.elf.gz spectrum.card cirrusgd542x.chip

(Use romsplit to extract A3000 scsi.device and include it in arosbootstrap command line if you want to boot from A3000 scsi controller, aros does not have built-in support)

Keep both mouse buttons pressed, wait for boot menu which should open on your RTG monitor, 640x480x8 resolution.

If not, include serial log (null modem cable + USB adapter is usually the easiest solution, 115200 8N1)

WARNING: current aros builds may be quite unstable again, there has been major internal change recently. It is always good idea to first test if boot menu or "no bootable media" image appears without any extra modules.

[Narf the Mouse]

I have a name idea - AROS AMOK.

...Although, considering programming, that may be too accurate...