Article ID: 138389
Article Last Modified on 12/8/2003
APPLIES TO
- Microsoft SNA Server 2.0, when used with:
- Microsoft SNA Server 2.1, when used with:
- Microsoft SNA Server 3.0, when used with:
This article was previously published under Q138389
SYMPTOMS
When you run the SNA Server Windows 3.x client process (WNAP.EXE), other
CPU-intensive Windows processes do not run properly. For example, a CPU-
intensive CAD application does not update the display in a timely fashion
when WNAP is running.
CAUSE
WNAP has a loop in it that is constantly calling PeekMessage(), and then
processing any message it finds. If there is a low-priority task trying to
run (e.g., something like a screen-saver), that task is shut out.
RESOLUTION
WNAP.EXE and WDMOD.DLL have been modified so that it now uses GetMessage()
instead of PeekMessage() if you add the line "PeekLoop=no" is in the [WNAP]
section of WIN.INI. For example:
[WNAP]
PeekLoop=no
NOTE: The default is PeekLoop=yes.
STATUS
Microsoft has confirmed this to be a problem in SNA Server for Windows NT.
This problem was corrected in the latest SNA Server for Windows NT, 2.11
U.S. Service Pack. For information on obtaining the Service Pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
KBCategory: kbnetwork kbinterop kbbug2.00 kbbug2.10 kbbug2.11
KBSubcategory: ntnetserv ntconfig
Additional query words: prodsna wnap yield 2.00 2.10 2.11
Keywords: kbbug kbfix KB138389