Access Violation When You Run 16-Bit Parent and Child Programs (219324)
The information in this article applies to:
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Server 4.0 SP1
- Microsoft Windows NT Server 4.0 SP2
- Microsoft Windows NT Server 4.0 SP3
- Microsoft Windows NT Server 4.0 SP4
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Workstation 4.0 SP1
- Microsoft Windows NT Workstation 4.0 SP2
- Microsoft Windows NT Workstation 4.0 SP3
- Microsoft Windows NT Workstation 4.0 SP4
This article was previously published under Q219324 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.
RESOLUTIONTo 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 the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in . This problem was first corrected in Windows NT 4.0 Service Pack Service Pack 5.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB219324 |
|---|
|