NeoGPC v1.1.0 - (11/9/2013)

[Flavor]

Keep in mind that RACE! was mainly developed to run on a single-application handheld platform. When it is running, it assumes that nothing else is important.

There are some places in the emulation that wait for things to happen. In particular, I can think of a main emulation loop that tries to emulate clock speed by waiting until the right time to execute the next set of operations. What I don't recall is how this loop is implemented. I think there were different versions of this. On a multitasking OS, you would not want to do something like this pseudocode...

while(it's not time for the next operation)
{
check what time it is
}

Essentially that would just keep checking the current time until the proper time is reached. This sort of thing should probably be changed to something more like.

if(it's not time for the next operation)
{
waitTime = calculate how long until the next operation
sleep(waitTime)
}

I don't know what state the code is/was in. Even if the main wait is already written like the second version, there may be other places that aren't releasing the CPU when they're not doing anything useful.

I'm not really telling you this as a coder, Cthulhu32. I'm more mentioning this generally to anyone reading.

Oh, and yeah, I have some bundles ready. I think I have 2 that are pretty much ready to ship. After that, I have about 6 more that just need a bit more soldering and testing.