Thanks for the assistance, List. I have two remaining issues.
1. Increasing the environment space for cmd.exe in NT4.0: how is it
increased? Is it even an issue for cmd.exe? I can increase the space for
the DOS env. provided by command.com, which I don't think will help me, but
can find no references to cmd.exe and its environment space.
My database update DOS batch file (running in a cmd.exe DOS box in NT 4.0)
contains one environment variable, a fully qualified file name for a log
file. I added an additional variable to the batch, a fully qualified file
name for a status file. This was maybe an additional 28 characters.
Blooey!!... the next night many servers "hung" in the update process. We
continued to have the problem until the additional variable was removed two
days later.
2a. To those on the List who are running on NT and are still running R:BASE
4.5+ or who can remember "the old days" prior to upgrade... did you run in
the cmd.exe or command.com DOS shell? We are running the R:BASE 4.5+
runtime (I know an upgrade is advisable and may be in our future... it's a
long story).
2b. Did you use command line switches on the runtime?
In my research comparing cmd.exe to command.com, I learned that command.com
is provided for backwards compatibility for older DOS apps that may have
problems interacting with the 32-bit cmd.exe.
Thanks,
Debbie
