Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!know!sdd.hp.com!think.com!linus!linus!tatum!dhf
From: dhf@tatum.mitre.org (David H. Friedman)
Newsgroups: comp.windows.ms
Subject: Opening a DOS window with TSR's
Message-ID: <127136@linus.mitre.org>
Date: 5 Dec 90 21:39:34 GMT
Sender: usenet@linus.mitre.org
Distribution: usa
Organization: The MITRE Corporation, Bedford, MA 01730
Lines: 33

.  I'm looking for a good way to set up a DOS window with some TSR's
loaded, specifically CED and the PC Magazine SETUP2 utility. I've
been using a PIF to run (windowed, in 800x600) a file COMMAND.BAT
that looks like

         ced
         setup2 myprintr.pmf
         command

This leaves the window open with CED loaded and the SETUP2 hotkey
active. To exit from COMMAND.COM, I enter EXIT and the window closes.
So far, so good. But I've found that if I minimize the window and
restore it, the CED command-history buffer is flushed (although CED
is still there) and the SETUP2 hotkey is no longer active.

   I realize that this scheme leaves three copies of COMMAND.COM in
memory: #1 on booting the system, #2 loaded by Windows to run the
batch file and exit, #3 loaded by the batch file to actually appear
in the window. If I leave out the line "command" from the file, #3
is not loaded, and Windows gives a message "Your TSR is ready to use.
Enter ^C to close this window.." instead of dropping me into copy #2.

   For the record, my system is a NEC 386/20 with 2 Mb, running in
386 mode, with CommandPost 7.0J as the Windows shell in place of
ProgMan and FileMan. The minimize/restore sequence described above
occurs even if no other applications are loaded, so memory isn't
necessarily the issue.

   Has anyone found a better way? I recall there was some discussion
on this topic a few weeks ago.


dhf@linus.mitre.org (David H. Friedman)