Mail Archives: djgpp/2014/02/16/08:00:20
On Sat, 15 Feb 2014 22:13:44 -0500, <rugxulo AT gmail DOT com> wrote:
>> I wanted to try to use PMODEDJ instead of CWSDPMI, since
>> AIUI it doesn't have paging enabled. The CWSDPMI TSR can
>> be told to stay resident with the '-p' parameter.
>
> You mean paging or swapping?
I meant paging. Thanks for the info though.
The issue is I need to keep PMODEDJ resident (to execute both programs).
Keeping PMODEDJ resident would allow me to see if the TSR code is working
or failing the same way for both. I.e., if it works for one but not the
other, then I likely have a paging or perhaps a memory locking problem.
If it fails for both, then I more likely have some other coding mistake.
I was going to look at PMODEJ's code when I get a chance to see what
triggers
it to unload. It stays resident for one use. So, there is something that
causes it to unload, e.g., counter, pointer, etc. It might be possible to
recompile it, or patch a byte to prevent it from unloading. A small TSR or
two to modify interrupts might work too.
I don't know if any of those ideas will be easy or if such an attempt will
"break" something internally in PMODEDJ. Usually, the DPMI host cleans up
when it exits. So, forcing a DPMI host to stay resident when it wasn't
designed to do so may prevent it from cleaning up or initializing things
properly with multiple uses. But, I won't know any of that for sure until
I look and try, unless someone more experienced with PMODEDJ posts some
in-depth information.
Rod Pemberton
- Raw text -