Aros/Developer/Docs/Devices/AmberRAM

Navbar for the Aros wikibook

Aros User

Aros User Docs

Aros User FAQs

Aros User Applications

Aros User DOS Shell

Aros/User/AmigaLegacy

Aros Dev Docs

Aros Developer Docs

Porting Software from AmigaOS/SDL

For Zune Beginners

Zune .MUI Classes

For SDL Beginners

Aros Developer BuildSystem

Specific platforms

Aros x86 Complete System HCL

Aros x86 Audio/Video Support

Aros x86 Network Support

Aros Intel AMD x86 Installing

Aros Storage Support IDE SATA etc

Aros Poseidon USB Support

x86-64 Support

Motorola 68k Amiga Support

Linux and FreeBSD Support

Windows Mingw and MacOSX Support

Android Support

Arm Raspberry Pi Support

PPC Power Architecture

misc

Aros Public License

References

if you direct your attention to the generated 'amberram_start.c', the 'InitHandler()' routine:

AmberRAM reverted to %build_module_simple. Reasons are:

1. It doesn't need to be added to FileSystem.resource - 'dosnode' handlers are no longer added to FileSystem.resource. Mixed handlers (ie if you wanted to have a built-in NFS network boot system, DOSTYPE=AROS_MAKE_ID('N','F','S',0) and DOSNODE=NFS) are now possible.
2. It can be initialized after dos.library and add DosNode directly. Yes. Note that expansion.library's AddBootNode() will operate correctly both before and after DOS initialization.