Browse Prior Art Database

Setup Program Configuration Interface for Personal Computers

IP.com Disclosure Number: IPCOM000116492D
Original Publication Date: 1995-Sep-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 6 page(s) / 239K

Publishing Venue

IBM

Related People

Trinh, HC: AUTHOR [+3]

Abstract

Described is a software implementation providing a specific configurational interface to the setup program of a personal computer, eliminating a need to write separate setup programs for different personal computer configurations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Setup Program Configuration Interface for Personal Computers

      Described is a software implementation providing a specific
configurational interface to the setup program of a personal
computer, eliminating a need to write separate setup programs for
different personal computer configurations.

      In this implementation, a setup user interface, called a User
Access Component (UAC), provides a configuration program function,
isolated from the access characteristics of the computer system.  The
UAC is a replaceable entity, providing support for input and output
devices without dictating the graphic functions of display devices by
setting, for example, pixel drawing markers or text fonts,.  Thus, a
user may implement his own design, as long as a defined call
interface is maintained.  Functions of the UAC open and close the
standard presentation environment of the system, facilitating the
display of messages, and providing for the user to enter numbers and
strings, and to make single or multiple selections through dialog box
controls.

      In system operation, the UAC is loaded by the set configuration
program during its initialization sequence.  If the UAC is not found,
the user is prompted to insert the appropriate reference diskette
into a drive.  If the UAC is still not found, the set configuration
program is terminated as an error code and message is displayed using
standard interrupt function calls.  If the UAC is found, the
parameter block, containing a pointer to the data structure used by
the UAC, is passed onto the stack.

      Fig. 1 is a block diagram of the user access interface calling
structure.  The UAC maintains the integrity of the calling component
during its execution by preserving the contents of various registers
as well as the stack and stack pointers.  Table 1 shows the various
Function Codes in the structure of Fig. 1, which are used to
implement the function calls of the UAC.

      As the binding mechanism between the calling component and the
UAC, the UserInit function call establishes a unique connection,
identified by the Connection ID (CID), between the two components.
Table 2 shows the Parameter Block Format of this function call.  This
function must be called before any other functions can be processed.
When the UAC is...