🚀 go-pugleaf

In article <49bt2q$sl3@bagan.srce.hr>, dcarapic@fly.cc.fer.hr says...
>
>Raymond Moon (raymoon@moonware.dgsys.com) wrote:
>: Fred (Frot) wrote:
>
>: > At the moment I am developing some kind of tool to call (spawn/exec)
>: > other commands (using swap of memory) in MS-DOS.
>: > 
>: > In order not to disturb the screen by messages from the called 
program
>: > I use redirection of stdout.
>: > 
>: >         e.g. 'dir > \it.txt'
>: > 
>: > I encountered a problem when this called program writes something to
>: > stderr. These messages are not redirected to the file, but corrupt 
the
>: > screen display and confuse the ignorant user.
>: > 
>
>'>' redirects stdout but it doesn't redirect stderr try '>&' (it's been a
>long time so i'm not sure if this works)


Inside your code, before you execute your spawn or exec, try the 
following:

                 close(2);

or
 
                 fclose(stderr); /* Assuming <stdio.h> */


I tested this with MSVC++ 1.5 (though I used the "system" function)
and it seemed to work okay. If you actually want to keep stderr available
for your use, you can dup or dup2 it, then close it, and re-dup or dup2
it.

                              Fred