WO2000065563A1 - Secondary user interface - Google Patents

Abstract

An alternate display content controller provides a technique for controlling a video display separately from and potentially in addition to the content displayed on the operating system monitor. Where the display is a computer monitor, the alternate display content controller interacts with the computer utility operating system and hardware drivers to control allocation of display space and create and control one or more parallel graphical user interfaces separate from the operating system desktop. An alternate display content controller may be incorporated in either hardware or software. As software, an alternate display content controller may be an application running on the computer operating system, or may include an operating system kernel of varying complexity ranging from dependent on the utility operating system for hardware system services to a parallel system independent of the utility operating system and capable of supporting dedicated applications. The alternate display content controller may also include content and operating software delivered over the internet or any other LAN. The alternate display content controller may also be included in a television decoder/settop box to permit two or more parallel graphical user interfaces to be displayed simultaneously.

Description

PARALLEL INTERFACE

TECHNICAL FIELD

This invention relates to user interface displays and, in particular, the use of a parallel user interface separate from the standard user interface display.

BACKGROUND OF THE INVENTION

There was a time when the most popular operating system for personal computers (DOS) did not include a graphical user interface. Any company could create a "menu" or "shell" which would be the first program launched upon starting the computer, and which would present options to the user for launching and managing various applications. Although graphics programming was difficult in the DOS environment, some companies even created graphical user interfaces that could then launch other programs.

Microsoft Corporation of Redmond, Washington, introduced such a graphical user interface for launching applications which it called "Windows". The first three versions of Windows were merely applications which ran under DOS and could be one of numerous items to be selected from a previously running shell or menu which might be offered by a company other than Microsoft. This continued to allow other companies to offer primary user interface programs to users without the user going through a Microsoft controlled user interface. However, with the introduction by Microsoft of Windows 95™, the initial loading of the operating system presents a Microsoft-developed graphical user interface (GUI) at the outset, which occupies the entire screen display. This operating system created GUI is commonly known as a "desktop". As with its previous operating system products, Microsoft arranged with manufacturers of the standard computer hardware to include this operating system with each computer sold. Microsoft's OEM licensing restrictions prevent vendors from altering, obscuring, or preceding the Microsoft desktop display. The Windows environment also presumes its ownership of the entire display and is designed in ways that assume that it can write to any screen location at any time. With Microsoft's domination of this market, it became impossible for other software vendors to present an interface to users other than as a Microsoft style icon within the Microsoft "desktop" consisting of the entire screen display. This prompted a need for access to a user interface which could be presented outside of the standard computer screen display and therefore independent of the dictates of Microsoft for items within its "desktop". Standard personal computers use VGA or Super VGA or XGA video display systems. These display systems operate in standardized graphics modes such as 640 x 480 pixels, 800 x 600 pixels, 1024 x 768 pixels, and 1280 x 1024 pixels. When one of these display modes is selected, this is the entire area available for display. In the Microsoft Windows environment, the user instructs the Windows operating system to select one of these standard display modes and the Windows operating system then presents all of the applications and their icons within the selected display area. There is no way at present to cause the Windows "desktop" to use less than the entire display area and still function as intended and allow another program from another vendor to control the remainder. What is needed is the ability to designate a portion of video memory separate from the Windows desktop, and to make sure that Windows functions normally but at the same time cannot obstruct anything subsequently allocated into that space.

SUMMARY OF THE INVENTION A first aspect of the present invention includes a technique for controlling allocation and content of display space among one or more user interfaces, operating systems or applications permitting an application or parallel graphical user interface (GUI) to operate outside the desktop, the area designated for display of the operating system interface and its associated applications. In a first aspect, a computer operating under the control of any utility operating system such as Microsoft Windows™, Linux, Apple O/S or Unix may have the allocation of visible display controlled by the present invention. The operating system desktop may be scaled and/or moved to a specific area of the display permitting a parallel GUI to operate in the open area. The present invention may be an application operating under the primary or utility operating system or it may be combined with an operating system kernel to control the display and content in the parallel display.

Another aspect of the present invention includes a technique provided for adding and using a parallel graphical user interface adjacent to the standard user graphical display interface, for example in the border beyond the standard screen display area. Conventional video systems, such as VGA, SVGA and XGA video systems, include a defined border surrounding the display area. The original purpose of this border was to allow adequate time for the horizontal and vertical retrace of the electron gun in a cathode ray tube display. However, with the advent of LCD displays and as retrace speeds have increased in modern monitors, it is now possible to present a user interface display in this border. The border which can be controlled as a user interface is a portion of what is known as the "overscan". This invention is a method for presenting one or more additional or secondary user interfaces, for example, in the overscan area surrounding the conventional user interface display often called the desktop.

When the electron gun in a CRT retraces to the left of the screen or the top of the screen, it requires a significant amount of time relative to the presentation of a scanned line of data. During the retrace, the electron gun is turned off ("blanked"). If the blanking time required for the retrace is equal to the amount of time available, there is no usable overscan. However, modern monitors have become much faster in their retrace speeds, leaving a significant amount of time when the electron gun need not be blanked, allowing a displayable border. In the prior art, although the border is usually "black" (the gun is turned off), it is well known how to specify that the border shall be given any one of six colors. Standard BIOS allows a specification of this color. The desired color is simply specified in one of the registers for the video controller. Typically no data for this color is stored in the buffer of video memory for the display. This invention establishes an additional video buffer for the border and allows this buffer to be written with display data like the regular display buffer. The additional video buffer is often present but unused in the graphics systems of most computers because video memory is usually implemented in sizes that are powers of 2 e.g., "512K", whereas standard desktop dimensions are not "e.g., 640x480=300K'\ The display area is thereby expanded, on one or more edges, to provide a visible area previously invisible. The pixels within this newly visible area of the display are made accessible to programs through an application programming interface (API) component of this invention. A program incorporating a parallel graphical user interface may be displayed in the previously blanked area of the display, functionally increasing the accessible area of the display without hardware modification. In other cases the desktop may be increased or decreased to non-standard sizes.

A further aspect of the present invention includes a method for displaying an image on a video display system in an area outside of the primary display area generated by the video display system. Two dimensions define the standard display area, each specifying a number of pixels. Selecting a video "mode" specifies these dimensions. The method is accomplished by adjusting parameters for the video display system to increase the number of pixels in at least one dimension of the display system. The number of pixels which is added is less than or equal to the difference between the number of pixels specified in the video mode and a maximum number of pixels which the video display system can effectively display. Any such difference is defined here as the overscan area. Thus, the overscan area may be the difference between the current desktop video mode and the display capability of the display device or more specifically, any portion of video memory unused when the operating system is in a given screen dimension. Because all interface displays are created by writing a desired image to a buffer or memory for the video display, the method requires allocating additional video display memory for the increased pixels. The image written to such memory is then displayed by the system alongside the original display area.

In a still further aspect of the present invention, only the vertical dimension is increased and the overscan user interface is presented above or below the primary display area. Alternatively, the horizontal dimension may be increased and the overscan user interface displayed to the right or the left of the primary display area. Similarly, the interface image may be displayed on any or all of the four sides of the primary display area.

In another still further aspect of the present invention, a parallel GUI is provided that includes access to existing search engines and browsers. In another embodiment, the parallel GUI includes a search engine and/or browser. A search - engine and/or browser using the present invention may be opened in either the overscan space or a space within or over the operating system display. The included browser functionality may also be included in every application or utility side of the GUI making the browser available to a user regardless of the application or utility side visible in the parallel GUI. These and other features and advantages of this invention will become further apparent from the detailed description and accompanying figures that follow. In the figures and description, numerals indicate the various features of the invention, like numerals referring to like features throughout both the drawings and the description.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram of a first embodiment of the present invention.

Fig. 2 is a block diagram of a second embodiment of the present invention.

Fig. 3 is a diagram of a standard display with an overscan user interface on all four borders of the display. Fig. 4 is a block diagram of the basic components of the present invention.

Fig. 5 is a diagram of a cursor or pointer within the overscan user interface and the hotspot above it within the standard display.

Fig. 6 is a diagram of the usable border within the vertical overscan and the horizontal overscan surrounding the standard display. Fig. 7 is an overview flow chart showing the operation of a preferred embodiment of the present invention.

Fig. 8 is a flowchart of the sub-steps in Identify Display step 102 of Fig. 7. Fig. 9 is a flowchart of the sub-steps of changing the display resolution step 114 of Fig. 7.

Fig. 10 is a flowchart of the sub-steps in the Paint the Display step 120 of Fig. 7.

Fig. 11 is a flowchart of the sub-steps of Enable Linear Addressing step 112 of Fig. 7.

Fig. 12 is a flowchart of the sub-steps of the Process Message Loop of

Fig. 13 is a flowchart of the sub-steps of the Check Mouse and Keyboard Events step 184 in Fig. 12. Fig. 14 is a flowchart of the sub-steps of the Change Emulation

Resolution step 115 in Fig. 7.

Fig. 15 is a diagram of a standard display of the prior art.

Fig. 16 is a diagram of a standard display with an overscan user interface in the bottom overscan area. Fig. 17 is a diagram of a standard display including a desktop, an overscan user interface in the bottom overscan area and a context sensitive browser on the side.

Fig. 18 is a diagram of a standard display with an overscan user interface in the bottom and on the right overscan area.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

