🚀 go-pugleaf

In article <Dn7Ex2.2s9@mccc.edu>, pjh@mccc.edu says...
>I have my PATH set in CONFIG.SYS, with a "set path="
>However, it's still only 128 bytes max. Is there a way to
>use SUBST in CONFIG.SYS?

Are you SURE it's only 128 bytes? I ask because if you use SET
to view it, SET will only SHOW you 128 bytes because it's stupid 
and thinks its limits on environment variables are The True Limits.
(And if you let it modify the PATH, it'll truncate it for you.)

MSD's OS option will show you the actual variable. You can also 
confirm that the PATH is being utilized correctly by testing. 
(Creating the test case is left as an exercise....)

And if you're thinking it's broken to have two SET commands with
different size limits...very good!  The commandline SET, PATH, 
and PROMPT commands have all been historically limited by 
command.com's input buffer.

CONFIG.SYS' parser doesn't have the same limitation. 

As far as I know, back when we added the SET option for CONFIG.SYS,
no one gave any thought to making CONFIG.SYS' SET command have 
the same limitation as COMMAND.COM's. In fact, it's a lot easier
to leave the respective command-length limits of config.sys'
parser and command.com's alone...

Finally, you can use the SUBST command in CONFIG.SYS via INSTALL=.

-- 
        -=- jennifer kilmer -=- jenk@microsoft.com -=-  
The opinions expressed in this message are my own personal views
and do not reflect the official views of Microsoft Corporation.