CONFIG.NT or PIF settings/DOS based databases

[CatPlus]

Hello all:

My application resided on a Novell server which has now been moved to a Windows 2000 server. Clients use a mix of Windows 98; 2000 Professional and XP Professional (both, in the Novell and Windows environment)

The application speed was super fast when clients accessed the database on Novell. With the database now residing on a Windows 2000 server, we could go to a coffee break and find the procedures still running, painfully slow!

Why not move back to Novell? Corporate decision to do away with Novell

Although the application is not DBase, it comes close to DBase in most respects and hence my question on this forum

How have DBase users transitioned into Windows 2000 on their DOS based Dbase? Any help in tweeking will be very much appreciated

Thank you and happy holidays to you all

Mickey

 

[dbMark]

Is there an antivirus program running in the background? If so, be sure it does not check the database tables and indexes. Another idea, try something called TameDOS mentioned in some of these threads.

thread290-590977 - a summay of various issues
thread182-580293 - sluggish response - suggests TameDOS
thread182-537721 - try TameDOS to avoid newer OS taking 100% utilization

Note that a couple of these posts were found on the FoxPro for DOS forum182.

Please leave a reply telling which suggestion (hopefully) helps you...

dbMark

 

[NasibKalsi]

After executing dbMark's suggestions, if problem persists, then try shutting down any non NT kernal machines connected to the NT server.

There is a problem in locking mechanism between W98 and NT(my own findings). If you eliminate all W98,W95 thing may improve.

Nasib Kalsi
Try it.