JP2005275664A - Uninstallation system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an uninstallation system by which software uninstallation is surely executed in consideration of the possibility of causing an adverse effect on separate software when a modification is applied to installed software in service or when the installed software is uninstalled. <P>SOLUTION: An uninstallation means determines the presence or absence of the replacement of a file executing the uninstallation by means of a file access management means or access to the separate software in executing the uninstallation for the file of the installed software. In the case of the replacement of the file executing the uninstallation or the access to the separate software, the file access management means describes the absence on a management file for the separate software to execute the uninstallation. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus such as an image forming apparatus such as a printer, a copying machine, a facsimile, or a multifunction machine having these functions to which an electrophotographic method is applied, and unnecessary software installed in the information processing apparatus. The present invention relates to an uninstall system that can be surely uninstalled.

JP-A-9-146664 JP 9-179727 A

  2. Description of the Related Art Conventionally, in an information processing apparatus such as a printer, a copying machine, a facsimile, or a multifunction machine having these functions, to which this type of electrophotographic method is applied, software (programs) for controlling the information processing apparatus ) Is written in advance in a ROM (Read Only Memory), and the functions that can be realized by this information processing apparatus are determined by software written in the ROM in advance and cannot be changed.

  Therefore, in the information processing apparatus, in order to add a new realizable function or newly update to a realizable function, it is necessary to replace the ROM in which software is written by a service engineer with a new one. there were.

  By the way, in recent years, information processing apparatuses such as the above-mentioned printers, copiers, facsimiles or image forming apparatuses such as multifunction machines having these functions have come to be used connected to a network. It has become possible to download a new version of software from a server provided by a manufacturer such as a computer, or a server provided by another software-dedicated manufacturer, etc., and update the function of the apparatus. In addition, the information processing apparatus is not limited to updating all of the software that controls the information processing apparatus by being connected to the manufacturer's server via a network, but partially adds software for applications, etc. It is also possible to update or update. Furthermore, in the information processing apparatus, it is possible to download not only software created exclusively for the information processing apparatus but also software for a desired service desired by the user from the server via the network. Yes.

  However, in the information processing apparatus, as described above, in order to add a new function, repeated installation of new software or uninstallation of software to delete unnecessary functions is repeated. Therefore, there is a problem that other functions other than the scheduled function may be affected. In addition, the information processing apparatus has a problem that a problem may occur in the operation of the entire apparatus while software installation and uninstallation are repeated.

  Therefore, as a technique that can solve such a problem, for example, those disclosed in Japanese Patent Laid-Open Nos. 9-146664 and 9-179727 have been proposed.

  In this software uninstall method according to Japanese Patent Laid-Open No. 9-146664, the state immediately before installation is temporarily saved, the changes made at the time of installation are saved, and the uninstall operation is executed based on the saved changes. Thus, it is configured such that unnecessary software can be uninstalled without depending on the installation order.

  More specifically, the software uninstall method according to the above-mentioned Japanese Patent Application Laid-Open No. 9-146762 is a software uninstall method in which any one or a plurality of software is removed from a plurality of software installed on a predetermined operating system. Means for temporarily evacuating the state immediately before installation, means for reproducing the state immediately after installation of the predetermined operating system (hereinafter referred to as "initial setting"), and software for the initial setting reproduced by the means Means for holding the changes made by the installation, and means for calculating the state after uninstallation of any one or more software from the one or more changes held by the means and the initial settings; Configured to include Those were.

  Further, the uninstall apparatus according to the above Japanese Patent Laid-Open No. 9-179727 is an uninstall apparatus that deletes a file installed on a storage medium, and stores the current file information including the name and content of the currently installed file. A file management means for recording in the storage medium the file past information including the name and contents of the file that is recorded before the file to be uninstalled is recorded, and instructing execution of the uninstallation An uninstall instructing unit that matches the file name of the file current information and the file past information in accordance with an instruction from the uninstall instructing unit, and the file current information is converted into the file past information in accordance with a collation result. The file changer to change It is obtained by configured with and.

  However, the conventional technique has the following problems. That is, in the case of the techniques disclosed in the above Japanese Patent Laid-Open Nos. 9-146664 and 9-179727, the state before the software is installed and the state after the software is installed are stored. In addition, by calculating the state after the software has been uninstalled, or by comparing the file name with the file current information and the file past information, any uninstallation can be performed based on the state before and after the software installation. There are no considerations for changes that can be made while using the installed software, but how it affects other software when the software is uninstalled. Resulting in incomplete uninstall The it has.

  Accordingly, the present invention has been made to solve the above-described problems of the prior art, and the object of the present invention is when changes are made during the use of installed software or when the software is uninstalled. Furthermore, an object of the present invention is to provide an uninstallation system capable of reliably performing software uninstallation in consideration of the possibility that other software may be affected.

