Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!nntp.neu.edu!hypnos!dave From: dave@hypnos.neu.edu (Dave Brady) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD + NT-- anyone done it? Date: 24 Apr 1996 20:25:16 GMT Organization: Northeastern University, Boston, MA. 02115, USA Lines: 33 Message-ID: <4lm2nc$l74@chaos.dac.neu.edu> References: <960418162400-rrwood@io.org> <3177852F.167EB0E7@mindspring.com> <317A208C.794BDF32@interbay.net.au> NNTP-Posting-Host: hypnos.acs.neu.edu X-Newsreader: TIN [version 1.2 PL2] > > **************************************************************************** > Want to do something similar but a little different, ie. install NT 3.51 > Server on on my first hard drive which currently had DOS/Windows 3.11 on > it. Am running FreeBSD 2.0.5 on my second hard drive, and the boout > manager (not OSBS) manages this as it should. My question is, will NT > overwrite the master boot record during install, will it allow multiple > boots across drived and pick up the FreeBSD drive. If not, can OSBS > replace the FreeBSD boot manager on the fly or must it be done at install > time. I've spent a lot of time customising etc. my FreeBSD system and > don't want to have to do it all over again. You might say why not install > NT on another machine. Well, I want to run httpd 3.0 and NT Server 3.51 > both from the same machine so as to compare them. Also I got NT at one of > those Microsoft OEM briefings and otherb than the doc etc. files on the > cd, there is no support from Microsoft or written documentation. I have NT 3.51, OS/2 and FreeBSD sharing two drives, using OS/2's Boot Manager. What I can tell you, though, is that after you install NT, do NOT, under any circumstances, run Disk Administrator. It will wreck your partition mapping and OS/2's fdisk will be unable to make any changes to your drives. I hear that Microsoft knows about this problem, but I haven't heard if they've fixed it. Anyone heard anything? -- Dave Brady Sr. UNIX System Administrator Administrative Computer Services Northeastern University Boston, MA 02115 dave@acs.neu.edu (617) 373-4156