Date: Tue, 29 Aug 2000 21:27:07 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: snowball3 AT bigfoot DOT com
Message-Id: <7458-Tue29Aug2000212707+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3979F2E3.23126.267C6E@localhost> (snowball3@bigfoot.com)
Subject: Re: Long command line patch for dosexec and friends
References:  <3979F2E3 DOT 23126 DOT 267C6E AT localhost>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

According to my testing, with COMMAND.COM and a Win32 app on Windows
98, the limit on the length of a command line passed via CMDLINE
environment variable is 1024 characters, including the "CMDLINE="
itself.  Passing more than this can have various adverse effects, from
bogus strings appended to the end of the arguments, to crashes of
varying severity (I even succeeded once to cause a GPF inside
KERNEL32.DLL and bring down the whole system).

This is consistent with the MSDN Knowledge Base which, as I'm told,
says that environment variables on Windows 9X are limited to 1024
characters.

Does anyone have different measurements?  I need this to set the limit
beyond which dosexec.c will fail with E2BIG for Win32 programs.