X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Martin Str|mberg Newsgroups: comp.os.msdos.djgpp,comp.os.msdos.programmer Subject: Re: resident service providers Date: Mon, 24 Feb 2014 09:53:39 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 46 Message-ID: References: NNTP-Posting-Host: ftvAZcRvOze4hbePWaim7g.user.speranza.aioe.org X-Complaints-To: abuse AT aioe DOT org User-Agent: tin/1.4.7-20030322 ("Suggestions") (UNIX) (SunOS/5.9 (sun4u)) X-Notice: Filtered by postfilter v. 0.8.2 Bytes: 2599 X-Original-Bytes: 2492 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In comp.os.msdos.djgpp Rod Pemberton wrote: > On Fri, 21 Feb 2014 03:17:50 -0500, Martin Str|mberg > wrote: >> In comp.os.msdos.djgpp Rod Pemberton >> wrote: >>> What I really need to know is how to code a resident service provider >>> (DPMI enabled TSR) for a DPMI 0.9 host which doesn't support the two >>> DPMI TSR calls (0c00h, 0c01h) that DPMI 1.0 supports. >> >> This isn't exactly what you want, but it should do that quickly and >> easily: >> Take the source code from CWSDPMI and remove support for those two TSR >> calls and recompile... >> > What?!?! It's not April 1st yet ... And, I don't see a smiley. Well I hope I entertained someone by this... > DJGPP provides functions for calling those two DPMI 1.0 calls, but CWSDPMI > being mostly DPMI 0.9 doesn't implement those two calls. So, I don't see > how removing two non-existant calls from the CWSDPMI source and recompiling > would help me quickly and easily ... If you're saying it's a long, painful > path not worth traveling, that would've been clearer to simply say. I misread/misunderstood you. I thought you wanted a DPMI server which didn't implement 0c00h, 0c01h. I got the impression that the ones that you have (like CWSDPMI) didn't do what you wanted, thus they DID implement those calls (this is where I went awry). Now I see that you're in the client position and want to to code a TSR in a DPMI 0.9 environment. Sorry for any confusion I've caused. Then it's not that simple. One way might be to add those support for functions 0x0c00 and 0x0c01 to CWSDPMI. -- MartinS