In order to solve the above problems, an invention described in claim 1 is an uninstall system for deleting software installed in a storage means.
File access management means for managing at least one of writing, file reference, and file deletion of software installed in the storage means;
Uninstalling means for executing uninstallation of the software file;
When uninstalling the software file by the uninstall unit, the file access management unit determines whether the file to be uninstalled is replaced or accessed by other software, and the uninstall is performed. When a file to be executed is replaced or another software is accessed, the file access management means describes that in the management file of the corresponding other software, and performs uninstallation. Uninstall system.

  Further, the invention described in claim 2 is that the file access management means, if at least one of file writing, file reference, and file deletion is instructed, whether the corresponding file is described in the management file. The uninstall system according to claim 1, wherein if the file is not described in the management file, the file is described in the management file.

  Further, in the invention described in claim 3, when the file access management unit executes the uninstallation of the software file by the uninstallation unit, the access from other software to the file to be deleted is performed. 2. The uninstall system according to claim 1, wherein if there is, the file to be deleted is moved to the management file of the corresponding other software.

  According to a fourth aspect of the present invention, when the file access management means executes the uninstallation of the software file by the uninstallation means, the other software is moved to a directory under the file to be deleted. 2. The uninstall system according to claim 1, wherein the file to be deleted is moved to the management file of the corresponding other software when accessed from.

  Furthermore, the invention described in claim 5 is provided with user interface means for inquiring the user whether or not to delete the file when the file to be uninstalled is a user file. An uninstall system according to claim 1.

  In this invention, when installing the software, a management file is created, and additions and changes made by the software are recorded, and if the file is accessed during the operation of the software, the management file is recorded. Update. When uninstalling, refer to the management file and execute uninstallation.

  According to the present invention, even if changes are made during the use of installed software or other software may be affected when the software is uninstalled, it is necessary to take these into consideration. It is possible to provide an uninstallation system capable of reliably performing software uninstallation.

  Embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1
