Date: Tue, 9 Sep 1997 14:26:10 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Philip de Groot <philipg AT sci DOT kun DOT nl>
cc: djgpp AT delorie DOT com, "Peter J. Farley III" <pjfarley AT dorsai DOT org>
Subject: Re: Another tip of the week
In-Reply-To: <34140CDD.3F54BC7E@sci.kun.nl>
Message-ID: <Pine.SUN.3.91.970909142427.7143H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


Peter J. Farley III wrote:

> In the spirit of Paul Derbyshire's "tip of the week" idea, here's one
> I just ran across in the Win95 SDK that could be useful for we
> commandline junkies:
> 
> In CONFIG.SYS, you can expand the DOS commandline length to 255 bytes
> by using the following parameter to command.com:
> 
> shell=c:\windows\command.com /u:255

There's no need to look for this as far as the SDK (which many people
don't have), you can have the same info from the on-line help.  Just
type this:

	     command /?

and read what's printed.  Sometimes Microsoft *do* document their
features.

A word of warning: if you use any command-line editor that adds
history, aliases and such to the bare-bones command line, you should
be aware that enlarging the maximum command line length might break
such editors if they only have 128 bytes in the input buffer.  For
example, DOSKEY has a special option /LINE:size to change the default
size (three guesses what the default is ;-) which should be used when
you give /u:255 switch to COMMAND.COM.  If your command-line editor
doesn't let you enlarge the buffer, you should probably test the
larger line size to see if they at all work, before you commit to
/u:255.