Hallo Raymond
RB> I have and only had one CONFIG.SYS file with different boot options.
You gave so much information, that I find it difficult to discern what you 
have tried and what you have not. Let us start with the above: fine. So you 
should have different boot sections with different names. Let us call this 
one 4DOS.
RB> I have/had only one AUTOEXEC.BAT to boot with COMMAND.COM
??? In the scenario outlined above, you should have an Autoexec.bat with 
labels that correspond to your section names (4DOS) and a line "GOTO 
%CONFIG%" at the beginning of that file, like this:
  goto %config%
  :4DOS
  ...
  ...
  goto END
  :MSDOS
  ...
  ...
  goto END
  ...
  ...
  :END
You can then put your 4DOS specific commands after the :4DOS label. Further 
places to look at are 4START.BTM, where 4DOS specific commands can be placed.
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 "/P"
RB> 
RB> I removed the DOS specific AUTOEXEC.BAT file (without 4DOS command) and 
RB> replace it with a 4DOS specific AUTOEXEC.BAT file (with 4DOS commands)
RB> 
RB> In every tests, MS-DOS refused to run it!
??? I cannot quite fathom this. MS-DOS cannot run any bat file. Only the 
command processor can, and that is determined by the shell= line in 
config.sys or defaults to command.com. I have a multiconfig too, with 
autoexec labels to match, and everything runs fine with CC or 4DOS in several 
setups. The above would mean that CC checks autoexec in it's entirety and 
refuses to execute it if it finds an unknown command and selects another 
(which? what is the contents of that file?) file instead of simply echoing 
some error message. Without testing I am tempted to say that I cannot believe 
that. (I know all this is unrelated to the disputed functionality of the 
4DOS.INI directive AutoexecPath)
Did you try to single step through the boot sequence (Key F8 afair)? 
RB> And all the above were checked without booting Windows 95.
Very sensible. Boot to shell 0, then give the WIN command manually (or by 
default after 2 seconds from autoexec). Perhaps your troubles come from some 
obscure MSDOS.SYS setting: Here are mine, mostly set to default values, and I 
have ommited those XXXs here:
  [Paths]
  WinDir=C:\WINDOWS
  WinBootDir=C:\WINDOWS
  HostWinBootDrv=C
  [Options]
  AutoScan=2
  BootDelay=0
  BootWarn=1
  BootKeys=1
  BootMenuDefault=1
  BootMulti=0
  BootGUI=0
  Network=1
  DoubleBuffer=1
  Logo=0
  DBLSpace=0
  DRVSpace=0
  LoadTop=1
Grsse aus Ostrhauderfehn, 
*Klaus Meinhard*
--- FIPS/32 v0.99b W95/NT [M]
---------------