FIG. 2 is a block diagram showing an information processing system including a multi-function machine (multifunction machine: MF machine) as an information processing apparatus to which the uninstall system according to Embodiment 1 of the present invention is applied.

  As shown in FIG. 2, the information processing system 1 includes a multifunction machine (multifunction machine: MF machine) 100 as an information processing apparatus according to the present embodiment, a server 200 that is a software download source, The network 100 is configured to connect the machine 100 and the server 200 so that they can communicate with each other. The multifunction machine 100 has functions such as a printer, a copier, or a facsimile, and software used in the multifunction machine can be installed by downloading from a server via a network. . The server is installed in a multifunction device manufacturer, a software development company, etc., and the basic software for controlling the image forming operation of the multifunction device and software for applications are installed on the network. Can be provided through. For convenience, only one multifunction device and server are illustrated, but the number of multifunction devices and servers is not limited, and any number of multifunction devices and servers may be connected to the network 300. Of course.

  The network 300 includes, for example, Ethernet (registered trademark), wired or wireless LAN (Local Area Network), general telephone line, ADSL (Asymmetoric Digital Subscriber Line), ISDN (Integrated Switched Digital Network), etc. The Internet constructed via these networks 300 is also included. Here, the network 300 is a network that connects the multifunction peripheral 100 and the server 200 so that they can communicate with each other, and identifies the information processing apparatus of the other party to communicate with based on unique information individually assigned to the network 300. Can communicate with each other. Typical information individually assigned to the network is an IPv6 (Internet Protocol, version 6) address or IPv4 (version 4) address and port number defined in the Internet. By specifying the IPv6 address or the combination of the IPv4 address and the port number, it is possible to communicate with a specific information processing apparatus via the Internet as a network, and to perform the specific information processing It is possible to receive information from the device.

  Further, as shown in FIG. 3, the multifunction device 100 includes a scanner device 6 that reads an image of a document on the upper portion of the multifunction device body 5. The document image data read by the scanner device 6 is converted into image format conversion, compression / expansion, show-through removal, color conversion (brightness / color space conversion), shading correction, and positional deviation by an image processor (not shown). Predetermined image processing such as correction, gamma correction, frame erasing, and color / movement editing is performed.

  Further, the multifunction device 100 includes a multifunction module (hereinafter referred to as “MF module”) 7 inside the multifunction device main body 5, and the MF module 7 stores images and images read by the scanner device 6. Based on image data sent via the logical network 4 or facsimile image data sent via a general telephone line, etc., image data transmission / reception, and copy and print processing based on the image data are performed. Configured to do. The MF module 7 forms a black and white or color image by, for example, an electrophotographic method, but is not limited to this, and forms an image by an arbitrary method such as an electrostatic recording method or an inkjet recording method. It includes things that perform.

  Further, a display operation unit 8 is provided at the upper part of the copying machine main body 5. For example, the display operation unit 8 is for displaying a screen for setting a site, setting a scan or print, or searching a home page, or giving an instruction for opening a site, scanning or printing. In addition to the display operation unit 8, an operation panel for performing basic operations such as a copy instruction may be provided at a predetermined position on the upper surface of the main body.

  Further, the multifunction device 100 can be accessed from an external device such as a server 200 connected to the network 300 via the external interface 108 as will be described later.

  In the multi-function device 100, when accessing the server 300 via the external interface 108, communication is performed using a protocol such as IPv4 (Internet protocol, version 4) or IPv6 (same, version 6). Is called. Here, when using IPv4, one IP address is assigned corresponding to one external interface, but when using IPv6 instead of IPv4, a plurality of IP addresses are assigned to one external interface. An address can be assigned. Therefore, when using IPv4, it functions as an information processing apparatus on one transmission side and one reception side by one port number corresponding to one IP address of the IPv4 and one external interface, and an unspecified number of The information can be received from the information processing apparatus. Also, by providing a plurality of external interfaces, it is possible to function as a plurality of information processing apparatuses on the receiving side by using a plurality of port numbers corresponding to one IP address and a plurality of external interfaces. On the other hand, when using IPv6, a plurality of IP addresses can be assigned corresponding to one external interface of the IPv6, and a plurality of transmitting and receiving sides are assigned by the plurality of IP addresses. It is possible to function as an information processing apparatus, and to receive information from an unspecified number of information processing apparatuses.

  On the other hand, as shown in FIG. 4, the server 200 communicates with an external information processing apparatus such as a multifunction peripheral, and is requested to receive various information such as software and usage thereof from the external information processing apparatus. A function of transmitting the requested information to the information processing apparatus of the other party who accessed it. In this server 200, in addition to basic software (operating system: OS), application software necessary for performing various types of information processing is stored in a storage device such as a hard disk. Among application software, software for performing print processing by the multifunction device 2 by IPP or the like, software for inputting image data read by the scanner device 6 of the multifunction device 100, or reading by the scanner device 6 of the multifunction device 100 Also included is software for performing desired image processing on the obtained image data and outputting the image data to another information processing apparatus. In this embodiment, because only one IP address is required on the server 200 side, one IP address is assigned to one external interface in both IPv4 and IPv6. May be configured so that these IP addresses can be selectively used.

  That is, the multifunction peripheral 100 according to this embodiment has the functions of a printer device, a copier, a facsimile device, and the like, and can respond to various information processing requests.

  As shown in FIG. 1, the multi-function device 100 includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a page memory 104, an NVRAM (Non Vapor Random). (Access Memory) 105, printing unit 106, U / I (user interface) 107, I / F (external interface) 108, hard disk (Hard Disk Drive) 109, reading unit (scanner) 110, FAX ( Facsimile) communication unit 111.

  The CPU 101 includes a ROM 102, a RAM 103, a page memory 104, an NVRAM 105, a printing unit 106, a U / I 107, an I / F 108, a hard disk 109, a reading unit 110, and FAX communication that constitute the multifunction peripheral 100. The central processing unit is configured to control the unit 111 via the system bus 112. A printing operation, a copying operation, or various operations as a facsimile in the multifunction peripheral 100 is executed under the control of the CPU 101. The control operation by the CPU 101 is determined based on software (program).

  The CPU 101 also has a function as file access management means.

  The ROM 102 is a read-only memory, and the ROM 102 stores a program for controlling basic operations among programs for controlling the multifunction peripheral 100. Examples of the program include a program for diagnosing each hardware of the multifunction peripheral 100 immediately after power-on and starting a control program stored in the NVRAM 105.

  A RAM 103 is a readable / writable memory, and is a data storage area used by each program operating on the multifunction peripheral 100 for work.

  The page memory 104 is a storage area for storing the result of converting document data into data that can be printed on paper.

  The NVRAM 105 is a non-volatile RAM, and most of the programs for controlling the multifunction peripheral 100 are stored in the NVRAM 105. The data stored in the storage area of the NVRAM 105 is retained even after the multifunction device 100 is powered off.

  The printing unit 106 is a unit that prints printable data stored in the page memory 104 on paper. For example, the printing unit 106 is not limited to a printing function of an image read by the reading unit 110, that is, a copying apparatus function, and is based on document data or an image file acquired from a client terminal such as a personal computer via the network 300. A so-called print function for printing an image and a FAX function for printing out based on FAX reception data received via a general telephone line are also provided.

  When the MFP 100 functions as a printer, for example, the printing unit 106 receives PDL data described in a page description language (PDL) from a client terminal (not shown), and stores the PDL data in the page memory 104. The raster data is developed as image data for each output unit (one page), and the raster data is sent to the printing unit 106 and printed out by the printing unit 106. When the multifunction device 100 functions as a color facsimile receiver, the printing unit 106 receives FAX reception data instead of PDL data, converts the received data into a Lab signal by the printing unit 106, and then prints out the printing unit 106. To do.

  The U / I 107 includes a liquid crystal display and a touch panel (not shown). A liquid crystal display as a display means is controlled by the CPU 101 and displays characters, a graphic screen, a menu screen, etc., and gives information to the user. The touch panel is installed so as to cover the liquid crystal display, and when the user touches the touch panel, the user can input information by sending a signal indicating the touched position.

  The I / F 108 is an external interface, a network interface for connecting to the Internet, a wireless communication interface for performing wireless communication by infrared or Bluetooth (registered trademark), an IC card, a PC card, a compact flash (registered trademark), It consists of an interface for data communication with portable media such as smart media and magneto-optical disks.

  The hard disk 109 stores print information and document data received from the outside via the I / F 108, fonts for converting the document data into printable data, setting information and status information of the multifunction peripheral 100, and the like. It is a storage medium. The hard disk 109 is generally used as an auxiliary storage area of the RAM or page memory because the cost per unit is generally lower than that of the RAM, NVRAM, or page memory.

  The reading unit 110 converts an image of a document into image data that can be handled in the multifunction peripheral 100, and is generally called a scanner.

  The FAX communication unit 111 is a device for receiving data via a telephone line and transmitting the data read by the reading unit 110 by FAX.

  Note that the multifunction peripheral 100 according to this embodiment is connected to the server 200 via the network 300, and also has functions as a network scanner and a network printer. In addition, the site managed by the MFP 100 is accessed via an I / F 108 from an external device such as the client terminal 200 connected to the network 300, and provides predetermined information and instructions. It also has a function to perform the processed information.

  For example, based on the image read by the reading unit 110 or an image received for print output or received as a FAX reception image, the MFP 2 generates and acquires the content of the site in the communication control unit 17. It is possible to provide information to other users based on the image obtained and prepared (stored in an image storage unit such as a hard disk device).

  The multifunction device 100 can provide a so-called Web site by connecting to the Internet via the network 300. In this case, the multifunction peripheral 100 can receive Web information prepared at an external site by the interface 108 and further provide it on the Internet. In this case, the multifunction device 100 functions as a so-called relay server that acquires and provides content from outside the device.

  The MFP 100 receives an image processing request for image data read by the reading unit 110 of the MFP 100 or a reading unit 110 of the MFP 100 from a client terminal (not shown) connected via the network 300. Various requests, such as a request for a copy process for printing image data read by the client, a request for a print process (IPP) for document data created at a client terminal, a request for a print process for an image viewed on a website, etc. An information processing request is sent.

  FIG. 5 is a hierarchical diagram showing the internal configuration of the multifunction device 100.

  In FIG. 5, reference numeral 120 denotes hardware such as the CPU 101, ROM 102, and RAM 103, 121 is basic software (operating system: OS) that controls hardware such as the CPU 101 and ROM 102, 122 is file access monitoring means, and 123. Is provided with application software such as FX-WEBSVC-001, FX-WEBSVC-002, and applications 1 to n.

  Thus, in this embodiment, in the uninstall system for deleting the software installed in the storage means, at least one of writing of the software file installed in the storage means, reference of the file, and deletion of the file is performed. A file access management means for managing, and an uninstall means for executing an uninstallation of the software file. When the uninstallation of the software file is executed by the uninstall means, the file access management means When there is a replacement of a file for performing the uninstallation or access of other software, and there is a replacement of a file for performing the uninstallation or access of other software, Describes the fact to serial file access appropriate other software management file of the management unit is configured to perform the uninstall.

  The file access management unit and the uninstallation unit are realized by a program executed by the CPU 101.

  The uninstall system according to this embodiment includes a file access management unit 122 located between an OS (operating system) 121 and application software (FX-WEBSVC-001, FX-WEBSVC-002, applications 1 to n) 123. It is realized as. Therefore, the file access management means 122 monitors file access regardless of the application software 123 and can perform processing at the OS level.

  In the above configuration, in the information processing apparatus according to this embodiment, when the installed software is changed or the software is uninstalled, the other software is affected as follows. Even if there is a possibility of giving, it is possible to reliably execute uninstallation of the software in consideration of these.

  Here, the operation of the uninstallation system that operates in the multifunction peripheral 100 according to this embodiment will be described in the order of installation, software operation, and uninstallation.

