Hallo Vic
VB> Anyone know why a 4dos command should be sent to another dos app running 
VB> in the background rather than run in the dosbox I'm using in the 
VB> foreground?
VB> 
VB> The problem concerns an alias I have used for some time with 4DOS.
VB> 
VB> RE=keystack up up "|*list/s" R
This problem is handled in the 4DOS help under compatibility w. W95:
>----
If you want to load KSTACK.COM (required for the KEYSTACK command) under
Windows 95, it should be loaded separately for each 4DOS window.  To do so,
include the KSTACK command on the startup command line when you set up the
corresponding shortcut(s).  For example, the command line for your shortcut
might read:
     c:\4dos\4dos.com c:\4dos\kstack.com
This will load KSTACK when the 4DOS window is opened, then display a prompt.
If you install KSTACK in AUTOEXEC.BAT it will not work properly when
multiple 4DOS windows are open -- stacked keystrokes will "bleed through"
from one window to another.  To prevent this, create your shortcut for the
4DOS window to load KSTACK using the /I option:
     c:\4dos\4dos.com c:\4dos\kstack.com /I
This option will force a separate copy of KSTACK.COM to be loaded for your
4DOS window even if there is a current copy of KSTACK in memory.
>----
Grsse aus Ostrhauderfehn, 
*Klaus Meinhard*
--- FIPS/32 v0.99b W95/NT [M]
---------------