Allocate more memory for Windows XP application by system setting
ntvdm.exe = New Technology Virtual DOS Machine
wowexec.exe = Windows on Windows (emulating 16 bit Windows)
I'm using the 16 bit word processor Ami Pro 3.0 (fresh installation) under a virtual XP Home Edition (32 bit). This works for many years, but now, as a document has reached 13.5 MB, I get the following messages by Ami Pro:
File too large to be loaded. Saving the file will truncate it.
Unable to complete copy.
Unable to complete paste.
Unable to save enough information to undo later.
These messages appear while free RAM is about 1.2 GB. They do not appear if I delete some pages of the document.
Since I suppose that ntvdm.exe is managing the memory allocation, my question is:
How can I change the settings in order to get more memory?
Found registry entries:
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_CURRENT_USERSoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
key HKEY_USERSS-1-5-21-2000478354-746137067-854245398-1004SoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
Command line for ntvdm.exe shown by Sysinternals Process Explorer:
"C:WINDOWSsystem32ntvdm.exe" -f -i1 -w -a C:WINDOWSsystem32krnl386.exe
windows-xp memory memory-management win32 ntvdm
asked Jan 16 at 7:50
PollitzerPollitzer
99115
add a comment |
ntvdm.exe = New Technology Virtual DOS Machine
wowexec.exe = Windows on Windows (emulating 16 bit Windows)
I'm using the 16 bit word processor Ami Pro 3.0 (fresh installation) under a virtual XP Home Edition (32 bit). This works for many years, but now, as a document has reached 13.5 MB, I get the following messages by Ami Pro:
File too large to be loaded. Saving the file will truncate it.
Unable to complete copy.
Unable to complete paste.
Unable to save enough information to undo later.
These messages appear while free RAM is about 1.2 GB. They do not appear if I delete some pages of the document.
Since I suppose that ntvdm.exe is managing the memory allocation, my question is:
How can I change the settings in order to get more memory?
Found registry entries:
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_CURRENT_USERSoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
key HKEY_USERSS-1-5-21-2000478354-746137067-854245398-1004SoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
Command line for ntvdm.exe shown by Sysinternals Process Explorer:
"C:WINDOWSsystem32ntvdm.exe" -f -i1 -w -a C:WINDOWSsystem32krnl386.exe
windows-xp memory memory-management win32 ntvdm
asked Jan 16 at 7:50
PollitzerPollitzer
99115
1
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami tortfformat and import into any current word processor.
– Mokubai♦
Jan 16 at 7:59
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29
add a comment |
ntvdm.exe = New Technology Virtual DOS Machine
wowexec.exe = Windows on Windows (emulating 16 bit Windows)
I'm using the 16 bit word processor Ami Pro 3.0 (fresh installation) under a virtual XP Home Edition (32 bit). This works for many years, but now, as a document has reached 13.5 MB, I get the following messages by Ami Pro:
File too large to be loaded. Saving the file will truncate it.
Unable to complete copy.
Unable to complete paste.
Unable to save enough information to undo later.
These messages appear while free RAM is about 1.2 GB. They do not appear if I delete some pages of the document.
Since I suppose that ntvdm.exe is managing the memory allocation, my question is:
How can I change the settings in order to get more memory?
Found registry entries:
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_CURRENT_USERSoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
key HKEY_USERSS-1-5-21-2000478354-746137067-854245398-1004SoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
Command line for ntvdm.exe shown by Sysinternals Process Explorer:
"C:WINDOWSsystem32ntvdm.exe" -f -i1 -w -a C:WINDOWSsystem32krnl386.exe
windows-xp memory memory-management win32 ntvdm
asked Jan 16 at 7:50
PollitzerPollitzer
99115
ntvdm.exe = New Technology Virtual DOS Machine
wowexec.exe = Windows on Windows (emulating 16 bit Windows)
I'm using the 16 bit word processor Ami Pro 3.0 (fresh installation) under a virtual XP Home Edition (32 bit). This works for many years, but now, as a document has reached 13.5 MB, I get the following messages by Ami Pro:
File too large to be loaded. Saving the file will truncate it.
Unable to complete copy.
Unable to complete paste.
Unable to save enough information to undo later.
These messages appear while free RAM is about 1.2 GB. They do not appear if I delete some pages of the document.
Since I suppose that ntvdm.exe is managing the memory allocation, my question is:
How can I change the settings in order to get more memory?
Found registry entries:
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet001ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMControlSet002ControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name cmdline
value %SystemRoot%system32ntvdm.exe
key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWOW
name wowcmdline
value %SystemRoot%system32ntvdm.exe -a %SystemRoot%system32krnl386
key HKEY_CURRENT_USERSoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
key HKEY_USERSS-1-5-21-2000478354-746137067-854245398-1004SoftwareMicrosoftWindowsShellNoRoamMUICache
name C:WINDOWSsystem32ntvdm.exe
value NTVDM.EXE
Command line for ntvdm.exe shown by Sysinternals Process Explorer:
"C:WINDOWSsystem32ntvdm.exe" -f -i1 -w -a C:WINDOWSsystem32krnl386.exe
windows-xp memory memory-management win32 ntvdm
windows-xp memory memory-management win32 ntvdm
asked Jan 16 at 7:50
PollitzerPollitzer
99115
asked Jan 16 at 7:50
PollitzerPollitzer
99115
asked Jan 16 at 7:50
PollitzerPollitzer
99115
asked Jan 16 at 7:50
PollitzerPollitzer
99115
asked Jan 16 at 7:50
PollitzerPollitzer
99115
99115
1
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami tortfformat and import into any current word processor.
– Mokubai♦
Jan 16 at 7:59
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29
add a comment |
1
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami tortfformat and import into any current word processor.
– Mokubai♦
Jan 16 at 7:59
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29
1
1
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami to
rtf format and import into any current word processor.– Mokubai♦
Jan 16 at 7:59
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami to
rtf format and import into any current word processor.– Mokubai♦
Jan 16 at 7:59
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394833%2fallocate-more-memory-for-windows-xp-application-by-system-setting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394833%2fallocate-more-memory-for-windows-xp-application-by-system-setting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
That you still have memory free and that removing pages of the document helps tells you that this is not a limitation of the operating system but is a limitation of the Ami program itself. Hacking around the operating system is counterproductive when the real problem is an old, unsupported and obviously limited program. Your best bet will be to get that document out of your current system and into a current and supported program. Some suggestions on the internet are to save from Ami to
rtfformat and import into any current word processor.– Mokubai♦
Jan 16 at 7:59
How do you know it is not a limitation of the software itself?
– Moab
Jan 16 at 14:53
@Moab: I don't, it's a try.
– Pollitzer
Jan 16 at 16:29