Grass Valley K2 Summit Client Service Manual Nov.23 2009 - Manual (Page 80)

80 K2 Summit Production Client Service Manual 12 October 2009
Chapter 4 Troubleshooting problems
This power connection sequence assumes that before power was removed, the K2
Summit Client was properly shut down from AppCenter, from the Windows
operating system, or from the standby button. If the power was removed without a
proper shutdown, when the first power cord is connected the K2 Summit Client might
go directly to the startup sequence. Refer to
“Shutdown/restart problems” on page 78 .
BIOS startup
A few seconds after startup, on the VGA monitor a black screen is displayed with
system information messages. This is the BIOS Power On Self Test (POST). Press
Delete on the keyboard during this time to enter the BIOS settings pages. When the
BIOS POST completes the Windows operating system begins to load.
If during the BIOS POST time a message appears that requires your input or if the K2
Summit Client does not progress to Windows startup, it indicates a problem at the
motherboard level. To correct problems of this nature, contact Grass Valley Support.
Windows startup
After the host startup processes complete the Windows operating system starts up.
Normally the Windows operating system completes its processes automatically
without the need to press keys or respond to messages. When the Windows startup is
complete the Windows logon dialog box is displayed.
If the Windows startup screen does not proceed automatically or if a message appears
that requires your input, it indicates a problem at the operating system level. Refer to
“Windows startup problems” on page 81 . If the problem cannot be corrected with a
supported procedure (such as networking), the Windows operating system is not
operating as it should. To correct problems of this nature, restore the system drive
image. Refer to
“Using recovery images” on page 65 .
K2 Summit Client system startup
After the Windows operating system startup processes complete, you must log in to
AppCenter to trigger K2 Summit Client system startup processes to begin. The K2
Summit Client determines that system health is adequate by checking critical
subsystems. Critical subsystems are those upon which the K2 Summit Client depends
for core media functionality. Critical subsystem checks are displayed in the System
Startup message box.