X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Rod Pemberton" Newsgroups: comp.os.msdos.djgpp Subject: Re: resident PMODEDJ? Date: Mon, 03 Mar 2014 19:00:21 -0500 Organization: Aioe.org NNTP Server Lines: 32 Message-ID: References: NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse AT aioe DOT org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Bytes: 2020 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Mon, 17 Feb 2014 16:59:38 -0500, Rod Pemberton wrote: > On Sat, 15 Feb 2014 04:57:39 -0500, Rod Pemberton > wrote: >> [...] >> >> PMODEDJ's documentation says it will only stay resident >> one time. Is there a switch, parameter, hidden switch, >> tweak, patch, etc that can be used to make PMODEDJ >> (pmodetsr.exe) stay resident longer? I.e., permanently. > > The patch below allow you to build a resident version of > PMODEDJ. PMODEDJ is a.k.a. PMODETSR.EXE. > > This version is experimental. Use at your own discretion. > Update: After a trivial amount of use, it seems this modified version of PMODETSR stays resident and can be used repeatedly for single-use execution of DPMI applications, i.e., one DPMI application after another. *But*, it *seems* it's not reentrant. When a PM TSR is loaded, executing another DPMI application causes a lockup. I haven't checked to see if there are any memory leaks etc. I probably won't be doing much more with this. I think it has served it's purpose. Perhaps, someone with more familiarity with PMODETSR can add a '-r' resident or '-p' permanent flag in the future. Rod Pemberton