AMIGASYSTEMDistro Maintainer Posted
16 days agoOkay thank you, then Early Startup will be used to run this application, basically it was to run uCommander, a simple Menu where you will be able to choose and run some useful applications to do some minor maintenance.
AMIGASYSTEMDistro Maintainer Posted
17 days agodeadwood a question, from the Grub menu you can add an application that is in the system, and then run it directly
Hello,
An update on the plan:
1) Release 64-bit version of Odyssey Web Browser for AROS, Linux and Windows
2) Implement first prototype of 32-bit-under-64-bit emulator for AROS [IN PROGRESS]
3) Release new version of ABIv0 refreshed to 20221221 codebase
Work on emulator prototype progresses well. If you are interested in details, please check a thread here on arosworld.org. I will be focusing on it in coming weeks. In parallel I'm thinking about releasing first update to 20220318-1 release. There have been a number of fixes since the release so it would be good to package them together and make available to users.
The long term horizon stays unchanged:
"On a longer horizon, there will be a lot of work related to ABIv0 and AxRuntime.
I want to update ABIv0 to be based on latest ABIv11 source code. This will be an enabler to:
1) develop an emulator that will allow running AROS 32-bit programs under 64-bit AROS.
2) develop a version of AxRuntime that is capable of running ABIv0 32-bit programs on top of Linux and Windows
Furthermore, ABIv11 64-bit native will be fixed to provide the same level of hardware compatibility on recommended hardware as current ABIv0 32-bit. On AxRuntime side, the goal will be to develop a working window manager (IntuitionWM) and Linux-native desktop, most likely in form of Scalos.
Once all these things are in place, there will be two development lines available:
For people preferring native AROS we will have ability to use majority the existing 32-bit software base on 64-bit AROS and native 64-bit system working on recommended hardware, which then is an enabler for creation of 64-bit distributions that match current 32-bit distributions in user experience.
For people interested in AxRuntime route we will have a Linux-native desktop and ability to run majority of AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing distributions could be re-created using Linux as a base without loosing existing functionality for users."
Amiwell79Distro Maintainer Posted
3 months agodeadwood we have a midi driver thanks to hitchhikr, kalamatee, Neil Cafferkey and Alfred Faust you must include it in the contrib archives?
Edited by Amiwell79 on 11-02-2024 09:28,
3 months ago You do not have access to view attachments
Yes, running 32-bit binaries on 64-bit system should be as transparent as possible.
Amiwell79Distro Maintainer Posted
3 months agodeadwood do you want to make an emulator integrated into the system?
mattson62Junior Member Posted
3 months agoWow,Everything sounds very exciting!
Hello,
Another update from me on the plan:
1) Release new version of ABIv0 refreshed to 20211214 containing switch to new C library [DONE]
2) Rebuild Odyssey Web Browser using GCC 6.5.0 and new C library [DONE]
These have been intensive two months, but we are finally pass that milestone!
Next actions to undertake are:
1) Release 64-bit version of Odyssey Web Browser for AROS, Linux and Windows
2) Implement first prototype of 32-bit-under-64-bit emulator for AROS
3) Release new version of ABIv0 refreshed to 20221221 codebase
With first item, I want to bring Odyssey to the level of stability that allows me to use it for everyday surfing of Amiga-related sites while continue using my main Linux Mint system for everything else. Any improvements that I will introduce will also be available to 32-bit version of Odyssey, so you may expect a small update there as well. With the second item, the emulator prototype, it's really the first steps to see what is needed and how to design the solution so that it takes least amount of work while supporting ~80% of existing third party 32-bit software.
The long term horizon stays unchanged:
"On a longer horizon, there will be a lot of work related to ABIv0 and AxRuntime.
I want to update ABIv0 to be based on latest ABIv11 source code. This will be an enabler to:
1) develop an emulator that will allow running AROS 32-bit programs under 64-bit AROS.
2) develop a version of AxRuntime that is capable of running ABIv0 32-bit programs on top of Linux and
Furthermore, ABIv11 64-bit native will be fixed to provide the same level of hardware compatibility on recommended hardware as current ABIv0 32-bit. On AxRuntime side, the goal will be to develop a working window manager (IntuitionWM) and Linux-native desktop, most likely in form of Scalos.
Once all these things are in place, there will be two development lines available:
For people preferring native AROS we will have ability to use majority the existing 32-bit software base on 64-bit AROS and native 64-bit system working on recommended hardware, which then is an enabler for creation of 64-bit distributions that match current 32-bit distributions in user experience."
For people interested in AxRuntime route we will have a Linux-native desktop and ability to run majority of AROS ABIv0 programs (32-bit), AROS ABIv11 programs (64-bit) and AxRuntime-recompiled programs (64-bit). This way existing distributions could be re-created using Linux as a base without loosing existing functionality for users."
AMIGASYSTEMDistro Maintainer Posted
4 months agoOK, thank you, the translation had led me to understand something else!
To answer questions on path forward:
There will be two paths: a Native 64-bit one and an AxRuntime 64-bit one.
AMIGASYSTEMDistro Maintainer Posted
4 months agoIf the future software is 64Bit, then AROS One will adapt, what is important is that it can always be used in Native/VM