Method and apparatus for verifying and analyzing computer software installation

• US 20030051235A1
• Filed: 09/07/2001
• Published: 03/13/2003
• Est. Priority Date: 09/07/2001
• Status: Abandoned Application

• Current Assignee: GE Fanuc Automation North America Incorporated
• Original Assignee: GE Fanuc Automation North America Incorporated
• Inventors: Simpson, Mark D.
• Application Number:
  US09/948,899
• Publication Number:
  US 20030051235A1
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A method for verifying and analyzing the installation of software onto a programmable device includes generating at least one installation data file containing information corresponding to at least one software file required for proper installation of the software, and comparing the information contained in the at least one installation data file with data pertaining to actually installed files on the programmable device to determine if the software is properly installed.

Claims

1. A method for verifying and analyzing the installation of software onto a programmable device, said method comprising:

generating at least one installation data file containing information corresponding to at least one software file required for proper installation of the software; and

comparing the information contained in the at least one installation data file with data pertaining to actually installed files on the programmable device to determine if the software is properly installed.

2. A method in accordance with claim 1 wherein the information contained in the at least one installation data file includes a designated location of the at least one software file required for proper installation of the software, said comparing the information contained in the at least one data installation data file with the data pertaining to actually installed files on the programmable device further comprises comparing the designated location of the data installation file with location data of the actually installed file on the programmable device.

3. A method in accordance with claim 1 wherein the information contained in the at least one installation data file includes the date of the at least one software file required for proper installation of the software, said comparing the information contained in the at least one data installation data file with data pertaining to actually installed files further comprises comparing the date of the at least one software file required for proper installation of the software with date data of the at least one actually installed file to determine if the software is properly installed.

4. A method in accordance with claim 1 wherein the information contained in the at least one installation data file includes the size of the at least one software file required for proper installation of the software, said comparing the information contained in the at least one data installation file with data pertaining to actually installed files further comprises comparing the size of the at least one software file required for proper installation of the software with size data of the at least one actually installed file to determine if the software is properly installed.

5. A method in accordance with claim 1 wherein the information contained in the at least one installation data file includes the version of the at least one software file required for proper installation of the software, said comparing the information contained in the at least one installation data file with data pertaining to actually installed files further comprises comparing the version of the at least one software file required for proper installation of the software with version data of the at least one actual installed file to determine if the software is properly installed.

6. A method in accordance with claim 1 wherein the programmable device comprises an installation source.

7. A method in accordance with claim 1 further comprising generating at least one log file containing the results of comparing the information contained in the at least one data installation file with data pertaining to actually installed files to determine if the software is properly installed.

8. A method in accordance with claim 7 wherein generating the at least one log file comprises documenting results of all file comparisons made while comparing the information contained in the at least one data installation file with data pertaining to actually installed files.

9. A method in accordance with claim 7 wherein generating the at least one log file comprises documenting only file discrepancies determined while comparing the information contained in the at least one data installation file with data pertaining to actually installed files.

10. A programmable logic controller (PLC) system for software having at least one installation data file, said PLC system comprising:

a central processing unit (CPU);

at least one input/output (I/O) module;

a memory;

a software installation source comprising at least one actually installed software file for loading into said memory;

at least software installation file containing information about said at least one actually installed software file; and

at least one software installation log generated by comparing the information contained in said actually installed program data file with corresponding data in said at least one software installation data file to determine if said software file is properly installed in said memory.

11. A PLC system in accordance with claim 10 wherein the at least one data installation file includes a designated location of said at least one software file stored in said memory, said actually installed program file comprising location data of said at least one software file stored in said memory, said log comprising a comparison of the designated location of with said location data to determine if said at least one software file is properly installed.

12. A PLC system in accordance with claim 10 wherein the at least one installation data file includes a designated date of said at least one software file stored in said memory, said actually installed program file comprising date data of said at least one software file stored in said memory, said log comprising a comparison of the designated date with said date data to determine if said at least one software file is properly installed.

13. A PLC system in accordance with claim 10 wherein the at least one installation data file includes a designated size of said at least one software file stored in said memory, said actually installed program file comprising size data of said at least one software file stored in said memory, said log comprising a comparison of the designated size with said size data to determine if said at least one software file is properly installed.

14. A PLC system in accordance with claim 10 wherein the at least one installation data file includes a designated version of said at least one software file stored in said memory, said actually installed program file comprising version data of said at least one software file stored in said memory, said log comprising a comparison of the designated version with said version data to determine if said at least one software file is properly installed.

15. A PLC system in accordance with claim 10 wherein said system comprises a CPU configured to generate said at least one log file containing the results of comparing the information contained in said actually installed program data file with corresponding data in the at least one software installation data file to determine if said software file is properly installed in said memory.

16. A PLC system in accordance with claim 15 wherein said at least one log file comprises results of all file comparisons performed by said CPU.

17. A PLC system in accordance with claim 15 wherein said at least one log file comprises noted file discrepancies of all file comparisons performed by said CPU.

18. A PLC system in accordance with claim 15 wherein said CPU is configured to indicate the location of said at least one data actually installed program data file.

19. A programmable device programmed to:

generate at least one installation data file containing the location, date and size of at least one software file required for proper installation of the at least one software file onto a microprocessor-based system;

compare the at least one installation data file with the actual location, date and size of the at least one software file on the microprocessor-based system to determine if the at least one software file is properly installed on the microprocessor based system; and

generate at least one log file containing the results of said comparison of the at least one data installation file with the actual location, date and size of the at least one software file on the microprocessor system.

20. The programmable device of claim 19 wherein the at least one installation data file further includes a version of the at least one software file required for proper installation of the at least one software file and said programmable device is further programmed to compare the installation data file version with the actual version of the at least one software file on the microprocessor-based system.

21. The programmable device of claim 19 wherein the at least one log file includes the results of all file comparisons made in said computer comparison of the at least one data installation file with the actual location, date and size of the at least one software file.

22. The programmable device of claim 19 wherein the at least one log file includes only the results of file discrepancies determined in said computer comparison of the at least one data installation file with the actual location, date and size of the at least one software file.

23. The programmable device of claim 19 wherein said microprocessor based system comprises a software installation source.