AROS builtin ROM and memory allocation

[leonard]

Hi,


Seems that LDOS demo doesn't properly boot if using AROS builtin winuae ROM, saying the demo needs more memory. After investigation, it seems AROS report very low amount of "free" memory at boot time. In LDOS bootsector I'm doing that:


here what happen on a 512KiB chip + 512KiB fake configuration machine:
(again, I'm talking about bootblock time)

 

        move.l    #(MEMF_LARGEST|MEMF_CHIP),d1
        jsr        _LVOAvailMem(a6)
        move.l    d0,m_chipSize(a7)     ; KS & AROS report around 500KiB
        moveq    #MEMF_CHIP,d1
        jsr        _LVOAllocMem(a6)
        move.l    d0,m_chipStart(a7)

        move.l    #(MEMF_LARGEST),d1 ; "any" ram request
        jsr        _LVOAvailMem(a6)     ; KS reports about 500Kib, AROS reports 0x18 bytes!!!!!!

Anyone knows why AROS reports less than 1KiB of free "fake" ram at bootblock time? ( some demos doesn't boot on AROS because of that too )
Is there a legit "AROS" way to workaround? (I can alloc available bytes, then align the returned address to 512KiB, and "test" if there is at least 512KiB by read/write at 512KiB-2bytes, but if there is a better way on Aros feel free to share)

( note: I just tested some bootblock amiga demos like "Planet Rocklobster, Rink a dink Redux and EON, and none of them are working on AROS with 512+512 config )

[AMIGASYSTEM]

The ROM integrated in WinUAE is not up-to-date, we have already discussed this HERE