Return to readme.txt CVS log

Up to [WindowsNT SDKs] / mstools / samples / sdktools / pviewer

Annotation of mstools/samples/sdktools/pviewer/readme.txt, revision 1.1.1.1

1.1       root        1: Sample: Process Viewer
                      2: 
                      3: Summary:
                      4: 
                      5: The Process Viewer sample shows how to read the various bits
                      6: of trivia and statistics from the Registry relating to the
                      7: various threads and process hanging about on your machine.
                      8: It also allows you to muck about with the priority of the
                      9: processes.  There is about a third of the code present to
                     10: do the same on a thread-by-thread basis, so if you feel
                     11: adventurous and/or wish to learn something, feel free to
                     12: flesh those sections out.
                     13: 
                     14: Addtional Information:
                     15: 
                     16: Two list boxes present themselves on startup, these being
                     17: the list of processes, and when a particular process is
                     18: selected, the other list box will contain the threads that
                     19: are associated with the selected process.  Clicking on the
                     20: "Memory Details" button will bring up another dialog that
                     21: conatins more detail on how the memory associated with that
                     22: process is being used.  Another list box allows you to see
                     23: how the memory usage breaks down at the DLL level.
                     24: 
                     25: Obscure Information about the source code:
                     26: 
                     27: The way the program works may be non-obvious at first, but
                     28: it will mostly clear up when you realize that when the
                     29: programmer named a function "PaintAddressSpace," it wasn't
                     30: named that because it fills the monitored process/thread's
                     31: memory with certain values, it fetches all of the various
                     32: bits of statistics pertaining to memory associated with the
                     33: specified process/thread.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.