JIM HOLSONBACK wrote in a message to MATT MC_CARTHY:

 JH> Sorry, guys.  I wrote this back on 12/15, and don't think I ever
 JH> sent it out.  (been purdy busy).

 JH> Hello, Matt, (and Roy).  I heard you both talking about  - - - 

 RJT> Why would this (Award) BIOS setup screen have an option in there
 RJT> that says:
 RJT> OS Select for DRAM > 64MB (the choices are OS2 or Non-OS2)

 MM>  Probably so you can use it with either OS/2 or DOS/Windows, or  
 MM>  Linux.

 JH> FWIW, I did a bit of internet research, and checked a few user
 JH> manuals for AWARD BIOS machines here - Manuals say take this BIOS
 JH> option if running OS/2 on a system with >64MB. BUT - At least two
 JH> Internet discussion pages say NO, to NOT take this option - it only
 JH> applies for OS/2 versions lower than 2.22 or something like that.

I'm vaguely aware of a 2.1 version,  but that was pretty early.  I have
Warp 3,  Warp Connect (v3 with networking),  and Warp 4 here.  There are
apparently some later versions,  and they continue to sell the product as a
"business server solution".

 RJT> when the board won't cache more than 64M in the first place?

 MM> Won't "_cache_ more", or won't hold more?

 JH> As I understand it, some mainboards with Intel 430VX (and TX) 
 JH> chipset can hold and work with more than 64Mb, but only the first
 JH> 64MB of RAM will be cached.

That seems to be the case based on what I read in "Upgrading and
Repairing PCs"...

 RJT> As it happens,  64M is what I have in the machine,  but more 
 RJT> would be nice,  if it would support it.  Unfortunately that VX
 RJT> chipset won't...

 MM> The setup option for OS/2 or Non-OS/2 has to do with the continuity of
 MM> RAM above the 64M mark.  Normal Intel based systems leave a hole in
 MM> memory at that point.  Windows writers have worked around it,
 MM> programming from the bottom of memory upwards.  OS/2 uses memory from
 MM> the top down, and requires all memory to be continuous.  Selecting that
 MM> CMOS Setup option swaps a bank of low memory into the hole Intel left.

 JH> That's news to me about a "memory hole" just above 64MB.  I've 
 JH> heard about some sort of "memory hole" between 15 and 16 MB, but 
 JH> not one just above 64MB.

I remember that 15-16M one too.  And I wonder if maybe the one that relates
to 64M is what happens when you go to the next bigger memory parts?  Or
something like that. 

 JH> ... Jim, at my age, just what I don't need is another Memory Hole -
 JH> Bubba 

Heh.

---