Hello Klaus!
Quoting Klaus's message:
 KM> Simply kill any _other_ CONFIG.XXX and AUTOEXEC.XXX than your current
 KM> CONFIG.SYS and AUTOEXEC.BAT. In my experience W95 will take the one
 KM> that's left for all modes (is that the right word?).
I tried something like that, if I understand what you are writing...
I have and only had one CONFIG.SYS file with different boot options.
I have/had only one AUTOEXEC.BAT to boot with COMMAND.COM
I have been trying to get 4DOS to call a 4DOS specific AUTOEXEC file using 
the 4DOS specific command "AutoExecPath" or the SHELL command "/P"
I removed the DOS specific AUTOEXEC.BAT file (without 4DOS command) and 
replace it with a 4DOS specific AUTOEXEC.BAT file (with 4DOS commands)
In every tests, MS-DOS refused to run it!
Unless it was a DOS specific AUTOEXEC file (without 4DOS command), MS-DOS 
insisted in using its own AUTOEXEC.BAT file, although I could not find any 
reference of it on the disk.
How do I know that MS-DOS was using its own AUTOEXEC.BAT file is that a path 
and some variables were set up and available...
And all the above were checked without booting Windows 95.
Sincerely, Raymond Beriau.
           Co-Moderator 4DOS
INFODATA Communications [+1 514 432 8467]
... If it wasn't for C, we would be using BASI, PASAL and OBOL!
--- GoldED 3.00.Beta3+
---------------