Clipper, Clipper 5.2e, Exospace and Win NT 3.51

Clipper 5.2e, Exospace and Win NT 3.51

Author	Message
Thomas Oate #1 / 3	Clipper 5.2e, Exospace and Win NT 3.51 Help ... We currently run a VERY large application using Clipper 5.2e and linked with Exospace. It runs fine under DOS. :) However, since we have installed Win NT 3.51 we have had massive "LOCK Failure" errors. This application runs on a Novell server serving around 550+ users. The .EXE borders around 3 MB. It's huge! Could our problem lie with the installation of Win NT? We have also encountered more corruption in our indices. Any help would be most appreciated. Thanks, Thomas Oatess United Healthcare Corporation
Tue, 25 May 1999 03:00:00 GMT

Ray #2 / 3	Clipper 5.2e, Exospace and Win NT 3.51 Quote: > Help ... > We currently run a VERY large application using Clipper 5.2e and > linked with Exospace. It runs fine under DOS. :) However, since we have > installed Win NT 3.51 we have had massive "LOCK Failure" errors. This > application runs on a Novell server serving around 550+ users. The .EXE > borders around 3 MB. It's huge! Could our problem lie with the installation > of Win NT? We have also encountered more corruption in our indices. > Any help would be most appreciated. > Thanks, > Thomas Oatess > United Healthcare Corporation Do you have Service Pack #5 installed? It's supposed to have cleaned up a few more locking problems. Also note several people have reported lock problems under Windows95 when linked with Exospace that were eliminated by changing the linker to Blinker. Ray
Wed, 26 May 1999 03:00:00 GMT

Frank Kjae #3 / 3	Clipper 5.2e, Exospace and Win NT 3.51 Quote: > Help ... > We currently run a VERY large application using Clipper 5.2e and > linked with Exospace. It runs fine under DOS. :) However, since we have > installed Win NT 3.51 we have had massive "LOCK Failure" errors. This > application runs on a Novell server serving around 550+ users. The .EXE > borders around 3 MB. It's huge! Could our problem lie with the installation > of Win NT? We have also encountered more corruption in our indices. Check that every workstation gets the NetBIOS loaded, if not - clipper is not able to communicate properly with the server. And, if you are using WfW 3.11 - There is a BUG in the network client. This bug occurs when you have over 30-50 open files (indexes included), downgrade to ver. 2.10 og upgrade to Win '95.
Wed, 26 May 1999 03:00:00 GMT

Page 1 of 1

[ 3 post ]