Abstract: A grid array socket pin field is protected during manufacture of an information handling system with a dust cap having first and second attachment devices. The first attachment device secures the cap to the socket during assembly of the socket in the computer. The second attachment device secures the cap to a load mechanism assemble proximate the socket. Engagement of the second attachment device to the cap automatically releases the cap from the socket to allow removal of the cap from the socket by actuation of the load mechanism to an open position. The second attachment device secures the cap to the load mechanism until a processor is placed in the socket.

Abstract: A grid array socket pin field is protected during manufacture of an information handling system with a dust cap having first and second attachment devices. The first attachment device secures the cap to the socket during assembly of the socket in the computer. The second attachment device secures the cap to a load mechanism assemble proximate the socket. Engagement of the second attachment device to the cap automatically releases the cap from the socket to allow removal of the cap from the socket by actuation of the load mechanism to an open position. The second attachment device secures the cap to the load mechanism until a processor is placed in the socket.

Abstract: A grid array socket pin field is protected during manufacture of an information handling system with a dust cap having first and second attachment devices. The first attachment device secures the cap to the socket during assembly of the socket in the computer. The second attachment device secures the cap to a load mechanism assemble proximate the socket. Engagement of the second attachment device to the cap automatically releases the cap from the socket to allow removal of the cap from the socket by actuation of the load mechanism to an open position. The second attachment device secures the cap to the load mechanism until a processor is placed in the socket.

Abstract: A computer system warranty upgrade method and apparatus are provided. The computer system is programmed to detect a change in its configuration such as when new components are installed. When such a configuration change is detected, the computer system sends a warranty upgrade request including configuration information to a remote warranty server computer. The warranty server prepares a warranty price quote specific to the particular configuration of the requesting computer. When the quoted price is paid, the warranty server digitally signs and transmits a warranty authorization to the requesting computer. The warranty authorization includes warranty type, duration, the specific configuration warranted and an identification number unique to the requesting computer. These data are authenticated and validated by a secure processor in the requesting computer. After validation, the verified data is stored in secure storage by the secure processor.

Abstract: A computer system warranty upgrade method and apparatus are provided. When a warranty upgrade is desired, the computer requesting a warranty upgrade sends its configuration information to a remote warranty server computer. The warranty server prepares a warranty price quote specific to the particular configuration of the requesting computer. When the price quote is paid, the warranty server encrypts and transmits a warranty authorization to the requesting computer. The warranty authorization includes warranty type, duration, the specific configuration warranted and an identification number unique to the requesting computer. These data are authenticated and validated by a secure processor in the requesting computer. After validation, the validated data is stored in secure storage by the secure processor.

Abstract: A computer system warranty upgrade method and apparatus are provided. When a warranty upgrade is desired, the computer requesting a warranty upgrade sends its configuration information to a remote warranty server computer. The warranty server prepares a warranty price quote specific to the particular configuration of the requesting computer. When the price quote is paid, the warranty server encrypts and transmits a warranty authorization to the requesting computer. The warranty authorization includes warranty type, duration, the specific configuration warranted and an identification number unique to the requesting computer. These data are authenticated and validated by a secure processor in the requesting computer. After validation, the validated data is stored in secure storage by the secure processor.

Abstract: A computer system warranty upgrade method and apparatus are provided. The computer system is programmed to detect a change in its configuration such as when new components are installed. When such a configuration change is detected, the computer system sends a warranty upgrade request including configuration information to a remote warranty server computer. The warranty server prepares a warranty price quote specific to the particular configuration of the requesting computer. When the quoted price is paid, the warranty server digitally signs and transmits a warranty authorization to the requesting computer. The warranty authorization includes warranty type, duration, the specific configuration warranted and an identification number unique to the requesting computer. These data are authenticated and validated by a secure processor in the requesting computer. After validation, the verified data is stored in secure storage by the secure processor.

Abstract: A system for automated testing of an graphical user interface (GUI) of a software application includes creating a test file of a plurality of test steps in a text file format. The test file may be created using any variety of text editor. The test file is used as input to a test harness. In execution, the test harness opens the test file and begins using each line of the test file as a test step. The test harness is configured to execute one of a plurality of automated tests in response to each line of test steps. Each automated test is configured to test a corresponding physical user interface element of the program through a GUI map. The GUI map is configured to define a logical name for each physical user interface element of the software application.