Error 1809 - FPW2.6 in XP PRO

[jsams]

I am getting and FPW2.6 error 1809 ("FoxPro has run out of memory trying to process your SELECT command"). I have NEVER encountered this error in this code before under W95 or W2K. This particular base code procedure is in use in 15 other applications. Hardware in use: PII, 450mhz, 128mb ram, running Win XP SP1.

This application is and has run without error for years on Win95, W2K, and now trying to run on XP box. Thought it might have been a SP2 problem, uninstalled SP2 back to SP1, still a problem.

Have also noted that a particular disk intensive table search is taking 2-3 minutes. Same program running on W2k takes 3-7 seconds. Have run with XP Firewall on/off, no difference.

TIA for any help or suggestions,
John

 

[DSummZZZ]

Start by checking your drive space and permissions. Especially in the application's default, temp or sortwork directories, wherever they may be.


-Dave Summers-

Even more Fox stuff at:

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

 

[dbMark]

Also make sure any agressive AV programs are ignoring access and changes to .DBF and the other FoxPro file types. Also, see if using command.com rather than cmd.exe makes a difference. Command.com is the colorful MS-DOS icon that has some compatibility settings in its properties, just in case that's part pf the problem.

Are other programs taking up the memory? If so, might that be forcing some disk caching for virtual memory?

 

[jsams]

Dave: Checked permissions and have full access both on C: drive and network area's in use. Plenty of free space available.

dbMark: Will re-check Norton Corp AV in use, but its same setup as used on W95 and W2K machines. This is FP2.6 for Windows so I don't think the Command.com makes a difference, not using DOS window to execute. Nothing else running while testing. Check of Task monitor CPU/Network acitivity shows about 20-30% utilization, rest is idle. But the network activity is almost a solid line of activity. Switch back to W2K box and response is back under 10 seconds for same test.

Thanks for responses
John

 

[bobmpalmer]

John

It does depend on the memory configuration on your system. From what you are saying 128MB is installed however XP needs this as a minimum to perform properly meaning that FoxPro is using (more than likely) your Virtual memory, hence the abundant disc activity. If you are using 32bit extended version of FoxPro it will use as much memory as you can give it.
You can check Memory using SYS(1016) amount of memory used by all objects in foxpro The defined objects include: user-defined windows, menu bars, popups, memory variables, arrays, OPEN TABLES, files opened with low-level file functions and so on.

And SYS(1001) which will return the total amount of memory available to the FoxPro memory manager.

Check if you have MEMLIMIT value in yr config.fpw Foxpro by default only allocates 1.5MB!! as default.


Heres an extract from a typical config.fpw we used
EMS=ON
MVARSIZ=64
MVCOUNT=2096
FILES=99
BLOCKSIZE=64
MEMLIMIT=30,4096
Syntax is <%of available Mem,Minmem inKb,Max Mem in Kb> though we never defined Max.

In general the more memory available the better FP performs





Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[jsams]

Checked the memory in the computer and found that one of the 128M simms was evidently not seated, computer now registering 256M, but problem still persists. Really wasn’t sure how much RAM was in the computer because I didn’t set it up.

Checked CONFIG.FPW file and that shouldn’t be a problem. Listed below is the file we have worked out and has been running for years on our development machines as well as the clients:

MVCOUNT=65000
FILES=250
MEMLIMIT=90,8192,16384

Haven’t had a chance to install the SYS( ) procedures to check memory but hope to do that later today. Having to switch kybd, mouse and monitor is a pain!

Thanks all for the help and suggestions.
John

 

[jsams]

I finally got it working. I discovered I didn't have a MEMLIMIT parameter in the CONFIG.FPW I was using. When I installed the one shown in my previous message, things really got squirley. The WAIT WINDOWS I was using to display the SYS() memory checks quit working among other problems. Apparently, XP does not want a third parameter on the MEMLIMIT spec. Definitely a memory allocation problem.

I installed the two SYS() procedures in the program and ran under both W2K and XP. Found Foxpro was using about 600K+ for the objects (W2k & XP) and the Foxpro memory manager had 10Mb+ in W2k, but only 1.3Mb in XP. When I removed the 3 parameter on the MEMLIMIT, the the memory came up to 10Mb+ in XP like it was in W2K and all my problems went away! Final CONFIG.FPW setup:

FILES=250
MEMLIMIT=90,8192

BTW, FoxPro 2.6 and VFP both work just fine in XP Pro with SP2 installed.

Thanks Bob for pointing me in the right direction and thanks to all who replied.

John

 

[bobmpalmer]

My pleasure John,

I must admit I did think about the third parameter on MEMLIMIT but just dismissed it, DUH! tho you'll notice I don't have a third parm in my config. Never mind.

Glad u sorted it and all is working.

Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[dbMark]

Unless I'm mistaken, FILES=225 is the highest value you can use in config.nt since 30 file handles are already allocated by Windows as the default.

30 + 225 = 255 (Windows' maximum)

From within FoxPro there may be a similar limit, as I know work areas are limited to 225, but I could be wrong...

dbMark