Access Violation When You Run 16-Bit Parent and Child Programs

This article was previously published under Q219324
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you run a 16-bit parent and child program in separate memory spaces of the parent program, the parent program generates an access violation error message.
CAUSE
This problem occurs because the address space of the parent program contains a Shared Object list. When you start a child program, it adds its task information to the Shared Object list. However, when you quit the child program, the child program's information in the Object List is not removed. The Shared Object list continues to grow as child programs start and quit until the parent program generates an access violation error message.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
Microsoft has confirmed that this is a problem in . This problem was first corrected in Windows NT 4.0 Service Pack Service Pack 5.

Properties

Article ID: 219324 - Last Review: 10/14/2013 19:43:46 - Revision: 2.2

Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 1, Microsoft Windows NT 4.0 Service Pack 2, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB219324
Feedback