AROS installation under 68060

[DiskDoctor]

Hi guys!  It's been a while since I wrote a message here.

Now I own real Amiga 1200 with WARP 1260 card.  I created 4 partitions on my microSD card: Amiga OS 3.2.1 + AmigaOS 3.9 + AmiKit (68k) + AROS (68k).

I downloaded AROS Vision distribution, a zip (7z) file containing folders.  I unzipped it on Amiga and copied all files to AROS partition.  I also installed MMULibs and WARP-related files.

When I run AROS partition, what I get is

"boot/amiga/AROSbootstrap - file is not executable".

I checked the flags of the said file and it has Exe checked.

I also use MapRom feature of my WARP card -- typically it points out at Kickstart 3.2.1.

I would be really grateful if someone helped me finalise the AROS install so that I could use it too!

[AMIGASYSTEM]

Hello DiskDoctor and welcome to this forum !

Regarding AROS 68k, the message you received is because you did not bootloader compatible with native AROS executables, let me explain:

AROS 68k can run OS 3.1 native software (no OS 3.9), but on the contrary OS3 cannot run AROS 68k native software.

There are two solutions to solve this problem, boot Amiga with native AROS 68k Roms, or remap Aros Roms through startup-sequence.

I also add that AROS 68k needs a very powerful Amiga, with 060 you will get too slow system, the best solution to boot AROS 68k is WinUAE, the only "Amiga" capable of running AROS 68k fast.

[OlafS3]

Hi guys!  It's been a while since I wrote a message here.

Now I own real Amiga 1200 with WARP 1260 card.  I created 4 partitions on my microSD card: Amiga OS 3.2.1 + AmigaOS 3.9 + AmiKit (68k) + AROS (68k).

I downloaded AROS Vision distribution, a zip (7z) file containing folders.  I unzipped it on Amiga and copied all files to AROS partition.  I also installed MMULibs and WARP-related files.

When I run AROS partition, what I get is

"boot/amiga/AROSbootstrap - file is not executable".

I checked the flags of the said file and it has Exe checked.

I also use MapRom feature of my WARP card -- typically it points out at Kickstart 3.2.1.

I would be really grateful if someone helped me finalise the AROS install so that I could use it too!

Welcome

As Amigasystem explained Aros 68k needs Aros Roms. There was a mechanism that made it possible to boot at least A1200 and A4000 with Aros 68k installing aros roms in fast ram during startup from harddisc but that mechanism was broken years ago and never fixed. So you need Aros roms preinstalled now.

[DiskDoctor]

Hi guys!  It's been a while since I wrote a message here.

Now I own real Amiga 1200 with WARP 1260 card.  I created 4 partitions on my microSD card: Amiga OS 3.2.1 + AmigaOS 3.9 + AmiKit (68k) + AROS (68k).

I downloaded AROS Vision distribution, a zip (7z) file containing folders.  I unzipped it on Amiga and copied all files to AROS partition.  I also installed MMULibs and WARP-related files.

When I run AROS partition, what I get is

"boot/amiga/AROSbootstrap - file is not executable".

I checked the flags of the said file and it has Exe checked.

I also use MapRom feature of my WARP card -- typically it points out at Kickstart 3.2.1.

I would be really grateful if someone helped me finalise the AROS install so that I could use it too!

Welcome

As Amigasystem explained Aros 68k needs Aros Roms. There was a mechanism that made it possible to boot at least A1200 and A4000 with Aros 68k installing aros roms in fast ram during startup from harddisc but that mechanism was broken years ago and never fixed. So you need Aros roms preinstalled now.

Hi.

You mean I ought to add the AROS ROM to MapRom?

So it is impossible currently to reload ROM in S-S?

[AMIGASYSTEM]

Yes you could try remapping the ROMs, beware on AROS there are two ROMs (see attached video), have you ever used AROS on WinUAE? I created a small comprehensive video on how to boot my AROS One 68k Distribution (currently not distributed) on WiunUAE, in the video you can see the requirements.

Probably in your case you will need to merge the two Roms so that you have only one 1MB KickStart (I can do it for you if needed)

https://youtu.be/y2Sh5jWZOYA

[DiskDoctor]

Thanks for the answer.

Frankly, I don't use UAE, I have an Amiga to do things Amiga.

Merging the two ROMs seems easy as there's a system command to do so.

The only question is, how would I trigger a ROM-mapping command, presumably in the first line of my S-S??

[aha]

Thanks for the answer.

Frankly, I don't use UAE, I have an Amiga to do things Amiga.

Merging the two ROMs seems easy as there's a system command to do so.

The only question is, how would I trigger a ROM-mapping command, presumably in the first line of my S-S??

I think this is what you are looking for:
https://en.m.wikibooks.org/wiki/Aros/Platforms/68k_support

