Sounds nice. =) Question though, will this emulator require you to dump your own Prizm's ROM, or will it be able to function just with an OS?

To be a true emulator a rom dump will be required, but it looks like some software will need to be written to do that.

Here is a prizm emulator modelling program.
It simply brings up a prizm graphic and responds to key presses - nothing more.
Modeling , is a means of coming up with better ideas or using  features of the model
for the first working prototype.
This program written in Python could easily be converted to a C program using Windows GUI API.

Alright the Prizm emulator is coming along quite well. So far it has support for 18 commonly used instructions with all of them in longword format. These instructions are most of the MOV instructions, Add and subtract, comparisons, and branching statements. Tomorrow I will code a simple user interface in to display the contents of each register. I hope to have the first pre-alpha version out either Saturday or Sunday. The code should compile on all systems.

Lastly I was having some trouble trying to emulate the NOP instruction. Help would be much appreciated because it is way to complex for my puny brain.

[j/k] 

NOP == Nu-Omnimaga-Pron?

j/k I'm glad to hear it's progressing well. Did you have any difficulty getting around the whole virtual memory thing?

I haven't tested it for speed yet, but how it works is when the program is started two dynamic arrays are initialized. The first one is an index of pointers. Every pointer in there represents a 64kb section of ram. The second array is the data in ram. An example of this would be for a write to memory. First the part of the emulator that needs to write to memory would call the memory write function with the syntax writememory(int data = 42, int address = 0x00000005);. Then the memory function would take the address 0x00000003 and see that it corresponds to the 0x00000000 page (pages are all 64kb long). The next step would be to then parse the the first array for 0x00000000. If it exists then the memory function writes 42 to the second array with the syntax memorydata [index][offset] =42. Where index is the index in the first array where 0x00000000 was found and offset is the lower word in data. and if 0x00000000 doesn't exist then it is added to the first array and another 64 kb are added to the second array. This might be kind of hard to understand, but I will have better examples later along with the source for review.

Has anyone figured out how to transfer calc files to this emu? I tried dragging them on the screen but it said invalid file type when I tried dragging add-ins and program files, and when I tried setting the emu in receive mode through the linking menu it said not supported in the emu.

Is it even possible at all? I liked how most TI emulators allowed such thing. It would be nice to make animated screenshots of games

Yeah you won't be able to do that with Casio's free trial.  Their emulator is not a real emulator in that it only emulates the software not the hardware. Meaning you can not add your own files.

Update:
To convince everyone that i'm not slacking off on this project. I am posting the entire project source as of right now. You will notice first off that you cannot compile the code yet because there is no main function. You can however review the code, which I am trying to keep well commented. The most interesting part is "instruction set.h" as it contains the emulated source for each machine instruction. Right now in the code, 9 of the instructions are fully written. 18 instructions (viewable in the source) will be included with the first release (hopefully this weekend). You will also notice that a file called spectrum.cpp is missing. Spectrum will be the official name of the project when I release it. With the first version a user will be able to upload a pre-compiled program (no header) and run that. There will also be a gui (I will be working on that later), that will display the current contents of the 16 registers and the cpu speed. Lastly there really isn't a whole lot left to code before the first release. Enjoy the source for now.  

Update:
Well the pre-alpha of the Prizm emu is finished. The only problem is that I have a pretty bad history with compilers and keep on getting errors that should not occur. Basically the main problem is that my complier, digital mars, does not recognize global variables properly. If someone else wants to help me compile this please PM me.

Alright I am now able to get the pre-alpha compiled to machine code. I just need to debug it before I can release it. The primary issue now is that I'm trying to emulate the SH3 proc which is in big endian mode, but my compiler works in little endian. This has the effect of causing many annoying bugs that can be hard to locate and remove. This isn't preventing me form releasing the first version, but it does slow me down a little.

I'm also now releasing a few details on how the emulator will work. The first version is not meant to emulate the Prizm, but instead only focus on the SH3 for now. This version also runs from the command prompt which displays several stats. Right now it tells you how many instructions are executed per second and the contents of the 16 general purpose registers. As of now the emulator only supports 18 simple instructions. Most of which involve longwords. The reason for doing this was that I wanted to release the emulator in only small steps. That way we could check that everything works perfectly before I move onto the next segment. Release 2 will feature mostly the same instructions, but with support added for bytes, words, and immediate data. For now though I only want to focus on the current 18 instructions which I will list with the release. When the emulator starts it will load the contents of "spectrum.data" into 0x80000000 on the memory. There are 2 bonus instructions to be used as well. One is (end 0xFFFF) which tells the emulator to stop and quit and (pause 0xFFFE) which pauses execution. For now they are included as standard instructions, but will later be implemented outside of the code.

Future releases will include a full gui that will help with hacking and development. In addition to a fully click able Prizm model there will be real time disassembly, display of memory contents, and stack along with numerous other tools. I am also planning on creating an easy to learn scripting language that will allow users to create their own tools to be run alongside the emulator. The scripting language will allow you to create ui objects, access the Prizm memory, access keyboard inputs, and even allow you to create your own variables with control loops and arithmetic.

If you have any questions, suggestions, criticism, or you want to  tell me I'm an idiot  I would love to hear from you.