The present invention includes techniques for providing and using an additional user interface, preferably a secondary graphical user interface or parallel GUI, to be present on the display at least apparently simultaneously with the primary user interface, such as the conventional desktop GUI. Referring now to Figs. 1 and 2, in a preferred embodiment, programming mechanisms and interfaces in a video display and control system such as computer system 7 or settop box 8 provide one or more parallel GUIs such as space 2C and/or space 4 in a display area such as display area 1 or display area 9 by providing access and visibility to a portion of the display otherwise ignored and/or inaccessible (hereinafter "overscan area"). Display areas such as display area 1 or display area 9 may be created on any type of analog or digital display hardware including but not limited to CRT, TFT, LCD and flat panel.

Alternate display content controller 6 interacts with the computer utility operating system 5B and hardware drivers 5C to control allocation of display space 1 and create and control one or more parallel graphical user interfaces such as context sensitive network browser (CSNB) 2 and internet pages 2A and 2B adjacent the operating system desktop 3. Alternate display content controller 6 may be incorporated in either hardware or software. As software, an alternate display content controller may be an application running on the computer operating system, or may include an operating system kernel of varying complexity ranging from dependent on the utility operating system for hardware system services to a parallel system independent of the utility operating system and capable of supporting dedicated applications. The alternate display content controller may also include content and operating software such as JAVA delivered over the Internet I or any other LAN. The alternate display content controller may also be included in a television decoder/settop box such as box 8 to permit two or more parallel graphical user interfaces such as pages 9A and 9B to be displayed simultaneously. The present invention may be compatible with conventional television formats such as NTSC, PAL, PAL-C, SECAM and MESECAM. In this configuration content and software may be delivered over any conventional delivery medium 10 including but not limited to over the air broadcast signals 10A, cable IOC, optical fiber, and satellite 10B.

Figs. 1 and 2 will be referenced in more detail later in the application. Fig. 15 shows a standard prior art display desktop generated by a Microsoft Windows 95™ operating system. Within the desktop 31 are the taskbar 32 and desktop icons 33.

In a preferred embodiment of the present invention, a graphical user interface image is painted onto one or more of the sides of the overscan area as shown in Fig. 3. Fig. 3 is a depiction of a Super VGA (SVGA) display with the addition of a graphical bar user interface displayed in the overscan area. The overscan user interface bar 30 is defined to reside outside the borders of the "desktop" display area 31. In Fig. 16, the display is modified to include a graphical user interface 30 in a bar 20-pixels high below the bottom edge. In Fig. 3, the display is modified to include a graphical user interface in four bars each 20-pixels high/wide outside each of the four display edges: a bottom bar 30, a left side bar 34, a right side bar 36, and a top bar 38. The overscan interface may include, and is not limited to, buttons, menus, application output controls (such as a "ticker window", or HTML browser/viewer), animations, and user input controls (such as edit boxes). Because the overscan interface is not obscured by other applications running within the standard desktop, the overscan interface may be constantly visible or it may toggle between visible and invisible states based upon any of a number of programming parameters (including, but not limited to, the state of the active window, the state of a toggle button, etc.).

Fig. 4 is a block diagram of the basic components of the present invention. Within the software component S are the operating system 63 and one or more applications such as application 61. Within the protected modes of modern systems, applications 61 do not have direct access to the video or Graphics Drivers 64 or hardware components such as the video card 66 which contains the video chipset 66A, 66B and 66C. Abstraction layers such as Application Interface (API) 60, and/or DirectX API 62, provide limited access, often through, and therefore limited by, the operating system 63.

The invention provides a technique for painting and accessing an area of the computer display not accessible, or used, in the operative desktop graphics modes. In the Microsoft Windows environments (including Microsoft Window 95 and derivatives, and Microsoft Windows NT 4.0 and derivatives) and other contemporary operating environments, the primary display area "desktop" is usually assigned by the operating system to be one of a set of pre-determined video "modes" such as those laid out in Tables 1 and 2 below, each of which is predefined at a specific pixel resolution. Thus, the accessible area of the computer display may not be modified except by selecting another of the available predefined modes.

TABLE 1 : ROM BIOS video modes

TABLE 2: SVGA video modes defined in the VESA BIOS extension

In one embodiment, as shown in Fig. 6, a displayed image is "overscanned". That is, the displayed video buffer data occupies less than the entire drivable screen size. The drivable screen size is determined by the total amount of video memory and the operative video display characteristics. The width of the usable overscan border depends on the amount of the horizontal overscan 52 reduced by the horizontal blanking 54 and the amount of the vertical overscan 53 reduced by the vertical blanking 55.

In a first preferred embodiment, only a border at the bottom of the standard display area is used. Consequently, only the vertical control parameters for the cathode ray tube (CRT) controller, shown as Control Registers 6H, 16H, 11H, 10H, 12H and 15H in Fig. 4 need to be adjusted. These parameters and others are shown in Table 3 below:

TABLE 3: Vertical timing parameters for CR programming.

In the standard 640x480 graphics mode, the nominal horizontal scan rate is 31.5 KHz (31,500 times per second) with a vertical scan rate of 60 Hz (60 frames per second). So the number of lines in one frame is 31,500/60, or 525. Because only 480 lines of data need to be displayed, there are 525-480, or 45, lines available for vertical overscan. Leaving a more than adequate margin for retrace, which requires only 2 lines worth of time, the preferred embodiment uses 20 lines for the alternate display. Thus the additional 23 unused but available lines may be used to increase the size of the accessible area of the computer display to some non-standard size while still allowing two lines for retrace, or may be left blank, or may be used for one or more additional alternate parallel user interface displays.

The disclosed method of the preferred embodiment of the present invention is accomplished by achieving three requirements:

(1) to address and modify the visible resolution of the video display system such that portions of an overscan area are visible as shown in Fig. 6,

(2) to address and modify the video display contents for the visible portion of the overscan area, and

(3) to provide an application programming interface (API) or other mechanism to allow applications to implement this functionality. Fig. 7, and the additional details and sub-steps provided in Figs. 8-13, provides a flow chart of an implementation of a preferred embodiment of the present invention meeting the requirements described above. The environment of this implementation is a standard Microsoft Windows 95™ operating environment, using Microsoft Visual C and Microsoft MASM for the development platform. That is not to imply that this invention is limited in scope to that environment or platform. The invention could be implemented within any graphical interface environment, such as X- Windows, OSF Motif, Apple OS, a Java OS, and others in which similar video standards (VGA, SVGA, XGA, 8514/ A) are practiced. The reference books PC Video Systems by Richard Wilton, published by Microsoft Press and Programmer's Guide to the EGA, VGA, and Super VGA Cards by Richard F. Ferrano, published by Addison Wesley provide more than adequate background information to implement this embodiment.

Referring now in particular to Fig. 7, upon initialization, at Identify

Display Type step 102, the program attempts to determine the display type, and current location in memory used by the display driver, in order to determine the size and locations of any display modifications to be made, e.g., to the size and location of overscan area(s) to be used.

As described in further detail in Fig. 8, the program first queries the hardware registry in Query Hardware Registry, step 131, to attempt to determine the registered display type. If successful, the program then determines compatibility information in Display Type Supported, step 135, to verify that the program supports that display type and determine memory allocation information.

If the hardware registry information is unavailable, as determined in step

131, or the display type determined in step 131 is unsupported as determined by step 104, the program may use an alternate approach, shown as subroutine Query hardware, steps 135 in Fig. 8, to query the BIOS, in step 134, and the video chipset 66, in step

136, for similar information as described immediately below.

If the BIOS is to be accessed in step 134, physical memory is first allocated in Allocate Physical Memory, step 132, and accessed using Microsoft's DPMI (DOS Protected Mode Interface) to map it to the linear memory address in which the

BIOS resides in Use DPMI to assign BIOS linear address to physical memory, step 133.

Thereafter, the program queries the BIOS in Read BIOS block, Search for VGA/XVA type and manufacturer ID, step 134. If successful, the driver and chipset are then further queried to determine the display type and memory location in Query driver/chipset for exact chipset, step 136.

If the compatibility information does not indicate a standard VGA,

SVGA, XGA, or 8514/A signature, step 134, this routine returns a failure. If a known chipset manufacturer's identification is found, the driver and/or chipset may be queried with manufacturer-specific routines, step 136, to identify and initialize, as necessary, the specific chipset.

If, at step 104, the program was unable to finally identify the display type, either because the registry query in step 131 or the hardware query in step 135 was unsuccessful, the user may be prompted at Run in emulation mode, step 13, or at Run in windowed mode, step 116, as to whether the program should continue to run as a secondary GUI using an alternative technique for emulation mode, or as a standard "application bar" or "toolbar". The program may either exit or proceed to run as a toolbar on the desktop.

Returning now to Fig. 8, if a supported display type is detected, the program then determines the screen borders to be accessed in Identify borders to display in overscan, step 106, based upon user preferences, and determines, as necessary, whether sufficient video memory exists to make the necessary display changes. For example, if the screen is currently set to a 1024x768 resolution at 16 bits- per-pixel, and the program is to include four graphical interface bars, one on each edge, with each bar 20 pixels deep, the program must check that video memory is greater than 1.7MB (required number of bytes = Pixels Width * BitsPerPixel * PixelsHeight).

