Solaris Caiman Text-based Installer UI Specification
Frank Ludolph
Modifed Jun 17, 2010 by Sue Sohn for PSARC/2010/165

Contents:

Introduction
Target Users
UI Design
Screens
  Navigation
  Welcome
  Disks
  Fdisk Partitions
  Select Partition
  Solaris Sliced
  Select Slice
  Network
  Manual Network Configuration
  Manually Configure: NIC
  Time Zone
  Date and Time
  Users
  Summary
  Install Progress
  Installation Complete
  Installation Failed
  Installation Log
  Help Topics
  Screen Help

Change List

Introduction

The Solaris text-based an OpenSolaris project. It is a mouseless, screen-oriented installer designed for use on SPARC and x86 systems that may not have graphic support such as many server-class machines. This user interface specification builds on the Caiman Slim GUI-based installer UI specification. As such this specification focuses on elements that are different from or extension to similar screens in the Slim installer.

Target Users

The target users for the text-based installer are individuals that want to install OpenSolaris on a few servers and SPARC systems in particular. While the Automated Installer can used to do this, it requires setting up an installation service on a local machine. While this provides good support for larger installations, it can be cumbersome for small shops and individuals wishing to try out OpenSolaris.

UI Design

The text-based installer has a screen-based, wizard-style application that utilizes the nCursos SDK. This particular design uses arrow keys for naviagation with a screen and F<n> keys for screen-to-screen navigation and the occasional screen specific command. For situations where F keys will not function, the user may use ESC-<n> key sequences.

Navigation within the Installer.

All screens, with a couple of exceptions, contain F keys for Next, Back, Help, and Quit. They function as follows:

• Quit: Displays a confirmation dialog with the message "Do you want to quit the OpenSolaris Installer?", and if confirmed, quits the installer and returns to the caller, either the installer media's "short menu" or a command line prompt if started from there. An additional message is added to the dialog when quiting from the installing progress screen, "The disk has been changed by the installer and will be left "as is." The confirmation dialog is not posted when the "last" installer screen is displayed. The terminal window allows the user to restart the installer or to perform other commands.

• Help: Replaces the current screen with content specific to the current screen. From here the user can go Back to the current installer screen or press F6 to display a list of help topics.

• Back: Returns the user to the previous installer screen. The previous screen should display the same content as when the user last saw the screen.

• Next: First performs any screen specific content checks; error conditions should be checked before warning conditions, from most serious to least serious. The next screen is displayed when there are no errors or the user proceeds in spite of any warnings. If the next screen has been previously seen by the user, its content should be the same as when previously viewed.

Warnings

1. User does Quit: "Do you want to quit installation of OpenSolaris?"

2. User does Quit on the Progress screen: "Installation is incomplete and not functional. The original data has been destroyed. Do you want to quit installation of OpenSolaris?"

Installer Commands

The commands available on each screen are listed at the bottom of the screen. The are invoked using F-keys. In the event that F-keys are not functional in the terminal environment the user can use an escape key sequence the replaces F# with ESC#.

When the ESC key is pressed the F-key commands at the bottom of the screen are replaced with the corresponding ESC key commands. The next number key will be interpreted as a command. The use of ESC is a one-time use since numbers are also used to edit field values on some screens. After the ESC command is entered, the F-key commands are redisplayed at the bottom of the screen. If the ESC key is pressed in error, pressing it a second time will redisplay the F-key commands at the bottom of the screen.

Installer Language

The installer runs in the language set by the user during boot..

Keyboard

The installer runs in the language set for the desktop during boot.

Welcome

The Wecome screen informs the user of the software to be installed, provides access to relevant documentation.

Defaults

1. None

Behaviors

1. None

Errors

1. There are no error conditions

Disks

The Disk screen lists all attached storage devices that could potential serve as installation targets. The user moves the selection to the desired disk and types F2.

If there are more that four disks, the disk list will need to scroll within its own four text lines. The partition table should not be pushed off the bottom of the content area.

In the mockup, only the top two disks have subsequent screens. The other disk entries do not have an implementation.

Partition/Slice Display Layout

All of the disk related screen have a table of partitions(slices). The organization of the partitions is the same on all screens as follows:

• Fdisk partitions

  • The primary partitions are listed on the left, the logical partitions, if any, on the right.

  • The logical partition column headings are always displayed even an Extended partition is not currently defined.

  • The partitions are listed in disk layout order on their respective sides (primary/logical).

  • The type of each partition is listed, e.g. Solaris, Extended, etc. If a partition is defined but its type is unknown, it is shown as "Unknown".

  • The primary side always has four entries. If less than four primary partitions are defined, "Unused" entries are added as necessary.

  • The primary Unused partition entries should be positioned in the list to represent the largest chunks of free space. If there not enough free chunks the additional Unused entries are placed at the bottom. If there are multiple sequential Unused entries the first has the size of the chunk, the rest zero.

  • If an Extended partition is not defined, "(No Extended partition defined)" is displayed under the Logical column headings.

  • There may be 0-32 logical partitions. If an Extended partition is defined, there is always at least one Unused partition listed on the Logical side of the table.

  • The number of logical entries is variable, one for each defined logical partition plus one Unused entry for each chunk of free space, up to a maximum of 32 entries.

• VTOC slices

  • A VTOC can have either 8 or 10 slices. This are displayed in two columns.

  • The slices are displayed in disk layout order, left column first, then right column.

  • The type of each slice is listed, e.g. Solaris, Extended, etc. If a partition is defined but its type is unknown, it is shown as "Unknown".

  • Slice 2 is traditionally an "all disk" slice that does not define a reserved part of the disk. If it is defined, it is diskplayed as (Backup) at the bottom of the right column.

  • Unused entries should be positioned in the list to represent the largest chunks of free space. If there not enough free chunks the additional Unused entries are placed at the bottom. If there are multiple sequential Unused entries the first has the size of the chunk, the rest zero.

Defaults

1. The minimum and recommended installation sizes are shown above the list of disks.

2. If the system's default boot disk can be determined, it should be listed first.

3. The first device in the installation target list should be selected.

4. If a disk is smaller than the minimimum installation size, the device's Notes field should display "Too Small"

5. If a disk is too large, the device's Notes field should display "Limited to x TB" where "x" is the maximum usable space.

6. If a disk does not have a recognizable fdisk partition table or VTOC appropriate to the machine type, fdisk for x86, VTOC for SPARC, create a proposed partitioning with a single partition/slice that fills the entire disk. In the case of SPARC/VTOC also create a (Backup) slice in the last slot (right column, bottom) sized to the full disk. See the last disk in the table (SATA 4000GB).

Behaviors

1. If there are more installation targets than can be displayed (while leaving room for the partition table below) the target device list should scroll.

2. When the user selects a target, the target's current partitioning is displayed in the partition table. ("Partition" refers to either Fdisk partitions or VTOC slices)

3. If the selected device does not have a recognizable fdisk/VTOC partition table, a proposed partiontion table is displayed with the entire space allocated to a single partition.

4. Fdisk: The number of logical partitions may exceed the available rows. If so the logical partitions should scroll, preferably without affecting the rest of the screen display.

5. Unsuitable disks should not be selectable, i.e., pressing an up/down arrow key to move the selection will skip over unsuitable disks. Unsuitable disks are those that are too small.

Errors

1. When the screen is displayed, if there are no disks found, display the error message "No disks found."

2. When the screen is displayed, if no disks are suitable, do not show a disk selection and display the error message "OpenSolaris cannot be installed on any disk."

Fdisk Partitions

The Fdisk Partitions screen displays that disk's partitioning (identical to that displayed on the prior Disks screen) and asks the user when the the entire disk should be used for installation or a partition of the disk.

Defaults

1. "Use a partition of the disk" is selected by default. While it is desirable to use the whole disk, a whole disk default is more dangerous in that a user might not realize what is happening and destroy an entire disks content.

2. The disk's partition table is shown identically to the Disks screen.

3. The screen title includes the disk size, type, and "Boot" if it is the default boot disk.

Behaviors

1. The uop/down arrow keys select the desired action.

Errors

1. There are no error conditions

Select Partition

The Select Partition screen enables the user to create and size a Solaris partition which will be used for installation. The screen enables the user to make some additional adjustmests to the fdisk partition layout such as the deletion of existing partitions, the creation of an Extended partition and logical partitions within it, and the creation and sizing of other types of partitions supported by OpenSolaris. The content of existing partitions is automatically preserved except for those whose size and/or type are adjusted. Note that if an Extended partition's size is increased, its logical partitions are preserved if they are not otherwise adjusted.

The partition types and sizes are displayed as on the previous screens except that an Avail space column is added. The Avail space for a partition is the sum of its own space plus all adjacent free space before and after the partition. See below for more details.

Defaults

1. If there is a Solaris partition it is selected, otherwise the top primary partition is selected.

