How to improve the speed for DOS Foxpro 2.6

[raphealchan]

We are using Foxpro 2.6 (Dos)at our outlets and the files are getting bigger. We want to improve the speed of the application. Our system is:
1. OS: Dos
2. Pentium 133 MMX
3. 16 M Ram

If we add some more ram, how to configure it so as to improve the speed? What is the best confirguation to run an application by Foxpro2.6 (DOS) ?

Thank you

 

[ramani]

HI

1. Use in your config.sys
DEVICE=c:\dos\himem.sys

or

DEVICE=c:\windows\himem.sys

(The actual path depends on your OS installation).

2. Dont use the EMM386 to occupy most of the extended RAM

3.Use the Extended version of FPD2.6a
i.e. FoxProX
If you are using runtime version. again use the extended versions FOXDX260.ESL

4. Make sure that you dont waste your below 640K RAM area. Make maximum vailable for FPD2.6a.

This should help you reasonably.
ramani
(Subramanian.G),FoxAcc, ramani_g@yahoo.com

 

[rgbean]

I don't believe FPD/W will actually use more than 16MB of available memory. So unless you are running TSRs or some kind of task switcher, I'm not sure you'll get any more performance simply from more RAM. Faster processors, faster hardisks and a faster network connections are going provide more help at this point. Of course what helps the most depends on what is really "slow". Perhaps changing the structure of the program to process less data is a better performance update.

Rick

 

[raphealchan]

Thank you guys!
However I don't want to upgrade my hardisk or CPU or other things but just adding more rams!!!
I have heard that Foxpro2.6 (Dos) is using EMS so if I add in the emm386.exe ram in the config.sys, then I checked the memory usage by " ? sys(1001)" and "? sys(23)" and it shows if I use 32M Ram it will increase. However I want to know more about and how to maximize it's speed and configuration.

Thank you

 

[rgbean]

While you might be able to store more in memory using EMS, by it's nature, EMS is slower than XMS (extended) memory. Depending on the version implemented, it works in 16KB or 64KB blocks or pages, and there is more overhead in swapping these in and out compared to the "linear" address space of XMS.

Note: These statements are based on my memory of things I no longer use on a regular basis. The best thing to do is set up two work stations - one with an XMS setup and one with an EMS setup, and see which gives better results for your data and network, and then go with it!

Rick

 

[JRB-Bldr]

Depending on the nature of your data, you might also want to consider "partitioning" your data so as to speed up execution.

In most cases applications have Necessary data and Old data. If so, many systems managers split their data into CURRENT and ARCHIVE data tables. This can be accomplished manually on a periodic basis or it can be done automatically via an over-night application.

By reducing the size of the tables your application works with to only the Necessary data, your program typically will execute faster.

Good Luck,
JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[raphealchan]

Let me re-phase my question:
If I add 32 Ram into it and add "emm36.exe ram" in the config.sys so as to enable the Foxpro2.6(Dos) to use EMS memory, will it faster? Or should I use XMS?

Thank you

 

[tilltek]

I've never found more than 16 meg to do anything with FPD2.6. I run a lot of 486 DX and low end pentiums and BY FAR the biggest speed hog is HDD access.
By the way, I once tested Dos, Windows and no himem in config sys and the Windows version wins hands down. Even the WFWG version.
Ken F

 

[advancepack]

I think your hardware is good for FPD2.6. Use FOXPROX.EXE with "Rushmore Technology" data access technique that permits sets of records to be accessed very efficiently.

 

[raphealchan]

How can I check whether the application is using "Rushmore" technology?

 

[advancepack]

Find topic "Rushmore Technology" in help file. Reply if you do not find.

I am using Rushmore and I used to say for my software "ANY COMPUTER & ANY DATA VOLUME GET REPORTS IN SECOND(S)"

Feel free to ask.

One more thing, To retrive data use SELECT SQL