Conflict checking using configuration images

Details Conflict checking using configuration images Conflict checking using configuration images

1998-08-20

2003-05-13

Dam, Tuan Q. (Department: 2124)

Data processing: software development, installation, and managem

Software program development tool

Managing software components

C717S168000, C717S174000, C713S001000

Reexamination Certificate

active

06564369

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates generally to computer systems and more specifically to checking for software conflicts using configuration images.
COPYRIGHT NOTICE/PERMISSION
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings hereto: Copyright© 1997, 1998 LANOVATION, All Rights Reserved.
CROSS REFERENCES
This application is related to a co-filed and co-assigned U.S. patent application entitled “Software Distribution, Error Detection and Repair System” Ser. No. 09/136,905.
BACKGROUND OF THE INVENTION
Installing or upgrading software frequently causes unnecessary duplication of files on a target computer. Installing or upgrading software also frequently causes a previously installed version of a file or a previously installed value of a registry key to be overwritten with a different version or a different value.
Duplicate files result in wasted space on a computer's hard disk. In addition, because some files, such as system files, are frequently shared among two or more application programs, duplicate files result in uncertainty for a user of which instance of the file is loaded when the application program is launched. Overwriting a file or registry value causes problems for a user if an application on the target computer requires the particular version of the file or the registry value that was overwritten. Overwriting a file or registry value also causes problems if the application on the target computer is incompatible with the version of the file or registry value installed.
System files, special system setup text files and program files are often duplicated or overwritten when software is installed or upgraded. A system file is a binary file used by a Windows operating system. Example system files include files ending with the extensions .dll, .sys, and .drv. Special system setup text files are files such as a menu file (for example the file that contains the “Start” menu or the “Desktop” menu), an autoexec.bat file, a config.sys file, and files that end in .ini. A program file is a file that executes a computer application. Example program files include files ending with the extensions .exe and .com.
Such problems caused by installing or upgrading software are difficult to predict, difficult to prevent from occurring, and difficult to identify when the problems do occur. Such problems result in lost productivity of a computer user and wasted time on the part of an administrator trying to identify the problems. Methods currently available for finding file conflicts only identify conflicting files after a problem occurs on a computer and no methods currently exist to identify or prevent conflicting registry values.
Therefore, there is a need for a system to identify files and registry values that will be overwritten during a software installation or upgrade before the installation or upgrade is performed. There is also a need for a system to prevent unnecessary duplication of files during a software installation or upgrade.
SUMMARY OF THE INVENTION
The above-identified shortcomings as well as other shortcomings are addressed by the present invention, which will be understood by reading and studying the following specification. The invention is a computerized system which identifies conflicts existing between two or more configuration image files.
A configuration image file is a single file containing all the information needed to troubleshoot, distribute, or delete software on one or multiple computers. Information contained in a configuration image file can be a file of any type or a registry setting. Each file and registry setting in a configuration image file is referred to as an entry. A conflict exists when one or more configuration image files include entries that are inconsistent.
One version of the conflict checking system of the present invention identifies folder conflicts. A folder conflict occurs when the same entry exists in different folders of one or more configuration image files. Installing the configuration image file or files containing the same entry results in duplicate copies of the entry on the target computer. Another version of the conflict checking system identifies version conflicts. A version conflict occurs when different versions of the same entry exist in the same location within two configuration image files. Installing the configuration image files containing different versions of the same entry results in one of the versions of the file being overwritten by the other version of the file. Still another version of the conflict checking system identifies registry conflicts. A registry conflict occurs when two registry values have the same name and belong to the same registry key, but have different data.
The conflict checking system detects conflicts within configuration image files associated with a computer before software is installed. The conflict checking system can also detect conflicts between a configuration image and a current state of a target computer. As a result, file version conflicts, registry value conflicts, and unnecessary duplication of files are avoided. In different embodiments of the invention, computers, computerized systems, application programs, methods and computer-readable media of varying scope are described. Still other and further embodiments, aspects and advantages of the invention will become apparent by reference to the drawings and by reading the following detailed description.


REFERENCES:
patent: 5155847 (1992-10-01), Kirouac et al.
patent: 5247683 (1993-09-01), Holmes et al.
patent: 5403639 (1995-04-01), Belsan et al.
patent: 5410703 (1995-04-01), Nilsson et al.
patent: 5430878 (1995-07-01), Straub et al.
patent: 5586304 (1996-12-01), Stupek et al.
patent: 5680548 (1997-10-01), Trugman et al.
patent: 5732275 (1998-03-01), Kullick et al.
patent: 5758154 (1998-05-01), Qureshi
patent: 5809251 (1998-09-01), May et al.
patent: 5819295 (1998-10-01), Nakagawa et al.
patent: 5835911 (1998-11-01), Nakagawa et al.
patent: 5842024 (1998-11-01), Choye et al.
patent: 5859969 (1999-01-01), Oki et al.
patent: 5860012 (1999-01-01), Luu
patent: 5867714 (1999-02-01), Todd et al.
patent: 5956513 (1999-09-01), McLain, Jr.
patent: 5964872 (1999-10-01), Turpin
patent: 5966540 (1999-10-01), Lister et al.
patent: 5983241 (1999-11-01), Hoshino
patent: 5995977 (1999-11-01), Presler-Marshall
patent: 6021413 (2000-02-01), Vaduvur et al.
patent: 6117187 (2000-09-01), Staelin
patent: 6298443 (2001-10-01), Colligan et al.
patent: 6202206 (2002-03-01), Dean et al.
McKinstry, “File Replication”, System Asdministration, Feb. 1998, pp 33-37.*
Hall et al., “An architecture for post-development configuration management in a Wide-area network”, IEEE, 1997, pp 269-278.*
Reiher et al., “Resolving file conflicts in the Ficus file system”, Proc. of the Summer USENIX conf., Jun. 1994, pp 183-195.*
Specker, S., “Using Novell Application Launcher 2.0 and snAppShot for Application Delivery”,Novell AppNotes, 53-72, (Aug., 1997).
“Conflict Catcher 8 released!”, File last modified Nov. 25, 1998. http://www.casadyg.com/products/press/default.html?recordID=1.
“LAN Escort Software Product Version 3.5”,Windows Software Distribution Evaluator's Guide; 3rd Ed., Pearson Technical Software dba LANovation, (Mar. 1996).
“LAN Escort Software Product Version 4.0”,Windows Software Distribution Administrator's Guide; 6th Ed., Pearson Technical Software dba LANovation, (Feb. 1997).
“Seagate Software Network and Storage Management Group, Technical Information Bulletin, TechNote No.: 41001”,Seagate Software, File last modified Jul. 7, 1997. http://seer.seagatesoftware.com/tnotes/installwin/41001.htm.
“Seagate Softwa

Affiliated with

Also associated with

Rating

Conflict checking using configuration images does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Conflict checking using configuration images, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Conflict checking using configuration images will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3084369