2. If there are too many logical partitions to be displayed, display as many as will fit down to the error message line. Display a ↓ two spaces to the left of the bottom-most line.

3. The partition table is displayed as in the previous screens with the addition of Avail columns for the primary and logical lists. The Avail column displays the amount of adjacent free space, both before and after the partition including adjacent Unused partitions, plus the space currently allocated to the partition. It represents the maximum potential size for that partition with destroying other partitions.

Limitations

1. Partitions cannot be moved.

Behaviors

1. Each user keystroke will result in a valid set of partition definitions. The only exception is that a Solaris partition may not exist.

2. Moving the selection:

   1. Up/down arrow navigation/selection wraps around, that is the next "down" from the bottom primary partition is the top logical partition and the next "down" from the bottom of the logical partition the the top primary partition. Likewise for up arrow but reversed..

   2. If there are too many logical partitions to be displayed, the up/down arrows cause the displayed list of logical partitions to scroll when the selection reachs the visible end of the list. Display a ↓ two spaces to the left of the bottom-most line and/or a ↑ to the left of the top-most line when there are more entries in that direction. Remove the ↑/↓ when the top/bottom entry is displayed.

3. Creating/deleting primary partitions:

   1. F5 cycles the selected partition (slot) though the possible types in order: Solaris, Unused, Extended, and other supported types. It is possible to cycle back to an original, unsupported type only if the user has not performed an operation other than F5 since the origianl unsupported type was displayed.

   2. The F5 cycle excludes Solaris and/or Extended if there is already another Solaris and/or Extended partition defined, that is, there can never be two Solaris partitions or two Extended partitions at the same time.

   3. Changing a partition's type to any other than the its initial type will destroy its content and cause its destroyed marker, "*", to be set. Cycling the type back to the initial type removes the destroyed marker provided it has its initial size.

   4. Setting a partition type to Unused deletes the initial partition and makes its space available to the nearest adjacent non-Unused partition on each side.

      1. Its Avail size is set to the amount of free space between the nearest adjacent non-Unsed partitions on each side.

      2. The size is set to zero.

      3. If there are adjacent Unused partitions, they will all show the same Avail size.

      4. If the user continues to F5 without performing another operation, the next F5 will display another type and the size will be returned to the partition size as the start of the F5 sequence.

4. Editing a partition's size:

   1. The size of a partition is highlighted with yellow if the size can be edited, otherwise it has the same highlight color as the partition type, blue.

   2. A partition can be resized if the installer can create partitions of that type: Solaris, Extended, other supported partition types, except the size of Unused partitions cannot be edited.

   3. Changing a partition's size will destroy its content and cause its destroyed marker, "*", to be set. If the size is changed back to the initial size, and the type is the initial type, the destroyed marker is removed.

   4. The size field is validated with each keystroke so that it is always valid. Keystrokes that would cause the field to invalid are ignored and an appropriate error is posted in the message area as defined in Errors below.

   5. Editing the size of a partition causes the Avail space of adjacent of adjacent Unused partitions, and the non-Unused partition beyond the Unused partitions, to adjusted by an inverse amount. This update is done on each keystroke.

   6. Decreasing a partition's size removes space from the end. Increasing a partition first adds free space to the end until exhausted, then adds free space to the front.

   7. A partition's size cannot be increased more than the Avail size. This prevents the inadvertant destruction of adjacent partitions.

5. Extended and Logical Partitions:

   1. Creating an Extended partition creates an Unused logical partition of the same size as the Extended partition.

   2. The size of an Extended partition cannot be changed if it currently contains defined logical partitions. The logical partitions must be deleted (changed to "Unused") before the Extended partition's size can be edited.

   3. Unused partition entries are created as needed to represent blocks of available freespace. They are usually created when the size of a defined partition is reduced. In a similar manner, if the size of a defined partition is increased, the increase may use all of a block of freespace, in which case the corresponding Unused logical partition should be removed.

   4. Deleting an existing Extended partition "disables" the logical partitions and marks them to be destroyed. They are not removed from the display since there would be no way of informing the user that the existing logical partitions are being destroyed. Cycling the initial Extended partition that was destroyed back to "Extended" re-enables its logical partitions.

   5. If the user destroys an existing Extended partition and creates another, the logical partition list will consist of both pre-existing destroyed partitions (at the top) and newly created Unused partition (and others the user may subsequently create) in the new Extended partition. 

Errors

