Abstract: Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, a hang resistance application layer intercepts a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the hang resistance application layer determines whether the application component is hung by transmitting a message other than the synchronous function call to the application component that requests that a response be received before transmission of the synchronous function call to the application component is permitted. Responsive to determining that the component is hung, a hung component recovery process is initiated.

Abstract: Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, a hang resistance application layer intercepts a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the hang resistance application layer determines whether the application component is hung by transmitting a message other than the synchronous function call to the application component that requests that a response be received before transmission of the synchronous function call to the application component is permitted. Responsive to determining that the component is hung, a hung component recovery process is initiated.

Abstract: Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, the guard mechanism receives a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the guard mechanism determines whether the component is hung. Responsive to determining that the component is not hung, the guard mechanism permits the synchronous function call to be transmitted to the component. If, however, the guard mechanism determines that the application component is hung, a hung component recovery process is initiated.

Abstract: Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, the guard mechanism receives a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the guard mechanism determines whether the component is hung. Responsive to determining that the component is not hung, the guard mechanism permits the synchronous function call to be transmitted to the component. If, however, the guard mechanism determines that the application component is hung, a hung component recovery process is initiated.

Abstract: A computer system and method are presented that allow a computer system to optimize background task scheduling. The method involves monitoring for the physical presence of a user associated with the computer. When the monitoring indicates that the user is absent, a background task is scheduled and executed. A computer task scheduling system is also provided for optimizing computer usage through proper scheduling of computer tasks. This computer system includes a computer having a memory. In addition, a physical presence detector is included that monitors for the physical presence of a user of the computer. This detector is in communication with the computer and informs the computer when the user is present and absent.

Abstract: Conventional computer systems include numerous application programs which by default store files, or documents, in folders containing the application program that creates them. For example, wordprocessing documents are stored by default in the folder with the wordprocessing application program, and so forth. Thus, users who choose not to organize their documents according to subject matter or other criteria end up having their documents dispersed across numerous application-program folders, sometimes making them difficult to find. Accordingly, the inventors devised a computer operating system that defines a common default document folder for application programs. Moreover, to promote use of the default document folder, one embodiment of the operating system includes a graphical user interface which provides links, that is, one-button access to the common default folder, at file access points, such as in file-open and file-save dialog boxes accessed by the application programs.