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 !


https://youtu.be/GI2WS4qum2k

Last edited by AMIGASYSTEM on 24-Mar-2025 at 06:51 PM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

New version of AROS One 68k for those who wish to test it before release.

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.

If you want to test on the fly without modifying anything, just unpack and run it from the Workbench, if you change path you have to modify the 2 ROM paths and Hardfile path.

This is the download link, if there are no major issues I will officially release AROS One 68k

https://drive.google.com/file/d/1uJ22ljlTqeF3bO2XZQCFgokZXuTRbmYv/view?usp=sharing

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

AMIGASYSTEM wrote: 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,

AROS goal was, and should still be, to reach 100% OS 3.1 compatibility (depending on the platform, of course).

For improving AROS it would be good to have a list of applications which aren't working or are having problems, to fix bugs in the OS and/or implement some missing APIs (if any still missing).
Quote:

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.

MUI isn't part of the Amiga o.s., but it'll be go here as well to have a list of applications which are having problem with AROS.
Quote:

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 ! https://youtu.be/GI2WS4qum2k

It looks nice. Any list of features / tools / applications integrated?
Quote:

AMIGASYSTEM wrote: New version of AROS One 68k for those who wish to test it before release. 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. If you want to test on the fly without modifying anything, just unpack and run it from the Workbench, if you change path you have to modify the 2 ROM paths and Hardfile path. This is the download link, if there are no major issues I will officially release AROS One 68k https://drive.google.com/file/d/1uJ22ljlTqeF3bO2XZQCFgokZXuTRbmYv/view?usp=sharing

Have you considered to split the HDF into different HDF images for:
- the OS;
- additional tools which "enrich" the OS (e.g.: new shell, new icons, etc.);
- third-party apps;
- games;
- development tools (if any)
?

This "modularization" will help maintaining clearly separated those elements, and getting updates only to the relevant part.

@cdimauro

Achieving maximum global compatibility with sofftware 3.1 will be very difficult, partly because some software is not designed to work well in RTG, others may require native OS3 libraries and system files to work.

As mentioned many MUI applications work well with "ZUNE", others you have to use MUI libraries because they don't exist on ZUNE.
For this need I created a MUI folder where these applications find and use the MUI libraries missing on ZUNE.

Then there are applications where the old versions of the software work fine, while the new ones do not, see AmigaAMP.

Splitting the Hardfile is not a good idea, this is because with each release there is a lot of change both in the Core and in compatibility, the inexperienced user could make the system unstable.

In any case you should try it maybe you will realise what I wrote, I attach a link where you can download a preview of AROS One 68k 2.0

https://drive.google.com/file/d/1uJ22ljlTqeF3bO2XZQCFgokZXuTRbmYv/view

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

AMIGASYSTEM wrote: @cdimauro Achieving maximum global compatibility with sofftware 3.1 will be very difficult, partly because some software is not designed to work well in RTG, others may require native OS3 libraries and system files to work. As mentioned many MUI applications work well with "ZUNE", others you have to use MUI libraries because they don't exist on ZUNE. For this need I created a MUI folder where these applications find and use the MUI libraries missing on ZUNE.

This is well understood. I was only asking to document those differences, when you face them, and report them to the ticketing system, so that AROS developers can have a chance to fix / improve AROS.
Quote:

Then there are applications where the old versions of the software work fine, while the new ones do not, see AmigaAMP.

I haven't checked it. It's good to document this as well.
Quote:

Splitting the Hardfile is not a good idea, this is because with each release there is a lot of change both in the Core and in compatibility, the inexperienced user could make the system unstable.

Right, but it's also difficult to update an existing "distro" once you've already worked on it and customized.
Quote:

In any case you should try it maybe you will realise what I wrote, I attach a link where you can download a preview of AROS One 68k 2.0 https://drive.google.com/file/d/1uJ22ljlTqeF3bO2XZQCFgokZXuTRbmYv/view

I've spent some time on it, and looks nice, but the backdrop image might be improved (it's too pixeled / blurry).

I haven't tried all applications, but some of them and in general looks good.
It's still unstable and I got several alerts (memory header corruption) when I launch some Hollywood applications, for example.