1. On keystroke when editing a partition's size: (the offending keystoke is discarded so that the size field remains valid)

   1. An invalid charater is entered: 'Only the digits 0-9 and "." are valid.'

   2. The size is greater than Avail: "The new size is greater than the available space."

   3. A second decimal point it typed: 'A number can only have one "."'

   4. More than one decimal place: "Size can be specified to only one decimal place."

2. F2 errors are displayed in the error message area. The error is removed when the user enters the next keystroke, such as up arrow, down arrow, F<key>, etc.

   1. There must one Solaris partition: "There must be one Solaris partition."

   2. The Solaris partition must be greater than the minimum size: "The Solaris partition size must be at least xGB"

Solaris (Partition) Slices

This screen lists the VTOC slices and asks the user if the installation is to be in one of the slices or use the whole disk.

There are two versions of this screen, one for SPARC systems where the VTOC covers the whole disk, and one for x86 systems where the VTOC exists within an Fdisk partition. In the x86 case, this screen is displayed only if there was an existing Solaris partition and it has not been altered, such as the user has resized the partition which would destroy the existing VTOC and the content of its slices.

The table listing the slices is laid out in two columns with half of the slice slots in the left column and half on the right. Depending on the type of VTOC, there may be eight or ten slices. "Unused" slices are used to represent chunks of free disk space in exactly the same way as Unused fdisk partitions are used on an x86 disk.

All slice slots are shown whether or not they contain a slice definition. The slices are ordered in disk layout order, top to bottom, left column first then right column. If the VTOC contains an "all disk" (Backup) slice, typically S2, it is listed at the bottom of the right column with the type "(Backup)" and the size set to the full size of the disk/fdisk partition that contains the VTOC.

Defaults

1. The action selection should be set to "Use a slice...". The wording of this action varies slightly on the two versions of this screen.

Behaviors

1. The user selects "Use a slice..." or "Use the whole..." with the up/down arrows. (Standard navigational operation.)

Errors

1. There are no error conditions

Select Slice

OpenSolaris will be installed into the slice that contains the "ZFS root pool". There should be only one of these. Note that the mockup screen for function is not operable. It is very similar to the operation of the Select Partition screen.

An Avail space column is added to the slice table. It is handled exactly the the Avail space column in the x86 fdisk partition table.

A slice number column, "#" is added to the slice table primarily to inform the user of the existing slice layout. Since the slices are layed out in the table in disk order, the slices numbers may not be sequential. The user has no control over the slice number associated with any entry.

Functionality

1. A slice's content can be changed to "ZFS root pool", which will delete its current content, or it can be deleted entirely to free up the space.

2. Slice content will be preserved if the slice is not explicitly altered by the user.

Limitations

1. There can be only one "ZFS root pool".

2. Only a "ZFS root pool" can be resized.

3. The user has no control over the slice numbers.

Defaults

1. The "ZFS root pool" is selected by default if one exists, otherwise the first slice is selected.

Behaviors

1. The (Backup) slice, if defined, is not selectable or modifieable.

2. F5 cycles a slice through the following: ZFS root pool, Unused, the initial slice content. The ZFS root pool choice is not displayed it another one exists. An uninterrupted sequence of F5 operations behaves as on Select Partition.

3. Resizing behavior is the same as fdisk partition behavior.

4. Avail space behavior is the same as for primary fdisk partitions.

Errors

1. On keystroke when resizing a slice: identical to the errors for fdisk partition resizing.

2. F2 errors are identical to fdisk partition editing with slightly revised text as appropriate.

   1. There must one ZFS root pool: "There must be one ZFS root pool.."

   2. The ZFS root pool must be greater than the minimum size: "The ZFS root pool size must be at least xGB."

Network

This screen asks the user for a computer hostname and how they would like the network connection to be configured.

Defaults

1. The selection is set to the hostname field.

Behaviors

1. If no wired NICs are detected, replace the "configuration" section with the message "No wired network connections were detected."

2. The manual choice goes to the Manual Network Configuration screen. The other choices skip the manual config screen.

3. If a static IP address is defined it is active and any other NIC configured to DHCP are set inactive (to prevent accidental network bridging).

4. If the user chooses "Automatically" then NWAM is enabled.

5. If the user chooses "None" then Network Physical is enabled.

6. If the user chooses "Manual", wireless connections are set to DHCP(inactive). The user will select the wired NIC to be configured on the next screen.

Errors

1. On editing the hostname:

   1. If an invalid character is input, discard the character and post the error "The Hostname can only contain letter, numbers, and minus signs (-)."

2. On F2:

   1. Blank hostname: "A Hostname is required."

   2. Configuration method not selected: Select how the wired network is to be configured: Automatically, Manually, or None."