The controller registers 6H, 16H, 11H, 10H, 12H and 15H as shown in Fig. 4 and detailed in Table 3, may be accessed through standard input/output ports, using standard inp/outp functions. The CR registers 6H, 16H, 11H, 10H, 12H and 15H must first be unlocked, as indicated in Unlock CRTC registers, step 108 in Fig. 7, to make them writeable. They are unlocked by clearing bit 7 in controller register 11H.

Addressing of video memory, step 112, is accomplished through one of several means. One is to use the standard VGA 64 Kb "hardware window", moving it along the video memory buffer 67 (Fig. 4) in 64Kb increments as necessary. The preferred method is to enable linear addressing by querying the video chipset for the linear window position address, step 138 of Fig. 1 1. This 32-bit offset in memory allows the program to map the linear memory to a physical address, steps 140 and 142 of Figure 11, that can be manipulated programmatically.

At this point the program can modify the size of the display, step 114 and Fig. 9, to include the border areas. This routine first checks to determine whether or not the system is running in "toolbar" mode, step 144, and, if so, returns true. If not, it then determines whether to reset all registers and values to their original state, effectively returning the display to its original appearance, step 152. The determination is based upon a number of parameters, such as whether the current resolution, step 146, reflects a standard value or previous programmatic manipulation, step 148. If a standard resolution is already set, the variables are reset to include the specified border areas, step 150. The CR registers are adjusted, step 154, to modify the scanned and blanked areas of the display. If the top or side areas are modified, existing video memory is moved accordingly in step 162 of Fig. 10. If any of the foregoing routines returns a failure, the program may prompt the user to determine whether "emulation" mode, step 13, or windowed mode step 116 should be used or if the program should exit at step 124.

In its simplest form, the invention can be treated as a technique for adding a secondary GUI by reconfiguring the actual display mode to add a modified, non-standard GUI mode in which the standard display size or resolution has been adjusted to include a secondary display in addition to the primary display. For example, a standard 640x480 display is modified in accordance with the present invention to become a larger display, one section of which corresponds to the original 640x480 display while another section corresponds to a 640x25 secondary GUI display.

There are various techniques or mechanisms required for modifying the system to include the secondary GUI, depending upon the requirements of the secondary GUI and upon the present circumstances of the unmodified system.

In another embodiment of the present invention system resources are allocated for a secondary GUI by fooling the video driver into going to larger resolution. This technique automatically guarantees that enough space is kept clean, since the video driver allocates system resources according to the resolution that the video driver believes it will be operating in. To operate one or more secondary user interfaces in one or more areas of the screen it is necessary to have the memory that was associated in video memory or in the frame buffer with that location, contiguously below the primary surface free and available. By writing a series of small applets specific to hardware known to have system resource allocation problems for a secondary user interface, the secondary user interface application may run such applet whenever resolutions will be switched, initializing the chip set pertinent to that particular applet. If the application finds an applet pertinent to the current particular chip set it will be launched. The applet or minidriver initializes itself, performs the necessary changes to the driver (e.g., modifying the video resolution tables), forces a reenable, and sufficient space is subsequently available for one or more secondary user interfaces. When reenabled, the driver allocates video memory as needed for the primary display according to the data on the video resolution tables. Therefore, the modified values result in a larger allocation. Once the driver has allocated memory necessary for the primary surface, the driver will allow no outside access to the allocated memory. Thus by fooling the driver into believing that it needs to allocate sufficient memory for a resolution exactly x bytes larger than the current resolution where x is the size of one or more secondary user interfaces, the application can be sure that no internal or external use of the allocated memory location can conflict with the secondary user interface.

This method ensures that system resources will be allocated for one or more secondary user interfaces by writing an applet that would address the video driver in such a way as to force the video driver, on its next reenable, to allocate video memory sufficient for a resolution higher than the actual operating system resolution. This may also be done by modifying each instance of the advertised mode tables, and thus creating a screen size larger than the primary user interface screen size.

This technique has an additional benefit of eliminating the need to prevent the driver from actually shifting into the specified larger resolution, handing the primary user interface a larger display surface resolution. The "hardware mode table," a variant of the aforementioned video resolution tables, is not advertised and not accessible. Therefore, when the driver validates the new resolution, checking against the hardware mode table, it will always fail and therefore refuse to shift into that resolution. Because this technique modified the advertised video resolution tables early enough in the driver's process, allocated memory was modified, and memory addresses set before the failure in validate mode. Subsequently when the CRTCs are modified, in step 114, the driver is reserving sufficient memory for one or more secondary user interfaces and not making it available for any other process or purpose. In yet another embodiment of the present invention, an enveloping driver is installed to sit above the existing driver and shims itself in between the hardware abstraction layer and the actual video driver in order to be able to handle all calls to the video driver and modify the driver and the driver's tables in a much more generic fashion rather than in a chipset specific fashion. The enveloping driver shims into the primary video driver, transparently passing calls back and forth to the primary video driver. The enveloping driver finds the video resolution tables in the primary video driver which may be in a number of locations within the driver. The enveloping driver modifies the tables (for example, increasing 800 by 600 to 800 by 620). A 1024 by 768 table entry may become 1024 by 800. Like the previously described embodiment, the primary driver cannot validate the new resolution and therefore cannot actually change the display setting. As a result, the driver allocated memory, allocated the cache space, determined memory address and moved cache and offscreen buffers as necessary. So the primary driver never uses all the space allocated, and will never draw in that space. As stated earlier, the method of the present invention may include three primary steps, finding or producing unused video memory, creating or expanding the overscan area, and putting data in the overscan area. The step of finding or producing the unused video memory requires a review of the contents of the Controller Registers, the CR registers, used by VGA compatible chip sets or graphic boards to identify where the overscan area, the blanking, the vertical and horizontal total and the sinking should be set. The CR defines the desktop display, how its synched, where its laid out left and right, how much buffer area there would be on each side, where it would be stored within the video memory area. A review of the contents of the CR data registers therefore fully defines and allows one to control the potential location and size of the overscan area.

In order to accomplish the step of creating or expanding the overscan area, the CRs may currently be used directly for systems with video display resolutions up to and including 1024 pixels in any dimension, that is, resolutions which can be defined in the generally accepted VGA standards by 10 bits per register. To expand the overscan area, new data is written into the CR using standard techniques such as the Inp and Outp, functions. A standard video port and MMIO functions may also be used to modify the CRs.

At greater resolutions, 11 bits may be needed to properly define the resolution. There is currently no standard way in which the 11^th bit location is defined. Therefore, at a resolution above 1280 by 1024, for example, an understanding about the video card itself, particularly how the 11 bits representing the resolution are stored, is currently required and will be described below in greater detail.

When expanding the overscan, it is important to make sure a previous overscan bar is not already displayed, possibly from a previous crash or other unexpected problem. Either the display must be immediately reset to the appropriate resolution defaults, or the CR queried to determine if the total screen resolution as understood by the video card and drivers differs from the screen resolution known by the operating system display interface. An overscan bar may already be displayed if the total screen resolution is not equal to one of the standard VGA or SVGA resolutions. In particular, if the total screen resolution is equal to a standard VGA/SVGA resolution plus the area required for the overscan bar or is greater than the resolution reported by the operating system display interface, the display is reset.

Once the display area or resolution as stored in the CR is determined, the resolution or display area can be extended in several different ways. The overscan area can be added to the bottom, the top, or the right of the current display area, and optionally, the display area can be repositioned so that the overscan bar can remain centered in appearance. Alternatively the overscan area can be added anywhere and the original or desktop display area can be centered to improve appearance. In any event, the height/width of the display area required for the overscan bar is presented adjacent the desktop area stored in the CR and the combination is written into the CR, overwriting the previous data.

The screen typically shows a quick flash as it is placed in a different mode, including the desktop display area as well as a parallel GUI such as a display bar in the overscan area. As soon as that change occurs, a black mask can be positioned over the new areas. The new menu data can then be safely written on top of the black mask so that the user never sees memory "garbage".

There is typically a few seconds of load time during which a simple message can be displayed, such as "Loading...", to avoid confusing the user. There are a number of mechanisms by which this may be done. A set of class objects is used, all derived from a common base class corresponding to the above described VGA-generic technique.

The first mechanism is an implementation of the VGA-generic technique. Using this mechanism, no information specific to a video-card is necessary, other than ensuring VGA support. Using standard application programming interface

(API) routines, primary and secondary surfaces are allocated. The new display data in the CR is simply the physical address at the start of the primary surface plus the number of pixels defined by the screen size.

Allocation of the primary surface will always be based on the entire screen display. Given the linear address of the allocated primary surface, from which a physical address can be derived, it can be extrapolated that the physical address of the location in video memory immediately adjacent to the primary surface is represented by the sum of the number of bytes of memory used to maintain the primary surface in memory plus the value of the physical address of the primary surface. Once the physical address of the primary surface is known, the size of the primary surface as represented in video memory can be determined.

For example, the system looks in the CRs for the resolution of the screen, 800 by 600, in terms of number of bits per pixel, or bytes per pixel. Then any data stored in the CR representing any horizontal synching space is added. This is the true scan line length. The scan line length is a more accurate measurement of the width in a given resolution.

Next, the physical address of the allocated secondary surface is derived from its linear address. In the case where the allocated secondary surface is, in fact, allocated in the memory space contiguous to the primary surface (the value of the secondary surface physical address is equal to the value of the primary surface physical address plus the size of the primary), the secondary surface is determined to be the location in memory for the overscan display. If, however, the above is not true and the secondary surface is not contiguous to the primary surface, another approach mechanism is required.