I had to tweak a bit the UAE config file to adapt to my system (I've two monitors).
One suggestion here, on Host/Display please set:
- Fullscreen: Native;
- Native: Full-window
- RTG: Full-window
and on Sound:
- WASAPI
to better use the host system.

Other suggestions:
- RTG / Multithreaded
- Chipset / Immediate Blitter
- Chipset / Collision Level: None
since the primary usage is RTG, those will improve the overall performance.

Finally, I've switched the CPU to 68030 + 68882 which avoids trapping the several FPU instructions which are used by more legacy software (I know that some from 68040/060 are missing).

@cdimauro

Thanks for testing and for your helpful tips!

But beware with CPU 030 some installed 060 applications will not work see AmiSSL, consequently NetSurf will not work.

Which Hollywood Application did you have memory corruption with? All Hollywood Applications included in the Distribution on my WinUAE and my configuration work fine, no errors.

In the Distribution all software has been tested one by one and none should give problems.

On WinUAE I do not use full screens, this is because in the window it allows you to drag Volumes, Folders and Files from the Windows Desktop to Wanderer, very convenient for quick tests.

This is also the reason that the backgrounds are 1024x768, of course on larger screens the quality is lost, but here it is not a problem users can change them.

For the seganalisation of the OS3 software that does not work, there are so many that the developers will surely be aware of the various incompatibilities, different for AROS x86 where the software that gives problems now are very few and deadwood in terms of a short time manages to fix them all.

Last edited by AMIGASYSTEM on 30-Mar-2025 at 09:38 AM.
Last edited by AMIGASYSTEM on 30-Mar-2025 at 09:36 AM.
Last edited by AMIGASYSTEM on 30-Mar-2025 at 09:35 AM.
Last edited by AMIGASYSTEM on 30-Mar-2025 at 09:23 AM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

Splitting the Hardfile is not a good idea, this is because with each release there is a lot of change both in the Core and in compatibility, the inexperienced user could make the system unstable.

Hardly... you can check how MorphOS does it, and they have thousand of users, and they don't seem to have a problem. Alas, modularization is one of AmigaOS greatest strengths, it's a pity it isn't used correctly. Having to download 800Mb to update just few Megabytes seems such a waste. Back in the day we all a lot of partitions where we put different data, we were young and yet we managed to live another day.

Split the Hardfile!
"It is the way"
"Do or do not, there is no try "

xD

Nice distro btw, thanks for the work you've put through.

Ps- I'd just wish ppcamiga1 would comment in this thread, just for the sake of the old analog engagement Gods

_________________
Indigo 3D Lounge, my second home.
The Illusion of Choice | Am*ga

@pixie

It is not necessary to reinstall everything, this only happens when both the Core and a lot of software has been 'elminated', 'replaced' or 'updated', in this case everything is faster.

Otherwise, as with AROS x86, if the updates are not extensive, my installer update will take care of updating, moving or deleting software.

Last edited by AMIGASYSTEM on 30-Mar-2025 at 10:32 AM.
Last edited by AMIGASYSTEM on 30-Mar-2025 at 10:30 AM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

AMIGASYSTEM wrote: @cdimauro Thanks for testing and for your helpful tips! But beware with CPU 030 some installed 060 applications will not work see AmiSSL, consequently NetSurf will not work.

I haven't tested it before, because I had not time to properly configure the system with a network connection.

However, NetSurf requires a 68020+: the problem is clearly AmiSSL, which sucks if it requires a 68060.
Quote:

Which Hollywood Application did you have memory corruption with? All Hollywood Applications included in the Distribution on my WinUAE and my configuration work fine, no errors. In the Distribution all software has been tested one by one and none should give problems.

AmigaAMP / RNOInfoScreen -> immediately crashes with Recoverable Alert!
Task: ArosOne:C/RexxMast
Error: 0x01000000F - Memory header not located

GrimoriumPDF / Manual.pfd (so, opening the default AROS' PDF reader) often completely crashes WinUAE (I'm using the last official one: 5.3.1) without any alert (WinUAE just immediately quitted). Sometimes, more rarely, it just resets the emulator (the Amiga is rebooted).

Sometimes on 68060 (which I've configured for these tests) Voxel generates a sky with random black & white pixel. The backgroud is mostly good, with some surfaces which are using chequered blank and white tiles/textures. It's was ok when I was using 68030+68882.

Unfortunately, I've found the Hollywood applications which crashed. As I've said, I've limited time for testing.
Quote:

On WinUAE I do not use full screens, this is because in the window it allows you to drag Volumes, Folders and Files from the Windows Desktop to Wanderer, very convenient for quick tests.

It wasn't full screen, but full window.

I understand your needs, but think about the general audience of your distro: full window offers a more "immersive" experience, without the annoying "switch" which happens when selecting full screen (e.g. because of the different refresh rate).
Quote:

This is also the reason that the backgrounds are 1024x768, of course on larger screens the quality is lost, but here it is not a problem users can change them.

Try to upgrade FullHD at least, which is much more visually compelling. Worst case, the users which still have monitors with minor resolutions can have it shrunk and still fitting.
Quote:

For the seganalisation of the OS3 software that does not work, there are so many that the developers will surely be aware of the various incompatibilities, different for AROS x86 where the software that gives problems now are very few and deadwood in terms of a short time manages to fix them all.

Being aware and having a ticket describing the problem is a bit different.

As a developer, I greatly prefer the latter.

As a QA engineer, I have to do the latter.

@cdimauro


Quote:

However, NetSurf requires a 68020+: the problem is clearly AmiSSL, which sucks if it requires a 68060.

No, AmiSSL provides three rails 020/040 and 060, on my Distribution when available I always prefer the native 060 rails because I've always used them on my Amiga 4000/060 as well, and they've always seemed to be faster.

However AmiSSL has always worked well on my OS3.1, 3.2, .39, AfA One systems, even the AROS x86 version works well even though it is obsolete.

Quote:

GrimoriumPDF / Manual.pfd (so, opening the AROS default PDF reader)

The problem is the stack, the icon was used on OS 3.9, on AROS a bigger stack is required, if you delete the icon, the system will give you the correct one set in def_PDF with the bigger stack and you will open Manual.pdf without any problems without any crashes.

Also, Manual.pdf is not very compatible with ArosPDF, if you load Manual.pdf with a Windows PDF reader and save him, it will be supported and the strange characters on the ArosPDF bar will disappear
Quote:

Task: ArosOne:C/RexxMast

Thanks for this report, the problem also exists on AROS x86 32Bit and AROS v11 64Bit, I will report the bug to deadwood who will surely fix it.

Quote:

AmigaAMP / RNOInfoScreen -> immediately crashes with Recoverable Alert!

I think it is related to a RexxMast bug, although on AROS x86 RNOInfoScreen works fine !

Quote:

Being aware and having a ticket describing the problem is a bit different.

Unfortunately age is advancing (70 years old) and running multiple AROS One x86, 68k, Hosted Windows and Hosted Linux Distributions (uin construction) takes a lot of my time and eye fatigue (I have a few problems), so I do the reporting on arosworld.org, then maybe someone will do it for me which I thank.

Last edited by AMIGASYSTEM on 31-Mar-2025 at 11:22 AM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

AMIGASYSTEM wrote: @cdimauro Quote: However, NetSurf requires a 68020+: the problem is clearly AmiSSL, which sucks if it requires a 68060. No, AmiSSL provides three rails 020/040 and 060, on my Distribution when available I always prefer the native 060 rails because I've always used them on my Amiga 4000/060 as well, and they've always seemed to be faster.

OK, understood. I'll try the 68020 version then.
Quote:

Quote: GrimoriumPDF / Manual.pfd (so, opening the AROS default PDF reader) The problem is the stack, the icon was used on OS 3.9, on AROS a bigger stack is required, if you delete the icon, the system will give you the correct one set in def_PDF with the bigger stack and you will open Manual.pdf without any problems without any crashes.

Got it, but think about a user that just tried your distro: he/she just got the crash and a bad experience.

Could you provide your distro with updated icons which avoid those problems?
Quote:

Also, Manual.pdf is not very compatible with ArosPDF, if you load Manual.pdf with a Windows PDF reader and save him, it will be supported and the strange characters on the ArosPDF bar will disappear

Then it's AROSPDF which should be fixed.
Quote:

Quote: AmigaAMP / RNOInfoScreen -> immediately crashes with Recoverable Alert! I think it is related to a RexxMast bug, although on AROS x86 RNOInfoScreen works fine !

Another report.
Quote:

Quote: Being aware and having a ticket describing the problem is a bit different. Unfortunately age is advancing (70 years old) and running multiple AROS One x86, 68k, Hosted Windows and Hosted Linux Distributions (uin construction) takes a lot of my time and eye fatigue (I have a few problems), so I do the reporting on arosworld.org, then maybe someone will do it for me which I thank.

No problem, I understand.

The important thing is report bugs, no matter how.

Thanks for your effort!

@cdimauro

The Distribution is still under construction, the Icons were those of AROS x86 where for those Applications did not need a High Stack.

Of course before distributing, I will test all the icons both the real ones and the def_icons !

Important !!!

I replaced the Core, now as in the previous versions of AROS One 68k the Core is the deadwood ones, much more compatible, for example with this core works "ModExplorerNG" with the Core "https://aros.sourceforge.io/nightly1.html" the buttons were blocked, also RNOInfoSCreen doesn't go in Guru anymore with the deadwood Core, I just have to understand why the Arexx script doesn't run correctly (see error in the attached link).

https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1337&rowstart=340&pid=8016#post_8016

Unfortunately deadwood cannot offer 68k support and I have to see if I can solve the problem myself!

I specify that the Core of "deadwood" is incompatible with the Core "aros.sourceforge", the Core and the Contrib of deadwood, as AROS x86 and compiled with the C library.

Last edited by AMIGASYSTEM on 01-Apr-2025 at 10:58 AM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM

Quote:

AMIGASYSTEM wrote: @cdimauro The Distribution is still under construction, the Icons were those of AROS x86 where for those Applications did not need a High Stack. Of course before distributing, I will test all the icons both the real ones and the def_icons !

If you need some help for automating something, just let me know: I can write Python scripts, if I've time (usually they don't take long. But it depends on the task, of course).

For example, you can keep a text file, CSV, Excel, etc. where there's a list of icon names/paths that should be replaced by other ones, and I can automate the process of copying them from a location to the root folder of your distro.
Quote:

Important !!! I replaced the Core, now as in the previous versions of AROS One 68k the Core is the deadwood ones, much more compatible, for example with this core works "ModExplorerNG" with the Core "https://aros.sourceforge.io/nightly1.html" the buttons were blocked, also RNOInfoSCreen doesn't go in Guru anymore with the deadwood Core,

Nice. Should I download again your distro from the previous link, or I have to wait for another release from you?
Quote:

I just have to understand why the Arexx script doesn't run correctly (see error in the attached link). https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1337&rowstart=340&pid=8016#post_8016

I'm not an expert with AREXX, but you can post your issue here as well: I think that some other Amiga user could help.
Quote:

Unfortunately deadwood cannot offer 68k support and I have to see if I can solve the problem myself!

Np. I understand that the focus is on x86/x64, but I'll try to help for the 68k version (I would love to see it reaching the 3.1 goal which was set at the beginning of the AROS project).
Quote:

I specify that the Core of "deadwood" is incompatible with the Core "aros.sourceforge", the Core and the Contrib of deadwood, as AROS x86 and compiled with the C library.

OK

@cdimauro

Thanks Mauro, every contribution is welcome, as soon as I reconfigure and check everything I will attach a new version where you can test.

The AREXX problem although strange is only on AROS 68k, on AROS x86 despite being "equal" the Core, RNOInfoScreen works very well.

I think however that there is some error in the compilation of "RexxMast" " and "rexxsyslib.library, I replaced them with those of OS3 and RNOInfoScreen worked, see screenshot link !

I also replaced AmigaAmp with a slightly more up-to-date version because the previously installed version with RNOInfoScreen only had a black screen.

https://www.arosworld.org/infusions/forum/attachments/rnoinfoscreen_2.jpg

Last edited by AMIGASYSTEM on 01-Apr-2025 at 05:45 PM.
Last edited by AMIGASYSTEM on 01-Apr-2025 at 05:45 PM.

_________________
AROS One Home Site
AfA One Amiga OS 3.9

@AMIGASYSTEM ok, I'll wait for your next distro. Looks promising.

If there's an AREXX problem which shows only on the 68k, it's still an issue that needs to be fixed, because it can pop-up also on other scenarios. So, it's good to investigate and find the root cause. AREXX is a key component for the Amiga OS...