Page 1 of 1

MajOS microkernel 0.6.6

Posted: Sat Feb 24, 2007 4:03 pm
by majo
Today, I released version 0.6.6 of MajOS micro kernel.

status: unstable
languages: C, assemly
type: micro kernel (drivers not yet separated)
platform/mode: x86 protected mode
kernel: GDT, IDT, IRQ, PIT, exceptions, software interrupts, kernel memory allocation, timer, software based sheduler, tasks, threads, paging(basic), kernel api, binary loader (pseudo)
drivers: clock, speaker, video, VGA, keyboard(PS2), mouse(PS2), harddisk(IDE)
GUI: yes (very simple)
compiler: gcc/djgpp (windows: extra package / linux: get djgpp cross compiler packages from the internet)
emulator: qemu (windows: extra package / linux: distribution specific)

Project opening: http://www.osdev.org/phpBB2/viewtopic.php?t=2798
Download: http://sourceforge.net/projects/majos

Posted: Thu Mar 08, 2007 10:45 pm
by piranha
How do you get it to compile under linux?

i have gcc, ld...etc

not working on bochs

Posted: Fri Mar 09, 2007 11:47 pm
by kubeos
Hey,

I tried image.bin in BOCHS and it just kept resetting, not sure if it even made it past the bootloader... maybe the image.bin isn't what I'm supposed to be using?? Maybe later I'll try on a real machine..

Compilation on Linux

Posted: Sat Mar 10, 2007 1:25 pm
by majo
I started to develop my os on windows with djgpp (gcc for DOS).
I tried to compile it with the linux native gcc, but there was a problem with different output formats together with linking.
So, I downloaded a djgpp port for linux, which works for now.

I will post the link to the following binary rpm packages if I can find them:
djcross-binutils-2.16.1-3.i686.rpm
djcross-gcc-4.1.0-2.i686.rpm
djcrx-2.04pre-4.noarch.rpm

May be you could also try to find another solution.

Thanks for your feedback!

MajOS on Bochs

Posted: Sat Mar 10, 2007 1:25 pm
by majo
The image.bin (btw, it's a floppy image) was only tested to run with qemu for now.
I also had some problems with other (virtual) machines.

Second, I did not test the os on real hardware for a long time, especially the harddisk driver!

At the moment, there is a temporary solution using a complete harddisk image to load an executable.

I would not recommend testing it on real hardware, but on qemu, for the above reasons.

Thanks for your feedback!