|
 |
|
Wrong Floppy Diskette Installation
(2550-xxxx Solaris 1.x diskettes installed into Solaris 2.5 systems)
(2552-xxxx Solaris 2.5 diskettes installed into Solaris 1.x systems)
The only visible difference between diskettes
destined for Solaris 1.x and 2.5 systems is the part number.
Solaris 1.x diskettes have a part number 2550-xxxx and Solaris
2.5 diskettes have a part number 2552-xxxx.
If you press 'Update Application' from the Master
Menu with the wrong diskette in the floppy drive, incorrect
binary files are written to the hard disk and the applications
will not run correctly. Please use the following procedure(s)
to return the hard disk files to the proper configuration.
The next release of each application diskette will
include a check to automatically reject an incompatible floppy.
- Which Solaris version am I running?
In an XTerm window, type the command '
% uname -rs
'. If the system prints "SunOS 4.1.x",
then you are running Solaris 1.x. If the system prints "SunOS
5.5.x", then you are running Solaris 2.5.
(where "x" is any number - it indicates a minor release)
- Only vibration applications are incorrect (Random, Sine, etc.)
- Solaris 1.x floppies (2550-xxxx) installed on
Solaris 2.5
Indications of trouble
- Update Application window has error messages, such
as "Unknown user: genrad" and "chmod: WARNING:
Execute permission required for set-ID on execution for bin/random".
- Pressing the application button on the Master Menu
causes error messages in the Console window, such as "WARNING
0mdsp00: no IOCTL: allowed" or "System warning: No such
file or directory, extras menu file /usr/openwin/lib/locale/C/xview/.text_extras_menu
(Textsw package)" for Random.
- Running a test has error messages in the Messages
box, such as "Child exited on a signal" for Random.
Remedy
- Insert the correct floppy disk into the floppy drive.
From the Master Menu, press 'Update Application' and answer all
questions with a 'y'.
- Solaris 2.5 floppies (2552-xxxx) installed on
Solaris 1.x
Indications of trouble
- Update Application window has error messages,
such as "Unknown user: diag".
- Pressing the application button (Random) on the
Master menu causes the Master Menu to snap back and there is an
error message "random-manager: Bad file number" in the
Console window.
Remedy
- Insert the correct floppy disk into the floppy drive.
From the Master Menu, press 'Update Application' and answer all
questions with a 'y'.
- VCS Installation floppy (255x-0600) is incorrect
- Solaris 1.x floppy (2550-0600) installed on Solaris 2.5
Indications of trouble
- Update Application window has error messages, such
as "unknown user: genrad" or "chmod: WARNING: can't
access floppy_util".
Remedy
- Insert the correct floppy, 2552-0600, into the floppy
drive. Then, open an XTerm window and enter the following commands:
% su
# csh
# setenv VCS_HOME /2550vcs
# volcheck
# cd /floppy/floppy0
# ./gr_install
(answer questions with a 'y')
(ignore error messages)
# cp /floppy/floppy0/user/.* /usr/home/vcs
(ignore error messages)
# cd
# eject
#
- From the Workspace menu, select 'Exit'. Login to
the 'vcs' account and the Master Menu should appear. If other
applications are still incorrect, follow the Remedy procedure
in the above section.
- Solaris 2.5 floppy (2552-0600) installed on
Solaris 1.x
Indications of trouble
- Update Application window has error messages, such
as "mkdir: /a/usr/home: No such file or directory" or
"grep: /a/etc/passwd: No such file or directory" or
"chmod: /a/usr/home/diag/xxxx: No such file or directory"
- The Update Application window and the Master Menu
disappear.
- After a new login, there is no Master menu
Remedy
- Insert the correct floppy, 2550-0600, into the floppy
drive. Then, open an XTerm window and enter the following commands:
% su
# setenv VCS_HOME /home/2550vcs
# mount /dev/fd0c /fd
# cd /fd
# gr_install
(answer questions with a 'y')
# cd
# eject
# reboot
- Login as usual into the 'vcs' account. If other
applications are still incorrect, follow the Remedy procedure
of the previous section.
|
|
