Yay!  Now I can prove that it actually is my calculator. 

This

Chatzilla next?

looks great

Looks pretty cool. I always get excited about this kind of thing.

Thanks Me too
So I've been trying to work on the file system to get better support for Directories atm, and it's kind of coming along

BootExe:
; File Header
   dw BootExeEnd-BootExe   ; Size of File
; Executable Header
   db 0         ; Size of Stack needed
BootExeStart:
; End Headers Start Data
   ldrDE(_-BootExeStart)
   call LoadFileToRAM
   if(SUCCESS)
      jp nz, KernelPanic
   ex de,hl
   rDrawWrappedString
   rFastCopy
   call FlushKeys
   call WaitKey
   rEndThread
_   db <0>,0
BootExeEnd:

Hrm, it seems to not parse db "string",0 statements correctly
everything else is great though, maybe add in some highlighting for commands too?

I'm drooling a little right now

Here's a suggestion: When the user holds down the ON button for, say, three seconds, the calculator either turns off immediately after quitting all programs (since RAM clears don't even matter at all), or goes into a "teacher mode" that looks like the TI-OS homescreen.

Umm, I'm not going to do that. I prefer letting people hold on to keep the overlay on as long as possible.
I'm also not going to support all the math functions by default so I'm not going to have a teacher mode. Someone could make a Teacher Mode addition to it if they want and they could add in a patch for the three second thing as well, but I'm going to let people hold the on button as long as they want. Especially since apps that disable multitasking or turn off the system pane need a way for the user to get out of them/ view the pane. Holding on will display the overlay as well as force show the system pane.

Anyways, here is the svn for you guys, feel free to load trunk/build/Rogue.rom into an emulator to see it in action. I would recommend against loading it onto your calc for the time being with the 8xu since it is really useless. If you want to help me work on it feel free to let me know and I can set up a branch for you
http://code.google.com/p/rogueos/

If any of you are wondering what my recent tweets have been about, or what I'm blabbering on about in IRC then let me enlighten you

I have recently been working on a OS inspired by KOS. Rogue has been in the works for a long time but has never really gotten off the ground until recently. RogueOS was originally going to be based on the Knight Kernel, but since I am unable to work with the Knight Kernel due to re-writes, I'm opting for just basing it off of a basic version of the Knight Kernel and working from there.
After making that decision I sat down and wrote out what my goals for Rogue were and here is a somewhat edited version of that original list.
Features

• Multitasking
• App Style programs
• Animated App Switching
• System Pane
• 3 Dedicated screen buffers
• Filesystem
• Power Menu

Multitasking

• Interrupt based
• States
  • 0 - No Thread
  • 1 - Zombie
  • 2 - Started
  • 3 - Running
  • 4 - Interruptable
  • 5 - Uninterruptable
• Shifts through Thread Table in a round-robin manner

App Style Programs

• Specific file structure for each app ( ie: app.exe, metadata, resources etc )

Animated Switching

• Switching between running apps will be animated with a slide in from left/right
• ON+left/right arrows will switch between the running apps

System Pane

• By default a bottom pane will be displayed showing different information
• Info
  • Free RAM ( percent )
  • Current App ( App # / Total running # )
  • Time ( I'm still on the fence about this one )
  • Battery low warning ( only if battery is low )

3 Dedicated screen buffers

• So apps don't have to allocate extra buffers for greyscale etc
• buffers
  • 0 - Main buffer
  • 1 - Back buffer
  • 2 - extra buffer

Filesytem

• Basic FAT style filesystem for now. Possible change to a Journaling system later
• Supports
  • Directories
  • Files
  • Symbolic Links

Power Menu

• Holding ON will bring up the power menu in an overlay ( interrupting any running apps ( so everything goes greyscale ) )
• Overlay
  • Up Arrow - Sleep
  • Down Arrow - Hibernate
  • Left Arrow - Go left one running app
  • Right Arrow - Go right one running app
  • Y=/F1 - Bring up System Menu ( ie: apps and options )
• Sleeping turns off the screen and halts processes, then puts the cpu into a low power state
• Hibernate Backs up the RAM State and turns the calculator off completely

Completed Milestones

• Multitasking
• FAT/Filesystem reading
• Loading Executables/Data to RAM
• LCD Locking for specific threads
• Integrating some of the Knight Kernel features

So right now, I have a working, but limited OS

Oh and before I forget, I am working on this project with a mix of wine, mono, spasm, wabbitemu, wxwabbitemu, make, gedit and os2tools. Right now the building process is aimed for linux, but I could add in support for windows later, when I get around to making an svn for you guys to grab from


( BTW: I'm writing my last Diploma exam tomorrow, so I'm not really active until after it, but I thought I should just post this now for the hype )

whats the nDoom policy?

Please see the first post, it explains it mostly