bb.donnay-software.com

Roger,

I swear I posted this yesterday..

Please read below. I know this is probably an Alaska question, but thought you (and others on the board) may have some insight. This was asked by a hardare tech person for a very large client we have. OIS is our app.

*******
OIS runs in a 64bit environment, we would still like to know if they have plans on coding toward a 64bit program. 64bit software would run much better on a 64bit environment, utilitizing all new technology. Also, OPMenu.exe Uses only 1cpu core when running and never takes advantage of the multiples core chips.
*****

thanks

Fred
Omni

I don't know why you think that Xbase++ does not use multiple core chips.

It is true that it is not automatic, but you can achieve this by using DC_SetCpu().

I don't know the answer to your question about 64 bit.
I will ask Steffen at the conference in October in Arizona.
Why don't you plan to attend?

omni wrote:OIS runs in a 64bit environment, we would still like to know if they have plans on coding toward a 64bit program. 64bit software would run much better on a 64bit environment, utilitizing all new technology.

Steffen always say "it is only 1 switch" in Compiler setting ...

omni wrote:Also, OPMenu.exe Uses only 1cpu core when running and never takes advantage of the multiples core chips.

Xbase++ are limited to 1 CPU and will "hang" if you try to enable Property "all CPU"

as Roger say you can "switch" to other CPU when running., but Xbase++ can not run a Thread on other CPU than "Main"

IMHO Xbase++ Thread are the Problem ( own Workspace, Memvar ) why Alaska still use the old OS/2 Concept.