Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!orstcs!prism!abukarb
From: abukarb@prism.cs.orst.edu (Bassam A. Abu-Karroum)
Newsgroups: comp.windows.ms
Subject: Re: WIN.INI Switches for Windows 286 and 386
Message-ID: <16199@orstcs.CS.ORST.EDU>
Date: 23 Feb 90 21:49:48 GMT
References: <2932@PEDEV.Columbia.NCR.COM>
Sender: usenet@orstcs.CS.ORST.EDU
Reply-To: abukarb@prism.CS.ORST.EDU (Bassam A. Abu-Karroum)
Organization: Oregon State Univ. -- Computer Science
Lines: 27

In article <2932@PEDEV.Columbia.NCR.COM> rogerson@PEDEV.Columbia.NCR.COM (Dale Rogerson) writes:
>
>EMMPageFrame = <Address>
>
>     This is set to the starting address where the 64K pageframe will
>     begin.  It allocates a 64K contiguous EMS page frame beginning at
>     the four-digit hexadecimal address specified; regardless of what
>     other adapters may be using the range of memory.  Valid addresses
>     begin at C000.
>     other adapters may be using the range of memory.  Valid addresses
>     begin at C000.
>
The above paragraph needs a little clarification. It is true that Windows/386
will set the pageframe at that address. However, if any other device or
adaptor is using the range, Windows File.About command will not report any
expanded memory. Also, to allocate the pageframe at the desired address you
need to precede the address with a zero. Yes, a zero on the left side. This is
the only WIN.INI switch that REQUIRES the zero. A sample line would be:

	emmpageframe=0D000

Without the leading zero, the above statement is useless.
Please note that all entries for the WIN.INI need to be in lower case.

(Unfortunately, not mentioning the leading zero was an error on Microsoft part)

Bassam