KM>Hallo Bill
BD> Hi, Raymond.  As far as I am aware, the subsidiary-batchfile-exec
BD> process is *in addition* to the Autoexec.Bat -- it is not a
BD> substitute.
BD> 
BD> The intent is to put 4DOS-specific commands in the 4DOSEXEC.BAT
BD> and leave commands that are generic to both COMMAND.COM and 4DOS
BD> in the AUTOEXEC.BAT file.
KM>Sorry, Bill, but I think you mistake that for 4START.BTM. 
KM>Raymond has a valid point / question / bug / whatever.
Hi, Raymond.  I've copied to you my reply to Klaus.
I've reviewed the docs, and I agree with Raymond and your
interpretations.  4DOSEXEC.BAT is supposed to replace AUTOEXEC.BAT
with the proper adjustments to 4DOS.INI.
However, DOS 7.0 and later has the ability to use "Exclusive Mode",
which transparently rewrites CONFIG.SYS and AUTOEXEC.BAT and reboots
the machine using those files in place of the originals (which are
saved under different names for reversion when the exclusive-mode
DOS session is complete).
As far as I can see, the exclusive-mode operational paradigm is
incompatible with changes to the bootfile names.  Retaining
compatability with exclusive-mode may be the reason for Raymond's
problem.
Best I can do for now. 
Bill
___
 * PW * 
--- Maximus 2.02
---------------