Mail Archives: djgpp/2002/10/16/15:00:27
From: | "ChaoTix" <ChaoTix AT c-a-t DOT nl>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | TSR Programs (Desperate)
|
Date: | Wed, 16 Oct 2002 20:54:29 +0200
|
Organization: | XS4ALL Internet BV
|
Lines: | 59
|
Message-ID: | <aokcl0$2h0$1@news1.xs4all.nl>
|
NNTP-Posting-Host: | 213-84-241-227.adsl.xs4all.nl
|
X-Trace: | news1.xs4all.nl 1034794464 2592 213.84.241.227 (16 Oct 2002 18:54:24 GMT)
|
X-Complaints-To: | abuse AT xs4all DOT nl
|
NNTP-Posting-Date: | 16 Oct 2002 18:54:24 GMT
|
X-Priority: | 3
|
X-MSMail-Priority: | Normal
|
X-Newsreader: | Microsoft Outlook Express 6.00.2800.1106
|
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1106
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
Man, I have been working around the clock, and "expirimenting" almost
everything using TSR's, but I still cant get it working stable. All together
I want the solution to my next idea:
--------------------------
Program Main
|
|
\>>>>>>>>>>>>>> Call Child.exe
|
|
Exit and keep resident
<<<<<<<<<<<<<<<</
/
|
Continue Doing stuff in Main
|
|
Exit of Main Program
------------------------------------
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. 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?
Because when I run RHIDE, and goes to the dos prompt I get the next results:
-----------------------
RHIDE dos blablablabla, type exit to jady jady jady
C:\> child.exe
Terminate and keep....
C:\> exit
This text should not be read
--------------------------------
<and the compleet dos session will crasch in 0.1 second. Just got time to
view the last line).
Please can somebody make a little bit of source of keeping this stupid child
in his place in the memmory. I dont really care if its in de higer memmory,
protected, or real, I just want to keep it steady there.
Already thanx for reading this (I am beginning to be really desperate).
ChaoTix
Ps: Sorry about my bad englisch, but I am original Dutch =)
- Raw text -