What are System Resources?
System resources are a special part of memory that Windows uses to draw things on the screen, open files, and perform other menial but important and frequent tasks. System resources are important because, on Windows 95, 98 and ME, they are limited in size (in contrast, Windows NT, 2000 and XP can expand the system resources if necessary). If system resources are exhausted, your computer effectively grinds to an immediate halt. Since system resources are used for everything, the computer doesn’t even have the chance to display a warning window, or take necessary steps to protect your computer. Because system resources are so precious, computers often crash when they become scarce. There is no good way around this problem. On the aforementioned Windows versions, the amount of system resources is strictly limited. No matter how much memory you buy, or how fast your computer is, your system resources will never expand and the danger of losing them will never diminish. Unlike conventional m
System resources are the parts within a computer that are available to be used by the operating system and other applications. The most notable of the system resources is the amount of memory in use, but CPU time should be considered here as well. Each time an application starts, the application will request memory from the operating system and a slice of CPU time to perform its function. For example, when a computer user starts the word processing application on the computer, they will click the icon for the application and shortly thereafter, the program starts. During the time while the user is waiting for the program to start, the operating system is provisioning system resources to handle this application. It is essentially making room for it among the other processes and applications that may be running at the time the program is started. When the word processor application starts, it sends a request to the operating system to provision the necessary system resources for it to fu
A system resource is known only to the z/VM system where it is located but it is remotely accessible from other systems. A system resource name only needs to be unique to that system. Any authorized user in the TSAF or CS collection can access the system resource. Authorized users from the SNA network can also access system resources. In this case, the system resource is accessible using a global gateway that is defined on the VM system on which the system resource resides; AVS must also be running on that VM system. From a requester on the same VM system, system resources are accessed the same as a local or global resource on that system. From a TSAF or CS collection, system resources are accessible using the system gateway of the system on which the system resource resides. In this case, the target LU is the system gateway name of the system on which the system resource resides. The transaction program name is the name of the system resource. See What Is a System Gateway? for more in
A system resource is known only to the z/VM system where it is located but is remotely accessible from other systems. A system resource name only needs to be unique to that system. Any authorized user in the TSAF or CS collection or the SNA network connected to the system on which the system resource resides can access the system resource. From a SNA system, they are accessed by an AVS global gateway. Note that AVS must be running on the same VM system as the target system resource. From a requester on the same VM system, they are accessed the same as a local or global resource on that system. From a TSAF or CS collection, system resources are accessible through the system gateway of the system on which the system resource resides. This is done using an LU name of SYSGATE, where SYSGATE is the system gateway of the target system, and a TPN of the name of the system resource. See What Is a System Gateway? for more information. See Table 68 for identifying the target of a connection requ
The term System Resources actually covers two main areas of Windows memory that are reserved for and used by specific Windows components. They are called User and GDI. User resources refer to the input manager user32.dll. It handles input from your mouse, keyboard, and other sources, such as communication ports, file handles, etc. GDI stands for Graphics Device Interface and is in charge of the visible components of Windows. It stores fonts, brushes, bitmaps, and other graphics stuff, as well as lends support to other graphic output devices such as printers. On Windows 9x/Me systems, you can monitor resources using the resource monitor. It returns the amount of free resources as a percentage.
