Filter
Top Products
CM9740-CC1 | 13
5.1.2 Category I–Upgrade Replacement (Hardware Only)
Object: Physical Replacement of the CC1
Assumptions:
• The CC1 to be replaced is part of an existing operational system configu-
ration that has failed.
• The software environment that existed on the failed CC1 is to be used on
the replacement CC1.
To physically replace the CC1:
1. Shut down any parts of the system that are running and turn off power
(where applicable). We assume here that the failed CC1’s power is al-
ready off.
2. Disconnect all peripheral equipment from the failed CC1, noting what is
connected to what.
3. Connect a PS/2 keyboard to the replacement CC1 and power it up inde-
pendent of the system to which it will be connected.
4. Take your most current copy of configuration files (flat files) for the system
in question and copy them to the C:\9740 directory on the hard drive of the
replacement CC1. If you don’t have a set, you are going to have create
one from scratch.
5. The 9740.EXE that exists on the replacement CC1 will be configured with
the latest revision of system software.
6. When power is applied to the replacement CC1 in step 3, it should boot to
the diagnostic screen after loading system files. This is a reflection of the
standard factory configuration of the autoexec.bat file and nothing else.
NOTE:
You can choose to edit and effect changes in the autoexec.bat file
after the system is hooked up and power is turned on. If you do, just keep
in mind that the following instructions assume that you have already
made the changes referenced.
7. Once you have loaded a copy of your current configuration files, the old
executable and the adjusted autoexec.bat (if applicable) on the new CC1,
turn off power to the CC1.
8. Replace the old unit with the new CC1 and reinstall, connector for con-
nector, all peripheral equipment disconnected in step 2.
9. Turn on power to all the peripheral equipment and to the new CC1. Check
system initialization and look for system errors. Correct any found, and
then, again, save to disk any copies of your configuration files and any
other files that you don’t want to have to create or scrounge around for
should similar circumstances occur in the future.
NOTE:
Normally, one thinks of hardware
and software as separate entities and that
upgrading or replacing one would not sig-
nificantly affect the upgrade or replacement
of the other. For new system configurations,
this is not a problem. Areas of concern do
arise, however, when upgrading or replac-
ing existing units within systems that are
out in the field. If the replacement equip-
ment contains preloaded software (for ex-
ample, the CC1) or contains programmed
ROMs (for example, the CM9760-KBD),
care must be taken. You must make a rea-
sonable effort to ensure that the new
hardware and the software it contains are
compatible with the system within which
it is to be placed.
NOTE:
You should always save your old
executables and flat files, along with your
autoexec.bat file, in case the upgrade in-
stallation doesn’t pan out.
NOTE:
You should always have a list of
the current version levels of all the soft-
ware that you are running on your system
or at least know where to find the informa-
tion. In general, it’s best to make a list as
soon as possible after receiving new soft-
ware or equipment containing software and
keep the list current.
The list would include version information
on the following:
1. The CM9740.exe
2. The 9760MGR software
3. The CM9760-KBDs