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!news.ecn.uoknor.edu!paladin.american.edu!gatech!news.emf.net!imci3!imci4!newsfeed.internetmci.com!news.mathworks.com!uhog.mit.edu!news.mtholyoke.edu!nntp.et.byu.edu!news.byu.edu!news From: clark@abraham.et.byu.edu (Clark B Sessions) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: BSDI v2.1 and OS/2 Warp Boot Manager? Date: 29 Apr 1996 18:38:17 GMT Organization: Brigham Young University, Provo UT USA Lines: 41 Message-ID: <4m32ap$353@jan.et.byu.edu> References: <4kl1i4$2uq@ananke.milkyway.com> <4kogm9$6c2@doctor.nl2k.edmonton.ab.ca> NNTP-Posting-Host: abraham.et.byu.edu X-Newsreader: TIN [version 1.2 PL2] 2,99985,99987,99989-99991,99993,99997,100002,100006,100008,100010,100017,100019,100021,100028,100034,100036,100040,100044-100046,100051-100053,100055,100060,100063,100066,100071-100073,100075-100076,100079,100081,100084,100089,100102-100104,100115,100122,100124,100127-100128,100131,100139-100141,100143,100146,100163,100165-100166,100187,100189,100191,100193,100195,100200,100202,100205,100212,100223,100232,100242,100246-100247,100259,100266,100270,100275,100277,100280,100287,100291,100293-100294,100296,1002 99,100301,100305,100308,100312,100315,100317-100318,100321,100327-100329,100341-100342,100346-100347,100349,100355,100357,100370-100371,100373,100379,100383-100384,100388,100393,100395,100397-100398,100404-100405,100407-100408,100411,100414,100423,100428,100430,100434-100435,100441,100449-100450,100452,100455,100460,100467-100469,100476-100477,100482,100487,100489-100491,100493,100501,100504-100505,100518,100524,100526,100528,100530-100531,100543,100548,100550-100551,100556-100558,100564,1 : In article <4kl1i4$2uq@ananke.milkyway.com>, : John C. Griggs <jgriggs@ananke.milkyway.com> wrote: : >Greetings, : > : >I'm attempting to help a colleague set up a Pentium 100 with an adaptec 2940 to run both Windoze95 and BSD/OS v2.1. He has decided to use the BootManager from OS/2 Warp to select which OS to run at boot time (it's got a nice menu and a timeout and stuff). We're having a devilish time getting BSD/OS and the BootManager to co-exist - it looks like BSD/OS confuses BootManager's idea of what the active partition is. : > : >My question is: Is what we're attempting to do fundamentally sane, or is there really no chance we'll ever succeed? Any advice and suggestions as to how to get this going would be much appreciated. : > : >Cheers, : > John Griggs : The easiest answer is: : Istall BSDI BM so that you can choose between BSDI and BM : and then let BM take charge. : -- : God, Queen and Country Member - Liberal International : NEVER Satan, President and Republic Board Member - Edmonton Heritage Nazarene : Hating Bachelor's Living; Doctor Who returns: 13 May at BAFTA for DWAS, 14 May on Fox for NA, 27 May on BBC1 - check rec.arts.drwho for local gatherings : http://doctor.nl2k.edmonton.ab.ca/~doctor British Columbia, beware of Van Der Zalm Reform and Harcourt/Clark NDP. I have WIn95. OS/2 and BSDI v2.1 going using the OS/2 BM. Here is how I did it: First, I had OS/2 parition the disk and create DOS paritions for each OS. This allowed OS/2 BM to make each of them bootable and add them to the BM. I put the BM at the end of the freespace. Second, Install each OS, noteabley WIN95 to the C:, next WARP, and then BSDI. While installing BSDI I deleted the DOS extended parition and used BSDI's disk setup to parition the freespace for BSDI. One note here is that I first installed BSDI 2.0.1 and then upgraded to 2.1. hope this helps, Clark Sessions clark@byu.edu