(1) During installation When software is installed in the multi-function device 100, the start of installation of the software is detected by the file access monitoring means 122 when the file is written. However, this does not apply to certain applications because installation is explicitly started.

  FIG. 6 is a flowchart showing the main operation of the file access monitoring means.

  First, the file access management means 122 determines whether or not the requested process is a file writing process (step 101). If the requested process is a file writing process, the corresponding application management is performed. It is determined whether or not the file exists (step 102). If the management file for the corresponding application exists, the management file is initialized (step 103), then the file writing process is executed (step 104), and the management file for the corresponding application does not exist. Detects the start of installation and immediately executes a file writing process (step 104).

  If the requested process is not a file writing process, the file access management unit 122 determines whether the file is a deletion process (step 105), and the requested process is a file deletion process. If it is, delete processing is executed (step 106). If it is not file deletion processing, it is determined that the processing is file reference processing, and file reference processing is executed (step 107).

  As the management file, for example, those shown in FIGS. 7 and 8 are used. The management file is created for each application software, and includes the program name, installation / uninstallation time, generated files and directories, changed contents and contents, replaced files, and access information from other application software. Is done.

  In the example illustrated in FIG. 7, for application software FX-WEBSVC-001, the application software program name “FX-WEBSVC-001”, installation start time and end time of the application software, and uninstallation start The time and end time are recorded.

  In addition, as the generated file and directory, No. 1: Data type “system”, file type “directory”, file name / directory name “/ etc / websvc-001 /”, No. 2: Data type “system”, file type “directory”, file name / directory name “/ var / websvcspool /”, No. 3: Data type “system”, file type “file”, file name / directory name “/ctc/websvc.conf”, No. 3 4: Data type “system”, file type “directory”, file name / directory name “/ usr / sbin / websvcd”, no. 5: Data type “user data”, file type “directory”, file name / directory name “/ home / userl / doc /”, no. 6: Data type “user data”, file type “file”, file name / directory name “/home/userl/work/template.xml” are recorded.

