Mail Archives: djgpp/2014/03/03/19:15:22
On Mon, 17 Feb 2014 16:59:38 -0500, Rod Pemberton
<dont_use_email AT xnohavenotit DOT cnm> wrote:
> On Sat, 15 Feb 2014 04:57:39 -0500, Rod Pemberton
> <dont_use_email AT xnohavenotit DOT cnm> 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
- Raw text -