DH> scheduled...hahaha  One server in particular, a Compaq Proliant 4500,
 DH> smp, 256Meg, 8 Gigs,
Dealer cost on one today is $15k+, so we know your orginization has money.
 DH> keeps on getting Abends on any NLM that I load that
 DH> needs to see and manage users or files that the users have open, such as
 DH> Sqlmon or Brtmon.  They will just hang and also cause the console prompt
 DH> to go away and also during this time the server comes up with a Page
 DH> Fault from the NCC.NLM in Threads.nlm .
Okay, so you have a repeatable failure.
 DH>    I have been told that 4.11 might take care of the problems but unless
 DH> I can come up with that 4.11 "Will absolutely" take care of the problems
 DH> they won't purchase it.
 DH>    The biggest problem with the server abending is that our 4Gig+
 DH> Btrieve data base gets corupt or at least some of the Data files that
 DH> are 250Meg+.
1. Don't go around crashing a production server repeatedly. It's too costly 
and
too risky.
2. Get Novell and Compaq involved _now_ and open an incident. You obviously 
have business partners - USE THEM, particularly Novell. You want an eval copy 
of 4.11 -- 2- or 5-user is fine -- for testing purposes. You want their tech 
onsite if that doesn't work.
3. Load your production server software onto the Proliant using a spare SCSI 
drive. Yes, your orginization has spare equipment or ought to. Now that you 
have a reasonably fast turnaround on a repeatable test, you will be quickly 
to a solution.
Jeff
--- GoldED/2 2.42.G0615
---------------