Debbie,
In NT if the root of C:\ has an autoexec.bat and/or config.sys file(s), they
are used to modify/add the environment for both command.com and cmd.exe.
Otherwise the default settings are used. You will have to reboot every time
you change the autoexec.bat & config.sys. Yes, RBTI isn't the only company
with undocumented features.
I have personally had great success using mstask.exe only and not specifying
cmd.exe or command.exe when running automated r:base tasks on my NT 4 server
while using the -r -c -k1 switches. The only kiss of death I have found is
ZIP-ing during a task.
Craig Keenan
> > I have saved e-mails from this list that recommend setting files and
buffers
> > to 60 and increasing the environment space if long paths or setting
> > environment variables. Since I'm not invoking this with a .pif, I've
> > updated \winnt\system32\config.NT with these enhancements. However, the
> > settings are not recognized and I get the default environment.
Microsoft
> > TechNet states that since cmd.exe is not 16-bit, it does not use
config.NT
> > nor autoexec.NT. Only if I use 16-bit command.com as the DOS
environment
> > will these files be used. Is there a way to increase files, buffers,
and
> > environment space when using cmd.exe? In which DOS environment should
the
> > dos4gw/rbase runtime be running (cmd.exe or command.com)? Also, I'm not
> > using any command line switches other than "-r" on the runtime.
