If there is no custom boot block, then dos.library has its own method of initializing and using the filesystem to continue booting. It is noteworthy that the custom code can choose whether or not to use the filesystem driver from Kickstart, or just do I/O via the vice and have data and code stored on the floppy based on its own bespoke track/sector layout. The boot block code can use the vice to continue loading and booting custom code, which is what most games will do. If it finds a boot block, then it loads it into newly allocated RAM and jumps to it. If it does not find a custom boot block, then it jumps into the Kickstart dos.library, and you boot into a shell. Floppy boot starts by searching the first two sectors of the disk for a "Boot block". If the trackdisk device driver detects a floppy in drive DF0, that is the default highest priority, so the Amiga will boot from floppy. After I/O and expansion devices have been enumerated and initialized (including any expansion ROM they contain, which provide more libraries or device drivers), Strap takes over bootstrapping.īootable disk devices have already been enumerated by Kickstart, and Strap's job is to boot a DOS from the highest priority bootable disk. One of the modules is Strap, as in Bootstrap. The Amiga Kickstart ROM is made up of numerous modules, libraries, and device drivers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |