Printable View
Does anyone have a suggestion as to how I would go about determining the total physical memory, available physical memory, total virtual memory, and available virtual memory?
I have been trying to implement the GlobalMemoryStatusEX, but I continue to run into a lot of errors.
I was just looking for something better.
Thanks.
I What errors do you get? Use GlobalMemoryStatus()
The following works ok;
Code:#include <windows.h>
#include <iostream>
using std::cout;
using std::endl;
int main(){
MEMORYSTATUS ms;
GlobalMemoryStatus(&ms);
cout << "Total Phisical Memory - " << ms.dwTotalPhys << endl;
cout << "Total Available Phisical Memory - " << ms.dwAvailPhys << endl;
cout << "Total Virtual Memory - " << ms.dwTotalVirtual << endl;
cout << "Total Available Virtual Memory - " << ms.dwAvailVirtual << endl;
return 0;
}
Thanks very much for your help. I did try your code and it compiled with no errors, but I am worried about this function returning the correct values. I was reading on the MSDN web site under GlobalMemoryStatus that there is a possibility that this function could return incorrect info if the machine has more than 4GB of memory. Also, they suggest to use the GlobalMemoryStatusEX for Windows 2000 and that is what I try to do, but I continue to receive errors.
For example, the compiler error:
MEMORYSTATUSEX: undeclared identifier
GlobalMemoryStatusEx: undeclared identifier
ms: undeclared identifier
I feel if these were taken care of the program would work.
Also, when I use the GlobalMemoryStatus function, I get incorrect values returned for my virtual memory. The physical memory is pretty accurate.
Look into this thread for GlobalMemoryStatus.
I cannot find the GlobalMemoryEx function in my helpfiles.
there is a GlobalMemoryVlm, but you don't need this.
Update:
GlobalMemoryEx exists, but is not neccessary if you don't work with server systems. "Windows 95/98/Me: Unsupported." means your program will not run on these systems if you use this function.
:Update
http://www.cprogramming.com/cboard/s...threadid=13000
dwLength
The size in bytes of the MEMORYSTATUS data structure. You do not need to set this member before calling the GlobalMemoryStatus function; the function sets it.
dwMemoryLoad
Specifies a number between 0 and 100 that gives a general idea of current memory utilization, in which 0 indicates no memory use and 100 indicates full memory use.
dwTotalPhys
Indicates the total number of bytes of physical memory.
dwAvailPhys
Indicates the number of bytes of physical memory available.
dwTotalPageFile
Indicates the total number of bytes that can be stored in the paging file. Note that this number does not represent the actual physical size of the paging file on disk.
dwAvailPageFile
Indicates the number of bytes available in the paging file.
dwTotalVirtual
Indicates the total number of bytes that can be described in the user mode portion of the virtual address space of the calling process.
dwAvailVirtual
Indicates the number of bytes of unreserved and uncommitted memory in the user mode portion of the virtual address space of the calling process.
TotalVirtual should be around 2 GB.
This is a normal result from the above mentioned threads program on my PC ( 512 MB RAM )
[code]
44 % of Memory in use.
536309760 bytes of physical memory.
295657472 bytes of physical memory available.
906985472 bytes of pagefile memory.
685002752 bytes of pagefile memory available.
Note that this number does not represent the actual physical size of the paging file on disk.
2147352576 bytes of virtual memory.
2141839360 bytes of virtual memory available.
Press any key to continue
[code]
Is that really a problem ? Does your program target server platforms with gigabytes of RAM ?Quote:
I was reading on the MSDN web site under GlobalMemoryStatus that there is a possibility that this function could return incorrect info if the machine has more than 4GB of memory.
Is it wrong or is it not what you expected?Quote:
Originally posted by ghe1
Also, when I use the GlobalMemoryStatus function, I get incorrect values returned for my virtual memory. The physical memory is pretty accurate.
For example, on Desktop Windows PCs, each process is allocated a 4GB address space. ....out of this address space, the only legally accessable range to your program is the usermode codespace available by your process.....on Windows NT based systems, this is the memory range 0x0010000 to 0x7FFEFFFF....or in decimal - 65,536 to 2,147,418,111 which is a total difference of 2,147,352,575 which is the same as the figure returned by nvoigt's return value for virtual memory (out by 1 byte....but what the hell!)
Its more probable that you have misinterpreted the meaning of this value that the possibility that it is wrong
I used what nvoigt had suggested and this is my output:
68 % of Memory in use.
511.418 Mbytes of physical memory
163.039 Mbytes of physical memory available
2047.875 Mbytes of virtual memory
2042.672 Mbytes of virtual memory available
Under computer management, system information I am seeing this memory:
Total Physical 523,692 KB
Available Physcial 155,532 KB
Total Virtual 1,801,592 KB
Available Virutal 1,051,136 KB
Just let me know if I am not correctly understanding the memory values.
Well one's in KB the other's in MB...haven't bothered converting them, but why don't you try?
I have converted them and I see that my phyical memory is very similar, but the virtual memory is off.
CONVERSIONS:
Computer Management:
Total Physical 511.418 MB
Available Physical 151.886 MB
Total Virtual 1759.367 MB
Available Virtual 1026.500 MB
OUTPUT:
68 % of Memory in use.
511.418 Mbytes of physical memory
163.039 Mbytes of physical memory available
2047.875 Mbytes of virtual memory
2042.672 Mbytes of virtual memory available
Fordy,
I see what you mean now...I guess my results are okay. I just really didn't understand the concept but now I do.
All,
Thanks for all the help!:)