Return to BSD News archive
Xref: sserve comp.unix.bsd:4379 comp.os.os2.misc:28234 Path: sserve!manuel!munnari.oz.au!uunet!usc!isi.edu!allard From: allard@isi.edu (Dennis Allard) Newsgroups: comp.unix.bsd,comp.os.os2.misc Subject: Re: DOS + OS/2 2.0 + 386bsd 0.1 installation ..... Message-ID: <22300@venera.isi.edu> Date: 1 Sep 92 01:26:55 GMT References: <1992Aug28.220423.9273@umr.edu> Sender: news@isi.edu Reply-To: allard@isi.edu (Dennis Allard) Distribution: world Organization: USC Information Sciences Institute Lines: 49 jlu@cs.umr.edu (Eric Jui-Lin Lu) writes: > After spending nights of reformats, reboots, and reinstallations, I > kinda came out a wierd combination of DOS, OS/2, and 386bsd in one > hard disk. I used os-bs ... I have not yet tried to use os-boot. I used to have DOS, OS/2, and 386BSD each in their own primary partion, and used the OS/2 boot manager in a fourth (and final) primary parition. In other words, I had: OS/2 boot manager 1 meg OS/2 HPFS 40 meg DOS FAT 200 meg or so 386BSD 200 meg or so (I'm on a 490meg Fujitsu disk) I did not like this solution for a couple reasons. First, since these are all primary paritions, they are invisibile to each other. Second, 386BSD /usr/dist/bin/shutdown -todos does not currently work if the DOS partition is > 32 meg. So, I now am using a different solution. free space 2 cylinders (I'm hoping that os-boot will go here) DOS FAT 31.2 meg (some integral number of cylinders) 386BSD 250 meg DOS extended 200 meg or so I have a 160meg logical D: FAT partition in the extended partion and I am going to install OS/2 in its own logical partition, which is possible, according to OS/2 documentation. I have not yet tried to do so, however. The advantages to my current setup are that I can now do shutdown -todos and, once I have OS/2 up, it will be able to see the DOS D: drive, hence enabling me to share DOS files with OS/2. > ... I'm not quite satisfied with this. Since > when I choose OS/2, OS2 boot manager menu comes up. I wish to > eliminate this OS/2 boot manager totally. The only reason I can think of for it to be there is because you have a seperate OS/2 boot manager partition which is what os-bs is actuallty booting to when you chose OS/2. Dennis allard@isi.edu