Abstract: An input including information specifying criteria for selecting computer resources is processed to produce an output comprising one or more function instances associated with computer resources satisfying the criteria. Included in each of the one or more function instances are metadata and information that specifies a mechanism for accessing a computer resource associated with the function instance.

Abstract: In response to receiving a request for function instances, underlying function instances are identified using API layer data. The requested function instances are then created based on the underlying function instances.

Abstract: An operating system for a computer system having a protection scheme with a plurality of privilege rings provides services for message broadcasting from applications at less privileged rings to virtual drivers at a most privileged ring, and from the virtual drivers to applications. The virtual drivers can perform user mode operations including message broadcasting as an application by synchronizing to a thread of a user mode message server at application time, and setting the thread's user mode context to perform the operations.

Abstract: A method and system are disclosed for invoking a limited or "fail-safe" functionality from a computer system having a graphical user interface (GUI). In one aspect, a computer operating system having GUI functionality can be activated with two different sets of GUI features. Normally, the operating system provides a full complement of GUI features. Alternatively, the operating system provides a more limited set of GUI features. The operating system invokes the limited set of GUI features either in response to a user command, such as a keyboard function key pressed during the bootstrap loading sequence of the operating system, or automatically in response to a failure of an attempt by the computer system to load the normal complement of GUI functions. With the limited set of GUI features, the user of the computer can take advantage of the power of graphical user interfaces even when the computer system is not operating normally.

Abstract: An operating system component allocates locked stack memory pages to threads on an as needed basis. Each thread has a permanent locked stack. A second locked stack page is mapped to each thread. If a thread is using the assignable locked stack page when the system scheduler switches away from that thread, the assignable stack page becomes owned by that thread. When the system scheduler switches to a thread the assignable stack page mapped to that thread is checked to see if it is owned by another thread. If so, an unowned assignable stack page is mapped to the thread prior to switching to that thread. The size of the pool of locked assignable stack pages is adjusted dynamically. If the number of unowned assignable stack pages exceeds a threshold, locked stack pages are released. If the number of locked assignable stack pages falls below a predetermined number, additional assignable stack pages are allocated.