Re: Dual booting FreeBSD and Win95

From: Adrian Chadd <adrian_at_freebsd.org>
Date: Wed, 8 Apr 2015 12:36:56 -0700
Hi,

You can just write a little command line win32 program that writes to
the boot blocks. it's win95; unless your BIOS somehow is blocking
things you should be able to set the same area that boot0cfg does to
tell the bootloader about what to do.



-adrian


On 8 April 2015 at 12:30, Ryan Stone <rysto32_at_gmail.com> 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?
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
Received on Wed Apr 08 2015 - 17:36:57 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:56 UTC