Windows 7 - Run Command - Add "Run in Separate Memory Space"

**Brink**

Add "Run in Separate Memory Space" to Windows 7 Run Command

Information

All DOS and 16-bit programs run on Windows 7 in the Windows Virtual DOS Machine (VDM) program. VDM simulates a 16-bit environment, complete with the DLLs required by 16-bit programs.

By default 16-bit programs run in a single VDM with a shared memory space. They share the memory space allocated to the vdm process and therefore, they cannot run simultaneously.

This will show you how to add the Run in Separate Memory Space check box to the Windows 7 Run command dialog box. When Run in Separate Memory Space is checked, a 16-bit program runs in a dedicated (not shared) (VDM) process with a separate memory space.

Warning

If added, the Run in Separate Memory Space check box option will be grayed out until a user enters a 16-bit program in the Run command dialog box.

EXAMPLE: Run Command with and without "Run in Separate Memory Space" Grayed Out

OPTION ONE

Through a Download

1. To Add "Run in Separate Memory Space" -
A) Click on the Download button below to download the
Add_Run_Memory_Check_Box.zip file below.

B) Go to step 3.

2. To Remove "Run in Separate Memory Space" -
A) Click on the Download button below to download the
Remove_Run_Memory_Check_Box.zip file below.

3. Click on Save, and save the .zip file to the desktop.

4. Open the .zip file and extract the .reg file to the desktop.

5. Right click the .reg file (On Desktop) and click on Merge.

6. Click on Run, Yes, Yes, and OK when prompted.

7. Log off and log on, or restart the computer to apply.

8. When done, you can delete the downloaded .reg and .zip files on the desktop if you like.

OPTION TWO

Through the Local Group Policy Editor

1. Open the Local Group Policy Editor.

2. In the left pane, click on the arrow to expand User Configuration, Administrative Templates, then click on Start Menu and Taskbar. (See screenshot below)

3. In the right pane, right click on Add "Run in Separate Memory Space" check box to Run dialog box and click on Edit. (See screenshot above)

4. To Remove "Run in Separate Memory Space" -
A) Select (dot) Not Configured or Disabled. (See screenshot below step 6)

B) Go to step 6.

5. To Add "Run in Separate Memory Space" -
A) Select (dot) Enabled. (See screenshot below step 6)

6. Click on OK. (See screenshot below)

7. Close the Local Group Policy Editor. (See screenshot below step 2)

That's it,
Shawn

Related Tutorials

jmortongoff · 11-09-2009

Does the "Run in separate memory space" method of running 16 Bit programs work with all the 32 Bit Versions of Windows 7 ?

This is a pre-purchase request; I will stick with Vista and XP if I cannot run a particular 16 Bit accounting program.

**Brink** · 11-09-2009

Hello Jmortingoff, and welcome to Seven Forums.

Yes, it is available in all editions of Windows 7.

However, that does not guarantee that the 16-bit program will work in Windows 7. You might check with the Windows Compatibility Center, and post a question if anyone else has the program running in Windows 7 in the Software forum to help make sure it does.

Hope this helps,
Shawn

jmortongoff · 11-10-2009

Thanks, Shawn, for your prompt reply.

I think I shall now install Windows 7 Home Premium on a Vista Notebook in a separate partition of 30Gb.

I see there are instructions for doing this in Issue 306 of Computer Active magazine (12 Nov 09).

That way I can do some tests with the 16 Bit programs; I will report progress.

Best Regards

John

**Brink** · 11-10-2009

Ok John. I look forward to hearing how it turns out.

jmortongoff · 11-13-2009

Hello Shawn

Well, I made the separate partition on the Dell 6400 Notebook as promised. Then I installed Windows 7 Home Premium to the new partition. No problems!

I then installed our 16 Bit PCC Payroll software. Much to my surprise it ran immediately with no adjustments needed such as "Run in Separate Memory Space".

I checked that some of the DOS system files normally required, such as config.nt and autoexec.nt, existed in the WINDOWS\SYSTEM32 folder; they were there.

So have Microsoft made it like Vista: 32 Bit versions will run 16 Bit programs?

Regards

John

**Brink** · 11-13-2009

That's great news John. I do not have these files, so maybe the program may have added them during it's installation.

jmortongoff · 11-14-2009

Quote: Originally Posted by jmortongoff

So have Microsoft made it like Vista: 32 Bit versions will run 16 Bit programs?

Hello Shawn

Just to confirm I bought a boxed, retail version of Windows 7 Home Premium; maybe OEM or earlier versions did not have the 16 Bit system files? Perhaps the automatic Windows Update added the files during installation.

What version(s) are you using and what is their origin?

Best Regards

John

**Brink** · 11-14-2009

I do not have any 16-bit programs running, so I do not have these files. I'm still leaning towards the system files being placed there when the program was installed though.

jmortongoff · 11-15-2009

Quote: Originally Posted by Brink

I do not have any 16-bit programs running, so I do not have these files. I'm still leaning towards the system files being placed there when the program was installed though.

The question in my previous post was 'What version(s) of Windows 7 are you running?'.

To sum up:

We agree that 64 Bit Windows 7 will not run 16 Bit programs.
Our company, PC Challenge, have produced 16 Bit Payroll and Cash Book programs for many years which definitely do not include any 16 Bit system files in their Install programs. Hence, I confirm that it was our Windows 7 Home Premium 32 Bit installation that included the 16 Bit system files.
The dates on the 16 Bit system files are as follows:
COMMAND.COM 13/07/2009
CONFIG.NT 10/6/2009
AUTOEXEC.NT 10/06/2009
Most files in the System32 folder are dated 14/07/2009. About Windows gives Version 6.1 (Build 7600).
Other posts on the WEB have confirmed that the 32 Bit version of Windows 7 can run 16 Bit programs.

Hope that helps

John