Abstract: A dead e-mail identification locator discovers dead e-mail addresses without forwarding messages to valid recipients. Existing headers in the mail protocol are extended to include a test header. A mail server that supports the protocol extension of the present invention may send a reply if the address does not exist and may discard the message if the address does exist. The test header allows a sender to test an e-mail address for validity without the message being forwarded to the user, as will be described below. The sender may be a dead e-mail locator program, which tests a plurality of e-mail addresses, such as an e-mail address list or white pages of e-mail addresses.

Abstract: A client station on computer network uses an operating system such as JavaOS which is permanently stored at the server rather than on storage media at the client location. JavaOS is loaded and installed at the client upon bootup of the client. The JavaOS is loaded and installed at the client upon bootup of the client. Once the basic system is booted using local firmware, and the base file systems on the network are enabled, an application can begin running, and when it needs to use a particular class file a request will be made through the file system and will be routed over to a generic file system driver, on the client, which will then determine, using a set of configured information, where this class exists; it will utilize the particular file systems available on to that booted client, whether it be NFS, or TFTP, to determine where the server is and how to retrieve that particular class file.

Abstract: Disclosed is a system, method, and program for displaying data. A program receives first input graphics commands from a first application program to display first output on a display monitor and second input graphics commands from a second application program to display second output on the display monitor. The second output is graphically blended with an overlapping portion of the first output. Output graphics commands are generated from the first and second input graphics commands to display the graphically blended second output superimposed over an overlapping portion of the first output and the first output non-overlapping with the second output. This allows the content of the secondary output to be displayed without affecting user operations with respect to the primary application window.

Abstract: A client station on computer network uses an operating system such as JavaOS which is permanently stored at the server rather than on storage media at the client location. The JavaOS is loaded and installed at the client upon bootup of the client. The client loads certain standard file systems as part of the basic OS code that it receives from the server. These employ a generic file system driver, which is located in Java code rather than in native code at the client. In addition to the standard file systems, other file systems may be installed, using this generic file system driver. For example, a file system for a hard drive may be installed at a particular client, even though this file system is not part of the set of standard file systems. Providing the generic file system driver or handler switch in Java code rather than native code allows file systems to be dynamically added to a running system.

Abstract: A three-dimensional graphical user interface is provided wherein the windows have a “thickness” property. In the preferred embodiment, a window will have a Z plane position (z) and a Z plane thickness (cz) as well as the traditional x, cx, y and cy. This allows positioning anywhere in three dimensional space. Using either a three axis mouse or a conventional mouse with supplemental control (perhaps keyboard), each axis may be traversed to navigate the desktop. As the pointer moves along an axis, the user's point of view can change, bringing the view either closer/farther/left/right, depending on the direction of motion, which may cause the windows perspective to change, e.g., larger or smaller. The user's perspective can pass into and through the window-blocks.

Abstract: A serializable object, formed by a device driver and containing characteristics (device state) of the device, is held by a device driver and made known to a data processing system's power manager. The power manager provides a device driver independent mechanism for saving device state by retrieving each device driver's object containing device state and storing the object in a location that provides for efficient and quick retrieval. The power manager, being aware of power levels for all devices on the system, may determine where, how and when to store objects retrieved from the device drivers for most efficient retrieval. Upon receiving an interrupt indicating the system should power up, the serializable objects are retrieved by the power manager and restored to each device driver.

Abstract: A serializable object, formed by a device driver and containing characteristics (device state) of the device, is held by a device driver and made known to a data processing system's power manager. The power manager provides a device driver independent mechanism for saving device state by retrieving each device driver's object containing device state and storing the object in a location that provides for efficient and quick retrieval. The power manager, being aware of power levels for all devices on the system, may determine where, how and when to store objects retrieved from the device drivers for most efficient retrieval. Upon receiving an interrupt indicating the system should power up, the serializable objects are retrieved by the power manager and restored to each device driver.