Date: Sun, 20 Apr 1997 08:27:53 -0400 (EDT) From: "Mike A. Harris" Reply-To: "Mike A. Harris" To: evand AT scn DOT org cc: OpenDOS AT delorie DOT com Subject: Re: Question regarding Opendos and Win#95 In-Reply-To: Message-ID: Organization: Total disorganization. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Thu, 17 Apr 1997, Evan Dickinson wrote: > On Thu, 17 Apr 1997 wfp AT ziplink DOT net wrote: > > At 00:05 97-04-17 -0400, List Server at delorie.com wrote: > [snip] > > Even simpler than that, I think. OpenDOS should execute DCONFIG.SYS before > > it even touches CONFIG.SYS, so you should be able to name it that (instead > > of ODCFG.SYS) and have it chain to its own autoexec file, bypassing > > CONFIG.SYS entirely, and avoiding the error from Win95. > > > > Oughtta work... > > Using dconfig.sys works, OpenDOS won't execute config.sys after > dconfig.sys. You can't, however, chain to a batch file from config.sys. > OpenDOS thinks the batch file is supposed to be part of config.sys. So > you still need the 'if "%config%" ...' line in autoexec.bat. No you dont. You need the full "/P:" command line option to the command processor in the SHELL= line of DCONFIG.SYS. For example: SHELL=C:\OPENDOS\COMMAND.COM C:\OPENDOS /P:C:\ODEXEC.BAT or for us 4DOS advocates... SHELL=C:\4DOS\4DOS.COM C:\4DOS /P:C:\ODEXEC.BAT This tells the command processor to use ODEXEC.BAT *INSTEAD* of AUTOEXEC.BAT. As an interesting addition, one may pass parameters to the file named in the /P: parameter. This is true for 4DOS, I'm not sure about COMMAND.COM in OpenDOS though. Enjoy. Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris Computer Consultant | Coming soon: dynamic-IP-freedom... My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html Email: mharris at blackwidow.saultc.on.ca <-- Spam proof address LINUX: The ONLY bulletproof 32-bit operating system that has it all.