Windows XP - Set Environment Variables Not Being Recognized
Posted on 2005-03-25
I have a 16-bit application that requires the use of three environment variables (set in System variables). The application will not launch unless it reads these variable.
Problem: The variables are properly entered and will show up in the variable list generated by the "Set" command in the "CMD" windows, but the application does not consistently read them, so it fails to launch. This is happening only on new builds of Windows XP Pro. After some playing around with the workstation (e.g. adding and deleting false set variables) the application will then read the set variables and being to work. After the application begins to work, the condition does not reappear (at least yet) on the workstations.
Is this the result of not having an environment (e.g. "File Handles", etc) set in the "config.nt" file or something of a similar nature? What are the default values for environment size, etc that could affect this condition?