Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Fox 2.6/2.5 running on XP Query (CPU Usage)

Status
Not open for further replies.

phavenhand

IS-IT--Management
Feb 21, 2003
13
GB
I am running a couple of applications using both Foxpro 2.5
and 2.6. The applications are on a Netware 3.12 Server and i am running them from a XP Pro machine.

The applications run fine , except that CP usage goes to 98% whenever they are run. Hence , opening any other applications (Word / Execl / Outlook etc) is very slow.

As soon as you close the Foxpro dos application the CPU usage drops straight down.

Does anyone know of a reason or better still a cure for this. It does not happen on Win98 or Win 95 machines.

Many thanks

Pete Havenhand
 
Pete,
This has been discussed a lot here. There are problems with running some DOS and some Win 3.x apps and FP is included "sometimes". It can depend on your OS SP level, the CONFIG file settings, virus checkers, the way you start it up (.BAT, .PIF, .LNK), the memory model you or FP chooses, the compatibility mode (if you use it), any third party .FLLs or PLBs and the network type and client(s) you are using. I just did a quick search (using the tab above) on Slow + XP and got the following list of threads (plus a few more) - check them out and maybe try the last one's application (it has a 30-day free trial).

thread182-474163, thread182-246331, thread182-392708, thread182-163118, and thread182-521024 offers the App TameDOS.

Rick
 
Do a Keyword Search on:
XP Memory Properties
Using the following switches:
ALL Words
Any Date

And you will find a number of questions similar to your own along with the replies.

Among them is: thread182-246331 which might have some clues for you to consider.

Additionally there are others listed as well which might point you in the correct direction.

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com
 
Hi

Many thanks for your replies , however none of the mentioned threads are in relation to what i am having problems with.

Let me try and explain ..

The Foxpro routine runs fine , absolutely fine , NOT slow .

However the processor is showing at between 90 and 100% capacity.

If you try and start another application (anything) , the system seems to run really slow on all applications except the Foxpro app. This must be as the Foxpro routine is using all 100% of processor.

The processor runs at 100% even when nothing is being done within the Foxpro app.

I have a system i wrote in Foxpro , and also use Pegasus Opera Dos accounting system , also written in Foxpro.

Every time any Foxpro app is run , the processor is 100% being used. This is the same whether using Foxr or Foxprox.

The runtime version i have is 2.5 , the full version is 2.6a.

The accounting package is a compiled exe, whilst my apps is the fxp , sct, scx files. Nothing makes a difference.

I have tried using the Memlimit line , but that does not do anything and is not even a recognised command according to the Foxpro dos manuals, (maybe this is a Foxpro for windows command)

I have tried running the apps form Batch files , pif's

Nothing seems to help.

Any help greatly appreciated.

Pete
 
Pete,
1) Thread182-521024 refers to TameDOS, will absolutely "fix" your 100% usage problem - it's just not free.
2) It's never a good idea to use mismatched runtimes vs. developement versions. I've even seen problems with differrences between 2.6 and 2.6a!
3) The MEMLIMIT is definitely documented in the FPD 2.5b help topic:
Doc Changes Since Printing

And in FPD 2.6a's help file in:
Doc Changes Since Printing
Internal Inconsistency Errs
Insufficient Memory

I found these by doing the following:
Code:
SET HELPFILTER TO "memlimit" $ lower(details)
HELP
Remember FPD was written for and tested under DOS where it had 100% of the system. When you run in an alternate environment (like under Windows), you either have to live with those limitations, find a third-party solution that "works around it", or upgrade the application to match the hardware and OS you are running.

Rick
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top