An operating system is responsible for several tasks. These tasks fall into the following broad categories:
1. Processor management -- breaks down the processor's work into manageable chunks and prioritizes them before sending them to the CPU.
2. Memory management -- coordinates the flow of data in and out of RAM, and determines when to use virtual memory on the hard disk to supplement an insufficient amount of RAM.
3. Device management -- provides a software-based interface between the computer's internal components and each device connected to the computer. Examples include interpreting keyboard or mouse input or adjusting graphics data to the right screen resolution. Network interfaces, including managing your Internet connection, also fall into the device management bucket.
4. Storage management -- directs where data should be stored permanently on hard drives, solid state drives, USB drives and other forms of storage. For example, storage management tasks assist when creating, reading, editing, moving, copying and deleting documents.
5. Application interface -- provides data exchange between software programs and the PC. An application must be programmed to work with the application interface for the operating system you're using. Applications are often designed for specific versions of an OS, too. You'll see this in the application's requirements with phrases like "Windows Vista or later," or "only works on 64-bit operating systems."
6. User interface (UI) - provides a way for you to interact with the computer.
A. The BIOS attempts to access the first sector of the drive designated as the boot disk. The first sector is the first kilobytes of the disk in sequence, if the drive is read sequentially starting with the first available storage address. The boot disk is typically the same hard disk or solid-state drive that contains your operating system. You can change the boot disk by configuring the BIOS or interrupting the boot process with a key sequence (often indicated on the boot screens).
B. The BIOS confirms there's a bootstrap loader, or boot loader, in that first sector of the boot disk, and it loads that boot loader into memory (RAM). The boot loader is a small program designed to find and launch the PC's operating system.
c. Once the boot loader is in memory, the BIOS hands over its work to the boot loader, which in turn begins loading the operating system into memory.
When the boot loader finishes its task, it turns control of the PC over to the operating system. Then, the OS is ready for user interaction.
What if you had a floating point program on the hard ware that used sub-processors to take of 1-6 incorporated on the bios. With a floating point program run by sub processors that should free up the main processor for just programs and math co processors for graphics. But this Is what Amiga did with it's multicore system to a small degree. With integration getting smaller and smaller an all in one chip would handle most of the smaller task with advanced AI to cordinated lesser floating point programs running on sub hardware.
Cooperation with subprograms might run some of this independently or by coordinated Artificial intelligence as floating point programs like the brain might run heart and lungs automatically. The goal is to free up the main processors and graphics or math co processors for task and more important programs.
Why do this at all? Because the Bits don't matter through multiplexing or monoplexing that data can be made to any size deph only processed in chunks or to make complex bits that are in multi step or more than one bit group in one cycle. That is for monoplexing 32 bit processor does 4 (8 bit )instructions per cycle or 2 (16 bit) per cycle or 1 32 bit instruction per cycle. Though this may be referring to the pieces of information that a chip manipulates it may be more in millions of instructions per second. The point is a 8 bit computer could be configured to any bit depth by multiplexing or super accelerated by monoplexing on larger chips. Sorry if I can not explain it any better.
This may be better suited for quantum computers and interconnected optoelectronic hardware connections. I doubt anyone would know where to begin how to do this all on one chip. Sorry for being odd or nutty.