From owner-freebsd-hackers Sat Mar 14 21:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13818 for freebsd-hackers-outgoing; Sat, 14 Mar 1998 21:21:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org (tc-8.acadiau.ca [131.162.2.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13806 for ; Sat, 14 Mar 1998 21:20:55 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id BAA00579; Sun, 15 Mar 1998 01:20:22 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 15 Mar 1998 01:20:16 -0400 (AST) From: The Hermit Hacker To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: Adding a Boot-Mgr... In-Reply-To: <199803090502.VAA13161@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Mar 1998, Mike Smith wrote: > > > > Until recently, I haven't had enough disk space in order to > > install other operating systems, but just acquired a couple of extra > > drives. I want to install Win95 onto one of them for the explicit purpose > > of running Simply Accounting for the business. > > > > How do I, if I can, go about adding in a boot-mgr so that I can > > dual boot? > > Windows 95 can only be booted from the first disk in the system, unless > you invest in one of the commercial boot managers. > > Lots of people have recommended System Commander for this. > > The cheaper way of doing it: > > - Reconfigure your /etc/fstab so that FreeBSD will run as the second > disk. > - Reconfigure the disk that FreeBSD is on to be the second disk. > - Install the new disk for W95 as the first disk, > - Install W95 on it. > - Put the 'bootinst.com' and 'boot.bin' files on a bootable DOS floppy > (get them in the tools directory on any FreeBSD release disk), and > use them to install booteasy on your first disk. Finally got a chance to work on this...First thing I tried was to leave the drives as is, and do the 'bootinst' to write the boot blocks...rebooted the machine, now it gives me: F1 - FreeBSD F5 - disk 2 If I hit F1, it gives me the menu back again...if I hit F5, I get: F1 - DOS F2 - FreeBSD F5 - disk 1 If I hit F1, I get "Non-system disk", if I hit F2, I get the 'boot:' prompt, where I have to type 'wd(0,a)/kernel' to get a boot to my hard drive. So, now I swap the drives, so that my 'Primary IDE' becomes Secondary, and vice versa, and then boot. I get the second menu first (as expected), at which I can hit F1, and it boots to DOS, and if I hit F2, I get the boot: prompt again. Note that my boot (FreeBSD) disk is now on disk 2, not disk 1, with disk two being primary drive on secondary IDE chain. At the boot: prompt, I type in wd(2,a)/kernel, and get a bunch of: Error: D:0x82 C:0 H:0 S:0 If I type in wd(1,a)/kernel, I get the boot sequence (dmesg output?), but after its reported all my hardware (accurately), I get a crash when it tries to mount wd1a ... If I boot off floppy and do the fixit disk, I can mount /dev/wd2a properly...so why can't I seem to get it from the 'boot:' prompt? I'm running 3.0-CURRENT right now, if that means anything... Help? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message