To summarize, the first mechanism determines how much physical area to allocate for the desktop allowing adjacent area for parallel GUI secondary space beyond that to display in the overscan area. The newly allocated area will be the very first block of memory available. If this block immediately follows the primary surface, the physical address will correspond to the value associated with the physical address of the primary surface, plus the size of the primary surface. If that is true, the memory blocks are contiguous, this VGA-generic mechanism can be used. If this first, VGA-generic mechanism cannot be used, the video card and driver name and version information retrieved from the hardware registry and BIOS, as described earlier, is used in conjunction with a look-up table to determine the best alternatives among the remaining mechanisms. The table includes a set of standards keyed to the list of driver names found, in the hardware registry. A class object specific to the video chipset is instantiated based, directly or indirectly, on the VGA-generic object.

If the hardware look up does not result in a reliable match, a reliability, or confidence, fudge factor may be used. For example, if the hardware look up determines that an XYZ -brand device of some kind is being used, but the particular XYZ device named is not found in the look up table, a generic model from that chipset manufacturer many often be usable. If no information is available, the user may get a message indicating that the hardware is not supported and that the program cannot run in the overscan area. The user may then be queried to determine if the system should be operated in the "application-toolbar" mode, which basically runs with exactly the same functionality but in a windowed environment within the desktop rather than in the overscan area outside the desktop.

The next alternative mechanism uses surface overlays. The first step to this approach is to determine if the system will support surface overlays. A call is made to the video driver to determine what features are supported and what other factors are required. If surface overlays are supported, for example, there may be a scaling factor required.

For example, a particular video card in a given machine, using 2 megabytes of video RAM, might support unsealed surface overlays at 1024x768 at 8 bits per pixel, but not at 1024x768 at 16 bits per pixel because the bandwidth of the video card or the speed of the card, coupled with the relatively small amount of video memory would not be sufficient to draw a full width overlay. It is often horizontal scaling that is at issue, preventing the driver from drawing a full width overlay. An overlay is literally an image that is drawn on top of the primary surface. It is not a secondary surface, which is described above. Typically, the system sends its signal from the video driver to the hardware such that it merges the two signals together, overlaying a second signal on top of the first. If a system can not support unsealed overlays, perhaps because of bandwidth issues or memory issues, this mechanism is not desirable. It is not rejected, but becomes a lower priority alternative. For example, if the scaling factor is below .1, then the normal bar can be drawn and it will be clipped closer to the edge. If the scaling factor is more than 10%, another approach mechanism is required. In the next set of alternative mechanisms, a secondary surface is allocated sufficient in size to encompass the normal desktop display area plus the overscan area to be used for display of the overscan bar or bars. Using these mechanisms, the allocated secondary surface does not have to be located contiguous in memory to the primary surface. However, these approaches use more video memory than the others.

The first step is to allocate a secondary surface sufficient in size to contain the video display (the primary surface) plus the overscan area to be used. If the allocation fails, that means that there is not enough video memory to accomplish the task and this set of mechanisms is skipped and the next alternative tried. After the new block of memory is allocated, a timer of very small granularity is used to execute a simple memory copy of in the contents of the primary surface onto the appropriate location of this secondary surface. The timer executes the copy at approximately 85 times per second.

Within this set of alternative mechanisms is a variant that uses the system page tables. This mechanism queries the system page tables to determine the current GDI surface address, that is, the physical address in the page table for the primary surface. A secondary surface is then created large enough to hold all of what is in the video memory plus the memory required for the overscan bar to be displayed. This surface address is then pushed into the system page table and asserted as the GDI surface address.

Thereafter, when GDI reads from or writes to the primary surface through the driver, it actually reads from or writes the new, larger surface. The overscan bar program can, subsequently, modify the area of the surface not addressed by GDI. The original primary surface can be de-allocated and the memory usage reclaimed. This mechanism, being more memory-efficient than the previously described mechanism, is the preferred alternative. But the page tables solution will not work correctly on a chipset that includes a coprocessor device. If the initial device query reveals that the device does include a coprocessor, this variant mechanism will not be attempted.

Other variations of the above-described mechanisms are accounted for in derived class objects. For example, the VGA-generic mechanisms may vary when the video card requires more than ten bits to represent the video resolution in the CR. Some instances may require 11 bits. Such registers typically do not use contiguous bytes, but use extension bits to designate the address information for the higher order bits.

In this example, the eleventh bit is usually specified in an extended CR register and the extended CR registers are usually chip specific.

Similarly, a variation of the surface overlay mechanism includes a scaling factor, as described above. This alternative is handled in specific implementations through derived class objects and may be the best solution in certain situations. Another implementation of this technology uses a "hooking" mechanism as shown in Fig. 14. After the display driver is identified through the hardware registry or the BIOS, as described above, certain programming interface entry points into the driver are hooked such as at step 117. In other words, when the video system device interface, Windows GDI for example, calls those entry points into the display driver, the program can take the opportunity to modify the parameters being passed to the display driver, and/or to modify the values being returned from the display driver.

By hooking the "ReEnable" function in the display driver, at step 117, the overscan bar program can allocate screen area in different ways in step 119:

(1) In step-up mode, step 121, by intercepting a resolution change request and identifying the next-higher supported screen resolution and passing that higher resolution to the display driver, then, when the display driver acknowledges the change, intercepting the returned value, which would reflect the new resolution, and actually returning the original requested resolution instead. For example, GDI requests a change from 640x480 resolution to 800x600 resolution; the overscan program intercepts the request and modifies it to change the display driver to the next supported resolution higher than

800x600, say 1024x768. The display driver will change the screen resolution to

1024x768 and return that new resolution. The overscan program intercepts the return and instead passes the original request, 800x600, to GDI. The display driver has allocated and displays a 1024x768 area of memory. GDI and

Windows will display the desktop in an 800x600 area of that display, leaving areas on the right and bottom edges of the screen available to the overscan program.

(2) In shared mode, step 123, by intercepting only the return from the display driver and modifying the value to change the operating system's understanding of the actual screen resolution. For example, GDI requests a change from 800x600 resolution to 1024x768 resolution. The overscan program intercepts the returned acknowledgment, subtracting 32 before passing the return on to GDI. The display driver has allocated and displays a 1024x768 area of memory. GDI and Windows will display the desktop in an 1024x736 area of that display, leaving an area on the bottom edge of the screen available to the overscan bar program.

(3) In step-down mode, step 125, the program performs the reverse of step-up mode: that is, the program intercepts a resolution change request; requests the resolution change, but returns the next lower resolution to the graphical device interface. For example, when GDI requests a change from

640x480 resolution to 800x600 resolution; the program intercepts the request and modifies it to change the video device driver to 800x600. The video device driver will change the screen resolution to 800x600 and returns that new resolution. The program intercepts the return and instead passes a next lower resolution, 640x480 (denying the request), to GDI. The driver has allocated and displays a 800x600 area of memory. GDI and the native OS will display the desktop in an 640x480 area of that display, leaving areas on the right and bottom edges of the screen available to the overscan program. After hooking, the overscan bar program can display by: (1) using standard API calls to render the bar to an off-screen buffer, as described in the next section, and then hooking the "BitBlt" function entry- point into the display driver in order to modify the offset and size parameters and subsequently redirect the BitBlt to the area outside of that which the API believes is onscreen. (2) using mechanisms of primary and secondary surface addresses, described earlier, the program determines the linear addresses for the off- desktop memory location(s) left available to it, and can render directly to those memory locations.

Phase 2 of the invention begins by painting the new images into a standard off-screen buffer, step 1 18, as is commonly used in the art, and making the contents visible, step 120, as described in Fig. 10. If the program is in "toolbar" mode, step 156, the off-screen buffer is painted into the standard window client space, step 166, and made visible, step 164, using generic windowing-system routines. Otherwise, the linear window position address is mapped, step 158, as described in Fig. 11 which has been previously explained. Once the linear memory is mapped to a physical memory address, step 142, the contents of the off-screen display buffer can be copied into the video buffer directly, step 154 of Fig. 10, or painted as to a secondary surface. The preferred embodiment application includes a standard application message loop, step 122, which processes system and user events. An example of a minimum functionality process loop is in Fig. 12. Here the application handles a minimal set of system events, such as painting requests, step 170, system resolution changes, step 172, and activation/deactivation, step 174. Here, too, is where user events, such as key or mouse events, may be handled, step 184, detailed in Fig. 13. System paint messages are handled by painting as appropriate into the off-screen buffer, step 178, and painting the window or display buffer, step 180, as appropriate, as described earlier in Fig. 10. System resolution messages are received whenever the system or user changes the screen or color resolution. The programs reset all registers to the correct new values, then change the display resolution, step 182, as earlier described in Fig. 9, to reflect the new resolution modified. User messages are ignored when the program is not the active application.

Fig. 13 describes a method of implementing user-input events. In this embodiment, there are three alternative mechanisms used to implement cursor or mouse support so that the user has a pointing device input tool within the overscan area user interface.

In the preferred mechanism, GDI's "cliprect" is modified to encompass the overscan bar's display area. That keeps the operating system from clipping the cursor as it moves into the overscan area. This change doesn't necessarily make the cursor visible or provide event feedback to the application, but is the first step.

