Paradox Slow in Windows 98

[LWB]

I tested my new Runtime 10 install on a Windows 98 machine we have. It has no Paradox and no BDE on it, so it should be a clean test.

The installation was successful and the application runs, but it is extremely slow. The old version in Runtime 7 runs much faster. And there is no problem with speed on the Windows 2000 installations.

None of these machines are connected to a network so I doubt it is the usual network settings problem.

I don't want a user to run into this problem and think the application is the problem. Any ideas?

Lynn

 

[footpad]

Lynn,

I don't have a Win98 machine immediately available for testing, but you might see if there's virus scanning software on your Win98 machine.

If so (and there should be), make certain the scanner is only looking a program files and not all files. Otherwise, every table, index, document, and other support file will be scanned before it opens. As you can imagine with a file-intensive application like Paradox, this can be a huge performance hit.

Also, check the size of the swap file. If it's too large, you'll get disk thrashing as your system spends more time maintaining the swap file than it spends doing "real" work.

Take a peek at

http://clankiller.com/tech/speedtweak.php

for some of the details. The writing's a bit wild, but the info is sound.

Hope this helps...

-- Lance

 

[LWB]

Lance,

No virus software on this machine. It has no modem and no network connections. And Runtime 7 runs at normal speed (same application). But the same query (for example) that is the blink of your eye in Runtime 7 takes about 5 seconds in Runtime 10 (with the same underlying data files).

I have not checked swap file size but will do so.

Lynn

 

[footpad]

Lynn,

Hm. Which version of Runtime 7 are you using, the 16-bit version (Paradox 7 for Windows 3.1 and Windows for Workgroups) or the 32-bit (Paradox 7 for Windows 95 and Windows NT)?

-- Lance

 

[LWB]

Lance,

It is the 32 bit version.

Lynn

 

[footpad]

Lynn,

Thanks; I'll try to duplicate the problem at home and let you know if I find anything.

-- Lance

 

[jlockley]

A late suggestion, but using a registry washer for some problems I recently had on a W2K machine speeded up Paradox performance considerably. While I am still waiting to see what went down the drain that I need, I don't see any problems after about two weeks. I had used this only after I had uninstalled and reinstalled the program (actually 2 versions) and found that many references had been left behind. Perhaps it would work for your problem, although it's a bit of a scary step.