Rebuilt a new version of AROS One 68k, the old version was no longer compatible with the new Aros68k ROMs.

This new version does not include any library or Amiga software, it will be the user who integrates the Amiga software into his private copy.

The user will be able to request the AROS One style icons for the Amiga software he will integrate in his AROS One, of course he will also be able to use the icons installed on the AROS One x86.

Can you explain what what not compatible? And which AROS ROMs do you refer as "newer"? I ask because compatibility with ROMs should always be preserved. Did you notice any m68k applications not working with "newer" ROMs?

In the Nightly Builds the Boot/Amiga folder includes the ROMs, I always use the latest Roms with each system update.

For some time now with the new Roms found in the Nightly Builds (51.7) my old AROS One 68k won't boot, I get a Guru, see first image screenshot.

Conversely if I use the older ROMs (51.5) with the new Nightly Builds I get a different Guru, see second screenshot image

On the other hand if I use the integrated Rom on WinUAE I get a black screen if I use a new Nightly Build, whereas if I use my old AROS One I get another Guru error, see third screenshot image.

Also if I try to boot the ISO of the latest Nightly Build directly from WinUAE with old Rom, I get error "FixFont: Could Open version0 or higher. Library STDC.library", IPrefs: Could Open version0 or highter. Library STDC.library"

Ok, thank you for the explanation. I'll keep that in mind when integrating changes from main repository.

AROS 68k arouses a lot of interest for owners of an expanded AMiGA, many owners of a V4 or a PiStorm have asked me to be able to download AROS One 68k, I will see if I can satisfy them as soon as I recreate a good and more stable AROS One!

https://eab.abime.net/showthread.php?t=98062&page=10

Since many people confuse AROS One x86 with AROS One 68k because of the same Themes and Icons, I decided to create new DualPNG Icons in Amiga GlowIcons sile, see screenshot !

deleted

Hi,

I have just fitted a Pstorm to an A500, can AROS 68K run?

I don't have a Pistorm, if it can map ROMs, has the right power, the video card is supported it might work, you should try it!

Hi,

I have downloaded AROS-20240514 from nightly builds, I will look into getting the system running on Pistorm and EMU68 and report back.

I tried to setup AROS-20240514 in WINUAE.

I setup the emulator as an A1200, selecting the AROM Kickstart ROMs from the AROS-20240514 ISO image in BOOT folder.

Loaded the ISO image as a CD Drive, added the IDE drive to the profile, Added the AROS Disk image to DF0 and started up.

The system seemed to boot, loading from ISO image, vbut stopped with this error:

Lib & Dv Loader Daemon

Could not open version 0 or higher of library "poixc.library"


shown in attached file.

Ok it seems to work fine, which version of AROS 68k are you using? the one from deadwood, or the one from aros.sourceforge.io?

Which Roms are you using, which version?

When you have to run an AROS 68k Build, you "always" have to use the Roms included in the Build that you find in the path Boot/Amiga

Hi,

I went to : Aros Sourceforge: https://aros.sour...ghtly1.php

Nightly Build Downloads (ABI-v1)

Downloaded the files:

2024-05-14
amiga-m68k-boot-floppy
amiga-m68k-boot-iso

I extracted the Aros kickstart roms from amiga-m68k-boot-iso boot/Amiga

Tried to setup WINUAE, with the files above, the system started booting from floppy image: amiga-m68k-boot-floppy and read the ISO in the virtual CD set up as IDE0

I was goint setup the system in WINUAE then transfer to SC Card to boot into EMU68.

I will re-read the installation documentation.

Forget the Floppy, it only serves for emrtgency !

The AROS ISO is bootable, which means it can be booted directly from WinUAE !

But beware InstallAROS on WinUAE is complicated, it often goes into Guru !

The easiest way to boot AROS 68k on the Emulator is this:

- Unzip the ISO, you can do this with WinRAR or other compactors
- You can use the unzipped folder as Hardisk (Directory Filesystem)
- You can also copy the contents of the folder to a HardFile, preferably formatted by AROS 68k, or Amiga OS3.9 "HDToolBox" the SFS Filesystem
- Starting AROS 68k go to Prefs, run Screenmode and choose a high resolution RTG Screen, if you use WinUAE in Window (handy if you have to drag files or folders from the Windows Desktop) I recommend a 1024x768 resolution

okay, thanks, for the advice, I will do ax you suggext.

This is it Grabri, thanks to your and other requests I have been getting from various users the new AROS One 68k is soon to be released!

For a few weeks now I have been working on the new version 2.0 of AROS One 68k, a version jump given the stability achieved by AROS x68k, of course it still does not reach the quality and power of AROS x86, but I must say that on WinUAE it works very well.

I found some regression to some OS3 software but better functionality on others, Hollywood applications represent modernity on AROS 68k, but opening Hollywood programs is a bit slow, then once opened the program runs fast.

AROS One can also run on expanded Amiga machines like the vampire and similar, but you have to install the software support for these machines

Here you find the first screenshot of AROS One 68k 2.0

AROS One 68k Finished soon publishing, it was very hard, AROS 68k as said is much more stable although still not compatible with OS 3.9 and old OS3 applications, MUI OS3 Applications work very well, many run through Zune, those less "well done" you have to direct them to MUI, created special MUI folder in Libs, alternative path where MUI Applications look for MUI libraries.

Same for older Hollywood Applications using older versions of Rapagui is respective Plug-In MUI in 'native OS3' version.

I enclose a small video showing some functions of AROS One 68k v2.0, the graphic appearance Themes and Icons included are identical to those used by AROS One x86 !

System is software should work well, the test is to check if there are any inconveniences since in the last few days or modified and added more on the hardfile.

Important, if you want to try other OS3 software, before installing it try it in RAM, as already said O3.9/3.2 software is not supported, as very old OS 2.0/OS 3.0/3.1 or poorly designed software is not supported, The software to be preferred is MUI software, much more compatible.

AROS One 68k can also run on Vampire and the like, but you have to add the necessary software to run these cards, the "SAGA" Monitor and the "sagagfx.hidd" Driver are already present by default on AROS 68k.

In the archive, in addition to the Hardfile, there is also the WinUAE config file and the ROMs (do not use other ROMs), which should not be modified to avoid incompatibilities, for example the Windows sound card is set to play Midi files at their best.

New tests of AROS One 68k with integrated Scalos. A few days ago, my friend “PeterK,” author of Icon.library, asked me about his involvement in the creation of an Icon.library for Scalos systems and improving icon management.

https://eab.abime...p;page=226

Thanks to deadwood's new AROS 68k build, Scalos seems to work well, except for the problem with icon management (it does not save data in Tooltype) and Guru when trying to use “Scalos FileType.”