<Language-code>

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\

Description

The Perflib subkey contains a <Language-code> subkey for each spoken language you configure for Windows 2000. The <Language-code> subkey stores performance counter names and their descriptions in the specified language. The <Language-code> subkey is named for the language code associated with the language. For example, the counters and definitions for the English language are stored in a subkey named 009, the language code for English (United States).

The <Language-code> subkey is a variable representing the subkeys under the HKCU\Software\Microsoft\Perflib subkey. It doesn't actually appear in the registry. This variable subkey displays the entries that can appear in any of the language code subkeys in the Perflib subkey. The actual <language-code> subkeys in your registry depend upon the spoken language you have chosen for your system.

Activation method

To make changes to entries in this subkey effective, restart the Remote Registry Service or restart Windows 2000.

Tip Image Tip

If particular performance counters do not appear in your performance monitoring tool, check the Application Log in Event Viewer for events recorded by Perflib. When Perflib detects disabling errors in a counter DLL, it records an event in the log and sets the value of DisablePerformanceCounters to 1 to disable the counters.

Caution Image Caution

Do not change the values of entries in this subkey. This subkey is maintained by the Performance Library. If you change it, the performance tools on your system will not operate properly.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.