Date: Thu, 17 Oct 2002 08:31:04 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: ChaoTix <ChaoTix AT c-a-t DOT nl>
cc: djgpp AT delorie DOT com
Subject: Re: TSR Programs (Desperate)
In-Reply-To: <aokcl0$2h0$1@news1.xs4all.nl>
Message-ID: <Pine.SUN.3.91.1021017082921.3848M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 16 Oct 2002, ChaoTix wrote:

> Yes, the child program will be left out there somewhere in the memmory and
> will cause a leak, but thats not the problem for now.

Memory leak is not your problem: you will have 2 DPMI programs active at 
the same time, which will totally confuse the DPMI server.

> Right now I have
> programmed this and gets the next result:
> 
> Program Main Started      (text from main.exe)
> Calling Child.exe         (text from main.exe)
> Terminat and keep....     (text from child.exe)
> (child programs keeps in memmory and returns to main program)
> Main program crashes directly with final text line "This text should not be
> read", wich is the last printf function in the Child.exe program.
> 
> How do i know that the child program has been exits and not causes to crash?

Just don't do that: don't TSR a child program.  Why do you need the child 
to be a TSR, anyway?