A System Restore fixed the problem.

I’ve had SysResources Manager up for over a week. Then it pretty much dies.

I run XP SP2. I got the “CPU Usage Query failed” on startup, like #72 said. Now menu items are in Unicode-Goop.

Worse, the main screen display is all labelled with “1″ and showing no data.

Don’t know if it is a product bug, windows bug, operator error … but the program lasted a little over a week.

Oh, well.

#44, mike, regarding the termination of XP support, I was merely informing users that the prudent thing is to download any desired updates and patches before the termination date, while automatic updates still functions properly. While some articles had concerns about the availability of patches and service packs beyond that date, I suspect that they’ll still be available via manual downloads. And yes, security updates will still be available.

#65, watcher13, I found your quotes in Windows Help and Support. The thing to remember about Windows Help and Support is that while it can be quite useful, it’s written by tech writers, not programmers. Some of it is flat-out incorrect or obsolete.

#67, lostinlodos, your comments indicate a lack of understanding of how virtual memory works. Yes, RAM is many orders of magnitude faster than hard disks. However, as long as the working set for any given process is in RAM, and doesn’t need any portion kicked out for another process, there won’t be any paging related to that process. Further, most people incorrectly assume that virtual memory means paging to disk. I’m not going to address whatever Microsoft does, but the general concept of virtual memory allows it to be used entirely in-RAM (and the following also applies to the disk-paging case). Allocating each process its own virtual memory space eliminates issues with memory fragmentation across processes (depending upon how a process manages its own memory space, it can internally fragment its own virtual memory space, but it won’t be affected by other processes). You should always leave virtual memory enabled; doing so will generally prevent issues related to the fragmentation of the physical memory.

If you want to read some of the details of how Windows manages memory, see Mark Russinovich’s Pushing the Limits of Windows: Physical Memory and Pushing the Limits of Windows: Virtual Memory, although there’s some incorrect information about multiple paging files, which you can read here (may not apply to Vista and higher). Also, I’ve linked a number of other Microsoft articles on virtual memory and page file management, in the past.

x64 and IA64 architecture allow for recognition of some-odd terabytes of ram; I can’t remember the exact number off my head at the moment. Since I do some extensive computer graphics and animation, video conversion and editing, as well as HDCAD modelling it’s quite useful to me. And as I stated above, quite a few of my more standard programs can make use of gluttonous amounts of ram too when you offer it up.

Allocation is not the same as use. And while Vista is better at “releasing” allocated memory addresses, both still need work. XP sequentially writes to the end of the group of allocated spots. That is, AFTER the last recorded point.

‘Windows XP support ends in April’?; April 2014!

But, since this is about the program at hand, with the exception of the memory release and defrag which I still won’t test, it runs stable, I has pretty graphs and bars! It looks all fancy.
It does mostly the same thing that XP does. It put everything into a nice sleek package.

But XP does all of this already.
My score 7-8.
Despite not doing anything that Windows includes already, the somewhat retro style graphics are nice. Beyond that, to see everything this shows for free from within Windows:

hold down ctrl, and shift, and hit escape. then release.
Click on the Performance and Networking tabs to see the same identical graphs in a less pleasing but also less expensive display.