OurOS

First i was wondering how systems (PC) get an auto start once the power is switched on.. Later i found it was the crime made by bootstrap loaders. These things are on the micro controller which initiates the start of OS on RAM.. That was wierd for me and it is still (lol...;))... So i took few steps to see how the bootloader scripts were...and if people are intrested in creating your own OS they definitely have to spend a quite an amount of time in banging their head against wall in writing the final bootstrapper scripts... not that difficult... if you have already completed your OS then you wont find it much difficult...
You can survive if you know C, C++ or Windows programming...
Boot system: This system is used to boot your microkernel OS
Boot entry- expected fields
Be_name – char, Be_offset – unsigned int, Be_type – unsigned int, Be_size - unsigned int, Be_vsize - unsigned int, Be_extra0 – unsigned int, Be_extra1 – unsigned int, Be_extra2 –unsigned int, Be_extra3 – unsigned int
File description should be present describing what are the files to be loaded while booting
The bootmaker util reads description file that looks like
[bootstrap] /* BE_name
type=boot
file=boot/boot.bin
ventry=128

[kernel]
type=code
file=kernel/kernel.bin

[namer]
type=code
file=srv/namer/namer.bin

[console]
type=code
file=srv/console/console.bin
Each entry must be a valid type and valid file to load.
So the file path mentioned should be present in the boot directory.
SYNTAX: Bootmaker <{description_file}> <{boot_image_file}> [-floppy]
Above mentioned is the command to run the bootloadstrapper.