Some current Windows applications continually reset the cliprect. It is a standard programming procedure to reset the cliprect after use or loss of input focus. Some applications use the cliprect to constrain the mouse to a specific area as may be required by the active application. Whenever the overscan display bar interface receives the input focus it reasserts the cliprect, making it large enough for the mouse to travel down into the overscan space.

Once the cliprect has been expanded, the mouse can generate messages to the operating system reflecting motion within the expansion area. GDI does not draw the cursor outside what it understands to be its resolution, however, and does not pass "out-of-bounds" event messages on to an application. The overscan program uses a VxD device driver, and related callback function, to make hardware driver calls at privilege or protection ring zero to monitor the actual physical deltas, or changes, in the mouse position and state. Every mouse position or state change is returned as an event to the program which can graphically represent the position within the menu display bar. An alternative mechanism avoids the need to expand the cliprect in order to avoid conflict with a class of device drivers that use the cliprect to facilitate virtual display panning. Querying the mouse input device directly the overscan program can determine "delta's", changes in position and state. Whenever the cursor touches the very last row or column of pixels on the standard display, it is constrained there by setting the cliprect to a rectangle comprised of only that last row or column. A "virtual" cursor position is derived from the deltas available from the input device. The actual cursor is hidden and a virtual cursor representation is explicitly displayed at the virtual coordinates to provide accurate feedback to the user. If the virtual coordinates move back onto the desktop from the overscan area, the cliprect is cleared, the virtual representation removed, and the actual cursor restored onto the screen.

A third alternative mechanism creates a transparent window that overlaps the actual Windows desktop display area by a predefined number of pixels, for example, two or four pixels. If the mouse enters that small, transparent area, the program hides the cursor. A cursor image is then displayed within the overscan bar area, at the same X-coordinate but at a Y-coordinate correspondingly offset into the overscan area. If a two-pixel overlap area is used, this method uses a granularity of two. Accordingly, this API-only approach provides only limited vertical granularity. This alternative mechanism assures that all implementations will have some degree of mouse-input support, even when cliprect and input device driver solutions fail. Fig. 7 describes the cleanup mechanisms executed when the program is closed, step 124. The display is reset to the original resolution, step 126, and the CR registers are reset to their original values, step 128, and locked, step 130.

In another embodiment of the present invention, the launching or initiating of alternate display content controller 6 may be modified and controlled. Alternate display content controller 6 may be launched as a service, as an application, or as a user application. As a service, alternate display content controller 6 may be launched as a service within the registry of utility operating system 5B. The first kind of application is launched in the Run section in the registry, and the user application may be initiated from the Start Up Group within the Start button. Thus, alternate display content controller 6 may be initiated any time from the first thing after graphics mode is enabled to the very last thing initiated. Launched as a service, alternate display content controller 6 may be visible shortly after utility operating system 5B such as Windows actually addresses the display, and how soon after depends on where alternate display content controller 6 is put it in the order of the things that will be launched as services. It may be possible to put alternate display content controller 6 so that it launches as essentially the first service and thus would launch almost at the same time as the drivers, very, very shortly after the drivers are launched. Accordingly, it is possible to have the screen change from text mode to graphics, draw the colored background, immediately re-display with the overscan addressed and a parallel GUI such as CSNB 2 display the very close to the same time as taskbar. Launched as a run-line application, alternate display content controller 6 may be visible in display space 1 shortly after icons appear.

NetSpace

Referring again to Fig. 1, in an alternate embodiment of the present invention, the technique of controlling the allocation of display area 1 is used to open a context sensitive network browser 2 (CSNB) adjacent but not interfering with operating system desktop 3 and/or parallel graphical user interface 4. A display controller such as alternate display content controller 6 may include CSNB 2 thus permitting the browser to create and control a space for itself on display 1 which may not be overwritten by utility operating system 5B. The combined controller/browser may be an application running on the computer operating system, or may include an operating system kernel of varying complexity ranging from dependent on the utility operating system for hardware system services to a parallel system independent of the utility operating system and capable of supporting dedicated applications. The alternate display content controller/browser may also include content and operating software such as JAVA delivered over the Internet I or any other LAN. There may also be more than one context sensitive network browser and more than one parallel graphical user interface in addition to the operating system desktop. Additional details are attached hereto as appendices A and B.

Context sensitive interface such as network browser 2 may respond to movement and placement of cursor IC controlled by a pointing device such as mouse 1M anywhere on display area 1. The generation and control of a cursor across two or more parallel graphical user interfaces was described previously. The location of cursor 1 C will trigger CSNB 2 to retrieve appropriate and related network pages such as web page 2A. CSNB 2 may store the last X number of CSNB enabled network addresses for display offline. In a currently preferred embodiment of the present invention, X is ten pages. If a user is examining a saved CSNB enabled page offline, a mouse click on the page or a link on the page will initiate the users dial-up sequence and establish an online connection.

In an alternate embodiment, alternate display content controller 6 may include a browser or search engine. In an alternate embodiment of the present invention, space 2C may include an edit input box 2D. Edit input box 2D may include conventional functionality's such as edit, copy, paste, etc.. A user may enter a URL into edit input box 2D using any conventional input device and then select a button to launch or initiate alternate display content controller 6 as a browser. This may be accomplished by using objects and or drivers from utility operating system 5B. Initiating alternate display content controller 6 as a browser would include a simple window to display the URL as a live HTML document with all conventional functionality. By implementing alternate display content controller 6 as a little applet that uses that DLL, it may slide on, or slide off. Thus initiating alternate display content controller 6 as a browser is like a window into the Internet. Secondly, a user may enter any text into edit input box 2D using any conventional input device and then select a button to launch or initiate alternate display content controller 6 as a search engine. By entering a search string and selecting "search" and enter any string and click on "search" and pass that to any number from one to whatever or existing search engines, and subsequently have the search string acted on by one or more selected search engines and or by alternate display content controller 6 as a search engine. Resulting in multiple different windows appearing in some sort of stacked or cascaded or tiled format, with the different searches within them.

Using alternate display content controller 6 as a search engine or browser, the results or HTML document may be displayed in any overscan area or on the desktop.

Referring now to Fig 17, a context sensitive network browser such as CSNB 13 may also include a suite of tools such as tools 14 that may or may not have fixed locations on the browser space. Such tools may include but are not limited to e- mail, chat, buddy lists and voice. As shown, spaces such as desktop 14A, web page 14B, secondary GUI 14C and browser 13 may be arranged in any convenient manner.

In one embodiment, the techniques of the present invention can be used to effectively reduce the operating system desktop (native graphical user interface) to a smaller area of the display such that one or more secondary user interfaces can occupy and use a significant portion of the display. In some scenarios, the secondary user interface may appear to the user as the primary user interface, while the operating system desktop may appear to take on a secondary role, because of the size each interface occupies on the display relative to each other.

For example, in Figure 17, the operating system desktop 14A is shown as occupying a lesser portion of the display screen, thereby leaving significant space to secondary user interface 14C, web page 14B, and browser 13. The operating system desktop functionality is not reduced, it is merely relegated to a smaller size. The remaining portions of the display area are then addressable and usable by other applications, such as secondary user interface 14C. These other applications may use, for example, an application programming interface (API) component that controls addressing, displaying on, and input / output to and from the area outside of that controlled by the operating system API.

These types of features and others may be accomplished by using a combination of the display allocation techniques already described. For example, the alternate display content controller may use a combination of the step-up and step-down "hooking" techniques previously described. Specifically, the alternate display content controller may request from the video driver the next higher resolution and the next lower resolution, so that the displayable area can be increased, while decreasing the area allocated to the operating system desktop by returning to it the received next lower resolution. Other combinations of the techniques previously described may also be used to effectively increase the displayable area while decreasing that allocated to the operating system desktop.

Alternative embodiments

1. Utilizing the VESA BIOS Extensions (VBE) in place of the CRT Controller registers (Fig. 5) to determine the linear window position address, step 138, as necessary.

2. Utilizing API's (application programming interfaces) 62 capable of direct driver and/or hardware manipulation, such as Microsoft's DirectX and/or DirectDraw, in place of the CRT Controller registers and/or direct access to the display buffer. 3. Utilizing API's (applications programming interfaces) 62, such as Microsoft's DirectX and/or DirectDraw, capable of direct driver and/or hardware manipulation, to create a second virtual display surface on the primary display with the same purpose, to display a separate and unobscured graphical user interface. 4. Utilizing modifications in the video subsystem of the operating system 63 in place of the CRT Controller registers and/or DirectX access to the display buffer.

5. Utilizing modifications in the video subsystem of the operating system 63 to create a second virtual display surface on the primary display with the same purpose, to display a separate and unobscured graphical user interface.

6. Building this functionality into the actual video drivers 64 and/or mini-drivers. Microsoft Windows provides support for virtual device drivers, VxDs, which could also directly interface with the hardware and drivers. These could also include an API to provide applications with an interface to the modified display.

7. Incorporating the same functionality, with or without the VGA registers, into the BIOS and providing an API to allow applications an interface to the modified display. Incorporating the same functionality into hardware devices, such as monitor itself, with hardware and/or software interfaces to the CPU.

This technique may be used to control the desktop (i.e., Windows) to easily enable the desktop to operate in virtually any non-standard size limited only by the capability of the display hardware. This may be in combination with parallel graphical user interface displays or exclusively to maximize the primary operating system desktop display area. This may not require any modification to the operating system.

