experiment with OC'ing eh? Yeah, ive done it be4.. and its not *that* dangerous. I've even overvolted my gpu to the max which is by default a locked function in afterburner but you can do it . and also that didn't really solve my freezing problem when i played it again after doing it. After it crashed crysis from overclocking too much, I decided to then on utilize benchmarking programs not to benchmark, but to find stability in my overclocking to get it where i need it.

Oh and also about more ram, theres a problem.. My cpu air tower is so big, it actually covers 2 of the ram slots effectively leaving me only with 2 available. Its not the tower itself, but the fans attached to it. Its the corsair A70 cpu tower.

Oh one more thing.. the motherboard i got, it overclocks to 4.2 GHz with a press of a button, so that will be easy if i decide to do this.

I meant more like overclocking can be dangerous if you don't know what you're doing but you seem to be quite skilled in this. For me it is very dangerous when I mess around with my memory clock multiplier ratios because if I don't increase the voltage sufficiently the computer will crash instantly and won't turn back on. The only way to fix it is to reset the bios setting which is a hassle.

And for the ram, these days 4gb often isn't enough especially if you're running games such as Crysis 2. Because of issues with the cooler's size you have two primary options for upgrade. One you could buy a new cooler in which I would recommend one from xigamatek because they are quite effective and take up little room on your mobo (note: they are very tall so check your case size to make sure it'll fit). After that you could then buy an additional 4 gb. The downside is that not only will you be getting rid of your current cooler (something I always hate to do with perfectly functioning hardware) it is also probably the most expensive option. Second plan is that you could buy a pair of 4 gb sticks and put those in place of your current two giving you 8 gb total. An advantage here is that if you later decide to change your cooler, you will have 2 more available slots for future use (16 gb anyone  ). The issue though is that you would still be retiring your once again perfectly functioning 4gb of ram.

We also need to modify the header files from both SDK's to have proper #ifndef blah_h, #define blah_h, #endif statements so that other libraries don't end up being accidently included twice once more third party libraries become available. 

That is very impressive! How many colors are available for shading?

There are 8 base colors to choose from but up to 3 can be combined to create numerous shades. If for example only what shade of blue is used, the result is light blue. Two shades of blue will create standard solid blue and adding a third blue will do nothing. But if you add 2 blues and a red, that creates a dark purple for example. Using some rough math I was able to calculate a grand total of 127 colors but someone else should check this though as it may be incorrect.

Edit: or if you only use 2 shades the total is 36 colors which I've already confirmed

I don't think the syscalls should be organized by number as it has little relevance to its actual use. A good way to have them organized could be by the library file each is stored in such as "display.h". But for the time being I'll see how well I can get the current list filled with important information.

That would really be great if we could get the wiki updated. I believe Jos Juice currently is the wiki admin and controls all of the major changes. In fact what I had in mind for the syscalls page was an organization system similar to wikiti.brandonw.net so that full documentation could be provided for each call. Right now the only syscall documentation is just copied from the .chm and is geared more towards asm coders and provides little insight to those who code in C. What we'll need in the discussion is an explanation of what each call does exactly, what all the args do, the use of the return value, ram locations destroyed, and how to effectively use it in a program.

But then again we aren't as reliant on syscalls for the Prizm as we were on the 83+. So far the only reason why I use a syscall is to draw the screen or depending on the program draw text. But they will become more important in the future as we start experimenting with some of the hardware such as the usb.

cool topic. ++Nerds & ++Geeks //prefix increment for optimization

C++ relies on the existence of the standard lib for the target platform. Since the Prizm doesn't have a fullly [implemented] standard library, not all C++ will compile for the Prizm.

That reminds me, once I can get my first release of Walnut out I need to start working on newlib. On the documentation page there is a list of OS subroutines that newlib relies on, with many of them not being too hard to write. For the more complex routines such as multi tasking, newlib provides default routines that just specify that the feature is missing while allowing all the libs to compile properly still.