Program Change History
----------------------

1.00.02 - If an Environment Variable File was specified in the REXECD Control
          Panel applet and the file did not exist, it could cause the service
          to abort with an exception error.

1.00.01 - Was skipping the last line in the Environment Variable File, so
          the variable specified on the last line was not set.

        - Windows 95/98 has a strange anomaly involving 32-bit programs
          calling 16-bit programs (including batch files, which are executed
          by command.com, which is still 16-bit).  32-bit programs cannot
          build an environment block (as REXECD/95 does when you specify and
          Environment Variable File) and pass it directly to a 16-bit program.
          It must use an intermediary 32-bit program to pass the variables.
          When redirecting standard I/O, REXECD/95 uses an intermediary program,
          so environment variables do get passed to 16-bit programs.  However,
          if standard I/O redirection is disabled (either by unchecking
          the "Attempt Redirection on Every Command?" option in the Control
          Panel or by using the "<[WIN]>" directive on the command line), these
          16-bit programs were not getting the environment created using the
          Environment Variable file.  Since I/O redirection was not necessary,
          REXECD/95 itself executed the program, directly passing it an 
          environment block, which Windows 95/98 did not pass on to the 16-bit
          program, so it did not see any of the variables set in the file.

          Now, if the program executed ends with .bat or you have checked the
          option "Execute All Commands through Command Shell?" and your
          default command shell is "command.com", and redirection is disabled,
          REXECD/95 will use and intermediary program to execute the command
          so the environment variables are correctly passed to the program.
          This does NOT solve all problems.  REXECD/95 cannot tell whether the
          program you are executing is 16-bit or 32-bit, so if you try to
          execute 16-bit .exe or .com files through REXECD/NT with I/O
          redirection disabled, they will NOT receive the environment variables
          in the Environment Variable File.  Again, this is a shortcomming of
          Windows 95/98, not REXECD/95.

          The only solution to passing environment variables to a 16-bit .exe
          or .com program is to enable I/O redirection if you have it disabled,
          either through the Control Panel or by using the "<[CON]>" directive
          on the command line.  (NOTE - by default, I/O redirection is enabled.)

1.00.00 - Initial Release