In overview, the visual display area is conventionally defined by the values maintained in the CRTC registers on the chip and available to the driver. The normally displayed area is defined by VGA standards, and subsequently by SVGA standards, to be a preset number of modes, each mode including a particular display resolution which specifies the area of the display in which the desktop can be displayed.

The desktop can only be displayed in this area because Windows does not directly read/write the video memory, rather it uses programming interface calls to the video driver. And the video driver simply reads/writes using an address that happens to be in video memory. So the value this mechanism needs to realize is the value the video card and driver assert is available for painting. This value is queried from the registers, modified by specific amounts and rewritten to the card. Subsequently, the present invention changes the area of writable visible display space without informing the operating system's display interface of the change

This invention doesn't necessary change the CRTCs to add just to the bottom. Preferably the top is also moved up a little. This keeps the displayed interfaces centered within the drivable display area. For example, rather than just add thirty-two scan lines to the bottom, the top of the display area is moved up by sixteen lines.

Nor does this invention depend solely upon the ability to change the CRTCs to modify the visible display area. Alternative mechanisms define other methods of creating and accessing visible areas of the screen that are outside the dimensions of the desktop accessed by the operating system's display interface.

From a consideration of the specifications, drawings, and claims, other embodiments and variations of the invention will be apparent to one skilled in the art of computer science. In particular, the secondary GUI may be positioned in areas not normally considered the conventional overscan area. For example, the secondary GUI may be positioned in a small square exactly in the center of the normal display in order to provide a service required by the particular system and application. In fact, the techniques of reading and rewriting screen display information can be used within the scope of the invention to maintain the primary GUI information, or portions of it, in an additional memory and selectively on a timed, computed, interactive, or any or other basis, replace a portion of the primary GUI with the secondary GUI such as a pop-up, window, or any other display space.

As a simple example, a security system may require the ability to display information to a user without regard to the status of the computer system and/or require the user to make a selection, such as call for help by clicking on "911 ?". The present invention could provide a video display buffer in which a portion of the primary GUI interface was continuously recorded and displayed in a secondary GUI for example in the center of the screen. Under non-emergency conditions, the secondary GUI would then be effectively invisible in that the User would not notice anything except the primary GUI.

Under the appropriate emergency conditions, an alarm monitor could cause the secondary GUI to present the "911?" to the user by overwriting the copy of the primary display stored in the secondary GUI memory. Alternatively, a database of photographs may be stored and one recalled in response to an incoming phone call in which caller ID identified a phone number associated with a database photo entry.

In general, the present invention may provide one or more secondary user interfaces which may be useful whenever it is more convenient or desirable to control a portion of the total display, either outside the primary display in an unused area such as overscan or even in a portion of the primary GUI directly or by time division multiplexing, directly by communication with the video memory, or by bypassing at least a portion of the video memory to create a new video memory. In other words, the present invention may provide one or more secondary user interfaces outside of the control of the system, such as the operating system, which controls the primary GUI.

Additional user interfaces may be used for a variety of different purposes. For example, a secondary user interface may be used to provide simultaneous access to the Internet, full motion video, and a conference channel. A secondary user interface may be dedicated to a local network or multiple secondary user interfaces may provide simultaneous access and data for one or more networks to which a particular computer may be connected. Having now described the invention in accordance with the requirements of the patent statutes, those skilled in this art will understand how to make changes and modifications in the present invention to meet their specific requirements or conditions. Such changes and modifications may be made without departing from the scope and spirit of the invention as set forth in the following claims.

Overall Descriptions and Definitions

The following Spec introduces the function and design specifications of the MySides bar.

There are two types of relationships/partnerships with MySides.

- Third Party Content Providers, parties that include their content on the MySides bar, however, these parties do not distribute the bar.

- Distributors and Sub-Distributors, parties distributing Co-Branded MySides bars with their own content, in addition to the third party content providers' content.

β sV P.

CL,

L H _Ct.uonr _m^_{t βlk ιiΛΛk}^^ I f r.r r. fB

Buttons - Appearance/Action Key

1. Distributor/ Distributor^'s logo is displayed here, a left mouse click will activate a hyper link to Distributor's or Sub- Distributor's web Sub-Distributor Logo page

2. Preset Buttons Users can mark a spot on the bar by right-clicking on a white Preset Button, then return to that place by left -clicking on that button These become colored once a setting is saved

