Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Windows Server 2008 Server Core : Managing Other Hardware - Determining Memory Status with the Mem Utility

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
9/26/2011 9:13:09 AM
Many applications that execute at the command line have strict memory limitations. For example, you might try to run an old DOS application and find that it doesn't work as anticipated (or at all). In some cases, the application will tell you that it lacks sufficient memory, but in other cases, you need to diagnose the problem yourself using the Mem utility. This utility provides you with detailed information about the memory at the command prompt, which differs from the memory that Windows provides. The standard output shows the total amount of conventional memory, the amount of memory available to run applications, the amount of extended memory, and the amount of expanded memory. This utility uses the following syntax:
MEM [/PROGRAM | /DEBUG | /CLASSIFY]

The following list describes each of the command line arguments.


/PROGRAM or /P

Displays the status of programs currently loaded into memory. Use this command line switch to identify applications that you can remove to free memory. Figure 1 shows typical output when using this command line switch. Notice that the output lists every memory usage, including the memory used by the command processor for requirements such as the file handles and drives. The size column shows the memory usage for the application or other element in hexadecimal. The – Free – indicator in the Type column shows areas of free memory in the current command prompt.

NOTE

The programs loaded into memory for the command prompt aren't the same programs that are loaded into the Windows environment. The list of applications that you see when you view the Applications tab of the Windows Task Manager won't match those shown at the command prompt. The environments are separate. Windows treats the command prompt as a single black box entity, even though it's running one or more applications.

Figure 1. The program mode of the Mem utility describes the way applications use memory.

/DEBUG or /D

Displays the status of the programs, internal drivers, and other elements of the command prompt. Use this command line switch to identify potential problems at the command line prompt. The output from this command line switch looks like a very detailed version of the program output shown in Figure 12.2.


/CLASSIFY or /C

Displays the programs based on memory usage. Categorizes the programs by size, provides a list of memory in use, and displays the largest memory block available. Use this command line switch to check for potential problems in memory allocation. As shown in Figure 2, the classify view is a little more readable than the other views and offers the memory allocation sizes in decimal. In addition, you can see the use of upper memory with greater ease.

Not all older applications require more memory. A few older applications actually fail when they have too much memory. If your efforts to run the application fail when it has as much memory as possible, try reducing the available memory.


Figure 2. The Classify mode of the Mem utility categorizes application use of memory.
Other -----------------
- Windows Server 2008 Server Core : Managing Other Hardware - Working with Line Printers
- Microsoft SQL Server 2008 Analysis Services : Designing More Complex Dimensions - Junk dimensions & Ragged hierarchies
- Microsoft SQL Server 2008 Analysis Services : Designing More Complex Dimensions - Slowly Changing Dimensions
- SharePoint 2010 : Social Architecture - Disabling social features for a user & Deleting a note associated with a page
- SharePoint 2010 : Social Architecture - Setting up a tag cloud and navigating to the Term Store
- Securing Windows Server 2008 R2 : Read-only Domain Controller
- Securing Windows Server 2008 R2 : File Classification Infrastructure
- SQL Server 2008 R2 : Join Selection (part 2) - Determining the Optimal Join Order & Subquery Processing
- SQL Server 2008 R2 : Join Selection (part 1) - Join Processing Strategies
- Managing Microsoft Windows Server 2003 Disk Storage : Configuring Disks and Volumes
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server