JPH1165900A - Install method of software and storage medium therewith - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable to install just when a minimum empty capacity exists even if empty capacity enough for the total size of a file to be installed does not necessarily exist. SOLUTION: A list composed of the updated date and time of all the files required for install and their file sizes is prepared and first of all, the presence/ absence of respective files in the list at the install destinations is successively checked (102). When they exist, the mark of ○ is described (105) and when the updated dates and times are equal, the mark of ○ is written (106 and 109) and write '0' in a corrected size column (110). When the updated date and time are not equal, the mark of × is described (106 and 107) and the difference is written in the corrected size column (108). When any file does not exist at the install destination (102), on the other hand, the mark of × is described (103) and a file size is written in the corrected size column (104). When the empty capacity is more than the sum total of corrected size columns, install is enabled.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software installation method and a storage medium for storing the installation program, and more particularly to an installation method with a minimum free space, and a reduction in the number of times installation is not possible. It relates to a possible installation method and a program recording medium.

[0002]

2. Description of the Related Art Conventionally, in order to execute and operate software recorded on a portable recording medium such as a floppy disk or a CD-ROM on a computer main body,
Read the software from the portable storage medium,
There is a program (called an installer) that performs processing for storing data in a storage device such as a hard disk built in a computer main body. In the installation process using the installer, the operator needs to secure in advance the total file size of various files necessary for executing the software created as a result of the installation process as an empty area in the hard disk drive. Was. In this case, the required size of the empty area differs depending on whether the program to be installed is an upgraded version or a new program. In the case of version upgrade, there are portions that have not been changed, and portions that have been changed may be almost the same as the original size. However, the conventional method requires a free space for the entire capacity of the program to be installed.

In the case of large-scale software,
In some cases, the operator specifies the disk capacity required for the installation process with options such as "minimum", "recommended", "full", and the like, and the installation process can be performed with a file size suitable for the execution environment of the computer. That is, when the program is large, it may not always be necessary to install the entire program as determined by the user. In other words, select "minimum" if you need to enter at least, select "recommended" if you want to install only those that should be installed, select "full" if you want to install all Was. Thus, the interruption of the installation process due to insufficient disk capacity is prevented in advance. For example, in the version number management method described in Japanese Patent Application Laid-Open No. 2-41523, a version number management table corresponding to each module of system software is provided, and when a new system is installed in an existing system, the contents of the version number management table And the version management table of the new system are compared. If they are the same, the replacement process is not performed. If the version of the new system is larger, the replacement process is performed. If the version of the new system is smaller, Inquiry processing to confirm the replacement is performed on the console. However, in this method, there is a problem that the installation cannot be performed with the minimum free space because the comparison of the free space is not performed only by the version number comparison.

[0004]

As described above, in the conventional software installation, especially in the upgrade (the process of replacing the software with new software such as adding a function), the same file is taken over as it is, or replaced with a new file having the same name. Often. However, even in this case, if you do not prepare the same amount of free disk space as the case of a new installation before installation, an error will occur in the check of free space, and although you should be able to actually install, There was a problem that it could not be installed. Therefore, an object of the present invention is to solve such a conventional problem and, when performing installation, calculate an appropriate installation size before installation, and it is not always necessary to have free space for the total size of the files to be installed. An object of the present invention is to provide a software installation method and a recording medium for the software that can be successfully installed with a minimum free space.

[0005]

In order to achieve the above object, in the software installation method of the present invention, a list including all files necessary for installation, the update date and time of the file, and the file size is created in advance. Keep it. Next, when starting the installation,
Check whether the files in the list exist on the installation disk. If a file in the list exists, the update date and time of the file are further referenced to determine whether the file is of the same version. If the result of the comparison indicates that the versions are the same and have different versions, the difference between the file size of the installed file and the file size of the file to be installed is calculated, and the size is recorded.
After these processes are performed for all the files in the list, all the differences between the file sizes of the files that did not exist on the disk to be installed and the file sizes of the files that existed but have different versions are totaled. The total file size is compared with the free space of the installation destination disk, and if the latter is larger, it is determined that the installation is possible, and the installation is executed. When the former is large, the installation process becomes impossible. Further, the recording medium of the present invention has
Is recorded on a recording medium.

[0006]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a system configuration diagram to which the installation method of the present invention is applied. In FIG.
10 is an installation medium (floppy disk or CD-RO) containing software to be installed.
M, etc.) for reading a flexible disk device, 2
Reference numeral 0 denotes an input / output device including a display for the user to specify, select, input, and the like regarding installation. Reference numeral 30 denotes a list of files necessary for installation from the installation medium of the flexible device 10 and user operation of the input / output device 20. Based on the file list generated by the file list generating unit 30, the file list generating unit 40
A file comparison unit 50 for checking the existence of the installation file and comparing the update date and time of the file is a hard disk device for actually installing the software.
In the file list creating unit 30, the file of the installation medium or the file to the user is input / output device 20.
A file list is created using a known means, such as selecting a file. Here, the free space of the hard disk device 50 is usually determined by an OS (operating system).
Is managing. The installation program obtains free space information by using an API (application program interface) of a command prepared by the OS. Note that the API is provided by the installer
This is a program-level function group (function group) for requesting some processing to S, and by using this, it becomes possible to perform operations such as accessing and changing information managed by the OS. .

