This conversation has not been ignored. I have been simply been talking with Roger by E-mail rather than visiting this bulletin board. And at the same time I have been doing some forecasting Web site page development work and talking with international researchers about the development of a nonprofit foundation that could dramatically move our world forward by getting some structure and organization into international scientific and medical research efforts.

Perl is being used simply because it will do anything computer and Internet CGI program related that you can imagine including feeding Windows information as if it the inforamtion were entered using a keyboard or mouse. It can also read and respond to a real keypress or mouse action as if it were Windows. And it can create .exe versions of itself. So the actual Perl compiler is not needed on the computer. It is apparently stored inside the compiled .exe program.

The main problem here is that Perl does not do calculations very fast. So, some other program such as TrueBasic or perhaps XBasic or FreeBasic or Fortran or even Python might be used for that. I don't care what program is used and am willing to learn any of them. But they need to be able to work with both Windows and Perl. And TrueBasic will only work with both of them for simple applications. Otherwise it hogs all of the processor time.

Perl is not a processor time hog. If you put a "sleep 2" statement into the program it truly goes to sleep for 2 seconds and doesn't use any detectable amount of processor time while it is sleeping. But no matter what you do, TrueBasic uses 100% of the processor time. FreeBasic is if I remember correctly not a processor time hog and it sounds like XBasic is also not a processor time hog. But Roger in the past refused to work with anything other than TrueBasic. So, if he is going to help with these efforts then they need to involve TrueBasic.

Something that he suggested that I had not thought of is that a TrueBasic program can be told not to hog the processor time by Windows Task Manager. And using that apporach is fine with me if it will work. I told Roger that if he wants to check and see how well that approach works then I would be happy to move in that direction. Perl can automatically direct the Windows Task Manger to change the priority of a TrueBasic program.

Another approach is to install some type of program that makes a single core system look like a dual core or multiple core system. One of my single core systems had that type of program on it when I bought it used. And TrueBasic can probably run on that system and hog 100% of one of the virtual cores while the other virtual core runs foreground programs. However, I don't know if that type of program is generally available. As I said, it was already installed and running on my single core system when I bought it. But that is a second approach to dealing with the TrueBasic processor time hog problem.

Yes. That particular single core computer normally runs at half its normal speed because of that "virtual core" program. However, it does have the advantage of being able to run multiple programs without having them interfere with one another.