Some time ago I wrote the following:
-----
 We are running portable NETWARE in order to accommodate our printing.(We
use nbspool in conjunction with NETWARE/iX to move files to a number of
Novell servers.
 
 We have had many occasions where the nbspool process goes into some loop
and consumes most of the cpu.  Quest (nbspool) is pointing the finger to HP
and HP is pointing back at Quest.
-----
 
I'm writing today to report that apparently the problem has been resolved.
It has been almost two weeks and the 'cpu hog' has not occurred.  It turns
out that Quest had written/ported netware for the MPE/iX 4.X but HP
re-wrote it for the 5.X version and provided libraries to vendors that
needed to interface.  It seems that as different fixes were applied to the
5.X version the changed libraries were *not* provided to Quest, at least,
for re-linking their routines.
 
Once the current libraries were made available and the Quest module
(NWSPOOL) was re-linked the problem was resolved.
 
Regards
 
Paul H. Christidis