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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Memory Leak Event 2019

Status
Not open for further replies.

samirlias

ISP
Oct 16, 2000
10
CA
Running a Clipper 5.2 app on Windows 2000 server, which we connect to using Terminal Services. A dos batch runs several other batches and Clipper programs. Every 4-5 days the server is hung randomly at one of the batches or PRGs, with Event 2019 "The server was unable to allocate from the system nonpaged pool because the pool was empty. The support people are saying this could be the DOS programs, which thay say are not meant to run on Windows 2000. We connect to those servers using Terminal Services and a Monitoring Tool is constantly running. Any one has the same experience who can share with me his pain and possibly, solution ? Thanks... Samir
 
Responding to myself in order to close this thread after we just found out that our INOCULATE anti-virus software is causing a memory leak when running with other DOS-Clipper programs. Clipper programs run fine without INOCULATE. It is a different ball game now.
 
we have an application in Clipper; but we have now 2 remte offices and need to run it.
I tryed Georgia Softwork TELNET SERVER, but had huge problems with printing on the Client side.
We have been recommended to go for the Windows Terminal Server; but worried how will perform running in the 2000 sever.
any experience on running clipper app with terminal server?
Walter
 
We are running a critical Clipper 5.2 application on Windows 2000 server and it is running fine, with printer connected to the workstation or the server.

It should be noted that you will experience slowdown if the user is running the clipper application along with other windows or DOS programs (MS Word, editor, etc...), since clipper uses all available (or 100%) CPU. This can be handled for the on-line application, using known OSLIB.lib or others to release CPU at idle times. For the batch programs however, this could be a problem if running several batch program together. We had to make sure they run one at a time, on a dedicated workstation.

Good Luck

clip4ever
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top