Hello Klaus!
Quoting Klaus's message:
 KM> You gave so much information, that I find it difficult to discern what
 KM> you have tried and what you have not. Let us start with the above: fine.
 KM> So you should have different boot sections with different names. Let us
 KM> call this one 4DOS.
This is one of the problem when someone try to jump-in a conversation without 
having followed ALL the threads...
The problem I was facing is that, with MS-DOS v7.0, I could not call another 
boot-up file other than one called AUTOEXEC.BAT eventhought 4DOS allowed me 
to do so with the "/P" command in the SHELL statement or the "AutoExecPath" 
statement in the 4DOS ini file.
 RB>> I have been trying to get 4DOS to call a 4DOS specific AUTOEXEC file
 RB>> using the 4DOS specific command "AutoExecPath" or the SHELL command
 RB>> "/P" I removed the DOS specific AUTOEXEC.BAT file (without 4DOS
 RB>> command) and replace it with a 4DOS specific AUTOEXEC.BAT file (with
 RB>> 4DOS commands) In every tests, MS-DOS refused to run it!
 KM> ??? I cannot quite fathom this. MS-DOS cannot run any bat file. Only the
 KM> command processor can, and that is determined by the shell= line in
 KM> config.sys or defaults to command.com.
Again, being late in the conversation you would have learnt that MS-DOS v7.0 
and 4DOS (under v7.0 of MS I/O) will call only AUTOEXEC.BAT and nothing else 
as indicated in the 4DOS on-line help.
I do know that it is the command processor that will call and load BAT/BTM 
files, but in the case of MS-DOS v7.0, the first file loaded after CONFIG.SYS 
must be called AUTOEXEC.BAT - otherwise, MS-DOS v7.0 will create its own.
Sincerely, Raymond Beriau.
           Co-Moderator 4DOS
INFODATA Communications [+1 514 432 8467]
... Docs? Why would I want to look at the Docs. Nurses are better :)
--- LoraBBS-DOS v2.41b3 (Eval.)
---------------