my name is Georg Wittmann (formerly Hoermann), the programmer of Amiga anti-virus software VirusZ and xvs.library.
I want to fix my programs to work on AROS (at least m68k) and need the following questions to be answered as I didn't find information about it in the SDK:
1a. Are the m68k ROMS always fixed at $f80000 and $e00000 or can they be located somewhere else e.g. using AROSBootStrap (doesn't work on my WinUAE to be tested)
1b. How can I determine the location and size of the ROM(s) (I found out that there are MemLists called 'Kickstart ROM' in Execbase's MemList, but is this the official way? At least ArosInquireA() doesn't give a result for AI_KickstartBase and -Size.
1c. Can there be more than two ROMs or can there be parts of it in other memory areas (like 'ROM Updates' for AmigaOS 3.5/3.9)?
1d. At offset $c/$e from the beginning of my ROM, we have two UWORDS holding version 46.12. Is that value really used by AROS or just there to be Amiga-compatible as all AROS ROMs I've found have this same value?
2. Although I have chip.memory in WinUAE from $0-$200000, and AROS creates a MemList entry for this, MaxLocMem in ExecBase is 0. Is that a normal behaviour? Is MaxLocMem always 0 inside AROS? Or does that indicate something?
3. Does AROS link ResModules using bit 0 instead of bit 31 on m68k-machines, too? Or only on other machines?
Thanks in advance!