Furthermore, as a change of the file contents, No. 7: File name "/ etc / passwd", contents "7a8,9
> websvcdmn: x: 88880: 88888: FX-WEBSVC-DAEMON: / usr / sbin: / usr / sbin / websvcd
> websvcadm: x: 88880: 88888: FX-WEBSVC-ADMIN: / usr / sbin: / usr / sbin / websvcd "
Is recorded.

  In addition, as replacement of a file, No. 8: The old file name “/usr/lib/libcmn.so” and the new file name “/etc/websvc-001/libcmn.so” are recorded.

  Furthermore, as access information from other application software, No. 9: Name of application software “FX-WEBSVC-002”, change file “/ctc/websvc.conf”, No. 9 10: Application software name “FX-WEBSVC-002” and change file “/ var / websvcspool / ws002 /” are recorded.

  In the example shown in FIG. 8, the application software program name “FX-WEBSVC-002” and the installation start time and end time of the application software are recorded for FX-WEBSVC-002 as the application software. ing.

  In addition, as the generated file and directory, No. 1: Data type “system”, file type “directory”, file name / directory name “/ etc / websvc-002 /”, no. 2: Data type “system”, file type “directory”, file name / directory name “/ var / websvcspool / ws002”, no. 3: Data type “system”, file type “file”, file name / directory name “/usr/websvc.conf”, No. 3 4: Data type “system”, file type “directory”, file name / directory name “/ usr / sbin / websvcd”, no. 5: Data type “user data”, file type “directory”, file name / directory name “/ home / userl / doc /”, no. 6: Data type “user data”, file type “file”, file name / directory name “/home/userl/work/template.xml” are recorded.

