16-Bit Visual Basic Programs Are Not UnloadedID: Q192515
|
When multiple instances of a 16-bit Microsoft Visual Basic program are run at the same time and then shut down, they all seem to close; however, the program may still appear in the task list. Once a computer has experienced this problem, the operating system can become unpredictable and may need to be rebooted to clear up the problem.
The Compobj.dll file, which is part of the Distributed Component Object
Model (DCOM) protocol, may not decrement an instance counter and never
fully unload the Visual Basic program.
A supported fix that corrects this problem is now available from
Microsoft, but has not been fully regression tested and should be applied
only to computers experiencing this specific problem. To resolve this
problem immediately, contact Microsoft Technical Support to obtain the
fix. If you are not severely impacted by this specific problem, Microsoft
recommends that you wait for the next service pack that contains this fix.
For a complete list of Microsoft Technical Support phone numbers and
information on support costs, please go to the following address on the
World Wide Web:
http://support.microsoft.com/support/supportnet/default.asp
Date Version Size File Name
----------------------------------------
8/18/98 2.3.2 31,184 Compobj.dll
ARTICLE-ID: Q154871
TITLE: Determining If Your Product Is Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in the Compobj.dll file prior to version 2.3.2
You can also see the processes using .dq with the Windows 95/98 WDEB debugger.
Additional query words: VB VC Hang freeze QBASIC OCX
Keywords : win95 win98
Version : WINDOWS:95,98
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: January 28, 1999