Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!newsfeed.internetmci.com!news.wwa.com!news.ucdavis.edu!relay.nuxi.com!obrien From: David E. O'Brien <obrien@relay.nuxi.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.2.1 install fails Date: 27 May 1997 00:44:05 GMT Organization: University of California, Davis Lines: 13 Message-ID: <5mdaol$kkj$3@mark.ucdavis.edu> References: <33813e59.68052@news.tiac.net> <33805bab.38282@news.tiac.net> <33807b44.302856@news.tiac.net> <3382059e.71622@news.tiac.net> NNTP-Posting-Host: nuxi.ucdavis.edu Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41642 > Some part of the install process also appeared to do something > obnoxious to System Commander 3.0, resident in c:\sc. - i had to You probably intalled the standard boot blocks, or the booteasy ones. I usually install the standard ones (allowing the install to over write my System Commander setup). Since it is quite easy to reintall SC and it finds most of my previous config, its not a big deal to me. Otherwise, select "do not write boot blocks" or what ever the real words are. Then after the install, reboot and at the SC prompt enter setup to add FreeBSD. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org)