Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA1918 ; Tue, 23 Feb 93 15:04:03 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!pagesat!spssig.spss.com!news.oc.com!convex!sunshine
From: sunshine@convex.com (Roger Sunshine)
Newsgroups: comp.os.386bsd.questions
Subject: 386bsd, OS/2 & Always IN2000
Summary: Do any of these work together?
Keywords: IN2000, OS2
Message-ID: <sunshine.730408077@convex.convex.com>
Date: 22 Feb 93 19:07:57 GMT
Sender: usenet@news.eng.convex.com (news access account)
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
Lines: 21
Nntp-Posting-Host: zeppelin.convex.com
X-Disclaimer: This message was written by a user at CONVEX Computer
Corp. The opinions expressed are those of the user and
not necessarily those of CONVEX.
Now that I finally have some disk space, could anyone answer for me the
following questions?
1) Does 386BSD coexist with OS/2 boot manager? I've got OS/2 installed
and would like to retain it. I'd like to install 386BSD in an extended
partition on drive 0 (up to 96M available) and then mount a partition
from drive 1 (also an extended partition, up to .5G). Since DOS (and OS/2)
both screw up the drive letter assignment when you add primary partitions,
putting 386BSD in a primary partition would be out of the question.
2) Does 386BSD support the Allways IN2000 scsi controller? Can the generic
"int 13" (eg mfm/wd1003) driver be used instead? OS/2 works just fine
(although probably not as fast as it should) using the generic int 13
driver, so I figure 386bsd should too?
Thanks, Roger
--
----------------
Internet: sunshine@convex.com
UUCP: ...!uunet!convex!sunshine
ATTNET: (214)497-4779