Date: Wed, 8 Apr 2015 23:03:29 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Ryan Stone <rysto32@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Dual booting FreeBSD and Win95 Message-ID: <20150408200328.GA1394@zxy.spb.ru> In-Reply-To: <CAFMmRNw=2fXw4ohn%2BxetuQtESEvMnmrNONi093Sz3FY2rQiAdQ@mail.gmail.com> References: <CAFMmRNw=2fXw4ohn%2BxetuQtESEvMnmrNONi093Sz3FY2rQiAdQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 08, 2015 at 03:30:41PM -0400, Ryan Stone wrote: > No, this isn't a late April Fools joke. :( > > I find myself in a situation where I need to integrate my employer's > manufacturing process with a third-party OEM's process. My employer's > hardware tests are all FreeBSD-based while the OEM is Windows 95 based. I > need to come up with a way to integrate them together. > > We're looking at dual-booting FreeBSD and Win95. We're thinking of booting > into Win95, the OEM can do their thing, switch to booting FreeBSD, run our > tests and produce a .csv file with the results, and then boot back into > Win95 for them to finish up. Ideally we would like to switch the boot > slice without human interaction. > > I've been playing around with trying to set one only slice as active to > make the loader boot it, but it appears that doesn't actually work. > boot0cfg would cover half of the use case (switching from FreeBSD back to > Win95), but I'm not sure how I could do the original switch from Win95 to > FreeBSD. > > We've discussed just switching hard drives, but we really want to shoot for > a 100% automated process. Anybody have any ideas? If hardware recognised by Win95 do next: 1. create MBR patition table. first patition dedicate to Win95. next partiton to freebsd 2. install Win95 3. Install FreeBSD with FreeBSD boot manager. 4. (optional) create windows95 boot.ini for fail back load FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150408200328.GA1394>