What do you mean?  Users won't have access to the RAM, if that's what you mean.  That's just stupid, and TI should have never done it.  Put valuable user data in a place that is wiped everytime the calculator crashes or the power is lost?

O_o you believe what?

Oh.  Well, programs will have as much RAM as the calculator can provide, minus a few hundred for the OS.

I'm not sure.  If programs call RequestFullAccess, then they get *all* of the RAM.

O_o you believe what?

  ninja'd

Update
Program loading now works almost completely, I'm going to work on the tasker later today, after band camp.

Cool!  This project is going quite well!

RAM
You can use SMC, but not writeback.

Update
KnightOS made a major stride today - relative address loading.  At runtime, a program has no idea where it will end up in RAM, and therefore cannot correctly load relative pointers, or perform relative jumps or calls.  I just implemented kld, which has the same syntax as ld, but it calls a system routine that adds the program's RAM offset to the specified address, and uses SMC to modify the executing code so that it only needs to run the system routine once.  It's pretty awesome.