From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 26-AUG-1989 06:41
To:	MRGATE::"ARISIA::EVERHART"
Subj:	RE: Description of VAX 8xxx MEMCONFIG.DAT file

Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Sat, 26 AUG 89 02:49:36 PDT
Received: from ucbvax.Berkeley.EDU by KL.sri.com with TCP; Sat, 26 Aug 89 02:22:58 PDT
Received: by ucbvax.Berkeley.EDU (5.61/1.37)
	id AA02657; Sat, 26 Aug 89 02:21:07 -0700
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 26 Aug 89 04:57:53 GMT
From: shlump.nac.dec.com!mountn.dec.com!coors.dec.com@decwrl.dec.com  (Mario Herodotus - Digital Customer Support Center (800) 525-6570)
Organization: Digital Equipment Corporation
Subject: RE: Description of VAX 8xxx MEMCONFIG.DAT file
Message-Id: <705@mountn.dec.com>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com


I had to post this here because mail to Greg was bounced back "node not known"

Hi Greg,

	I think this is the info you are looking for.  I hope this helps you.

        First of all the file MEMCONFIG.DAT will be recreated by SYSINIT.COM 
if the file is deleted or renamed.  If you are having a problem with it, the 
first thing to do is rename it and see if you get a good one after running 
SYSINIT.  If you are using EMC2 memory or you don't get a good MEMCONFIG 
after running SYSINIT here's the info you're looking for.

The number in the first column is the primary array.
The number in the second column is the secondary array.
The number in the third column is the Valid bit
The number in the fourth column is the range of memory.

The primary and secondary baords are the two bords that are interleaved.
The Valid bit set means the boards are interleaved. (Must be set)
The range of memory is the range of memory that these boards will contain.

 2 4 1 0   Array 2 and 4 are interleaved and contain loacations 0 to 2meg
 4 2 1 2     "   4  "  2  "       "       "     "        "      2meg to 4meg
 0 2 1 4     "   0  "  2  "       "       "     "        "      4meg to 6meg
 2 0 1 6
 3 0 1 8
 0 3 1 10

The valid bit should always be set.  If you would like non-iterleaved memory
change MEMCONFIG so it looks like this.

 0 0 1 0    This example assumes 4meg modules are in use.
 0 0 1 2
 1 1 1 4
 1 1 1 6
 2 2 2 8
 2 2 2 10

If you are using larger than 4meg arrays you will have to repeat the pattern
until you reach the array size (in 2 meg increments unless you have V9 console)

In Console versions below version 9 the range of memory is always specified
in 2meg chunks.  In version 9 this was changed to 4meg chunks.  If you are
using EMC2 modules that are 32meg in size you will need to make the file up
yourself becuase SYSINIT does not deal with 32meg boards (DEC doesn't make
a 32 megger).  If this is not the info you need or not enough info just let
me know, I think I can give you a little more, especially if I dig into 
the V9 console release notes.

Good luck 
Mario

--------------------------------------------------------------------------------
                                |
Mario Herodotus                 |        m_herodotus@coors.dec.com
Digital Equipment Corporation   | - or - ...!decwrl!coors.dec.com!m_herodotus
Customer Support Center         | - or - m_herodotus%coors.dec@decwrl.dec.com
305 Rockrimmon Blvd.            |
Colorado Springs, CO 80920      |
(800) 525-6570  Ext 5520        | 
--------------------------------------------------------------------------------

