delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: WinTix (hope you can help me) |
Date: | Sat, 19 Oct 2002 00:04:36 CDT |
Organization: | Rice University, Houston TX |
Lines: | 25 |
Message-ID: | <3db0e7e4.sandmann@clio.rice.edu> |
References: | <FE180C431068D411B20B00508BA58DD22A0E96 AT POST> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1035004609 2647 128.42.105.3 (19 Oct 2002 05:16:49 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 19 Oct 2002 05:16:49 GMT |
X-NewsEditor: | ED-1.5.9 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> will hook up a interrupt and returns to the WinTix.exe by using the keep > function. This part won't work. You can't use nested TSRs with DPMI. You will have to load your programs (and return to main) with a different method. > Maybe you can think of another way to make this happen in djgpp. These are > the specs I need. There are several ways I can think of making this happen, but ... > Child programs have to be EXE Why? Not a horrible problem, but it does limit you a bit. > Child programs should be called by the kernel This can be done via a DXE type load, or via a v2load (used by some debuggers) to get a child running without nesting DPMI. > kernel can load up more programs > The kernel and every child program should communicatie using the same > memmory part. Not a problem
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |