OSDev.org

Hi, I'm a new guy and I wanted to show my os.
It doesn't do anything useful but it works
It's called Annie, yep i know it's dumb to give your project a girls name.

An 1,44 mb floppy is provided here

There are a few commands:

• time
  matrix
  display info
  display tux
  display test
  debug

Works for me in bochs and qemu as long as they have 32 mb mem.
In VirtualPC the whole thing freezes after you entered one character, no idea why?

I currently dont have an emulator installed yet as I just reformatted my PC. It's not bad to give your OS a girls name, IMHO it's better than naming it with a suffix of OS (crapOS, blahOS, etc...OS).

yep 01000101 (45h or 69? )
OS suffix, for sure, it is boring to see always simple programs named OS.
and mostlly, the suffix OS is really something to avoid. it is a lack of imagination.

Annie. yeah! why not.

But it maybe the only way to get a good google rating or your own domain.
Eg: see how many Dex there are .

Well, instead of commenting on your project's name, I actually tested your OS .

When I first start it, it shows a blank line near the bottom of the screen. I didn't know what to do, until I realized this was the console.

Tried typing in random words - they just print, nothing happens on enter. Backspace doesn't work.

The commands you gave us work properly (time prints out the time, display tux prints out an ASCII image of Tux)

I noticed that the output is printed before the actual command - it would print "This is a test" and then it prints "display test".

It seems like a good start (I mean, I haven't gotten to the shell stage yet!). Is the shell in kernel mode or actually a usermode task?

Hope you continue OSDev!

Edit: For some strange and inexplicable reason, typing just 's' or 'e' causes your OS to triple fault...

Edit: For some strange and inexplicable reason, typing just 's' or 'e' causes your OS to triple fault...

Actually, any single letter typed and then enter cause a triple fault.
String Handling?
Keyboard Input?

-JL

Well, for me, typing other single letters like 'q' and 'h' didn't triple fault. Strange...

The shell is actually the keyboard driver who did overgrow itself a bit
not really sure why it triple faults, has something to do with the routine that searches mem for the program to run I think