home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.setup
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsc!cbfsb!cbnewsg.cb.att.com!rnichols
- From: rnichols@cbnewsg.cb.att.com (robert.k.nichols)
- Subject: Re: Virtual Memory Setup
- Message-ID: <1993Jan22.204807.2637@cbfsb.cb.att.com>
- Sender: news@cbfsb.cb.att.com
- Organization: AT&T
- References: <1993Jan22.033537.19302@rock.concert.net>
- Date: Fri, 22 Jan 1993 20:48:07 GMT
- Lines: 32
-
- In article <1993Jan22.033537.19302@rock.concert.net> toddwall@rock.concert.net (R. Todd Wall -- Catholic Diocese of Raleigh -- Computer Services) writes:
- >
- > I have Windows 3.1 running on a 386-25 w/ 2 megs of RAM. When I run
- >windows it creates approximately 2 megs of virtual memory. The manual says
- >I can set up to 7 megs of virtual memory, but it won't let me. Why???
- >
- > Oh, one more thing. I'm running QEMM 6.0....
-
- Two things come to mind.
-
- 1. A permanent swap file needs CONTIGUOUS space on the disk. You may
- need to defragment your free space. (This does not apply to
- temporary swap files.)
-
- 2. On a machine with limited memory, Windows will not create a large
- virtual address space without prodding. In the [386enh] section of
- SYSTEM.INI, add (or change) the parameter: "PageOverCommit=nn".
- This specifies a factor by which the amount of available physical
- memory will be multiplied to determine the size of the virtual
- address space. The default value is 4. (The Windows Resource Kit
- claims that the available memory size is rounded up to a multiple
- of 4 MB before being multiplied. I have observed behavior that
- appears to contradict this claim.)
-
- On a 2MB machine, #2 is probably your problem. You can force Windows
- to create more virtual memory, but your machine will really crawl.
- Most prople consider 4MB of physical memory the minimum necessary to do
- anything useful under Windows.
-
- Bob Nichols
- AT&T Bell Laboratories
- rnichols@ihlpm.ih.att.com
-