Date: Mon, 19 Oct 92 11:15:29 GMT
From: kuku AT acds DOT physik DOT rwth-aachen DOT de (Christoph Kukulies)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: system()

When I do a system("c:\\command.com") from within a small application it is
no problem to switch to command level very quickly, but when I'm doing this
out of my 10 MB application it takes often 20 to 30 secs until the command
prompt (or bad command or filename) appears.

I'm using the MS_SH200 sh.exe to start a shell script. This script starts 
a second sh script which in turn starts the final executable.
I don't know whether this twofold nesting of shells is responsible for
the intolerably long time for switching - the msh200 swaps itself out of memory - 
or if the problem lies in go32's implementation of system(). QEMM is also in the
game but I have on the other hand no problems running large compiles and other
large programs.

Does go32 swap out the exectuable from memory to disk when executing the
system() call?

--Chris