From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 19:36:57 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB92B4E3 for ; Wed, 8 Apr 2015 19:36:57 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D24BD74 for ; Wed, 8 Apr 2015 19:36:57 +0000 (UTC) Received: by iget9 with SMTP id t9so35683509ige.1 for ; Wed, 08 Apr 2015 12:36:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3rC3NGNSxzLH7Uoj6o4XnKEoHOX+yUlQjqNa3xqFozs=; b=HlxOhDuHcM8x4fmaKfuX0lqXy/09nXZo8ETqcOkwTIfxoK3bCF/4VkOjtULkDgg/Co eooi/wwSXy57y0lpIB2HAE+Em6jMNUGxBcBa5GWgE+qPwXt7In2ysIVKFmRTfmNiWhZq 5IOCBFcenRkZ/nMtlKmn1M1AGuPhCi769QQilGDW5Q6XMZTZ6rrrP5iPusiGAaxpdUij IJ6LjwegdsmCwehy4R2aNhnD1phR3mswQYsova+LXAoPtOq7lJi+Zuc3wR5N73ntmuHK xXTGwWagfNNhu5IBcPc/iufii8gEqvFr448I48+/x2K0u4PQgvw0Ga7+4soJTmaQAkt8 0kRg== MIME-Version: 1.0 X-Received: by 10.50.73.168 with SMTP id m8mr14473841igv.32.1428521816890; Wed, 08 Apr 2015 12:36:56 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Wed, 8 Apr 2015 12:36:56 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 Apr 2015 12:36:56 -0700 X-Google-Sender-Auth: yiEIcVhOJfIxk63wR6sqp6tW7mI Message-ID: Subject: Re: Dual booting FreeBSD and Win95 From: Adrian Chadd To: Ryan Stone Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2015 19:36:57 -0000 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 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"