Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!microsoft!michaelt
From: michaelt@microsoft.UUCP (Michael Thurlkill 1/1029)
Newsgroups: comp.windows.ms
Subject: Re: NetBios and MS Windows
Message-ID: <5860@microsoft.UUCP>
Date: 5 Jun 89 16:18:53 GMT
References: <11567@netnews.upenn.edu>
Reply-To: michaelt@microsoft.UUCP (Michael Thurlkill 1/1029)
Distribution: na
Organization: Microsoft Corp., Redmond WA
Lines: 22

In article <11567@netnews.upenn.edu> lau@kings.wharton.upenn.edu (Yan K. Lau) writes:
>Has anyone written applications using NetBios calls in Windows?
>I have an application that works most of the time but it sometimes
>crashes.  It seems to be sensitive to when network messages are
>received.  The usual symtoms of failure is either a FatalExit or
>unresponsive mouse.  Sometime the mouse cursor is gone.  Other
>times mouse movement is okay but selecting any of menu options
>doesn't display a pull-down menu but rather gives a beep.
>
There are a couple common things that will cause this:
1. If you have an asynchronous notification routine, it is being moved
   or banked out. It must be in a fixed code segment DLL. Also, memory
   associated with the notification routine should be fixed and non-
   bankable (see #2).
2. If you are polling the NCB, the NCB is being moved or banked out.
   It must be GlobalAlloced with GMEM_NOT_BANKED, and must be either
   GMEM_FIXED, or locked prior to the asynchronous netbios call.

Basically, something is moving, and memory is getting walked on.
That's my best guess.

Mike Thurlkill