Too many memory variables

[Geland]

I am using Visual Foxpro 6.0. I bought a new computer which a AMD Sempron 3400+. Everytime I run my DOS app i get an error saying "Too many memory variables". I believe this is because of the CPU usage upto 100% when i run the program. I change the sensivity already under MISC tab of the application, change files = 90, increased physical and extended memory on the app, downloaded tame, but did not fix the problem. Any suggestions? Thanks for the help

 

[Geland]

Thanks Myearwood. But that didn't fix the problem. I wonder if it is physical issue. Never had a problem on this before till i got the AMD's.

 

[cricket]

Turn off hyper threading (HT) if you are running it.

 

[JanBucek]

1. VFP6 is not DOS application. What "DOS" application do you run?
2. Does "Too many memory variables" come from FoxPro or from OS?

 

[Geland]

JanBucek
Im sorry its foxpro 2.6. The error comes from Foxpro not OS. Thanks

 

[DSummZZZ]

If it's foxpro windows, you need to add Mike's line to the config.fpw instead of config.fp.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[JanBucek]

In re 100% CPU usage while running FxoPro DOS app: download

http://www.ezop.cz/sw/foxfree.com

(author tchvatal@ezop.cz) and launch it just before launching FoxDOS app, for example in batchfile. I have tested it in Win2K/XP, it decreases CPU usage down to cca 1-3 %.

 

[tesar]

Geland,
is your config.fp (with mvcount and mvsize)
in current working directory ?
Tesar

 

[Geland]

Tesar,
Yes config.fp is with mvcount and mvsize in current directory and i already increased the size. i have a feeling its the CPU

 

[octavian2006]

In case your appl. is an ".app", and you run "foxpro.exe", try "foxprox.exe" (the extended version).

 

[tesar]

Geland,
list memory to file mymemory.txt
wait wind "See file.."
or simply
disp memo
as first commands, and an appropriate places,
say you if your commands are accepted...
Tesar

 

[tesar]

Geland,
is ntvdm.exe in new identical with older instalation ?
Try change command.com / cmd.exe to run foxpro and see disp memo..
Tesar

 

[dbMark]

As said above, use command.com (the colorful MSDOS icon) rather than cmd.exe (the black icon).

To get Compatibility Mode (right click on icon, select Properties) you should use Command.com not Cmd.exe. Also try adjusting the Idle sensitivity in the Misc tab in Properties and slide it more towards the right, the high setting.

 

[Goofus828]

Geland, try putting a memlimit statement in your config.fpw statement

memlimit = 16384,100,100

This will allocate 16meg of ram to use and the max and min you can use of it is 100%.

Also look for you Config.NT file in the windows\system32 folder. bump up the files from 40 to 100.

All this stuff works for me in FoxPro for DOS - it might work for FoxPro for Windows.