Xref: utzoo comp.sys.ibm.pc:27121 comp.dcom.lans:2646
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdahl!pacbell!att!cuuxb!fmcgee
From: fmcgee@cuuxb.ATT.COM (~XT6510300~Frank McGee~C23~M24~6326~)
Newsgroups: comp.sys.ibm.pc,comp.dcom.lans
Subject: Novell ELS 2 concurrent client/server performance
Keywords: Novell 3COM
Message-ID: <2693@cuuxb.ATT.COM>
Date: 6 Apr 89 21:27:02 GMT
Expires: 19 Apr 89 23:00:00 GMT
Reply-To: fmcgee@cuuxb.att.com (Frank W. McGee)
Followup-To: comp.dcom.lans
Distribution: usa
Organization: AT&T, Data Systems Group, Lisle, IL
Lines: 27

I'm working on a problem where one of our 6386Es (a 20 Mhz 80386 clone)
is configured as a concurrent client/server under Novell ELS version
2.0.  The problem is that keyboard is VERY slow and unreliable (missed
keystrokes, etc.) when the ELS software is running.  The network
hardware is from Novell (presumably it is from 3COM originally).  My
guess is that the Novell program is just stealing too many clock cycles
to have MSDOS process normal keyboard input.

Rumor has it that Compaq had a similar problem and solved it by writing
a new keyboard driver.  I've also heard from a few people that this is
inherent in the ELS product, and that keyboard servicing is
unacceptable under any hardware cofiguration.

Any comments, clues, past experiences (good or bad) would be
appreciated.  I like email responses, but if you want post a follow-up
please post it in comp.dcom.lans since I don't normally read
comp.sys.ibm.pc anymore.

Thanks in advance,

Frank McGee, AT&T
Tier 3 Indirect Channel Sales Support
attmail!fmcgee
-- 
Frank McGee, AT&T
Tier 3 Indirect Channel Sales Support
attmail!fmcgee