FPW 2.6a Memlimits > 16 megs = internal inconsistany error

[zimbaliza]

Anyone else out there have any problems,if you bump your
memlimits above 16 megs, foxpro crashes...

Have had the same problem under 3.11 and now under NT
(all different machines)

my config.fpw is:

KEYCOMP = WINDOWS
CATMAN=OFF
date=british
memlimit=40,16000,16000
EDITWORK = C:\TEMP
PROGWORK = C:\TEMP
SORTWORK = C:\TEMP
tmpfiles = C:\TEMP
MVCOUNT=512

when I change my memlimits to 32000, it will result in
a crash, (internal inconsistancy error)normally when I
do some heavy work, (that probably uses more that 16 megs)

any ideas?, just a little problem that has annoyed me for many years......

Thanks
Zim

 

[benzhaotb]

Hi zimbaliza;
I am not a programer. We have the same probelm as you had when we are using an appilitcation of FP2.6 on Novel/NT in a Mcirobiology lab. If anyone has idea, please help. Ben

 

[rgbean]

Zim,
While I couldn't find any supporting documentation, it seems reasonable to assume that 16MB is the maximum that can be used. Remember that "newest" release of FPW 2.6a was in August of 1994 (about a year before Win95 was released!), and that it is strictly a 16-bit application. At that time, other than file servers, very few PCs had more than 4 or 8mb (the standard motherboads didn't support it) and few of us could afford more anyway.

Perhaps it's time to consider upgrading the application to the 32-bit world - it won't be long before we start using 64-bit processors anyway.

Rick

 

[ramani]

Try protecting the area 15-16MB RAM area in the Computer BIOS. I have not tried this, but a flook suggestion ! ramani
(Subramanian.G)
FoxAcc
ramani_g@yahoo.com

 

[zimbaliza]

From a Faq I read a few weeks ago from dgrewe

> It looks like the maximum amount of memory that FPW can
> handle is about 16 Megabytes. If more memory is alocated > and there is a large set of data, some memory
> transgression occurrs. Since Windows 2000 manage the
> memory of applications, this error never occurred there.

I may have to look at trying FPW on my home Win2k Machine
but I think Win2k may cause other problems :-/

Zim