From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: Terminate and Stay resident in CWSDPMI Date: Wed, 16 Oct 2002 10:38:43 CDT Organization: Rice University, Houston TX Lines: 23 Message-ID: <3dad8803.sandmann@clio.rice.edu> References: <3dab979d DOT sandmann AT clio DOT rice DOT edu> <3dacfa00 DOT sandmann AT clio DOT rice DOT edu> NNTP-Posting-Host: clio.rice.edu X-Trace: joe.rice.edu 1034783456 14172 128.42.105.3 (16 Oct 2002 15:50:56 GMT) X-Complaints-To: abuse AT rice DOT edu NNTP-Posting-Date: 16 Oct 2002 15:50:56 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 > Wow....this seems really good. Thaxn a LOT! I'm glad you found it useful. > Are you an DJGPP maker? I'm a frequent and long time contributor, yes. I built the first DPMI GO32 for DJGPP 1.09d, helped bring V2.00 to release, and built CWSDPMI based on DJ's GO32 extender. > Right now I am working on the new version of WinTix GUI for Dos. Its > something like seal, except seal is already using DJGPP and ALLEGRO, and > WinTix still used the stupid slow BGI drivers from borland. And why I need > intterupts callings is because every EXE program made for WinTix will be an > Interrupt. So the "kernel" can call the program every time he wants. I originally was playing with the TSR as a way to support a protected mode networking and a libc kernel, but then I decided to make it a dynamic load from the first image running and have nested images detect it and use it if already loaded. Never finished ... Good luck with your project.