Furthermore, as a change of the file contents, No. 7: File name "/etc/websvc.conf", contents "3a4
> name: 002
8a10,14
>
> [websvc-002]
> port: 8080
> session: 1
> timeout: 30
Is recorded.

  In FIG. 6, the file writing process in step 104 is performed as shown in the flowcharts of FIGS.

  That is, as shown in FIG. 9, the file access management means 122 determines whether the file writing process is creation of a new directory (step 201), creation of a new file (step 203), or modification of the contents of an existing file (step 205), it is determined whether the existing file is to be replaced (step 207). If a new directory is created, the process of FIG. 10A is performed (step 202), and if a new file is created, FIG. (Step 204), in the case of changing the contents of an existing file, the process of FIG. 11 (a) (step 206), and in the case of replacement of an existing file, the process of FIG. 11 (b) (step 208). Run each one.

  In the case of creating the new directory, as shown in FIG. 10A, it is determined whether or not the upper directory is already described in the management file (step 301). Then, it is determined whether or not it is a management file of its own application (step 302). If it is the management file of the own application, the processing is immediately terminated, and if it is not the management file of the own application, it is described in the management file of the corresponding application (step 304). On the other hand, if the upper directory has not been described in the management file, after creating the directory (step 304), the directory is described in the management file (step 305), and the process ends.

  In the case of creating a new file, as shown in FIG. 10B, it is determined whether or not the creation destination directory has been described in the management file (step 401), and the creation destination directory is described in the management file. If it is already determined, it is determined whether or not the file is a management file of its own application (step 402). If it is the management file of the own application, the processing is immediately terminated, and if it is not the management file of the own application, it is written in the management file of the corresponding application (step 404). On the other hand, if the creation destination directory is not already described in the management file, the file is created (step 404), then written in the management file (step 405), and the process is terminated.

  Further, in the case of changing the contents of an existing file, as shown in FIG. 11A, it is determined whether or not the corresponding file has already been described in the management file (step 501), and the corresponding file has already been described in the management file. In this case, it is determined whether or not the file is a management file of its own application (step 502). If it is a management file of its own application, it is determined whether or not other application software is accessed (step 504). If there is no other application software access, the process is terminated as it is. If other application software is accessed, it is described in the management file of the application (step 505), and the process is terminated. On the other hand, if it is not the management file of its own application, it is described in the management file of the corresponding application (step 503), the contents of change are described in the management file (step 506), and the process ends. Further, even if the relevant file is not already described in the management file, the contents of change are described in the management file (step 506), and the processing is terminated.

  In the case of replacement of an existing file, as shown in FIG. 11B, after the new file is stored in a different area from the existing file (step 601), the management file is described as being replaced (step 602). ), The process ends.

  Here, as shown in step 304 of FIG. 1 or No. 2 as described. Similarly, if the file is to be created, No. 1 in FIG. 3 or No. It is described as shown in FIG. The content change of an existing file means that if an existing file exists and this file belongs to another application (not generated by itself), No. in FIG. As shown in FIG. In this embodiment, a description using a general diff command is adopted. The file replacement means that an existing file exists, this file belongs to another application (not generated by itself), and this file is replaced with its own file. For example, updating a shared dynamic link library. In this case, without actually replacing (overwriting copy), the file to be updated (“new file” in the figure) is stored in another area as shown in FIG. As shown in FIG. 8, the new file name is described in correspondence with the old file name. The above processing is repeated until the installation is completed. At this point, No. 1 in FIG. 9 and no. 10 does not exist.

  Further, the deletion process in FIG. 6 is executed as shown in FIG.

  In this deletion process, as shown in FIG. 12, it is determined whether or not there is a description in the management file of the corresponding application (step 701). Therefore, the deletion process is not executed as an error (step 705). On the other hand, if there is no description in the management file of the corresponding application, it is determined whether or not there is an access from another application (step 702). Therefore, the deletion process is not executed as an error (step 705). If there is no access from another application, the file is deleted (step 703), the corresponding part of the management file is deleted (step 704), and the process is terminated.

  Further, the reference process in FIG. 6 is executed as shown in FIG.

  In this reference process, as shown in FIG. 13, it is determined whether or not the corresponding file is described in the management file (step 801). If the corresponding file is not described in the management file, the file reference process is performed. Is executed (step 804), and the process ends. If the file is described in the management file, it is determined whether or not the file is to be replaced (step 802). If the file is to be replaced, a replacement file reference process is executed (step 803). If the file is not replaced, a file reference process is executed (step 804).

