number of work areas in foxpro.exe

[themasedog]

I have been troubleshooting the age old NTVDM.exe memory leak. I've modified the config.fp file, config.nt file, the registry and tried 3rd party apps (tame.exe) but none of it works (windows 2000 server.) I even tried windows NT 4.0-TSE (for DOSKBD) but still no luck.

I then tried executing foxpro.exe instead of foxproX.exe and my memory was great but my app seems to be maxing out the available work areas.

I know foxproX supports about 225, what about foxpro.exe?

I feel like I've tried everything, but any suggestions for running my app w/foxpro.exe or throttling memory w/foxprox.exe would be greatly appreciated.

Thanks!

 

[ramani]

The best way is to have the high memory available and use Foxprox. This will really zoom the performance.
You have to put in the config.sys file
DEVICE=c:\windows\himem.sys
and dont use EMM386. If you change the config.sys, you have to restart the computer to have its effect.
If you are using NT, modify the config.nt file for above. Also in NT you can modify the PIF fil to provide for himem.
Hope this is helpful to you. ramani :-9
(Subramanian.G)
FoxAcc
ramani_g@yahoo.com

 

[themasedog]

This is what was already in my config.nt.

dos = high, umb
device=%SystemRoot%\system32\himem.sys
files=150
shell=%SystemRoot%\system32\command.com /e:2048

It seems to be ignoring it as well as any .pif changes I try. I know I want to run in FoxProX, but as far as FoxPro.exe goes, just how limited is it? I fired it up and I couldn't even modify my project w/out getting 'insufficient memory.' Is that right? The .pjx is approx. 128kB and the .pjt is approx. 2200kB.

 

[rgbean]

I just created a link (.LNK) file under NT 4.0 SP6a, with the following:

Program Tab:
Foxprox.exe
Cmd line: D:\APPS\FPD26\FOXPROX.EXE -cc:\fpd26\config.fp -t
Working: D:\APPS\FPD26
Batch File:
Shortcut key: None
Run: Normal window
(checked) Close on exit

Memory Tab:
Conventional memory
Total: Auto
Initial environment: Auto
(no check) Protected
Expanded (EMS) memory
Total: None
Extended (XMS) memory
Total: 0
(checked) Uses HMA
MS-DOS protected-mode (DPMI) memory
Total: Auto

Screen Tab:
Useage
Window

Window
(checked) Display toolbar
(checked) Restore settings at startup

Performance
(checked) Fast ROM emulation
(checked) Dynamic memory allocation

Misc Tab:
Everything checked but QuickEdit (disabled) and Exclusive mode.

I only have the following in my config.nt:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=99


I don't seem to have a problem opening a 2,465KB project (.PJT) file that compiles into a 4,600KB .EXE. It's a X-Platform app that also opens just fine in FPW.

Rick

 

[tesar]

If RAM your computer is greater than 256 MB,
reduce it.

 

[rgbean]

I'm not so sure that tesar's comment is relevant under NT - I'm currently running 392,628KB physical memory. However in my CONFIG.FP, I do have this line:
MEMLIMIT = 80, 2048, 16384

Rick

 

[tesar]

Excuse me, please.
Limit 256 MB is not my own experience.
Before time i read in net about trouble
with VFP 3.0 and increase memory.
Short circuit in my brain,
VFP 3.0 disappear,
and i wrote nonsens above ...
Thanks Rick for warning.

 

[rgbean]

You're right, see

http://support.microsoft.com/support/kb/articles/Q137/8/09.ASP

- FIX: Insufficient Memory on a Computer That Has 512M of RAM. But as you say this was only for the original release of VFP 3.0 and it was fixed in 3.0b. (But of course the question was about FoxPro DOS 2.5/2.6. <g>)

Rick