Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Hardware Incompatibility with 2.6?
Message
 
To
25/11/1997 11:21:44
Joe Fleeman
Scb Computer Technology, Inc.
Nashville, Tennessee, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00062171
Message ID:
00062202
Views:
22
>I am using FoxPro 2.6 for Windows and have had no trouble runnning
>my applications running out of memory until we purchased
>some Compaq Deskpro 166MMX machines w/32 Megs of RAM.
>
>I get the out of memory error code returned whenever the
>user uses a big screen with multiple Tabs (using FoxExpress
>and Genscrnx to generate Tabs), but it also can occur
>randomly. My config.fpw contains:
>mvcount=1200
>memlimit=25,2048,10240
>files=149
>
>Win '95 config.sys - I've tried adding files=199, left
>blank (for dynamic), files=159, etc.
>I'm running this fine on every other computer other than
>MMX machines - using Win. 3.1 and '95. Is there some
>weird use of memory from 640K-1Meg that MMX machines
>demand? Is there some easy fix like turning Shadow RAM off
>or anything goofy like this? Note: we also have other
>applications that run fine on all other computers except
>the 166MMX machines.
>Anybody else out there had this problem?
>jfleeman@mail.state.tn.us

Bravo Joe!! I've been waiting for someone else to come across this. My Department buys and distributes mass quantities of PC's for the company. We had one of the early MMX machines and put it through our own testing before deciding how many to purchase. I can't remember if it was a 166 or a 200, but my notes say it had 32 MB of memory and it would of been an HP model. The only place the MMX failed our testing was when running my 2.6 application and once when working with big graphics in printshop. I got out of memory errors randomly in 2.6, but usually around the 75% point in on SQL Select statements that joined 2 or more large tables.

From what you are saying, you have tried alot more things to resolve your out of memory errors than I did. But I didnt "have to" make the machine work, I only had to help determine if we wanted to set MMX as new purchasing standard. FYI, we sent that machine back because of what I seen. Instead we purchased a small surplus of non-MMX pentiums to distribute while we wait and see what becomes of MMX technology.

Hopefully somebody else here on UT can help us figure out what the problem is with these MMX machines. My tech support guys are practically begging me to get the boss to purchase another MMX for us to test again to see if we can determine that they would be a safe & reliable investment for our company, but I just aint had the time.
Roxanne M. Seibert
Independent Consultant, VFP MCP

Code Monkey Like Fritos
Previous
Reply
Map
View

Click here to load this message in the networking platform