Message-ID:	<68C4CF842BD2D411AC1600902740B6DA02CDC5B7@mcoexc02.mlm.maxtor.com>
From:	"Dykstra, Sean" <Sean_Dykstra AT maxtor DOT com>
To:	"'djgpp AT delorie DOT com'" <djgpp AT delorie DOT com>
Subject:	FW: Various spawns
Date:	Fri, 14 Sep 2001 17:08:03 -0600
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)
Reply-To:	djgpp AT delorie DOT com

Sorry, what I had intended to say is that spawnlp and spawnvp give me the
same slow response as the system command (I have not tried to figure out a
way to get to the command prompt with spawnvp).  However, I can indeed send
a spawnlp and get to the command prompt very quickly, but spawnlp with
parameters is slow.

To simply reproduce, boot to a dos system with smartdrive disabled (if it is
enabled the "system" command works just fine).  

Then if you write any program that does a system call:  (It can also be DOS
commands, batch files, or executables, but here is the simplest form I have
found to fail, to make it easy to reproduce).

system ("");  //This function will give you a dos prompt very quickly, you
              //can then say dir and you get a very quick response

and you can write a program that does:

system ("dir");  //This function call will take a really, really, really,
really long time.  
                 //The system I am using is a 933Mhz machine with an award
BIOS, but I am told
                 //by one of our other development teams it will fail on any
machine

The version of DJGPP is:  2.952

My DPMI host is configured as follows:
Paging disabled
Auto number of page tables to allocate
512k min app mem before paging
3840 paragraphs to reserve when 640K paging
512 paragraphs internal heap memory for CWSDPMI
128Mb maximum size of swap file
Value of run option flags - 1

My config.sys
Device=himem.sys
device=emm386.exe RAM NOEMS
dos=high,umb
buffershigh=10

There is nothing in my autoexec.bat


Thanks!

- Raw text -