[AMIGASYSTEM]

The only question is, how would I trigger a ROM-mapping command, presumably in the first line of my S-S??

I don't know your WARP 1260 Card (surely I'll be too slow for AROS 68k) and I don't know if it allows you to map Roms, I think you'll have to do as it used to be done when mapping KickStart 3.1, read the link posted by aha, maybe you'll find some help.

[DiskDoctor]

Thank you all for that valuable resource.

Alas, it says nothing about bootstrapping the (1MB) AROS Kickstart file.

All I need it ROM bootstrapping command syntax.  I already merged both AROS ROMs into a 1MB file.

WARP card does possess a MapRom capability but yet, only 512KB images are supported.  This is to be changed in subsequent FW releases (2023).

So I think all I need is first line of S-S to map the ROM manually.

[AMIGASYSTEM]

I can attach you a startup-sequence or the system, of an old primordial version of my AROS One 68k that started from Kickstart 3.1, maybe you study it, with the new Builds this procedure does not work because the Core has changed a lot.

I read on AEB the problems with YOUR card to start 3D games, did you use snoopdos to get a good understanding of what is not being found?

[aha]

Thank you all for that valuable resource.

Alas, it says nothing about bootstrapping the (1MB) AROS Kickstart file.

All I need it ROM bootstrapping command syntax.  I already merged both AROS ROMs into a 1MB file.

WARP card does possess a MapRom capability but yet, only 512KB images are supported.  This is to be changed in subsequent FW releases (2023).

So I think all I need is first line of S-S to map the ROM manually.

In the link I posted you’ll find under the caption „Installation“:

you need to modify only the first line of the startup-sequence to:

   boot/amiga/AROSBootstrap ROM boot/amiga/aros.hunk.gz

[DiskDoctor]

I read on AEB the problems with YOUR card to start 3D games, did you use snoopdos to get a good understanding of what is not being found?

This is an OS3.2.1 problem.  Some of my 3D games run well.  I will use the SnoopDos next.

In the link I posted you’ll find under the caption „Installation“:

you need to modify only the first line of the startup-sequence to:

   boot/amiga/AROSBootstrap ROM boot/amiga/aros.hunk.gz

Those lines are present in my S-S from the beginning.  It is just that from the beginning too, I am getting

boot/amiga/AROSBootstrap - file is not executable

I used the instruction from the Wiki to fix rwed file rights and the error message prevails.  I have no idea at all how to fix it.

[AMIGASYSTEM]

This is an OS3.2.1 problem.  Some of my 3D games run well.  I will use the SnoopDos next.

I don't think it's an OS3.2.1 problem, then maybe tell me the titles of the games and I'll do some tests on my OS 3.2.1 (WinUAE)

[DiskDoctor]

If you need to know, I was attempting to install and run some early PC games, namely:

- Doom, Quake_RTG, Diablo_RTG, Duke Nukem 3D_RTG, Abuse_RTG, Heroes 2

I took the lha from AmiNet, whilst the game files I found on the web (archive.org).

Among these currently, only Abuse does not work.  I have game files (all?) but despite that, the message says out of memory (after processing game for ca. 30 secs).

Feel free to help me launch Abuse.

However, I would strongly prefer that someone would help me trigger the erroneous Bootstrap command.  I assume when KICK3.2.1 loads, it treats AROSbootstrap as OS3.2 binary, since it's not, it cannot be run; so all I need is OS3.2 command that bootstraps AROS ROM.

[AMIGASYSTEM]

Among these currently, only Abuse does not work.  I have game files (all?) but despite that, the message says out of memory (after processing game for ca. 30 secs).

Are you using the AGA or RTG version? what resolution?

I tested Abuse on WinUAE and OS 3.2.1 and had no problem, of course I had to use the old "ixemul v47.3"

However, I would strongly prefer that someone would help me trigger the erroneous Bootstrap command.  I assume when KICK3.2.1 loads, it treats AROSbootstrap as OS3.2 binary, since it's not, it cannot be run; so all I need is OS3.2 command that bootstraps AROS ROM.

Unfortunately, what is reported from the link posted by aha is no longer functional with the new Builds.

Booting AROS with KickStart 3.1 could be done in the past with the old AROS 68k builds, in fact now in the new Bulds there is no longer the Emergency Floppy "ADF".

As said if you want to try it I have an old AROS One Distribution of mine that boots with KickStart 3.1, without the need of the Roms (are integrated in an archive and unpacked in the boot process)

I should add that KickStart 3.2 is not usable because it is missing libraries inside that are present on OS 3.1.

On KickStart 3.2 due to space issues they have removed some libraries, and put them as files in the Libs folder.
In fact if you try to boot Workbench 3.1 with KickStart 3.2, the system will not boot because it needs some libraries, it is solved by copying the missing libraries to the floppy