A benefit of me using version 2 of the .net framework for this program is that microsoft have added some proceedures that help with cpu and memory handling, i.e boosting processes more. For the non-developer people, this means they may help to increase the speed of PearPC!
actually, i got an e-mail today confirming that the new process-thread booster helps with this exact kind of program (or at least the way it is executed).
and again, like magellan said, the intention of making this program was never to speed pearpc up (though through simple research it has), it was to provide an easier link between pearpc and your computer.
i'm using the framework basically as a middle-man between pearpc and your computer. as magellan said, by taking away the need to output everything to the command line window (the heart of a command line program), i've effectively turned the program into an isolated executable. the framework takes the brunt of pearpc's processing needs, instead of directly piling it all onto the host hardware. this, in effect, is a caching exercise, so it goes nicely with the JITC version. By using the garbage collector, coupled with the process booster, i've managed to speed up pearpc by a large margin.
but what do i know.