From owner-freebsd-questions Fri Nov 22 08:25:24 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26808 for questions-outgoing; Fri, 22 Nov 1996 08:25:24 -0800 (PST) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA26803 for ; Fri, 22 Nov 1996 08:25:20 -0800 (PST) Received: (from dubois@localhost) by night.primate.wisc.edu (8.8.2/8.8.2) id KAA13883; Fri, 22 Nov 1996 10:26:56 -0600 (CST) Message-Id: <199611221626.KAA13883@night.primate.wisc.edu> Date: Fri, 22 Nov 1996 10:26:55 -0600 From: dubois@primate.wisc.edu (Paul DuBois) To: jack@diamond.xtalwind.net (jack) Cc: freebsd-questions@FreeBSD.org Subject: Re: System Commander 3.0 and FreeBSD 2.1.5 In-Reply-To: ; from jack on Nov 22, 1996 10:03:53 -0500 References: <199611220612.AAA06997@night.primate.wisc.edu> X-Mailer: Mutt 0.47 Mime-Version: 1.0 Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk jack writes: > > Any special trick to it? > > Not that I know of. In both cases I just installed the boot manager first > then installed FreeBSD where I wanted it. > > > When I installed FreeBSD on a second IDE drive, System Commander > > recognized that there was a system there, but when I told it to boot > > from it, the system just hung. > > I'd be inclined to point the finger at System Commander. Possibly, but System Commander has been one of the few bright spots in my association with DOS/Win stuff. I'd be inclined to point the finger at some mistake I made. I'll have to investigate further. -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software