Last change
on this file since 99016 was 99016, checked in by vboxsync, 2 years ago |
manual: Some scm corrections for dita files. bugref:10302
|
-
Property svn:eol-style
set to
native
-
Property svn:keywords
set to
Id Revision
|
File size:
1.1 KB
|
Line | |
---|
1 | <?xml version='1.0' encoding='UTF-8'?>
|
---|
2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
---|
3 | <topic xml:lang="en-us" id="ts_win31-ram-limitations">
|
---|
4 | <title>Windows 3.x Limited to 64 MB RAM</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>
|
---|
8 | Windows 3.x guests are typically limited to 64 MB RAM, even if a
|
---|
9 | VM is assigned much more memory. While Windows 3.1 is
|
---|
10 | theoretically capable of using up to 512 MB RAM, it only uses
|
---|
11 | memory available through the XMS interface. Versions of
|
---|
12 | HIMEM.SYS, the Microsoft XMS manager, shipped with MS-DOS and
|
---|
13 | Microsoft Windows 3.x can only use up to 64 MB on standard PCs.
|
---|
14 | </p>
|
---|
15 | <p>
|
---|
16 | This is a known HIMEM.SYS limitation. Windows 3.1 memory limits
|
---|
17 | are described in detail in Microsoft Knowledge base article KB
|
---|
18 | 84388.
|
---|
19 | </p>
|
---|
20 | <p>
|
---|
21 | It is possible for Windows 3.x guests to utilize more than 64 MB
|
---|
22 | RAM if a different XMS provider is used. That could be a newer
|
---|
23 | HIMEM.SYS version, such as that shipped with Windows 98, or a
|
---|
24 | more capable third-party memory manager, such as QEMM.
|
---|
25 | </p>
|
---|
26 | </body>
|
---|
27 |
|
---|
28 | </topic>
|
---|
Note:
See
TracBrowser
for help on using the repository browser.