However, the length of these files cannot change, since this map has no real knowledge of the file system. Some basic C functionality is included in these libraries, libstdc, and libsolo. A circular message buffer is kept of all output, and designed to survive many types of system traps, including CPU reset in many cases. Since it tells the program it loads what physical memory it can safely use, it can run well-behaved programs and still allow the programs to return back to the OS that called them. This is not, of course, its intended purpose, but the interface could support this if someone wanted to implement it.
SOLO can co-exist on the same partition or floppy disk as another operating system.
SOLO can become your new master boot record, and be used to boot everything else on your machine, or it could just exist in a partition, to be loaded when you select it from your main boot selection program. Or, if you prefer not to touch your hard drive, you could just put SOLO on a floppy, from which you can still use it to boot from any partition your hard drives. Since your 32-bit programs start right up in protected mode, there is no need for your kernel or standalone utility to worry about the details of switching from real to protected mode. Also, paging is already enabled when the program starts, so that you can just link your kernel at the address you want it to run at, and SOLO will map it to that address before executing it. From there on, of course, your kernel can remap memory as it sees fit.