From owner-freebsd-questions Thu Jan 4 10: 4:25 2001 From owner-freebsd-questions@FreeBSD.ORG Thu Jan 4 10:04:21 2001 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from pfa0frpk001.panasonicfa.com (unknown [38.248.119.1]) by hub.freebsd.org (Postfix) with ESMTP id 20DC437B404 for ; Thu, 4 Jan 2001 10:04:20 -0800 (PST) Received: by exchange.panasonicfa.com with Internet Mail Service (5.5.2650.21) id ; Thu, 4 Jan 2001 11:58:08 -0600 Message-ID: <054F7DAA9E54D311AD090008C74CE9BD01F1E839@exchange.panasonicfa.com> From: "Zaitsau, Andrei" To: 'Nicholas Basila' , "'SKemokai@ORA.FDA.GOV'" Cc: "'freebsd-questions@FreeBSD.ORG'" Subject: RE: FW: Mutlti-boot w/win2k professional Date: Thu, 4 Jan 2001 11:58:05 -0600 Return-Receipt-To: "Zaitsau, Andrei" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmmm...That's really interesting. I installed FreeBSD 4.1.1, but when I boot. Boot Manager can see only FreeBSD.... But not W2K NTFS partition. But as soon as I changed NTFS to FAT it works fine. I have 15GB for W2K and 5GB for FreeBSD. May be I should try 4.2 version. Or did you have to pass some special options arguments to boot NTFS? Interesting - I'm running 4.2 FreeBSD on a laptop with Win2K Pro using NTFS. I have no problems. I had to make FreeBSD the active partition, but the FreeBSD boot manager works without a hitch. I have the root filesystem in a small eight meg partition at the beginning of the drive, then a 10GB partition for Windows. Perhaps the older version of the Boot manager (3.3?) didn't support NTFS? > From: Zaitsau, Andrei [mailto:AZaitsau@panasonicfa.com] > Sent: Thursday, January 04, 2001 11:05 AM > To: 'Kemokai, Saffa'; 'freebsd-questions@FreeBSD.ORG' > Subject: RE: Mutlti-boot w/win2k professional > > I think You can use 1 Drive but with 2 partitions on it.... 1st one For > FreeBSD 2nd one for W2K. > But if it's already installed(I mean W2K and FreeBSD) try to set FreeBSD > partition as active (e.g. with help of fdisk), but do not set Microsoft > partition as active. > And one more thing, I do not know if FreeBSD boot Manager will boot NTFS > Microsoft Partition (At least I could not work it out), but when I used FAT > filesystem with W2K pro it boots fine with FreeBSD. > Good Luck ! > > > I think you have just provided me with major issues to look at now. My W2K > is in NTFS format. NTFS/FAT may in fact be the issue. Let me play with it > with these new info. > > Thanks > > Saffa > > I had the same configuration. > The thing I did: > 1) Created 2 partitions on Hard Drive > 2) On the second partition I installed W2K Pro > 3) I made 1st partition active and installed FreeBSD 4.1.1 > 4) I used FreeBSD boot manager. > Whoalah, it worked ! I had choice between W2K and FreeBSD :) > Andrei. > > Thanks Andrei: > > It does look exactly what I did except I used 2 separate drives - drive 0 > holding w2k and drive 1 holding FreeBSD. I was hoping that by default, > FreeBSD will load the bootloader on drive 0 or C. Maybe I do have machine > situation since I started out doubting the Bios itself anyway...:) > > SaffA > > > Hello: > > I am not sure whether I have a machine problem per se or config problem > trying to multi-boot FreeBSD 3.3 with Windows 2000 Professional. > > I had Win2k installed first. I later installed FreeBSD 3.3 making sure that > BfreeBSD boot manager is accepted or included during the process of creating > the slices. The installation completed fine but does boot to multi > environment to select the OS I want to use. Instead, it boots directly into > Win2k. > > Any ideas what needs to be done here? > > Thanks ..:) > > Saffa > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message