OSDev.org

Hi

Release 0.1.2 of my hobby OS Mojo is ready. I have implemented all features
and fixed all the bugs mentioned in the discussion about the previous version.
I have also implemented some more items from my todo list and found and fixed
a few bugs. Everything is nicely on schedule for the next major release in
February

Please test it and let me know if you find any bugs or weird behaviour. I am
especially interested in results from booting on a real pc. All your feedback
gets top priority.

You can download floppy and ISO images from http://softwarewizard.dk/mojo/.

New features:
- Driver interrupts handled by simple VM instead of x86 handlers
- IRQ VM assembler
- Kernel timers: will send a message to user processes at fixed intervals
- Tetris game (uses timer)
- Supports both English and Danish in console and keyboard
- Keyboard handles all keys
- Tools to generate code pages and key mappings
- Nice startup screen and panic screen
- Lots of minor improvements

Old features:
- Micro kernel
- Preemptive multitasking
- Partial asynchronous IPC
- Simple shell and simple GUI applications
- Follows standards (libc, STL, POSIX)
- Good test coverage

Merry Christmas

clange

Just tested using the .iso from your site on my OSDev testing machine #1 (see link below). I get the following panic right after GRUB loads the modules and the kernel starts:

PANIC: kernel::memory_init::calculate_physical_memory_info() => Weird memory size

I have to say though, very nice panic screen.

EDIT: Tried again with only 1 stick of RAM (256MiB), and I get the same error.

The way I calculate the memory size is (too) simple. It is really one of the weak spots with regards to running on real hardware. I have written a small DOS tool to dump the BIOS memory map to a file so I can inspect it - I just have to polish it a bit. When I'm done I would appreciate if you could run it and email me the dump file. That way I can easily debug the problem. I have moved this to the top of my todo list and will post here when it is done.

Yeah I like the panic screen too - I thought that since I see it quite often it should at least look nice.

Thanks for testing.

Unfortunately I don't have any OS installed on my test machine, and it doesn't have a floppy drive, so running a DOS-based tool is going to be difficult.

I have compiled a version which prints the memory map. That will provide all the needed information. It can be downloaded from here http://softwarewizard.dk/mojo/index.php?page=download (version 0.1.3 alpha)

clange

Nope, I still get the same kernel panic as before.

Does it print a memory map? If it does could you please provide it to me.

Tested it on Virtual PC and I didn't mange it to crash (except with the double faule thingy).
I looks very cool. Keep up the good work.

No, it doesn't print out anything. It just gets straight into the kernel and panics, doesn't show anything else. The memory map might flash up for half a second, but that's it.

Hi cyr1x

Nice to hear that it also works on VirtualPC. It has been quite a while since I have used that as a test target. And thanks for the encouragement.

clange

@JackScott:

I have uploaded another version. It should print the memory map provided by GRUB or print no memory map found. here is a screen shot of what it look like in Bochs except the panic message should be different

Nope. Using the 0.1.3-alpha ISO image from your site, I still get the same as before: completely red panic screen, "Weird memory size" error.

D'oh, I disabled the panic screen the wrong place. I have corrected it and this time I have also tested it correctly.
[EDIT] Well i didn't do it correctly after all

But thanks a bunch for testing - it is really cool that I can upload something to my page and a few hours later a guy (literally) on the other side of the earth helps me test it. Amazing experience

No worries. Unfortunately I'm still not having any success with the latest image pulled from your site, it still panics to the red screen.

Now the kernel will not switch VGA start address and will halt right after the memory map dump. I have downloaded the image from the homepage and tested that (I did that before too - but to no effect).

If this doesn't work I have no other choice than to blame Santa's elves for messing up the packages on the network