AROS World Exec
Development => Development (General) => Topic started by: Amiwell on February 27, 2023, 06:02:11 AM
-
After deadwood published the first native alpha I tried the system installs on USB key at least to me does not work to boot from HD and seen and considered that there are still not many programs should do a momentary installation on the stick, including there are development tools ;)
(https://i.ibb.co/HK3hLKG/2-aros-x64v11.png) (https://ibb.co/Pr0Dsr1)
downloads
http://tinyaros.flazio.com/
Software
Utility System
MCAmiga
Amifox
MPlayer
ArosPDF
BeeBase
PovRay
-
Here is ZuneArc x64 that you can try.
-
try it but do not works i try all Apps of zunetools
-
try it but do not works i try all Apps of zunetools
Well then I can't use IcarosDesktop 64bit anymore for testing. So bye, bye Icaros! Hello, TinyAros. ;)
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
-
Just seen this thread... Looking forward to playing with it! :)
Thank you Amiwell
-
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
miker, all software created before "ABIv11" does not work, even those that seem to work like Dopus, AmiTube and others, as soon as you use them they go to Guru.
I believe that this Build "ABIv11" before using it to develop or to create a Distribution, we have to wait for deadwood to provide us with a Build ready for the purpose.
-
miker, all software created before "ABIv11" does not work, even those that seem to work like Dopus, AmiTube and others, as soon as you use them they go to Guru.
That is why miker offers to compile them /for/ ABIv11 ;)
I believe that this Build "ABIv11" before using it to develop or to create a Distribution, we have to wait for deadwood to provide us with a Build ready for the purpose.
As long as miker is using the (latest) ABIv11 version from deadwood he should be able to build existing software for it. He might run into issues but when he does i'm sure we are going to hear that :)
Thank you AmiWell for the distribution and miker1264 for his offer :thumbsup:
-
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
Thanks for volunteering :)
-
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
Thanks for volunteering :)
deadwood
Is it only a temporary situation where the software compiled for ABIv1 x86-64 won't work with ABIv11 or is it that way going forward?
-
Is it only a temporary situation where the software compiled for ABIv1 x86-64 won't work with ABIv11 or is it that way going forward?
It is going to stay. ABIv11 is a different ABI than ABIv1 (actually if you dig bit deeper, it is called ABI_WIP to underline that it is still work-in-progress, not stable).
-
Thank you all User and Developer enjoy :D
-
if I had the web browser I immediately used Tiny x86_64, I hope in albs with his amifox :)
-
That is why miker offers to compile them /for/ ABIv11 ;)
Yes I understood this, the problem that even existing ABIv11 applications on contrib such as Dopus4 or Amitube, go into Guru even a simple rotation of the mouse wheel !
-
everything works for me except some problems with AHI but nothing irreparable
-
everything works for me except some problems with AHI but nothing irreparable
Try to configure Dopus4 or change some characters or buttons and you will see the system crash !
-
eh... dopus have a problem do not configure it!
-
Exactly, not configuring it means unusable, Dopus by default has nothing that can be useful, this problem is on many existeni software compiled x86_64 v11.
I for the time being will not distribute AROS One x86_64 v11, to make a Distribution with these software problems is to lose credibility,
-
ok Carlo :)
-
That is why miker offers to compile them /for/ ABIv11 ;)
Yes I understood this, the problem that even existing ABIv11 applications on contrib such as Dopus4 or Amitube, go into Guru even a simple rotation of the mouse wheel !
The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.
Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift :)
-
I had problems with dopus4 if you configure at will, if you leave it so it works, fryingpan does not start and even text2pdf, the programs mentioned at the beginning of the thread all work :)
-
try it but do not works i try all Apps of zunetools
Well then I can't use IcarosDesktop 64bit anymore for testing. So bye, bye Icaros! Hello, TinyAros. ;)
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
Many Thanks Miker :)
-
Just seen this thread... Looking forward to playing with it! :)
Thank you Amiwell
You are welcome :)
-
The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.
Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift :)
With VMWare AROS we are talking about many years ago, when there were many more developers on AROS, I will definitely continue to test as always for ABIv11 as well, but right now as deadwood said, the priorities reside in ABIv0
-
try it but do not works i try all Apps of zunetools
Well then I can't use IcarosDesktop 64bit anymore for testing. So bye, bye Icaros! Hello, TinyAros. ;)
I will compile the ZuneTools, FileMaster, Picture Viewer & LunaPaint for use with TinyAros in the next several days.
Many Thanks Miker :)
First I need to update my sources for x86-64 for ABIv11 then rebuild the tool chain. That will take 3 or 4 hours.
When my wife asks "what are you doing?" when she sees all the text scrolling on the screen I just tell her "I'm building something". To which she replies "No you aren't. You're playing with pixels! Now do something useful." LOL 😂
-
@ Amiwell
With ABIv11 the Network on the native Works ? on VM the Network does not work !!!
@miker
My wife doesn't care what I do in my study, so for her it's a good reason not to bother her in the house ;D
-
ok miker ;D, @amigasystem the network works fine
-
At the moment the browser is also essential @Miker if you can do something it would be great :D
-
At the moment the browser is also essential @Miker if you can do something it would be great :D
I don't do any work with browsers.
-
I was referring to the compilation of Odyssey but okay we'll wait
-
I fixed the iso await further developments by deadwood
-
The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.
Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift :)
With VMWare AROS we are talking about many years ago, when there were many more developers on AROS, I will definitely continue to test as always for ABIv11 as well, but right now as deadwood said, the priorities reside in ABIv0
This is the exact attitude that ran off a few of the most active developers.
-
I fixed the iso await further developments by deadwood
Thanks for your efforts in setting up Tiny AROS x86. It is much appreciated.
It also gives me a good starting point to setup a testing environment. I don't especially like to use the default layout filled with Gorilla Icons and no applications other than system apps. Sometimes those extra utilities are needed.
And besides I like the concept of Tiny AROS. Quick & easy!
PS - I will refresh my ABIv11 Build System this weekend then I can compile some existing software for ABIv11.
(this time for real ;) ).
-
ok miker thanks so much :D
-
The only way forward is to compile things for ABIv11, test them, report errors so that they can be fixed. Otherwise AROS will stay in limbo for another couple of decades.
Does that mean you can make a full working distribution yet: no it does not. But I remember something called vmware AROS that started out exactly the same way if you catch my drift :)
With VMWare AROS we are talking about many years ago, when there were many more developers on AROS, I will definitely continue to test as always for ABIv11 as well, but right now as deadwood said, the priorities reside in ABIv0
The problem is that we must take the first steps in the direction of ABIv11 in order to make future distros possible.
The other problem is that deadwood is only one person and he has to focus on the most important tasks first. But if there are situations where changes benefit both ABIv11 & ABIv0 then that's good. That's beneficial for everyone.
Until we can attract more active developers to AROS this situation probably won't change. But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.
That's how I see it but others may see it differently.
-
The problem is that we must take the first steps in the direction of ABIv11 in order to make future distros possible.
The other problem is that deadwood is only one person and he has to focus on the most important tasks first. But if there are situations where changes benefit both ABIv11 & ABIv0 then that's good. That's beneficial for everyone.
Until we can attract more active developers to AROS this situation probably won't change. But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.
That's how I see it but others may see it differently.
+1
-
But then there are some changes that the Apollo Team have made to AROS 68k which maybe can be applied to ABIv11 development but there isn't time at the moment or anyone to bring those forward.
That's how I see it but others may see it differently.
If I have to be honest, I find AROS x86 ABIv0 more functional than AROS 68k, I use both, on AROS 68k I have not seen anything more than AROS x86 ABIv0.
AROS 68k in my opinion is a hybrid system, which does not have any native software, and that much of the Amiga software does not work or works poorly, I say this given my extensive Amiga experience for almost 40 years, this is why I decided not to distribute AROS One 68k, despite having had so many requests, an example on these link:
https://eab.abime.net/showthread.php?t=98062
http://eab.abime.net/showthread.php?t=97987
http://eab.abime.net/showthread.php?t=106295
-
Amiwell
Instead of TinyAros it is becoming a discussion about ABIv11.
AMIGASYSTEM
You misunderstood. I wasn't talking only about AROS 68k.
The code base that AROS 68k uses was ABIv1 but that may be ABIv11 now. But deadwood can explain it better.
The Apollo Team has made changes to their branch (should we call it ABIv10 or ABIv12 ?). These changes can be brought into ABIv11 which in some way is also the basis for ABIv0. I know I'm not explaining it correctly. It's complicated.
For various reasons we haven't worked directly with Apollo Team for a long time now. Rony Beck and a few others have gained some experience dealing with the boot from hard disk issue for the V4 Standalone (real hardware for 68k).
There were several problems preventing boot from hard disk such as with the current ABIv11. I believe the two problems are the same. It was mostly a timing issue if I remember correctly. Scsi.device was waiting indefinitely for a signal that never arrived. But all that was fixed a few years ago. That's just one example of how we can co-operate.
But more importantly we must also consider development with ABIv11 in mind in order to improve it to move forward. Once ABIv11 can boot from hard disk either on real hardware or in a virtual machine it makes testing easier.
@Amiwell
Does TinyAros work in Native Mode or just Hosted Mode?
-
Of course it's necessary to focus on development for ABIv0 because that's what the majority of the people use daily.
But it's also important to have distros like TinyAros x86-64 so we can compile software as needed or when it becomes available so we can test it. That's necessary to move forward with development.
Whether anyone else chooses to support ABIv11 that's up to them. But I'm certainly in favor of x86-64 flavors of AROS.
-
Ok miker, sorry I just wanted to point out that I always updated AROS 68k with the Nightly Builds ispreviously taken from HERE (https://aros.sourceforge.io/nightly1.php), I don't know if it is produced by Apollo, for sure in these years the compatibility with Amiga software and its functionality has never changed, so for for me, at the moment it doesn't make any sense to Distribute a new version of AROS One 68k.
About ABIv11, at the moment I believe it is not worthwhile to make a Distribution, since many things are unfinished, testing for the moment is better to do it with deadwood's reference Build.
When deadwood says ABIv11 is ready to be used for a Distribution, I will be happy to upgrade my AROS One ABIv11, which I have already announced here:
https://ae.amigalife.org/index.php?topic=1087.0
-
The code base that AROS 68k uses was ABIv1 but that may be ABIv11 now. But deadwood can explain it better.
It still is ABIv1 for 68k and it will not change.
The Apollo Team has made changes to their branch (should we call it ABIv10 or ABIv12 ?). These changes can be brought into ABIv11 which in some way is also the basis for ABIv0. I know I'm not explaining it correctly. It's complicated.
afaik Apollo forked AROS so if you need specific information on that topic then you should ask the Apollo developers :)
What I do know is that some of their work/fixes is/are incorporated back into the official AROS source-tree.
-
But more importantly we must also consider development with ABIv11 in mind in order to improve it to move forward. Once ABIv11 can boot from hard disk either on real hardware or in a virtual machine it makes testing easier.
@Amiwell
Does TinyAros work in Native Mode or just Hosted Mode?
You should really try TinyAros x86_64 and see for yourself ;)
-
@miker1264
If you try TinyAros x86_64 in VirtualBox you will get not keyboard nor mouse, because PS/2 driver is removed.
Add this to grub module list
module /Devs/Drivers/i8042.hidd
Also when you try running GCC you will get a crash in C library. I will fix this over weekend.
-
Miker this distribution is native installs on USB stick and preset to work only in vesa mode at the moment
-
@miker1264
If you try TinyAros x86_64 in VirtualBox you will get not keyboard nor mouse, because PS/2 driver is removed.
Add this to grub module list
module /Devs/Drivers/i8042.hidd
Also when you try running GCC you will get a crash in C library. I will fix this over weekend.
Thanks
-
I'm trying to boot the ISO in VirtualBox but in Vesa Mode the screen is black. What configuration do I need. Will it boot from the ISO ?
-
I'm trying to boot the ISO in VirtualBox but in Vesa Mode the screen is black. What configuration do I need. Will it boot from the ISO ?
On VMware it starts AROS x86 v11 without problems, as soon as I finish updating the ISO of AROS One 64 v11, I will do some Testing on VirtualBox and check what configuration is needed.
-
I'm trying to boot the ISO in VirtualBox but in Vesa Mode the screen is black. What configuration do I need. Will it boot from the ISO ?
On VMware it starts AROS x86 v11 without problems, as soon as I finish updating the ISO of AROS One 64 v11, I will do some Testing on VirtualBox and check what configuration is needed.
Thanks. I tried to boot in VMWare Workstation instead.
It boots fine into the Live CD and it works fine so far but unfortunately no mouse. How do I configure GRUB ?
-
Let me know if the Network works for you, on my VMware it doesn't work !
-
Let me know if the Network works for you, on my VMware it doesn't work !
On VMWare even in Ubuntu the network connection is problematic.
I'm still trying to get my mouse to work in GRUB. The initial GRUB menu items don't work. I can't use mouse or keyboard for GRUB either.
I suppose I can't edit GRUB on the ISO. So I need an ISO with mouse hidd enabled.
@Amiwell
You say you boot from pendrive (USB Flash?). Did you have to edit GRUB for the mouse & keyboard?
-
On VMWare the Network works fine, only with AROS 64 v11 it does not work.
On VMWare with x86_64 v11, you should have no problem with Mouse, it works fine for me !
-
I Use the ISO of AROS One x86_64 v11, I am also setting up the GCC run.
However on the reference build in the Grub, the Command "module /Devs/Drivers/i8042.hidd" is present.
-
Ok. I seem to be missing something here. Everyone else seems to be using Flash Drives.
Here's what i did. I downloaded alpha3 ISO then I used the Live CD in VMWare. It booted into AROS & I have both mouse & keyboard. So I will start from there.
Maybe I will start my own distro just for fun? AROS Vanill x86-64 ? Let's start compiling...
-
Ok. I seem to be missing something here. Everyone else seems to be using Flash Drives.
The way you use the iso with your virtualization software is the way it should be done.
The flash drive part comes in when you use the VM booted from the ISO and then install AROS onto a flash drive.
It is required to make the flash drive partitioned the Amiga way and which uses the Amiga filesystem. Once you have that done you can then use the flash drive to try and boot the installed AROS distribution directly on your hardware.
And by the looks of it, that seem to fail for some people.
afaik grub does not support mouse but it should detect the keyboard so that you are able to select a grub option or modify the grub entry. If you try to use the grub menu from the VM (when you boot the ISO) then it might require some additional VM setup in order to make your keyboard work that early in the boot process with grub (for VBox I have/had to setup USB filtering correctly, not sure if that is still required) but your mileage may vary.
-
Everything is good so far. i'm still working on the icons. Copying icons in the shell is no fun. I need IconClone for ABIv11.
I've noticed that USB support is a little touchy at times. The first time the USB is attached it's ok. After that it requires a reboot of AROS.
Maybe the USB issue is particular to VMWare.
-
Miker yes I removed an entry on grub because I did not start the system
-
Everything is good so far. i'm still working on the icons. Copying icons in the shell is no fun. I need IconClone for ABIv11.
I've noticed that USB support is a little touchy at times. The first time the USB is attached it's ok. After that it requires a reboot of AROS.
Maybe the USB issue is particular to VMWare.
Regarding Icons, for the moment you can configure icons on Other OS, AROS x86 or OS3 RTG
Regarding USB devices, with VMware "only" with AROS 64 v11, if you leave the USB device Mounted, on reboot the system struggles to start, so you don't have problems, before closing AROS you have to disable (unmount) the USB device.
-
@miker1264
Also when you try running GCC you will get a crash in C library. I will fix this over weekend.
Here is fix for GCC crash:
https://axrt.org/development/crt.library-2.1-x86_64-v11.zip
-
Miker I fixed the iso of Tiny Aros so that you can use it in VM :)
https://drive.google.com/file/d/1f6Z3ls5VSEu50KCLL039noi5nZhI5blB/view?usp=sharing
-
added amifox :)
-
now changed the theme later upload the new iso, with amifox Tiny Aros 64 is more fuctionally
(https://i.ibb.co/QYfs2gc/tiny-64-1.png) (https://ibb.co/XFbmhQ4)
-
now changed the theme later upload the new iso, with amifox Tiny Aros 64 is more fuctionally
(https://i.ibb.co/QYfs2gc/tiny-64-1.png) (https://ibb.co/XFbmhQ4)
It looks great. Nice job!
-
thanks Miker :)
ah new build for you for vm :)
http://tinyaros.flazio.com/
-
added the new iso on my web site also added programs
http://tinyaros.flazio.com/
-
added other software mcamiga(file manager), hex2(advanced calculator), muiplot :)
-
Does TinyAros for ABIv11 have gcc at the command line?
-
yes I have updated everything now in the link you will find the distribution for VM
http://tinyaros.flazio.com/
-
Does TinyAros for ABIv11 have gcc at the command line?
On 64 v11 the GCC works, but the compilation does not work, it goes to error, in Development important files are missing, we discussed it with deadwood here:
https://ae.amigalife.org/index.php?topic=881.120
-
ah! in hosted mode there is not the problem
https://axrt.org/downloads-aros
-
ah! in hosted mode there is not the problem
https://axrt.org/downloads-aros
Do you have a link to instructions on how to install gcc at the command line for future reference?
-
Combining both downloads is straighforward
1. extract AROS archive
2. extract contrib archive
3. copy output of 2 into 1 keeping directories (copy AROS directory from "contrib archive" over AROS directory from "AROS archive")
-
Thanks :)
-
Does TinyAros for ABIv11 have gcc at the command line?
On 64 v11 the GCC works, but the compilation does not work, it goes to error, in Development important files are missing, we discussed it with deadwood here:
https://ae.amigalife.org/index.php?topic=881.120
@miker1264
If you ran into problems using GCC for x86_64, let me know.
-
Does TinyAros for ABIv11 have gcc at the command line?
On 64 v11 the GCC works, but the compilation does not work, it goes to error, in Development important files are missing, we discussed it with deadwood here:
https://ae.amigalife.org/index.php?topic=881.120
@miker1264
If you ran into problems using GCC for x86_64, let me know.
I will test it with some small single file applications.
-
ah! in hosted mode there is not the problem
https://axrt.org/downloads-aros
Have you tried compiling ?
--- ITA ----
Hai provato a compilare ?
-
Miker you are working natively or hosted
-
I use VMWare on Windows 7 Pro x64.
Native in VMWare.
-
ok Miker :)
-
@Amiwell
I downloaded the newest TinyAros ABIv11 to test the dev tools.
BTW 225MB is a good download size. I have very limited hard disk space. :)
-
the iso in total does not exceed 800 Mb only the dev tools are 500 mb
-
Fix the iso for usb stick and vm i have changed icon theme with kens v4 and i deleted the development drawer do not works at moment :-\
(https://i.ibb.co/KXMhzg6/tiny-64-2.png) (https://ibb.co/37DdYb1)
http://tinyaros.flazio.com/
-
Available for download with new Deadwood fixes :)
AROS ABIv11 20230430-1 changes:
Functionalities:
Implemented network driver for certain nVidia chipsets (Neil)
Synchronize Zune configuration across all builds (deadwood)
Restore build and functioning on pc-x86_64 AROS (deadwood)
Make native kernel more reselient in case of early error (deadwood, Kalamatee)
Added broadcom4400.device network driver (Neil)
Synchronize on use of ISO-8859-2 for Polish across all builds (deadwood)
First working version of nvme.device is available (Kalamatee)
Implemented FORMAT64 and SEEK64 commands in ahci.device (Kalamatee)
Stabilized handling of WARM reset, implemented missing shutdown handlers (Kalamatee)
Requesters add scroll bars if too much text is shown (Kalamatee)
64-bit support:
Correct size of fpos_t and ino_t C library types (deadwood)
68k support:
ARM support:
muimaster.library (bugs: MUI_Request not compiling) (deadwood)
Restore build of armhf AROS (deadwood)
Updates:
AROS build system (Kalamatee)
libz 1.2.13 (Kalamatee)
libpng 1.6.39 / png.library v53.2 (Kalamatee)
freetype 2.13.0 / freetype2.library v6.6 (Kalamatee)
libudis86 (Kalamatee)
Functional fixes:
Correctly handle __stdiowin when also using C library (deadwood)
gl.library (bugs: race condition during initialization) (deadwood)
hostgl.library (make it work with newer 64-bit hosts) (deadwood)
exec.library (bugs: wrong disassembly due to wrong start address) (deadwood)
ata.device (bugs: media insert/eject detection not working) (deadwood)
muimaster.library (bugs: MUIA_String_Acknowledge not readable) (deadwood)
png.datatype (bugs: 1-bit APLHA pngs not supported) (deadwood)
fat-handler (bugs: partition check too strict) (deadwood)
InstallAROS (bugs: not working with > 2GB RAM) (deadwood)
dos.library (bugs: SFS not working with > 4GB RAM) (deadwood)
C:Install-Grub2 (bugs: not working with > 4GB RAM) (deadwood)
GCC (bugs: sometimes generates non-loadable executables) (deadwood)
Kernel (bugs: wrong configuration of IRQ pins in IO-APIC, TaskReady list damaged) (deadwood)
Area.mui (bugs: events sent when not expected to) (deadwood)
pciusb.device (bugs: EeePC USB boot not working) (Neil)
Register.mui (bugs: tab text cannot be formatted) (deadwood)
String.mui, Area.mui, Cycle.mui (bugs: setting same value is causing notification) (deadwood)
pciusb.device (bugs: too long boot delay on AspireOne ZG5) (Neil)
ntfs-handler (bugs: accessing non existent entries) (Kalamatee)
DiskInfo (recognize more filesystems) (Kalamatee)
pciusb.device (workaround for MosChip MCS9990, detect addtional ports) (Kalamatee)
Kernel (bugs: SSE registers not preserved during interrupt) (Kalamatee)
timer.device (bugs: can issues interrupt after warm reboot) (Kalamatee)
C:Decoration (bugs: wrong rendering of paletted pngs) (Kalamatee)
i8042.hidd (bugs: regression in mouse detection) (deadwood)
crt.library (bugs: wrong time returned by clock_gettime) (deadwood)
Stability fixes:
graphics.library (bugs: boot driver not unregistered correctly) (deadwood)
MultiView (bugs: crash in About window when using amigaguide.datatype) (deadwood)
exec.library (bugs: crash when showing disassembly in alert requester) (deadwood)
Prefs/ScreenMode (bugs: crash on certain drivers) (deadwood)
acpica.library (deadwood)
-
deadwood said he wants to do an abstraction layer to make the system compatible with ABIv0 applications currently there is not much software