Discussion Locked

Why Network Hangs On clipper Application

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a problem using my clipper based aplications in my Win2000 network... I have a W2K Advanced Server installed in a Compaq ProLiant ML370 with 2 processors and 1Gb ram for 80 Win95/98/DOS based clients...
During the day the network works ok, but sometimes when a client use the Administrative application based in clipper this hangs for a very long while, the cursor stay still and don't let the system go to the next part... even sometimes the clipper application hang in a red error form.
this problem happens 3 or 4 times in a day... and I don't know how to deal with it.
I hope you can help me in this problem...
By the way, my network work over a TCP/IP protocol...with an internal DNS using the internal Class C 192.168.1.0
If need more info I gladly send all you require.
Thenx a Lot

Jose Rios

1 reply

by dheupel

I might have an idea that could help you out, Jose. Clipper is very file I/O intensive, as I understand. On your Windows 9x/DOS clients, you might want to add a line to the users' AUTOEXEC.BAT file add a line to read FILES=xx, where xx is any integer that is sufficient to alleviate your problem. You might want to start at 35, and then increase to a maximum of 99. This tells the computer that it can have a maximum of xx number of file handles open at one time, and should allow Clipper to operate properly. If there aren't enough file handles available for Clipper (and other running apps), then the system will hang (or appear to hang) until a handle becomes available.

Good luck!

This discussion is closed to new replies.