Thanks again. Still unable to make SHELL= work. It doesn't matter, since setx.exe worked.


>>Thanks Ed.
>>
>>SETX.EXE worked. However, I wasn't able to increase the size of the environment for a single session as suggested. Perhaps because I call a batch file with parameters? Also, what is the format for the SHELL= statement in CONFIG.NT ?
>
>In CONFIG.NT:
>
>SHELL=
>
>You can check your exisitng command processor by looking at the default COMSPEC environment variable; on my system here, it's C:\WINNT\System32\cmd.exe
>
>To set a 4K environment space, I'd have an entry:
>
>SHELL=C:\WINNT\System32\cmd.exe /e:4096
>
>>
>>TIA
>>
>>Alex
>>
>>
>>>>Hi all,
>>>>
>>>>I have links to several versions of the same project in different icons on the desktop. They all call a bat file which sets up environment variables, (with the DOS set command). Now one station is NT, but it limits the value of variables set this way to 20 chars. Does anybody know how to change this parameter? NT Resource Guide does not tell.
>>>
>>>It sounds like you're running out of room for environment variables. On a global basis, you can change the size of the environment through the SHELL= statement in CONFIG.NT; for a single session, you can change the space as follows (quoted from information from the NT FAQ, one of the best free net resources, available at http://www.ntfaq.com
>>>
>>>Q. How can I increase the environment space for a single command session?
>>>
>>>A. While you can update the config.nt with a larger shell= to effect all command sessions, to set the environment space just for a single session, call the command with the /e switch, e.g.
>>>
>>>COMMAND /E:2048 MYAPP.EXE
>>>
>>>where /e:nnnnn is sets the initial environment size to nnnnn bytes.
>>>
>>>Q. How can I change environment variables from the command line?
>>>
>>>A. The resource kit has a utility called SETX.EXE. It enables the user to change environment settings, e.g.
>>>setx johnvariable 1
>>>setx johnvariable -k HKEY_LOCAL_MACHINE\...\DefaultDomainName