FIG. 2 is a diagram showing a specific example of a file list created by the file list creating section of FIG. 1 and used by the file comparing section. FIGS. 3 and 4 are flowcharts showing a processing procedure by the file comparison unit according to the embodiment of the present invention. A method of calculating an appropriate installation size according to this installation method will be described with reference to the flowcharts of FIGS. First, it is assumed that the file list creating unit 30 shown in FIG. 1 has created a list as shown in FIG. 2 including the file name of the file to be installed, the update date and time, and the file size. First, the file comparison unit 40 reads file information (file name to be installed, update date and time, file size) created by the file list creation unit 30 one by one (step 101). Next, a search is made in the hard disk to be installed to determine whether there is a file having the same file name (step 102). If there is no file with the same name, "Exist" in the file list
Enter "x" in the column (step 103), and write the file size of the file to be installed in the "correction size" column as it is (step 104).

On the other hand, if there is a file with the same name,
"O" is entered in the "existence" column (step 105), and it is further compared whether or not the file update dates and times match (step 106). If they do not match, enter "x" in the "match" column of the file list (step 10).
7) In the "correction size" column, a value obtained by subtracting the file size of the file existing in the installation destination hard disk from the file size of the file to be installed is written (step 108). As a result of the comparison, if they match, the files are completely the same, so “「 ”is entered in the“ match ”column (step 109), and 0 is written in the“ correction size ”column (step 110). The above processing,
This is performed for all files in the list file (step 111). Thereafter, if the sum of the “correction sizes” is obtained, the installation size that is truly necessary for the installation can be calculated.

When the flow of FIG. 3 ends, the flow of FIG. 4 starts. First, the values written in the correction size column of the file list in FIG. 2 are summed (step 201).
This total value is the capacity value required for installation. Next, an inquiry is made for the free space of the hard disk device 50 at the installation destination by a command (API) (step 202). Next, the total file size, that is, the file size required for installation, is compared with the free space of the storage device 50 as a result of the inquiry, and it is determined whether the free space is larger than the install size (step 203). If the free space is larger, the installation is executed (step 204). On the other hand, if the free space is smaller than the installation size, the installation is stopped (step 205).

FIG. 2 shows a specific example of the created file list, and the operation in this case will be described. The left three columns (file name, update date and time, file size) of the list are entered by the file list creation unit 30, and the right three columns (existence, match, correction size) are entered by the file comparison unit 40. Here, “exists” indicates whether a file with the same name exists in the installation destination hard disk, and “matches”
Indicates whether the versions are the same when “exists” (whether the update date and time match). Furthermore, the correction size is
"Existing" is the same as the file size to be installed, "Existing" and "Matching" is the difference between the size of the file to be installed and the existing file size, "Existing" and "Matching" Is written with 0. In other words, it is the size of how much additional hard disk capacity is used depending on the files to be installed.

In FIG. 2, for example, a file name AAA
Is "existing" and "matched", so there is no change in the used capacity of the hard disk. Therefore, ○ is written in the presence column, に も is written in the match column, and 0 is written in the correction size column. The file name BBB does not “exist”, and thus requires a new capacity for the file size. Therefore, in the existence column, ×
“-” Is written in the matching field, and 300,000 is written in the correction size field. Since the file name CCC was “existent” but did not “match”, it is necessary to add the difference size between the size of the new file to be installed and the file of the same name in the hard disk. Therefore, ○ in the existence column,
X in the match column and 400,000 and 3 in the correction size column
100,000 which is a difference of 00,000 is written. Note that DDD is a file that did not exist, like the BBB, and EEE existed, like the CCC.
The files do not have the same update date. The total file size is compared with the free space of the installation destination disk, and if the latter is larger, it is determined that the installation is possible, and the installation is executed. In the case of FIG.
The total file size of the AAA to EEE part is 1.00
If the free space of the hard disk device 50 at the installation destination is equal to or larger than this value, the installation can be executed.

In the above embodiment, the software to be installed is read from the flexible disk. However, as another embodiment of the present invention, the software to be installed is a server computer connected to a computer network. May be stored in the storage device. In this case, the server computer reads the data from the storage device and transmits the data to the hard disk device 50 at the installation destination via the network. Also, if the program, which is the installation method of the present invention, is recorded on a recording medium such as a hard disk, a flexible disk, a magnetic tape, or an optical disk, the program is read and executed. It becomes possible to install.

[0013]

As described above, according to the present invention,
At the time of installation, the free space for the total size of the files to be installed is not necessarily required, and the installation can be successfully performed with a minimum free space. As a result, it is possible to avoid a situation where an error occurs in the check of the free space and the installation cannot be performed, although the installation can be actually performed.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram to which an installation method of the present invention is applied.

FIG. 2 is a diagram illustrating a specific example of a file list created by a file list creating unit in FIG. 1;

FIG. 3 is a flowchart illustrating an operation procedure of a file comparison unit in FIG. 1;

FIG. 4 is a flowchart of a process for performing installation performed after the process of FIG. 3;

[Explanation of symbols]

10: Flexible disk device, 20: I / O device,
30: file list creation unit, 40: file comparison unit,
50 ... Hard disk device.

Claims (2)

[Claims] A step of creating a file list including each file name required for installation, each file's update date and time, and each file size; and said file name, said file's update date and time, and said file size. Reading from a recording medium in which software to be installed is recorded; and checking whether or not files listed in the file list exist in a storage destination storage device, respectively. If the file exists in the destination storage device, then a step of checking whether the update date and time of the file match, and a file that does not exist in the storage destination storage device and a file that exists but has a different file update date and time Only the file to be installed, Summing the file size, comparing the totaled file size with the free space of the storage destination storage device, and performing the installation only when the comparison result shows that the free space of the storage destination storage device is larger than the file size. Executing the software. 2. A recording medium on which software is recorded, wherein a program comprising the steps of the installation method according to claim 1 is recorded.