Starting Applications with /REALTIME May Hang Windows NT

ID: q103475

The information in this article applies to:

Microsoft Windows NT operating system version 3.1
Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

From a Command Prompt (CMD.EXE), if you start an application with the /REALTIME switch, Windows NT may appear to hang.

CAUSE

The /REALTIME switch starts an application at a higher priority level than normal. This gives the application more processor time to use during its execution. If you use this switch on applications that are not designed for it, Windows NT will not respond to any other commands and will appear to hang, even though Windows NT is actually still running and executing as instructed by the command line switch.

RESOLUTION

To prevent this situation from occurring, it is possible for the Administrator of the system to set a User's rights so they are unable to use this feature of setting thread priorities. Power Users are given the right to Increase Scheduling Priorities by default.

To remove the right to Increase Scheduling Priorities, use the following procedure:

1. Open the User Manager in the Administrative Tools group.

2. Select Policy from the menu and then select User Rights.

3. Select the Show Advanced User Rights check box.

4. Open the Rights box.

5. Select Increase Scheduling Priority.

6. Remove any desired Users or Groups from the Grant To box.

Without the Increase Scheduling Priority right, users will be unable to use the /REALTIME switch.

MORE INFORMATION

Steps to Reproduce Problem

1. Open a Command Prompt from the Main group.

2. Type the following command:

   START /REALTIME EDIT.COM

3. When Edit is opened, select the File menu.

At this point, the system will not respond to any keyboard or mouse commands.

Additional query words: prodnt hung lock freeze

Keywords          : kbtool
Version           : 3.1
Platform          : WINDOWS

Last Reviewed: August 14, 1998