🚀 go-pugleaf

In article <MATHIAS.95Jan19121219@sp2.eas.iis.fhg.de>,
Mathias Grimmberger <mathias@eas.iis.fhg.de> wrote:
)>>>>> "Device Null" == Device Null <dev> writes:
)In article <8752021574.KAA54198@null.port.nl> /dev/null@null.port.nl (Device Null) writes:
)
)
[deleted]
)
)    Device Null> yeah, i tried mem /c & /d, but i'd still be more
)    Device Null> comfortable with ps instead. i could also use a dos port
)    Device Null> of the unix kill command if there is one so i can stops
)    Device Null> jobs. since i got my computer, i have spent a lot of time
)    Device Null> stocking it with gnu utilities, and i practically have
)    Device Null> unix running on my dos box. i just need a few more things
)    Device Null> like ps and kill to complete the circle. i'm posting this
)    Device Null> to gnu.misc.discuss in case anyone there can help me out.
)    Device Null> thanks.

(In reply to original poster)

What you have seen so far is all that DOS supplies directly. You cannot
kill a process in DOS externally (at least not easily). Doing so could be
dangerous. Many applications hook various interrupt vectors. Killing a
process and removing it from memory (yes, it could be done) might very
well leave those interrupt vectors hooked. This would be fine until you
loaded another process, and it re-used the memory freed up by removing
the one previously occupying that memory. Then you would have a real
problem. 

Two utilities which do something like what you want are MARK and
RELEASE. They allow loading of TSRs and removing them without hassle.
They snapshot critical areas of memory to disc, then restore them. But
they are primitive by comparison to DOS.

Mike
----
char *p="char *p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}