Hello Gerald!
Quoting Gerald's message:
 GM> I can't help but wonder if the "@C:\4DOS\4DOS.INI" section in your
 GM> CONFIG.SYS could be causing _some_ of the problem...  I had my 
ONFIG.SYS
 GM> file established in a manner similar to yours and for some reason that I
 GM> forget, I dropped the "@C:\4DOS\4DOS.INI" from the line and I've not had
 GM> a problem.
I removed the "@C:\4DOS\4DOS.INI" from the SHELL statement in my CONFIG.SYS 
file:
    SHELL=C:\4DOS\4DOS.COM C:\4DOS /F
and kept the following statement in my 4DOS.INI file:
    AUtoExecPath = C:\4DOSEXEC.BTM
and, as expected, 4DOS called/loaded AUTOEXEC.BAT
 GM> With your /PC:\4DOSEXEC.BTM example, I think you should try renaming it
 GM> to a BAT file and use a LOADBTM ON statement within your 4DOSEXEC.BAT
 GM> file...
Prior to giving the BTM extension, the file was called 4DOSEXEC.BAT and it 
was never loaded...
 GM> Or -- Drop the C:\4DOSEXEC.BTM part from your /P directive; you have
 GM> it specified within the 4DOS.INI file (AutoExecPath =
 GM> C:\4DOSEXEC.BTM) and the system could be confused that the filename
 GM> is specified TWICE! ???
That is what I tried, again without success...
4DOS insist in caling/loading AUTOEXEC.BAT
 GM> Try the following:
 GM>     SHELL=C:\4DOS\4DOS.COM C:\4DOS\ /P
 GM> and maintain your "AutoExecPath = C:\4DOSEXEC.BTM" within your 4DOS.INI
 GM> file (or maybe move it to 4DOS -- "AutoExecPath = C:\4DOS\4DOSEXEC.BTM")
 GM> [you may also have to move the AUTOEXEC.BAT file to C:\DOS]...
I tried some of the above suggestions, except moving AUTOEXEC.BAT to another 
directory) and in every tests, 4DOS called/loaded AUTOEXEC.BAT
Sincerely, Raymond Beriau.
           Co-Moderator 4DOS
INFODATA Communications [+1 514 432 8467]
... You are a Redneck if: Your mother has ever been involved in a fistfight 
at a Hi
--- GoldED 3.00.Beta3+
---------------