(2) At the time of software operation Next, processing at the time of installation and operation of FX-WEBSVC-002 which is application software replacing FX-WEBSVC-001 will be described.

  The flowchart of this operation is as shown in FIGS. 9 to 11 described above. For example, as shown in N0.2 of FIG. 8, when a new directory is created, “/ varlwebsvcspoo1 / "Is determined to be FX-WEBSVC-001, and is described in its own management file as indicated by N0.2 in FIG. 8, and is also included in the management file of FX-WEBSVC-001 in FIG. As shown in FIG. 10, the fact that there was an access from another application is described. When the existing file (/etc/websvc.conf) of FX-WEBSVC-001 is changed, the change contents are described and the management of FX-WEBSVC-001 is performed as indicated by N0.7 in FIG. The file also indicates that another application has accessed, as indicated by N0.9 in FIG.

The contents of the file “/etc/websvc.conf” this time are as shown in FIG.
That is, after installing websvc-001,
“[Websvc]
num: 2
name: 001

[websvc-001]
port: 8000
session: 5
timeout: 30 "
It is.

On the other hand, after installing websvc-002,
“[Websvc]
num: 2
name: 001
name: 002

[websvc-001]
port: 8000
session: 5
timeout: 30

[websvc-002]
port: 8080
session: 1
timeout: 30 "
It becomes.

  In addition to directories and files automatically created by application software, there is user data created by the user. For example, the data is stored when “user data storage” (not shown) is set in FX-WEBSVC-001. Such user data is also shown in No. 5 of FIG. 5 and no. 6 is described in the management file.

