Hello Bill!
Quoting Bill's message:
 RB>> Well, no matter what I do and what I try, I cannot get 4DOS to call
 RB>> (load) directly 4DOSEXEC.BAT - for some unknown reasons, 4DOS alway
 RB>> call (load) AUTOEXEC.BAT first.
 BD> As far as I am aware, the subsidiary-batchfile-exec process is *in
 BD> addition* to the Autoexec.Bat -- it is not a substitute.
Not according to the help file - check the AutoExecPath information:
    Sets the path used to find AUTOEXEC.BAT if 4DOS is started as a
    primary shell with the /P option in CONFIG.SYS.  If you include
    only a path, 4DOS will look for AUTOEXEC.BAT in the specified
    directory.  If you include a complete filename, 4DOS will look
    for the specified file, and will not look for AUTOEXEC.BAT.  The
    default is the file AUTOEXEC.BAT in the root directory of the
    boot drive.
    Using AutoExecPath with a complete filename lets you store multiple
    startup files in a single directory.  you may find this useful if
    you have multiple boot software and use different startup files under
    different configurations...
 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.
I don't think so...  As I explained already, I have 4DOSEXEC.BTM in both 
CONFIG.SYS:
    SHELL=C:\4DOS\4DOS.COM C:\4DOS @C:\4DOS\4DOS.INI /PC:\4DOSEXEC.BTM
and in 4DOS.INI:
    AutoExecPath = C:\4DOSEXEC.BTM
and, if I don't place a special command in AUTOEXEC.BAT, 4DOSEXEC.BTM is 
never loaded...
 BD> Best I can do for now. 
I just wish that Rex Conn would answer my question...  :(
Sincerely, Raymond Beriau.
           Co-Moderator 4DOS
INFODATA Communications [+1 514 432 8467]
... !sdohtem noitpyrcne devorppa-tnemnrevog troppus I
--- GoldED 3.00.Beta3+
---------------