3. Category (noi aciive. isplay onw Displays the title of a major category (or Distributor or Sub-Distributor name), such as Entertainment, News and

Sports, etc.

4. Help / (?) When the user clicks on the Help button (?), it appears to depress and launches the pop up window (Welcome, Help, Map, About and Preferences tabs are accessed here)

5. Rotator When clicked, Rotators turn the portion of the bar to the right of the Rotator, left click turns upward, right click turns downward

6. Non-Action buttons Non-Λction buttons function only as title buttons or place holders They do not launch anything, don't highlight and cannot be depressed with a mouse down or keyboard command

7. Action buttons Most buttons are depressible and launch web pages They highlight and function as described under Button Highlighting (previous page)

8. Ticker Tickers display scrolling text and, when clicked on, can activate a hyperlink to launch an associated web page Text and hyperlink can be updated Content partners, Distributors and Sub-Distributors have the ability to update their own tickers. Users will receive the updated Ticker text and URL when they connect to the Web and click on any MySides Internet hyperlink

9. Exit / (X) When the user clicks on the Exit button (X), a window appears that confirms the user's choice to exit MySides

10. Pixel logo When the mouse cursor is over the Pixel brand and logo, the logo turns with an animation. The button, when clicked, links to www thepixelcompany com, or another Pixel Company website

Distributor Placement

Distributed directly by Distribution Partner (InfoSpace Example)

Uisliibiilor Content ''

ADDITIONAL PIXEL AND CONTENT-PARTNER CONTENT WILL BE INCLUDED

Category A could be Directories, for example.

Category B could be Entertainment.

Category C could be Finance, etc.

Categories (other than the Distributor or Sub-Distributor) are in alphabetical order.

For an example of a category breakdown, see page 7

,. Sub-Distributor Placement

ADDITIONAL PIXEL AND CONTENT-PARTNER CONTENT WILL BE INCLUDED

Category A could be Directories, for example.

Category B could be Entertainment.

Category C could be Finance, etc.

Categories (other than the Distributor or Sub-Distributor) are in alphabetical order.

For an example of a category breakdown, see page 7

Pixel Content Partner Placements Under Categories (Gold, silver, and Bronze)

Depending on their level of partnership (Gold. Silver or Bronze), content partners own a series of nineteen, eleven or five buttons within a given Platinum cartridge

Gold Placement: Gold level Content Partners receive a maximum ol 19 buttons including 3 tickets

t** Silver Placoment: Silver-level Content Partners receive a maximum of 1 1 buttons including two lickers

category

Bronze Placement: Bronze-level Content Partrfers receive a maximum ol 5 buttons

[ j| Category C g

Bronze-level partner under Category C (eg Finance) will be a Company with content relevant to that cate 2gBorΞy

Example of a Category with Multiple Content Partners

Summary of Pixel Conten and Third .Party Content included in generic version as of EFFECTIVE DA

MySides Functions

Startup Sequence: Once the user has downloaded installed and launched the program, the user is prompted by a dialog lo deride tiow they want the product to load The startup option default from the dialog is for automatic load during the Windows boot sequence While¹ the product software loads a text message is displayed in the horizontal blank area |ust blow the start bar informing the user that the program is "Adding Overscan Area to Display" or "Initializing MySides Display " (MySides startup does not interfere with the display of startup sequence of Windows )

At Start-up: Following the above text message, the bar appears, and the Distributor or Sub-Distributor cartridge is displayed, unless the user has set a different startup category under Preferences, a dialog box accessed through the "?" button The first time that MySides runs, the Welcome screen appears when the user moves the mouse cursor over the MySides bar Simultaneously, ttie MySides bar rotates quickly through all of its content, to show the bar rotation

Rotation Action: Rotators turn different elements of the bar On any Rotator, left click turns the bar upward, and right click turns the bar downward The portion of the bar to the right of the Rotator is turned

Button Actions: Action Buttons, when clicked, launch the associated function, including launching Tiles, documents, URLs, applications, etc Buttons with no action function as title areas only, have no associated hyperlink, and do not highlight (Distributor and Sub-Distributor buttons are limited to web page hyperlinks, unless otherwise agreed to )

Ticker (See description on following page )

Button Highlighting: Mouse over When the mouse cursor is over a MySides button, a lighting effect appears in the lower left corner of the button frame

Mouse down When the left mouse button is depressed, additional highlighting makes it appear that the MySides button is actually depressed

Mouse up: When the left mouse button is then released, the function is activated, and the MySides button appears to spring back, reverting to "mouse over" state descnbed above

Sound: A subtle mechatiical sound is generated with each action, lo enhance the MySides experience Sound will add to the "feel," not overshadow it

Pop-up Window: A Pop-up window will launch when the user clicks on the "7" button The Pop-up will have tabs such as Welcome, Help, About, Map, and Preferences

Screen Saver Mode: The MySides bar slowly rotates through all content when the computer is in Screen Saver mode Pop-up Help When the mouse cursor rests over a button for a moment, a pop-up window appears Pop-up Help may contain sub- level menus, descriptive text, etc

User Cartridge

Description: User buttons are found in the User Cartridge in MySides™ These are buttons the user can tailor to their needs by adding links to items of their choice by dragging and dropping (or copying and pasting) into the user button This provides a way for the user to manage and access their most frequently used applications, documents, files, and URLs

The user can rename the user button by right clicking on the button and selecting "rename" in a pop-up menu.

To clear a User button, right-click on the button, then left-click on "Delete" in the pop-up menu that appears, or select and highlight a User button and press the DEL key on your keyboard.

To rename a User button, right-click on that button, then left-click on "Rename" in the pop-up menu that appears Type the new name in the field that appears, then hit "Enter" on your keyboard or click on "Yes" with the mouse to keep the change - or select "No" with the mouse to cancel the change

Additional Notes

Upgrade Path and Merging Function

Our newest product under development is called "xSides". xSides is differentiated from MySides with its advanced functionality and it comes a la carte for users, one side at a time. This technology will allow users to add new features and merge xSides branded bars of their choice to their MySides bar via download from our partners' or an xSides web site (under construction). The user will have full discretion to download any number of sides, hence the name "xSides". This new metaphor will give some control and flexibility to the user to keep the application fresh, useful and personalized.

Logo and Branding Guidelines

T he MySides logo and branding is incorporated into the design of Co-Branded MySides and the MySides download button(s). The MySides and Pixel logo and branding signify that your company uses Pixel's patented MySides technology. They shall be used with your marketing materials, including brochures, presentations, advertisements The Pixel and MySides logo and branding must be used according to the guidelines included with the Deliverables provided to Distiibutor and Sub-Distributor by Pixel. Any deviation from these guidelines must be approved by Pixel.

Overall Descriptions and Definitions

The following document outlines the function and design specifications of a Pixel Company product technology named xSides xSides is based on a proprietary technology that opens up new screen real estate outside the operating system desktop

The xSide technology is available to partners in two versions

1 xSides - SDK Allows partner to build any function into the bar including applications, bookmarks, links, tickers, etc or their own technological function Partner can design (with or without The Pixel Company [TPCJ design help) their own look and feel

2 xSides - Basic Allows partner to modify functions of presently existing _w Pixel technology including launching, ticker messaging and help Partner can

>4 modify look and feel within defined parameters (outlined by I C). or can work o Ό directly with TPC to design new, partner specific design guidelines Function,

X size and number are restricted jj}^* Product is made up of a series of cartridges, or containers, that "hold" and display functionality The minimum number of containers is three one for partner content, one for help, frequently asked questions and web support, and one for "user buttons" that may be modified and manipulated by the user (see User Ca ndge - page x) Product is designed to be part of a wide selection of xSides products available to users through many distribution sources, therefore, the partner's specific xSides product will have the ability to exist with other such products in this space Upgrades and future products will be offered through a product / Pixel Company link within the "Help" cartridge or container

*

The "Array". This term describes the look and feel of the set of buttons, tickers, rotators, windows, etc , that presently make up the functionality of the MySide product (see the MySide product specification) Pattners will be able to modify their look and feel by adopting one of the "arrays" provided by TPC, or by designing their own In each case, the look and feel will be changeable by the user, that is, when a new xSides - Basic product is loaded, the user will have an option to adopt its look and feel to apply to the test of the MySides bars.

IMPORTANT Specifically designed xSides - SDK products may carry their own look and feel without affecting the look and feel of other xSides products This will carry a small overhead of having another design DLL loaded in memory

xSides - Basic Design & Feature Guidelines

This section contains design and feature parameters that apply to xSides-Basic products only.

(please see "Overall Functional Guidelines" section for parameters that extend to both xSides-Basic, and xSides-SDK products)

xSides- Basic

The "SDK" version of xSides provides Partners the option to change the look and feel of their application within the guidelines of Pixel

Company guidelines. There are a specific set of button "arrays" (see sample below) that the partner can adapt as their own The partner can also work with Pixel (time and resource permitting) to have a unique "array" built, on a for hire basis The following restrictions apply to xSides presentation and function

^• The size of the space will match the other "xSides" products This will enable users to "mix and match" cartridges, or content cylinders as they discover new xSides applications in Ihe maikelplace

^• Each xSides product will include two additional cartridges, a "User" cartridge and a I lelp/Support cartridge (See "User Bar" section and "Support" section)

^• The user will be able lo remove this application from Ihe computer screen by exiting and/or uninstalling Ihe program from their system, either as part of a larger group of xSides "caitπdges", or as a stand alone product

^• xSides- SDK products have a limited set of buttons and functionality that must be present and supported in every instance of Ihe product in addition to Partner defined/developed buttons/functionality (Please see "xSides - SDK' Buttons - Appearance/Action Requirements".)

xSjdes-_Basic: Buttons - Appearance/Action Requirements - page 1

1. Pixel logo When the mouse cursor is moved over the Pixel brand and logo, the logo animates and rotates The logo button, when clicked, links to a Pixel Company web destination

2. Preset Buttons Users can mark a spot on Ihe bar by right-clicking on a Preset Button, then return to that place by left-clicking on that button. These become colored once a setting is saved

3. Category moi acti e dismay onl ) Displays the title of major categories

4. Help / (?) When the user clicks on the Help button (?), it animates a depress and then launches a pop up window (Welcome, Help, Map, About and Preferences tabs are accessed here)

5. Rotator When clicked, Rotators turn the portion of the bar to the right of the Rotator; left click turns upward, right click turns downward

=» O

2. 5. 4.

xSides- Basic: Buttons - Appearance/Action Key - page 2

6. Non-Action buttons Non-Action buttons function only as title buttons or place holders They do not activate a launch or highlight and cannot be depressed with a mouse down or keyboard command

7. Action buttons Other buttons are depressible and launch web links They highlight and function as described under Button Highlighting (see "Functions" page)

8. Ticker Tickers display scrolling text and, when clicked on, can activate a hyperlink to launch an associated web page Text and hyperlink can be updated as defined in each partner's contract

9. Exit / (X) When the user clicks on the Exit button (X), a window appears that confirms the user's choice to exit xSides

10. Partner Logo Partner's logo is displayed here A left mouse click activates link to partner web page

"xSides Basic" - Functions

Startup Sequence: Once the user has downloaded, installed and launched the program, the user is prompted by a dialog to decide how they want the product to load T he startup option default from the dialog is for automatic load during the Windows boot sequence While the product software loads a text message is displayed in the horizontal blank area just blow Ihe start bar informing Ihe user that Ihe program is "Adding Overscan Area to Display" or "Initializing xSides Display " (xSides startup does not interfere with the display of startup sequence of Windows )

At Start-up: Following the above text message, Ihe bar appears, and Ihe Distributor or Sub-Distributor cartridge is displayed, unless the user has set a different startup categoiy under Preferences, a dialog box accessed thiough the '"•^>" button The first time xSides runs, the Welcome screen appeals when the user moves the mouse cursor over the xSides bar Simultaneously, the xSides bar rotates quickly through its content, to show bar rotation

Rotation Action: Rotators turn different elements of the bar On any Rotator, left click turns the bar upward to the next bar, and right click turns the bar downward to the previous bar he portion of the bar to the right of the Rotator is turned

Button Actions: Action Buttons, when clicked, launch the associated function, including launching files, documents, URLs, applications, etc Buttons with no action function as title areas only, have no associated hyperlink, and do not highlight

Ticker Tickers display scrolling text and, when clicked on, can activate a hyperlink to launch an associated web page in Text and hyperlink can be updated Partners have the ability to update their own lickers Users will receive the updated Ticker text and URL when they connect to the Web and xSidesis running

Button Highlighting: Mouse over At "mouse over ", a lighting effect appears in the lower left corner of the button frame Mouse down When the left mouse button is depressed, highlighting shows xSides button is actually depressed Mouse up: When the left mouse is released, the function is activated, and the xSides button appears to spring back, reverting to "mouse over" state described above

Sound: A subtle mechanical sound is generated with each action, to enhance the xSides experience Pop-up Window: A Pop-up window will launch when the user clicks on the "?" button The Pop-up will have tabs such as Welcome, Help, About, Map, and Preferences

Screen Saver Mode: The xSides bar slowly rotates through all content when the computer is in Screen Saver mode Pop-up Help When the mouse cursor rests over a button for a moment, a pop-up window appears Pop up Help may contain sub- level menus, descriptive text, etc

xSides - SDK Design & Feature Guidelines

This section contains design and feature parameters that apply to xSides-SDK products only.

(please see Overall Functional Guidelines" seclion for parameters that extend to both xSides -Basic, and xSides SDK products)

Ihe "SDK" version of xSides will allow partners to modify Ihe function of the xSides technology Fach partner works with The Pixel Company to embed application functions directly into the space, with, or without use of calls to the operating system This function will display anywhere within the space, as defined by the partner The following restrictions apply to xSides presentation and function f e size of the space will match Ihe other "xSides^" products T is will enable users to "mix and match" cartridges, or content cylinders as they discover new xSides applications in Ihe marketplace

Fach xSides product will include two additional cartridges, a "User" cartridge and a Help/Support cartridge (See ^"User Bar" section and "Support" section)

The user will be able to remove this applicalion from Ihe computer screen by exiling and/or unmstalling re program from their system, either as part of a larger group of xSides "cartridges", or as a stand alone product xSides- Sf)K products have a limiled set of buttons and functionality thai must be present and supported in every instance of Ihe product in addition to Partner defined/developed buttons/functionality (Please see "xSides - SDK Buttons - Appearance/Action Requirements" )

Pixel will provide graphic design, HTML, and product architecture resources lo suppoit partner efforts to create applications in the xSides domain Pixel web server space is also available to house content, support, upgrade and partner company information

xSides-_SDK Buttons - Appearance/Action Requirements

Partner developed xSides - SDK products must carry the following button appearance and actions.

1. Pixel logo When the mouse cursor is over the Pixel brand and logo, Ihe logo animates and rotates The logo button, when clicked, links lo a Pixel Company web site Size of Pixel Logo buttons are pre-defined (outlined in the deliverables)

2. Partner logo Partner's logo is displayed heie, a left mouse click will activate a link lo a web destination of Ihe partners choice Size of Pixel Logo buttons are pre-defined

3. "Array" of buttons/and / Partner's own buttons will be displayed within this area T he buttons and tickers, rotators are restricted in height as shown below Partner button lengths can be varied within the xSides' two endcap locations in the partner cartridge

4. User and Support Size of User and Support buttons are pre defined, as outlined in the User Cartridge section buttons:

Example graphic loυk

xSides Overall Functional Guidelines

This section contains parameters extending to both xSides -Basic, and xSides SDK products.

Color / Button Style System

The following guidelines describe where look and feel of xSides products may be modified

1 xSides - Basic. Partners have the option lo change the look and feel of their application within the guidelines of Pixel Company guidelines There are a specific set of button "arrays" (see sample below) that the partner can adapt as their own The partner can also work with Pixel (time and resource permitting) to have a unique "array" built, on a for hire basis

As "Arrays" are loaded into the bar area with new products, the new graphic array is applied to all installed user xSides and xSides basic products All of the cartridges on all the bars will match the look and feel of the latest Array" until the user loads another product with another "Array", or until the user switches the look and feel using "Preferences" controls

o

2 xSides - SDK Each xSides SDK product can carries it's own function DLL and/or resource DLL, and as a result, can have 6 unique look, feel, and, in some cases, specific button structure and presentation to match specific application delivery All xSides SDK products can load separately and act independently.

"xSides Basic andLSDK^ -JJser Cartridge

Description: User buttons are found in the User Cartridge in xSides In these cartridges the User can tailor buttons lo suit their needs by adding links to items of their choice xSides products comes with seven default User cartiidges

Buttons can be added to User Cartridges in a number of ways With xSides Users may add links by dragging and dropping (or copying and pasting) into Ihe user button xSides has the additional ability to add links to the User area hy clicking on xSides link icons on partner web sites T his provides a way for the user to manage and access their most frequently used applications, documents, files, and URLs

Additional bonus User bars are added to the User Cartridge when a User clicks on a partner web site xSides link icon The new User bar is added, titled with the partner's name, containing the link that was just selected The bonus User bars have the added feature of being able lo be deleted from the User Cartridge

T he user can rename the user button by right clicking on the button and selecting "rename" in a pop-up menu

To clear a User button, right-click on the button, then left click on "Delete" in the pop-up menu that appears, or select and highlight a User button and press the DEL key on your keyboard tπ Example User bar and addition or Bonus bar:

Graphics shown heie are representational of how a user-click on an xSides link icon from a partner site adds a bonus User bar to the xSides product

"xSides Basic and SDK" - Upgrade and Support

Description: Each xSides product has a'cartπdge specifically designated for support and upgrade use. Using these cartridges the user can access links lo frequently asked questions, upgrade pages where other xSides products can be found, and can receive news and information about xSides products

The bar has one side containing combination of button links and tickers

WLZ jmk laSi l m

"xSides" Product Specification - Additional Notes

Upgrade Path and Merging Function

The xSides upgrade/merge functionality provides some control and flexibility to the user, keeping the application fresh, useful and personalized, one side at a time. xSides technology is designed to be delivered a la carte to users, with the advanced ability to allow users to add new product features and merge any xSides branded bars they choose to any other previously installed xSides product(s) Users will be able lo upgrade and merge their xSides products via download from our partners' or an xSides web site (under construction). The user will have full discretion to download any number of sides, hence the name "xSides".

Logo and Branding Guidelines

The xSides logo and branding is incorporated into the design of the product and the product's download button(s). The xSides/Pixel logo and branding signify that your company uses Pixel's patented Sides technology. They can be used to enhance your marketing materials, including brochures, presentations and advertisements. The Pixel and xSides logo and branding must be used according to the guidelines outlined in the deliverables. Any deviation from these guidelines must be approved by Pixel.

Claims

1. A method in a computer system for displaying a user interface on a video display system in an area outside of a display area controlled by and occupied by an operating system user interface, comprising: modifying the size of the display area allocated to the operating system user interface in a manner that is transparent to the operating system user interface, thereby modifying the size of the area outside of the display area; and displaying the user interface that is not under the control of the operating system in the area outside of the display area.

2. The method of claim 1 wherein the modifying of the size of the display area decreases the amount of display area allocated to the operating system user interface, thereby increasing the size of the area outside of the display area.

3. The method of claim 1 wherein the modifying of the size of the display area increases the amount of display area allocated to the operating system user interface.

4. The method of claim 1 wherein the size of the area outside of the display area is larger than the size of the display area controlled by the operating system user interface.

5. The method of claim 1 wherein the modifying of the size of the display area further comprises: communicating with the video display system to increase the total number of pixels available for display in a manner transparent to the operating system; and modifying the size of the display area allocated to the operating system user interface so that the operating system user interface occupies a smaller area than that occupied prior to the modification.

6. The method of claim 5, the video display system enabling display of images to a current resolution, wherein the communicating with the video display system and modifying the display area allocated to the operating system user interface further comprises: requesting and receiving from the video display system a higher resolution than the current resolution; requesting and receiving from the video display system a lower resolution than the current resolution; returning to the operating system the received lower resolution; and utilizing the difference between the received higher and lower resolutions to increase the size of the area outside of the display area.

7. The method of claim 1 further comprising increasing the total number of pixels available for display, in a manner transparent to the operating system, by adjusting the parameters of the video display system to include pixels previously not addressable.

8. The method of claim 7 further comprising increasing the size of the area outside of the display area.

9. A computer system comprising: a video display system having a display area that is controlled and occupied by an operating system user interface and having a secondary display area that is located outside of the display area controlled by the operating system user interface; an image that is not produced by and that is not controlled by the operating system user interface; and a display controller that communicates with the video display system to modify the size of the display area in a manner that is transparent to the operating system user interface; and causes the video display system to display the image in the secondary display area.

10. The system of claim 9 wherein the display controller further communicates with the video display system to increase the total number of pixels available for display and allocates a portion of the increased total number of pixels to the secondary display area to increase the size of the secondary display area.

11. The system of claim 10 wherein the display controller decreases the size of the display area controlled and occupied by the operating system user interface thereby further increasing the size of the secondary display area.

12. The system of claim 10 wherein the display controller increases the size of the display area controlled and occupied by the operating system user interface.

13. The system of claim 9 wherein the display controller decreases the size of the display area controlled and occupied by the operating system user interface thereby increasing the size of the secondary display area.

14. The system of claim 9 wherein the display controller increases the size of the display area controlled and occupied by the operating system user interface.

15. The system of claim 9, the video display system having a current resolution and a resolution modification subsystem, wherein the display controller utilizes the resolution modification subsystem to receive from the video display system an indication of a higher resolution than the current resolution and an indication of a lower resolution than the current resolution; and causes the operating system user interface to operate within the size indicated by the received indication of the lower resolution.

16. The system of claim 15 wherein the display controller further increases the size of the secondary display area by the difference between the size of the received indication of the higher resolution and the size of the received indication of the lower resolution.

17. A computer-readable medium containing instructions for controlling a computer system to display an image on a video display system in a secondary display area outside of a display area controlled by an operating system user interface, by performing: modifying the size of the display area controlled by the operating system user interface, thereby modifying the size of the secondary area; and displaying the image, the image not generated by or controlled by the operating system, in the secondary display area.

18. The computer-readable medium of claim 17 wherein the instructions control the computer system to increase the total number of pixels available for display and to allocate a portion of the increased total number of pixels to the secondary display area to increase the size of the secondary display area.

19. The computer-readable medium of claim 18 wherein the instructions control the computer system to decrease the size of the display area controlled by the operating system user interface.

20. The computer-readable medium of claim 18 wherein the instructions control the computer system to increase the size of the display area controlled by the operating system user interface.

21. The computer-readable medium of claim 17 wherein the instructions control the computer system to decrease the size of the display area controlled by the operating system user interface.

22. The computer-readable medium of claim 17 wherein the instructions control the computer system to increase the size of the display area controlled by the operating system user interface.

23. The computer- readable medium of claim 17 wherein the instructions control the computer system to retrieve from the video display system an indication of a next higher resolution and an indication of a next lower resolution; and cause the operating system user interface to function within the size indicated by the retrieved indication of the next lower resolution.

24. The computer-readable medium of claim 23 wherein the instructions control the computer system to increase the size of the secondary display area by the difference between the sizes indicated by the retrieved indications of the next higher resolution and the next lower resolution.