From owner-freebsd-chat Sat Oct 4 10:53:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27233 for chat-outgoing; Sat, 4 Oct 1997 10:53:02 -0700 (PDT) Received: from shasta.wstein.com (shasta.wstein.com [207.173.11.132]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27228 for ; Sat, 4 Oct 1997 10:52:59 -0700 (PDT) Received: (from joes@localhost) by shasta.wstein.com (8.8.7/8.8.7) id KAA01607; Sat, 4 Oct 1997 10:52:39 -0700 (PDT) From: Joseph Stein Message-Id: <199710041752.KAA01607@shasta.wstein.com> Subject: fbsdboot.exe In-Reply-To: from Tim Vanderhoek at "Oct 3, 97 05:27:18 pm" To: hoek@hwcn.org (Tim Vanderhoek) Date: Sat, 4 Oct 1997 10:52:39 -0700 (PDT) Cc: chat@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > No, but there is /usr/mdec/fbsdboot.exe. It won't work if you're > running too many memory managers, or whatnot. FWIW, I have a > Win95 login, "fbsd", which just boots to DOS mode and runs > fbsdboot.exe... Is using fbsdboot "the same as" a warm reset into freebsd? (I have a PNP card that requires an DOS program _each_ time the system is power-cycled; therefore I have a DOS disk with the autoexec batch file set to run that utility, but then I have to be around to warm boot the machine.) joe