Manual Network configuration

This screen is used to select the wired NIC to be configured. Display the screen only if the user chose to manually set the machine's network settings on the preceeding Network screen and if there is more than one wired NIC that can be configured.

Defaults

1. The top-most NIC is selected.

Behaviors

1. The up/down arrows will not move outside the NIC list. If there are more than fifeteen NICs they will scroll. Scrolling is indicated by a psuedo scroll bar as shown on the Time Zone Locations mockup screen.

Errors

1. None

Manually Configure: NIC

Display this screen if the user has chosen to manually set the machine's network settings on the Network screen. The screen title indicates the NIC the user has selected to configure on the prior Manual Network Configuration screen.

The mockup screen is only partially implemented.

Defaults

1. The static IP address is blank.

2. The netmask is set to 255.255.255.0

3. The router/gateway address is dynamically set if it can be automatically determined, otherwise it is blank. If an address is found the comment field tells the user it was found, else the comment is "The IP address of the gateway on this subnet."

4. The DNS IP address is dynamically set if it can be automatically determined, otherwise it is blank. If an address is found the comment "A DNS server was found on the network" is displayed to the right of the field.

5. The Domain name is dynamically set if it can be automatically determined, otherwise it is blank. If an address is found the comment "The machine appears to be in this domain" is displayed to the right of the field.

Behaviors

1. The up/down-arrows move the selection and edit highlights across the five fields.

2. The gateway, DNS, and Domain name fields can be empty.

Errors

1. On F2:

   1. If an IP field is invalid: [Field] must be of the form xxx.xxx.xxx.xxx

   2. The IP Address field cannot be empty.

   3. The Netmask field cannot be empty.

Time Zone

Three screens are used to set the time zone: region, location, and time zone.

Defaults

1. The time zone region, location, and time zone selections should be defaulted from the computer's internals settings or the network if either are available, otherwise the top item on each screens list should be selected by default. If this is not available, the Region default should be "UTC/GMT".

Behaviors

1. The selection on a screen alters the content on the subsequent screens, i.e. each region has a unique list of locations and each location has a unique list of time zones.

2. The user selects a list item using the up/down arrow keys.

3. If "UTC/GMT" is selected on the Region screen, on F2, skip the Location and Time Zone screens.

Errors

1. None

Date and Time

This screen enables the user to configure the computer's internal clock.

Defaults

1. The date and time should be defaulted from either the computer's current clock values or, if not available, from the network if possible. If there is no valid time available, set the clock to 2009, 1, 1, 00, 00 (Midnight, Jan. 1st, 2009).

2. The top-most field, Year, should be selected.

Behavior

1. Keystrokes are validated as entered. Invalid characters are ignored and an error message is posted in the error message area.

2. Leading zeros are allowed all but the year field, but they are removed when field string exceeds two digits.

3. Field values are range checked when they lose focus. If an error is noted it is displayed to the right of the field.

4. When the month is changed and the focus leaves the month field, update the Day field's range.

5. When a field is edited, i.e. the user deletes, adds, or replaces a character in the field, the field's and screen error messages, if any, are immediately hidden.

Errors

1. When the focus moves out of a field, range check its value and if out of range display "The value is out of range." to the right of the range.

2. When the Day range comment is changed, if the current day value is out of range, display "The value is out of range." to the right of the range.

3. When the user types F2, if any field errors exist the screen error is set to: "Invalid date/time. See errors above."

Users

The Users screen enables the user to set the root password and to create a user account that will be available at login.

Defaults

1. The top-most field, "Root password" is selected by default.

Behaviors

1. The user is not required to create a root password.

2. The user is not required to create a user account. A user account requires only a Login name and password to be valid.

3. There is no password "complexity" checking.

4. During password entry the cursor displays a bullet, •, for each character typed..

5. Several fields, as noted under errors below, are checked for validity when they lose focus. If invalid, an error is posted to the right of the field. The field is not cleared as the user may not immediately notice the error message and a cleared field may not be caught when Next is clicked. When the user begins to edit a field that has a posted error, the error message is cleared and the default informational message, if any, is restored.

6. When F2 is pressed, if an error is detected, the error is posted in the message area and the focus is automatically given to the field referred to by the error.

Errors

1. The "re-typed" password is compared with the initial entry when the re-entry field loses focus. If they do not match a failure message is posted next to the re-typed password and both password fields are cleared. The focus is not reset to the password field as the user may not be looking at the screen. On the first edit keystroke into the first password field, immediately reset the error message on the re-enter password field to its default string.

   • Passwords do not match

