home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!virtech!cpcahil
- From: cpcahil@virtech.uucp (Conor P. Cahill)
- Subject: Re: >16MB on a 486
- Message-ID: <BuILEt.1MG@virtech.uucp>
- Organization: Virtual Technologies Inc.
- References: <2AB008AB.42F2@telly.on.ca> <BuFF20.1tq@constant.demon.co.uk> <2659@aegis.or.jp>
- Date: Sun, 13 Sep 1992 11:32:52 GMT
- Lines: 24
-
- davidg@aegis.or.jp (Dave McLane) writes:
-
- >>MEMRANGE=0-640K:0,1M-64M:0
-
- >I don't see such a file for ISC 3.2 v3.0. Anybody have any ideas?
-
- It cannot be done with ISC 2.2 or 3.0 and the testing that I did with 2.0.2
- made me believe that regarless of the setting of this file the
- system would start swapping at 16MB, so even though you can set this
- parameter in 2.0.2, I'm not sure it has any benefitial effect other
- than getting the kernel to say it sees more than 16MB.
-
- The only way that you can get more than 16MB in 3.0 is with an EISA
- system and a non-dma controller or an EISA controller in EISA mode.
- (i.e. an IDE drive, an ST-506 controller, most ESDI controllers, a
- Future Domain controller, an Adaptec 1740, Bustek 742, etc)
- Crontrollers that down work in this mode: adaptec 1542, bustek 542 and
- probably others. Remember, this is only when you have an EISA motherboard.
-
- --
- *** SENTINEL(tm) The ultimate Debugging Environment - email for more info ***
-
- Conor P. Cahill (703)430-9247 cpcahil@virtech.vti.com
- Virtual Technologies, Inc. 46030 Manekin Plaza Dulles, VA 20166
-