Thanks, I was wrong about the patch..
No problem. I thought i mentioned it because stating otherwise would not be entirely correct
.
Whether or not that fixed or did not fixed the issues as experienced on deadw00ds distro, i have no clue as i haven't checked yet.
I show with screenshots how it looks in practice. I usually don’t give a virtual machine more than 1 GB and discovered it by accident. To doubt is right. Let's take a look.
...
Thanks, but i did know that already
What i was trying to say is that 32 bit AROS is limited with regards to memory allocation, if only for the fact that it can only address 2^32 (4gb) at the most. It is simple physics. afaik AROS does not offer PAE support. Windows suffer from the same limitation(s), sometimes limited in software, sometimes limited by hardware (there are specific versions of Windows that are not allowed to be installed on hardware that allows to address more than 4GB of memory).
I can't remember what exactly is the reason for the 3GB limit, but it has been there for ages. Most likely some of the additional memory is reserved/allocated for system use, but i do not know the exact details. Of course the 64-bit version of AROS does not suffer from restrictions such as the 2^32 limit.
Therefor it has no use whatsoever to allocate more than 4GB memory to your VM for running the 32 bit version of AROS, or for that matter expecting a ginormous ramdisk to be present when you boot AROS 32-bit on your 8 GB memory equipped machine. It will simply be capped.
And the other thing i was trying to point out is that the 64 bit abiv1 version of AROS divides the memory between chip and fast-ram (at least that is what the OS reports) while the 32 bit abi-v0 version of AROS does not. There are technical reasons for that, but those reasons elude me atm.
Long ago, follow here:
...
Ah, i seem to have missed some of your reports. Thank you for having filed those (and showed me where they are).
