Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!wugate!uunet!mcvax!kth!sunic!maxim!prc
From: prc@erbe.se (Robert Claeson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DOS 3.30 PATH and Environment lengths
Keywords: Please HELP: What's wrong with this picture?
Message-ID: <767@maxim.erbe.se>
Date: 28 Jul 89 08:42:00 GMT
References: <3695@i.sei.cmu.edu> <2811@ndsuvax.UUCP>
Reply-To: rclaeson@erbe.se (Robert Claeson)
Organization: ERBE DATA AB, Sweden
Lines: 28

In article <2811@ndsuvax.UUCP> nebezene@ndsuvax.UUCP (Todd M. Bezenek KO0N) writes:
>In article <3695@i.sei.cmu.edu> gjp@sei.cmu.edu (George Pandelios) writes:

>>I'm having trouble setting my PATH to a length larger than an small 
>>(127?) number of characters.

>Try putting a "shell=..." into your config.sys.  This will start
>a new shell (in your case DOS).  With this new DOS shell, you can
>specify the environment size with the /e option.

Sorry, but that won't help. COMMAND.COM *never* allows you to input anything
longer than 127 characters. What an extended environment space gives you is
room for more environment variables, but a single variable cannot be
longer than 127 characters. I've tried to spread the PATH variable out over
several lines, like

PATH=x;y;z
PATH=%PATH%;q;w;e

or something like that, but it doesn't work either. As soon as a single
variable becomes longer than the magic limit (127 characters), COMMAND.COM
complains.

If there's anyone (anything?) that knows a work-around (or have a fix) for
this, PLEASE let us know.
-- 
          Robert Claeson      E-mail: rclaeson@erbe.se
	  ERBE DATA AB