2. The Login name field is checked for "root" when the field loses focus. If found, the Login name field is cleared and the following error message is displayed next to the field. The focus is not reset to the login field as the user may not be looking at the screen.

   • "Root" cannot be used.

3. The Login name field is checked for invalid usernames, e.g. those with invalid characters.

   • Must start with an alphabetic character.

   • Must contain only alphanumeric characters.

4. On F2 do the following checks in order. Do not proceed beyond the first failure, i.e. only one error message at a time.

• Verify the root passwords match and put up an error dialog if they don't.

  • Root Password Invalid: the two root passwords do not match.

• Verify the username exists and put up an error message if it doesn't

• Verify the user password exists and put up an error message if it doesn't

• Verify the user passwords match and put up an error message if they don't match.

  • User Password Invalid: the two user passwords do not match.

• Verify the Login name is not "root".

  • "Root" is not a valid Login name.

• Verify the user account has a Log-in name if any other user account fields are non-blank.

  • Invalid User Account: enter a Login name or clear all user account fields

Warnings

When Next is clicked, after all error checks are completed: Post a warning dialog:

• The user is warned if the root password is not defined or if the user account information is improperly defined (only a Login name is required).

  • "No root password<p>A root password had not been defined. The system is completely unsecured.\nClick Cancel to set a root password.

Summary

This screen lists information provided by the user during the earlier screens:

• The disk and, if specified, partition target information (install) or disk and solaris instance information (upgrade)

• The version of Solaris, desktop, and specific tools to be installed and the size of the software to be installed.

• Language support and primary language

  • The language is set to the installer language.

  • The locale is set based on the Time zone country.

• Timezone, but not date and time

• User: root only if "No root password" warning; user account name or "No user account" warning;

• computer name

• Network configuration

Defaults

1. None

Behaviors

1. None

Errors

1. None

Install Progress

The progress screen informs the user of approximate progress of the installation. All software is installed while this page is visible.

Defaults

1. None

Behaviors

1. User-level status messages above the progress bar are updated no more frequently than every two seconds. They may remain much longer. There should be no "Installing package x" type messages that flash rapidly.

2. The progress bar should display and update a completion percentage number that reflects the current length of the progress bar.

3. Quit warns the user that the disk may be left in an indeterminate state..

4. If the Solaris installation fails, go to the Installation Failed screen.

5. If the Solaris install/upgrade succeeds, go to the Installation Finished screen.

Errors

1. If Solaris fails to install, proceed to the Install Failed screen.

Warnings

1. None.

For the Future

• Requests for consideration

  1. Some form of fine-grained feedback to the user can know that the install isn't locked-up. (Moinak)

  2. A scrolling list of packages being installed for fine-grained feedback. (Moinak)

  3. Align the content of the marketing messages with the content of the Developer Guide. (UIRB TCA 5.7)

  4. Consider showing more detailed installation progress information, e.g. package names and estimated time to completion. This info might be hidden by default. (UIRB TCA 5.8)

Finished

The Finished screen informs the user of the successful completion of the Solaris installation/upgrade. (If Solaris failed to install properly the InstallFailed screen is displayed.)

Defaults

1. None

Behaviors

1. Log displays the installation log screen.

2. Reboot quits the installer and forces a system reboot.

3. Quit does not request confirmation. It does not force a system reboot.

Errors

1. None

Install Failed

This page is displayed if the Solaris portion of the installation fails. It contains the failure message and the path to the installer log file.

Defaults

1. None

Behaviors

1. Log displays the installation log screen.

2. Quit does not request confirmation..

Errors

1. None

Install Log

This page displays the installation log. It is displayed via F4_Log on the Installation Complete/Failed screens.

There is a "scrollbar" to indicate the user can scroll the log to see the portion that is off-screen.

Defaults

1. None

Behaviors

1. The up/down-arrows scroll the content

2. F3_Back returns to the calling screens.

Errors

1. None

Help Topics

This page is provides an overview of help and a list of the help screens for each screen in the installer.

Defaults

1. The selection is set to the help screen from which Help Topics was called.

Behaviors

1. Use the up/down arrows to select a help screen, then F2 to view that screen.

2. Back, F3, always goes back to the installer the screen the user was viewing when Help, F6, was initially clicked.

Errors

1. None

Screen Help

This page is displayed help text specific to the screen from which it was called..

Defaults

1. None

Behaviors

1. Standard F# operation.

Errors

1. None

Change List