Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!overload.lbl.gov!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (A Wizard of Earth C) Subject: Re: EISA CONFIG (was: AHA1742) Message-ID: <1993Jul14.202530.11033@fcom.cc.utah.edu> Sender: news@fcom.cc.utah.edu Organization: Weber State University, Ogden, UT References: <1993Jul13.172743.15441@fcom.cc.utah.edu> <9307140053.aa03714@post.demon.co.uk> Date: Wed, 14 Jul 93 20:25:30 GMT Lines: 20 In article <9307140053.aa03714@post.demon.co.uk> damian@centrix.demon.co.uk (Damian Ivereigh) writes: >terry@cs.weber.edu (A Wizard of Earth C) writes: >: In this same vein, isn't it about time that we got some EISA configuration >: code ported to something other than DOS? > >Yes an excellent idea. Although isn't there a problem in that basically >you are messing about in people's CMOS setup, i.e. that it is all >proprietry to each manufacturer. I never found you use the config >disk reliably from one m/c to another. This is generally due to differences in system board configs rather than a real difference in the config software itself (ALR/Dell/Compaq/NoName config experience speaking). Terry Lambert terry@icarus.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.