Anyone know why a 4dos command should be sent to another dos app running in 
the background rather than run in the dosbox I'm using in the foreground?
The problem concerns an alias I have used for some time with 4DOS.
RE=keystack up up "|*list/s" R
I use it to recall previous command/redisplay screens which have scrolled off 
the screen.
Eg: My mailer (BinkleyTerm) is running minimized in the background.  I open a 
new dos box (4dos prompt).  After a display has scrolled I issue the alias 
command, but nothing seems to happen.  I try a few times but still nothing.
When I check my mailer later on, lots of junk keypresses were sent there!
If I don't have anything else running in the background then all is fine.
Why is this happening? Is something different about using keystack with w95?
I've just noticed that 4dos help mentions something about keystack bleed thru 
between win95 dos boxes.   I'm not sure what that means, but it sounds like 
it may be what I'm experiencing.  Why does this happen?  It also says to load 
keystack from the command to start each 4dos prompt.  Surely this means I 
will have less conventional memory available as win95 can't load things high 
at this point.  Also, I suspect that I'll not be able to re-use stacked 
commands between multiple windows, which I find very handy.
Rgds, Vic
--- GoldED/386 2.50+43UK1
---------------