(3) At the time of uninstallation Next, an operation flowchart at the time of uninstallation will be described based on FIG. 15, FIG. 16, and FIG.

  First, when the uninstall operation is started, a management file is selected (step 901), and an inquiry is made as to whether or not an uninstall log should be kept (step 902). Here, when leaving an uninstall log, the uninstall operation itself can be uninstalled. If an uninstall log is to be left, a management file is stored separately (step 903), and the log mode is turned on (step 904).

  Thereafter, after the created files are selected in order (step 905), it is determined whether or not other application software has been accessed (step 906). If another application software is accessed, the contents are moved to the management file of the corresponding application (step 909). If no other application software is accessed, has the file contents been changed? If there is no change in the file contents, the process proceeds to step 910 as it is, and if there is a change in the file contents, the added contents are deleted (step 910). 908), the process proceeds to step 910 as it is.

  In step 910, it is determined whether or not the file is a user file. If the file is not a user file, the file is deleted (step 912), and the corresponding portion of the management file is deleted (step 913). If the file is a user file, confirmation with the user or a preset content is determined (step 911). If the file is to be deleted, the file is deleted (step 912). If not deleted, only the relevant part of the management file is deleted (step 913).

  Thereafter, it is determined whether or not the log mode is ON (step 914). If the log mode is not ON, it is determined whether or not all files have been processed (step 916). ), If all the files have not been processed, the process returns to step 905. If the log mode is ON, after adding to the log (step 915), it is determined whether or not all files have been processed (step 916).

  When all the files have been processed, as shown in FIG. 16, after the created directories are selected in order (step 1001), it is determined whether or not other application software has been accessed (step 1002). If another application software is accessed, the contents are moved to the management file of the corresponding application (step 1005). If no other application software is accessed, the other directory is moved to another directory. It is determined whether or not an application has been accessed (step 1003). If another application has accessed a lower directory, the contents are moved to the management file of the corresponding application (step 1005), and then the management file. Are deleted (step 1006). If no other application accesses the lower directory, the directory and the following are deleted (step 1004), and the corresponding part of the management file is deleted (step 1006).

  Thereafter, it is determined whether or not the log mode is ON (step 1007). If the log mode is not ON, it is determined whether or not the processing of all directories has been completed (step 1009). ), If all the directories have not been processed, the process returns to step 1001. If the log mode is ON, after adding to the log (step 1008), it is determined whether or not the processing of all the directories has been completed (step 1009).

  Next, when all the directories have been processed, as shown in FIG. 17, after selecting the replacement file in order (step 1101), the replacement file is deleted (step 1102), and the corresponding management file is selected. The part is deleted (step 1103).

  Thereafter, it is determined whether or not the log mode is ON (step 1104). If the log mode is not ON, it is determined whether or not the processing of all directories has been completed (step 1106). ), If all directories have not been processed, the process returns to step 1101. If the log mode is ON, after adding to the log (step 1105), it is determined whether or not the processing of all the directories has been completed (step 1106).

  Next, when all the directories have been processed, the management file is deleted (step 1107), and the uninstall operation is terminated.

  In this way, the management file items are processed in order. No. of FIG. 1 is deleted, and No. 1 in FIG. If it is 2, since there is access to another application, the actual state is not deleted, and information is added to the management file of FX-WEBSVC-002. No. of FIG. If it is 7, the changed contents are restored based on the information described in the management file. No. of FIG. For 8, only the new file is deleted. No. of FIG. 5, no. In the case of user data such as 6, the user is allowed to select whether to delete at the U / I 107, and is deleted or left as it is. If the log mode is ON, the log file is associated with the management file stored in a separate area and left in the log at each processing. This log is, for example, as shown in FIG. Then, as described above, the management file that became unnecessary last is deleted (step 1107), and the uninstall operation is terminated.

  As described above, according to this embodiment, when software is installed, a management file is generated, additions / changes by the software are recorded, and there is a file access during the operation of the software. , Update the management file. By referring to the management file at the time of uninstallation, it is possible to execute reliable uninstallation without affecting other applications.

FIG. 1 is a block diagram showing a control circuit of a multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 2 is a diagram showing a control system including a multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 3 is an external configuration diagram showing the multifunction machine to which the uninstallation according to the first embodiment of the present invention is applied. FIG. 4 is an external configuration diagram showing the server device. FIG. 5 is a hierarchical diagram showing the control circuit of the multifunction machine to which the uninstallation according to the first embodiment of the present invention is applied. FIG. 6 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 7 is a chart showing software management files. FIG. 8 is a chart showing a software management file. FIG. 9 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 10 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 11 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 12 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 13 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 14 is a diagram showing a file whose file contents have been changed. FIG. 15 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 16 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 17 is a flowchart showing the operation of the multifunction machine to which uninstallation according to Embodiment 1 of the present invention is applied. FIG. 18 is a chart showing log files.

Explanation of symbols

  100: MFP, 101: CPU, 122: file access management means, 123: application software.

Claims (5)

In an uninstall system that deletes software installed in the storage means,
File access management means for managing at least one of writing, file reference, and file deletion of software installed in the storage means;
Uninstalling means for executing uninstallation of the software file;
When uninstalling the software file by the uninstall unit, the file access management unit determines whether the file to be uninstalled is replaced or accessed by other software, and the uninstall is performed. When the file to be executed is replaced or another software is accessed, the file access management means describes the fact in the management file of the corresponding other software, and executes the uninstallation. Uninstall system. The file access management means determines whether or not the corresponding file is described in the management file when at least one of file writing, file reference and file deletion is instructed. The uninstallation system according to claim 1, wherein if it is not described, it is described in a management file. The file access management means, when executing the uninstallation of the software file by the uninstallation means, if there is an access from the other software to the file to be deleted, the corresponding other software The uninstall system according to claim 1, wherein the file to be deleted is moved to the management file. The file access management means is applicable when there is an access from another software to a directory under the file to be deleted when the uninstallation means executes the uninstallation of the software file. The uninstallation system according to claim 1, wherein the file to be deleted is moved to a management file of another software. 2. The uninstallation system according to claim 1, further comprising user interface means for inquiring the user whether or not to delete the file when the file to be uninstalled is a user file.

Images