test

Solaris 8 (Intel Platform Edition) Online Release Notes Update

Installation Bugs That Occur During an Interactive Installation

ddi: net: x86 Network Boot Only Works on First Network Interface of a Given Type (1146863)

Booting over the network must be done on the primary network interface of IA based systems.

Identifying the primary network interface is a matter of trial and error, but the first or last network device listed on the Boot Solaris menu is likely to be the primary interface.

As soon as you have determined the primary interface, it remains the primary interface every time you boot unless you make a change to the hardware configuration. If you change the hardware configuration, the primary interface may or may not change, depending on the type of changes made.

If you boot from a non-primary network interface, the booting system will hang and a boot server will not be contacted. (This problem can also occur if the system is not registered as a client of the boot server.)

Installation Progress Bar May Be Inaccurate (1266156)

The Installing Solaris Software - Progress bar sometimes indicates that an installation is complete when it is still in progress. The install program may add packages for several minutes after the progress bar has indicated that the installation is complete.

Do not rely on the progress bar to indicate that the installation is complete. The installation displays the following message when the program has completed all installation operations.


Installation complete

Warnings May Occur When Creating a File System (4189127)

One of the following warning messages may be displayed when creating a file system during installation.


Warning: inode blocks/cyl group (87) >= data blocks (63) in last cylinder group. This implies 1008 sector(s) cannot be allocated.
or

Warning: 1 sector(s) in last cylinder unallocated
The warning occurs when the size of the file system being created does not map exactly to the space on the disk being used. This can result in unused space on the disk that is not incorporated into the indicated file system. This unused space is not available for use by other file systems.

Workaround: Ignore the warning message.

No Error Occurs If # Is Included In A Path (4294586)

If a # is included in the path of a JavaTM program, the following message is displayed when you execute the program.


Exception in thread "main" java.lang.NoClassDefFoundErrorVolume Management (vold) sometimes uses a pound sign in a pathwhen creating directory names:

Workaround: Delete the # from the path or do not use any Java installation wizards.

Custom JumpStart Does Not Prompt for the Solaris 8 Software 2 of 2 CD (4304912)

After installing the Solaris 8 Software 1 of 2 CD, a custom JumpStartTM installation does not prompt you to install the Solaris 8 Software 2 of 2 CD.

Workaround: If you are installing only the End User software group, you do not need to install the Solaris 8 Software 2 of 2 CD as the End User software and its basic locale support is contained on the Solaris 8 Software 1 of 2 CD.

Wizard Stops If You Insert the Solaris 8 Software 2 of 2 CD When the 1 of 2 CD Is Requested (4306752)

For some English-only versions of the Solaris 8 Installation CD, the installation program enables you to insert the Solaris 8 Software 2 of 2 CD at the point the installation program requested the Solaris 8 Software 1 of 2 CD.

If the incorrect CD has been inserted, the installation program attempts to use it even though it can no longer install the Solaris operating environment.

If you are performing a default installation, the following message is displayed in the summary panel's Details window:


ERROR: Could not load the media (/cdrom)" error message
If an Installation CD custom install had been selected, a blank panel would be displayed immediately after choosing Custom and selecting the Next Panel button.

Workaround: Insert the Solaris 8 Software 1 of 2 CD when requested. If you inserted the Solaris 8 Software 2 of 2 CD after a blank screen was displayed, you need to restart the installation by beginning with the "Boot CD-ROM" step.

An Arithmetic Exception Occurs When a Zip Drive is Attached With No Media in a Drive (4307035)

Solaris Web Start reports an arithmetic exception when a zip drive is attached and no disk has been inserted in the drive. The following message is displayed: 


Starting the Web Start 3.0 Solaris installer
./W00.findswap[1823]: 173 Arithmetic Exception
Could not get disk information.
Exiting
Workaround: Either disconnect the zip drive before you boot your system or insert the zip disk into the drive.