Aros m68k (Kickstart substitute)

[mfilos]

Outstanding news Toni! Thanks for the update

[onkelarie]

This is quite frankly amazing....

[cosmicfrog]

\o/

[Mequa]

Holy Moly! AROS can run AMOS!

It's not usable yet (keyboard and mouse input don't appear to be functional), but it WILL launch AMOSPro now (provided RTG isn't being used) and WILL launch the editor, default screen, splash dialog box (which will disappear in time) and play sounds, with flashing cursors operational!
I enclose a screenshot using WinUAE 2.3.2's internal AROS ROM with AROS fonts, and for comparison AMOSPro running under Kickstart 3.1.

This only appears to work for AMOS Professional now (tested version 2 with compiler), not AMOS 1.3 or Easy AMOS.

Also, AMOSPro will run in Run Only mode now (e.g. go to AMOSPro_System: and do AMOSPro "MyProgram.AMOS"). As for the editor, keyboard/mouse input doesn't seem to be working yet, but demos which require no input WILL work! Similarly, you can use the AMOSPro Compiler (with real Kickstart for now) to create an Amiga executable. and the compiled program (depending on which extensions are used) will run under AROS 68k, albeit with the same limitations for now as interpreted programs.

Another point: Many games and apps created in Blitz Basic 2 (including some of my own) appear to work now under AROS, without the current issues with AMOS games. (Disabling RTG helps.)

I'm just thinking how making AMOS and Blitz games runnable without a copyrighted Kickstart ROM will make it so much easier to legally distribute homebrew Amiga games to run on other platforms.

AROS 68k is a great project!


UPDATE:
Joystick input DOES work in AMOS under AROS 68k - check out my attached AMOS game "Eater" as a zipped ADF file. Try booting the ADF in the latest WinUAE without an external ROM file. Or load Wanderer (or Workbook), insert the floppy and click on the executable icon. It even launches when using RTG (unlike the AMOSPro editor).

In contrast, support for Blitz Basic 2 apps/games seems to be more complete (keyboard and mouse input do work), but it doesn't seem to play well with RTG at present.

Apart from keyboard and mouse input (and 3D extension which seems to give an error, or synthesised speech using the narrator.device and translator.library), AMOS support seems to be almost there!

[NovaCoder]

Wonder if AROS 68k will become the future FPGA Amiga's OS of choice (eg no legal crap to worry about).

If this could replace the 'official' 3.1 ROM one day, would it be possible to boot to 3.9 from it?

[Toni Wilen]

Originally Posted by Mequa

It's not usable yet (keyboard and mouse input don't appear to be functional)

Attach some test cases, thanks (Note that I don't want to know anything about how to use AMOS = step by step example required)

[Mequa]

Quite possibly. I'd also like to see it working on UAE for Android, PSP and other mobile platforms (even if it is slower). Maybe even for Fellow/WinFellow, although that may require implementing support for a 1MB extended Kickstart.

A ROMable version is an excellent idea, but would it also be possible to make a non-ROM version of AROS 68k bootable with a standard AmigaOS ROM, so e.g. Wanderer and AROS apps can run on a real Amiga without tampering with the Kickstart ROM chips?

[Toni Wilen]

A ROMable version is an excellent idea, but would it also be possible to make a non-ROM version of AROS 68k bootable with a standard AmigaOS ROM, so e.g. Wanderer and AROS apps can run on a real Amiga without tampering with the Kickstart ROM chips?

Implemented long time ago, see previous posts.

Download amiga-m68k-boot binary package, included disk image contains loader (arosbootstrap) and special relocatable rom image that works on any Amiga with at least 2M of chip RAM or at least 1M of local (mainboard) fast RAM.

[Mequa]

Toni, here's the latest version of AMOS Professional (2.0) as a single zipped bootable ADF. I also attach the WinUAE log files on running it with AROS-68k.

Downloaded and updated from: http://www.back2roots.org/Tools/Dev/

With WinUAE 2.3.2 built-in ROM it loads the editor, only the keyboard and mouse don't seem to respond. Joystick does work, however (see my last post and attached ADF). The editor's initial dialogue box will clear after leaving it for a minute or so, giving a flashing editor cursor.

[Mequa]

YouTube video: [ Show youtube player ]

This is really impressive work.

[Toni Wilen]

Originally Posted by Mequa

keyboard and mouse input don't appear to be functional

Fixed (in AROS svn). Input.device refused to open if message size was too small.
AOS does not care -> many AOS programs won't set it properly either.

Not the first "fix" that means disabling sanity checks...

[Bamiga2002]

Awesome! <holds breath>

[Mequa]

I don't yet have access to the AROS svn, could I please have a link/download to the latest ROMs to make a video of the AMOSPro editor working in AROS-68k?

BTW, I sent François Lionet a link to this thread, I'm sure it will be followed with interest.


P.S.

Toni, would you mind testing the AMOSPro ADF when running Wanderer and launching from the AMOSPro icon? I'm not sure if there are still issues here when using RTG or with RTG enabled (both when launching and quitting).
Also, the floppy icon may not be visible in Wanderer on that ADF (it works from hard drive with icon left out, as demonstrated in the video).

[Toni Wilen]

http://aros.sourceforge.net/download.php amiga-m68k-boot (updated daily)

[Mequa]

Following rapidly in your footsteps Toni, and probably the first of many. Here is a proof of concept:

AMOS for Windows (Zip archive)
[ Show youtube player ]

This is a Win32 install program (12.5MB) for a complete out-of-the box AMOS Professional install, fully scanned for viruses with the latest Avast, which includes WinUAE 2.3.2 and AROS-68k 20110713 ROMs. Most of it is already working, including the AMOSPro compiler and 'CRAFT' extension.
(Other versions of AMOS are included too, but won't yet run.)

The launcher also works with a WinUAE install in Program Files [or "(x86)"], just delete its internal WinUAE folder, and it works with several versions of WinUAE. It also works without the 2 AROS ROMs (20110713), but as of WinUAE 2.3.2 these are still required to get input in AMOS without an official Kickstart ROM.

I'd like to keep this as legit as possible, so let me know if you are happy with it. I know Francois Lionet made AMOS BSD-licensed a while back, so this entire package should be legally redistributable now.

So long as everything is fine, if anyone would like to host this, I'd be happy too.
Edit: much thanks to Vairn for hosting it.

Mequa

[Vairn]

Hey guys, I have a mirror of Mequa's file, so you don't have to go through a file sharing site.


http://mequa.dragotech.net/AMOS%20for%20Windows.exe
http://mequa.dragotech.net/AMOS%20for%20Windows.zip


Laters, Vairn.

[Vairn]

Your config file is pointing in the wrong place for the HDD
it is using full paths, not a relative one.

So you might want to install it to, c:\program files x86\amos for windows etc

[Mequa]

The script I used manually overrides the WinUAE configuration paths using WinUAE command line options in a .bat file (which I converted to .exe as the launcher).
I installed it to My Documents, installing to Program Files would require administrator access when running to change the AMOS config files, etc.
(Merge post) Apologies for thread hijack: I removed all absolute paths, this build seems to work correctly now using its launcher (.bat or .exe) in mounting the HDD directory from anywhere.
This installer seems to work on Wine / Linux too (subject to the usual Wine/WinUAE "F12" bugs).

P.S. Excellent work Toni!

[Vairn]

yeah, everything else was correct, just not the HDD directory, all roms etc were correct

[Vairn]

done, link updated for you.