George Wittmann (Former Hörmann) is back to make changes to VirusZ and xvs.library, but George needs your help.
George writes: After 15 years of doing absolutely nothing on my Amiga, and many people asking me again and again if I would like to release the sourcecodes of VirusZ and xvs.library, I now have decided to do so... But before that, I finally want to fix VirusZ and xvs.library for MorphOS, AROS and AmigaOS 4.x systems, and therefore I need some help as I actually don't have any of these systems (only AROS inside WinUAE as m68k version).
So this is why I've written this small tool here. MAA4SIC just collects information about your system and dumps that to your Shell window. Just redirect the output to a file and send it to: schorsch.wittmann@gmx.de
If you are running on MorphOS, AROS or AmigaOS 4.x MOS/AROS/AOS4 System Info Collector tool
Ok just received another mail from him, probably some extra info about installed memory needed aswell
Quote:
Thanks for the old and new report, AmigaOS 4.x seems not ot use MemList in ExecBase any longer as there's unfortunately no list of memory after the ResModules in your report
Do we have any other system info tool on your Amiga that can show a list of installed/available memory?
Thanks for the old and new report, AmigaOS 4.x seems not [to] use MemList in ExecBase any longer as there's unfortunately no list of memory after the ResModules in your report.
The OS4 memory system doesn't work that way any more. You can't just interrogate ExecBase to find out the limits of physical memory (ExecBase is no longer open to the world), and you can't access any part of system memory using physical addresses anyway, since it is all relocated to virtual addresses for each task.
Only the kernel's memory system knows where everything is and it's not telling - you don't need to know.
You could probably get the size information from U-Boot before AmigaOS is booted, but once the system is running, you won't find memory at those addresses and your task will just crash.