From: wfp AT ziplink DOT net, wfp AT usa DOT net Message-Id: <3.0.1.16.19970417004836.3d377c98@pop3.ziplink.net> Date: Thu, 17 Apr 1997 00:48:36 -0400 To: OpenDOS AT delorie DOT com Subject: Re: Question regarding Opendos and Win#95 In-Reply-To: <199704170405.AAA09430@delorie.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Precedence: bulk At 00:05 97-04-17 -0400, List Server at delorie.com wrote: ... >Date: Tue, 15 Apr 1997 23:12:20 -0700 (PDT) >From: Evan Dickinson >Reply-To: evand AT scn DOT org >cc: OpenDOS AT delorie DOT com >Subject: Re: Question regarding Opendos and Win#95 ... >[snip] > >Funny thing happened just now. I had a few extra minutes, and I decided >to try booting 95 from D. And *it worked*. So first, thanks for getting >me to try. Now the caveats: > >On my computer, C and D are both partitions of the same disk. I don't >know if this'll work with two different disks. > >Win95 still uses config.sys, autoexec.bat and probably msdos.sys from c:. >There is a work-around. Copy your OpenDOS config.sys to something like >odcfg.sys. Rename autoexec.bat, too. In the first line of config.sys, >put in the command: > >CHAIN=C:\ODCFG.SYS > >This will stop processing of config.sys and start processing odcfg.sys >under OpenDOS. Win95 will print an error and stay in config.sys. >Somewhere in odcfg.sys, enter the line > ... 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... ___ ___ _ | Bill Phillips (/__) . /) /) (/__) /_ . /) /) . _ _ | ShoeString Projects /__) (__(__(___ / / )_(__(__(__(_ /_)_/_)_ | DTP Graphic Design ( ( ( | Internet Consulting NEW E-MAIL: