Hello Raymond,
 \|/  Subject:  Calling another batch file...
 /|\  On Tuesday April 21 1998 at 14:59, 
      you wrote to Gerald Miller saying:
 GM>> I can't help but wonder if the "@C:\4DOS\4DOS.INI" section in
 GM>> your CONFIG.SYS could be causing _some_ of the problem...  I had
 RB> I removed the "@C:\4DOS\4DOS.INI" from the SHELL statement in my
 RB> CONFIG.SYS file:
 RB>     SHELL=C:\4DOS\4DOS.COM C:\4DOS /F
                                         ^???  I assume this to be /P?
 RB> and kept the following statement in my 4DOS.INI file:
 RB>     AUtoExecPath = C:\4DOSEXEC.BTM
 RB> and, as expected, 4DOS called/loaded AUTOEXEC.BAT
 RB> I tried some of the above suggestions, except moving AUTOEXEC.BAT to
 RB> another directory) and in every tests, 4DOS called/loaded AUTOEXEC.BAT
At this point, all I can say is to move AUTOEXEC.BAT to somewhere not on the 
path...  If 4DOS.INI could see: "AUtoExecPath = C:\4DOS\4DOSEXEC.BTM" and 
AUTOEXEC.BAT was located as C:\DOS\AUTOEXEC.BAT, would that improve the 
possibilities?
Number one, because both these files are in the root directory, I think the 
command processor (both 4DOS.COM and COMMAND.COM) default to loading 
AUTOEXEC.BAT.
Number two, keep a bootable floppy close at hand for the possible failure 
when you finally decide to relocate these two files elsewhere.   :-))
              G'Day ... Gerald
--- GoldED/386 2.50 UNREG
---------------