JPH1011282A - Installing system and executing system for software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software installing system preventing the illegal use of a software stored in an installing medium. SOLUTION: The software installing medium 1 is provided with ID storing areas 12 to 14 storing ID showing the presence/absence of the execution of installing, ID showing the kind of the software, etc., and the nonvolatile memory and the secondary storage device 28 of a computer system 2 are provided with areas 23 to 25 and 281 to 283 for storing the same ID as these. At the time of installing the software, each ID stored in the medium 1 and IDs stored in the storage areas 23 to 25 of the nonvolatile memory are compared with each other to decide whether installing is to be executed corresponding to this comparing result or not.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to installing software stored in a storage medium in a computer system (to be stored in an executable form, the same applies hereinafter).
In particular, the present invention relates to unauthorized copy protection for preventing unauthorized copying and use of software, and technology for preventing double installation.

[0002]

2. Description of the Related Art Programs, application software, and the like (hereinafter referred to as software) that are used by being installed in a computer system are installed on an FD (flexible disk) or a CD-ROM (installation medium). It is provided to the user by a compact disk ROM) and is expanded by the installation means in a secondary storage device or the like of the user's computer system. However, if the installation medium is left as it is, a malicious user may install it on another computer system. For this reason, traditionally, installation media is destroyed, software providers manage them to prevent unauthorized copying,
A method of providing an ID number storage unit in a computer system, comparing an ID in the computer system with an ID number stored in an ID number storage area of an installation medium, and preventing illegal copying due to a mismatch between the ID numbers. (See JP-A-63-213027).

[0003] However, destroying the installation medium,
The method in which the software provider manages the installation medium has a problem that an authorized user cannot quickly respond to a case where the installed software is destroyed for some reason. Also, JP-A-63-21302
In the method described in Japanese Patent Application Publication No. 7 (1994), an area for storing an ID number on the installation medium side is provided,
In this method, the ID number is stored in the D number storage area and the ID is stored in the computer system. In this method, when an ID is stored in the installation medium, it is determined that the installation medium is a used installation medium, and reinstallation is permitted only when the ID matches the ID stored in the computer system. However, in this method,
There were the following problems.

(1) When a plurality of computer systems are provided with the same number of installation media,
If an unused installation medium is used by mistake on a computer system that has already been installed, reinstallation is performed, and the misused installation medium cannot be reused. (2) When a plurality of pieces of software are stored in a large-capacity storage device, for example, a CD-ROM, and provided to a user, the user cannot selectively install required software. (3) It is not possible to respond when the software is upgraded.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a backup system capable of preventing software from being illegally copied while securing a backup, and preventing a situation in which the same software is installed twice in a computer system by mistake. It is an object of the present invention to provide a software installation method. Another object of the present invention is to provide a method of executing software installed by the above method.

[0006]

According to the present invention, there is provided a software installation method for installing software stored in a storage medium into a storage device of a computer system having a non-volatile memory. An installation ID storage area for storing an installation ID indicating whether or not the software has been installed;
A software ID storage area for storing a software ID indicating a type of software, and a version I for storing a version ID indicating a version of the software
D storage area, and a storage area for the installation ID, the software ID, and the version ID in the non-volatile memory, and further, when the software is first installed in the computer system, Installing ID generating means for generating an ID, writing the generated installation ID into an installation ID storage area of the storage medium and an installation ID storage area of the nonvolatile memory, and reading a corresponding software ID from the software ID storage area Means for writing to the software ID storage area of the non-volatile memory, reading the corresponding version ID from the version ID storage area, and writing the read version ID to the version ID storage area of the non-volatile memory. And wherein the door.

In the software installation method of the present invention, a storage area for the installation ID, the software ID, and the version ID is further formed in a storage device of the computer system. And
Each ID stored in the storage medium when the software is installed in the computer system
Means for verifying the match between the IDs and the IDs stored in the storage areas and determining whether or not to execute the installation based on the verification result.

The computer system has interface means for displaying a predetermined message at the time of installing the software and receiving a response result to the message. Based on the received response result, it is determined whether the installation can be executed or not. It is preferable to decide.

According to another installation method of the present invention, software stored in a storage medium is installed in a storage device of a computer system having a non-volatile memory, and is rewritable and accessible to the storage medium. It has a common medium. Then, at least the installation ID storage area is formed in this common medium, and the software ID storage area for storing the software ID and the version I for storing the version ID are stored in the storage medium.
A storage area for the installation ID, the software ID, and the version ID are formed in the non-volatile memory, and the storage area is further stored in the computer system when the software is first installed. Means for generating an installation ID; writing the generated installation ID to an installation ID storage area of the common medium and an installation ID storage area of the nonvolatile memory; and reading a corresponding software ID from the software ID storage area Means for writing to the software ID storage area of the non-volatile memory and reading a corresponding version ID from the version ID storage area and writing the version ID to the version ID storage area of the non-volatile memory. It is characterized in.

The software execution method of the present invention is a method of executing software installed in a storage device of a computer system having a non-volatile memory, wherein the installation ID storage area, the software ID and the software ID are stored in the storage device. While forming a storage area and a version ID storage area for storing a version ID,
The non-volatile memory forms storage areas for the installation ID, the software ID, and the version ID that are input when the software is installed, and is further stored in the storage areas in the computer system. Means for verifying the matching between each ID and each ID stored in the non-volatile memory, and determining whether or not to execute the software based on the verification result.

[0011]

Embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a configuration diagram of an embodiment of the present invention. In this embodiment, the software to be registered in the computer system and the installation program for performing the installation have the same storage medium (F
D) shows an example in the case where it is stored in D). The storage medium is hereinafter referred to as an installation software medium.

In FIG. 1, reference numeral 1 denotes a software installation medium 1, which is a storage area for software 11, a software ID storage area 12 for storing an ID indicating the type of the software 11, and a version ID of the software.
And an installation ID storage area 14 for storing an installation ID indicating that the installation has been performed when the software 11 is installed in the computer system 2.

The computer system 2 includes a known installation means 3 for installing software, and a secondary storage device 2 for storing software to be installed.
8 and a loader 26 for loading software. The loader 26 is provided with ID number comparing means 27. The secondary storage device 28 has a storage area for software 29, a software ID storage area 281, a version ID storage area 282, and an installation ID storage area 28.
3 are formed. The computer system 2 also has an installation ID for generating an installation ID number.
A number generation unit 21, an ID number input / output unit 22 for input / output control of the installation ID number generated by the installation ID number generation unit 21, and a non-volatile memory (BUM) (not shown) are provided. In
An installation ID storage unit 23, a software ID storage unit 24, and a version ID storage unit 25 are formed.

The installation ID storage unit 23 in the BUM
Software ID storage unit 24, version ID storage unit 2
5, no ID is stored in an initial state in which no software is installed. Also, at the first time when the software installation medium 1 is provided to the user or the like, no ID is written in the installation ID storage area 14 in the software 11, and the ID is firstly recorded when the software is first installed. Is written. On the other hand, the ID of the software ID storage area 12 and the ID of the version ID storage area 13
Is information of the software 11 itself, and the ID is written at the time of being provided to the user.

Whether the software stored in the software installation medium 1 is to be installed in the computer system 2 depends on the installation ID in the BUM.
It depends on the combination of the storage unit 23, the software ID storage unit 24, the version ID storage unit 25, and whether or not an ID is recorded in the installation ID storage area 14 on the software installation medium 1.

The processing corresponding to each combination is as follows. (1) When all the IDs of the installation ID storage unit 23, the software ID storage unit 24, the version ID storage unit 25, and the installation ID storage area 14 on the software installation medium 1 in the BUM are not stored. In this case, the software installation medium 1 is properly provided to the computer system 2 in an initial state where the software is not installed. When the software installation medium 1 is set in an input / output device (not shown), the ID number input / output unit 22 starts. FIG. 2 is an explanatory diagram of a processing procedure after activation of the ID number input / output unit 22. Referring to FIG. 2, the ID number input / output unit 22 first obtains a software ID from the software ID storage area 12 (S1). Next, the software ID in the software ID storage unit 24 in the computer system 2 is read (S2), and it is verified whether the software ID matches the software ID read in S1 (S3).
In this case, since the software IDs do not match, a new registration process is executed (S4). The procedure of the new registration process is as shown in FIG.
The processing of S11 to S18 shown in FIG. 3 is performed. In this example, S13 is executed because the installation ID is not stored in the installation ID storage unit 23 and the installation ID storage area 14.

In S13, the install ID number generating means 21 generates a new install ID.
The installation ID is generated by, for example, the date and time when the installation was to be performed or a random number. That is, it is sufficient if the number is unique among many computer systems. After generating the installation ID number, the installation ID number generation unit 21 passes the generated installation ID number to the ID number input / output unit 22. In response to this, the ID number input / output unit 22 stores the install ID number in the install ID storage area 14 and the install ID storage unit 23 (S14).

Next, the ID number input / output means 22 stores the software ID acquired in S1 in the software ID storage unit 2.
4, and obtains the version ID from the version ID storage area 13 to store the version ID in the version ID storage unit 25.
Is stored (S17). The ID number input / output unit 22 activates the installation unit 3 upon completion of the ID number storage process. The installation means 3 includes the software 1
1 is installed in the secondary storage device 28 (S18).
As described above, the software 29 storing the same installation ID as the installation ID storage unit 23 is stored in the secondary storage device 28. Then, the computer system 2
When the use of the software 29 is started and the loader 26 is started, the loader process shown in FIG. 6 is executed.

Referring to FIG. 6, the loader 26 first
Installation ID of software 29 requested to load
Each ID is read from the storage area 283, the software ID storage area 281, and the version ID storage area 282, and the installation ID is read from the installation ID storage unit 23.
From the software ID storage unit 24 to the software 29
ID that matches the software ID of
The version ID paired with the software ID read from the software ID storage unit 24 is read from the storage unit 25 (S41), and the ID number comparison unit 27 determines whether or not both IDs match (S41). S4
2). If any one of the installation ID, software ID, and version ID does not match, the loading process is not performed and the execution of the software is abnormally terminated (S4).
3). In this example, since all IDs match, the software 29 is loaded and executed (S44).

(2) Each ID is stored in the installation ID storage unit 23, the software ID storage unit 24, and the version ID storage unit 25. However, no ID is stored in the installation ID storage area 14, and the software ID is stored. A combination in which the same ID as the software ID in the storage area 12 is not stored in the software ID storage unit 24. In other words, this is a case where the software 11 is newly installed in the computer system 2 in which another software has already been installed, using the software installation medium 1 provided in a formal manner. In this case, similarly to the case shown in the example (1), in the processing procedure diagram shown in FIG. 2, the software ID is acquired in S1 and S2, and the consistency of the ID is verified in S3. Now, the software ID in the software ID storage area 12
Since the same ID does not exist in the software ID storage unit 24, they do not match, and the new registration process shown in FIG. 3 is executed.

In the new registration process shown in FIG. 3, since the installation ID exists in the installation ID storage unit 23 and the installation ID does not exist in the installation ID storage area 14, the installation ID storage unit 23 is stored in the installation ID storage area 14 in S16. Is registered. Here, the ID number input / output unit 22 reads the installation ID already stored in the installation ID storage unit 23 and stores it in the installation ID storage area 14 without generating a new installation ID by the installation ID number generation unit 21. I do. Next, in S17, the software I
D and the version ID are acquired from the software installation medium 1 and stored in the software ID storage unit 24 and the version ID storage unit 25 as a pair. Then, the software 11 is installed in the secondary storage device 28 by the installation means 3 (S18).

In this example (2), the same ID as the install ID, software ID, and version ID stored in the software 29 of the secondary storage device 28 is stored in the install ID storage unit 23 and the software I
Since the IDs are registered in the D storage unit 24 and the version ID storage unit 25, the verification of the matching of each ID in S42 has the same result. When the loader 26 is executed, S44 is executed and the software 29 can be executed. .

(3) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25,
And a combination in which each ID is already stored in the installation ID storage area 14 and the same ID as in the software ID storage area 12 is not in the software ID storage unit 24. In other words, this is a case where the software 11 is illegally copied to the computer system 2 in which another software is already installed, for example, by using the software installation medium 1 provided for another computer system.

In this case, the software ID storage area 1
2 is the same software ID as the software ID storage unit 2
4, the processing shifts from S3 to S4, and the new registration processing shown in FIG. 3 is executed. When the new registration process is performed, the process proceeds from S11 to S15. Installation ID
Since the installation ID is stored in the storage unit 23 and the installation ID storage area 14, the new registration process ends. Therefore, the software 11 is not installed in the secondary storage device 28. However, in some way,
Assuming that the software 11 is copied to the secondary storage device 28 without using the regular software registration method provided by the present invention, first, when the software stored in the software installation medium 1 is illegally copied, the software And each ID are integrated, so the software ID, version ID, and installation ID are also copied from the software installation medium 1 to the secondary storage device 28. For this reason, in the execution stage of the copied software (see the loader process in FIG. 6), in this example (3), at least the software ID does not match the one in the software ID storage unit 24, and
The software ends abnormally in the processes of S2 and S43. As a result, illegally copied software cannot be used.

(4) A case where the installation ID storage unit 23, the software ID storage unit 24, and the version ID storage unit 25 do not store an ID, but store an ID in the installation ID storage area 14. That is, for the computer system in the initial state where the software is not installed in the secondary storage device 28 of the computer system 2, the software 11 is illegally used by using the software installation medium 1 provided to another computer system. Is copied.

Also in this case, a new registration process is executed from the process of S3 in FIG. After executing the new registration process, the install ID is stored in the install ID storage unit 23 in S11.
, The process proceeds to S12. Also, install ID
Since the installation ID is stored in the storage area 14, the process ends without activating the installation unit 3. Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 8. However, even if the software 11 of the software installation medium 1 is copied to the secondary storage device 28 by any method, the software ID and the version I
D and the installation ID are also copied from the software installation medium 1 to the secondary storage device 28. Accordingly, the process proceeds from S42 to S43 shown in FIG. 6, and the software is abnormally terminated, so that illegally copied software cannot be used.

(5) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25
Each ID is stored in the software ID storage unit 24 in a combination that has no ID in the installation ID storage area 14 and the same ID as the software ID in the software ID storage area 12.
The version ID stored in the storage area 13 is
When the combination is newer than the version ID in the version ID storage unit 25. That is, for the computer system 2 in which the software 11 in the software installation medium 1 has already been installed, using the software installation medium 1 provided in a formal manner,
This is a case where the software 11 is upgraded and installed again.

In this case, the software ID storage area 1
Since the same ID as the second software ID exists in the software ID storage unit 24, the process proceeds to S5 in FIG. The ID number input / output means 22 acquires the version ID from the version ID storage area 13 for the software 11 (S5), and then the version paired with the software ID acquired in S2 from the version ID storage device in the computer system 2. The ID is read (S6). S
5 and the version IDs read in S6 are compared, and software 11 to be installed from now on is compared.
Of the new and old software and the software 29 installed in the secondary storage device 28 (S7).

In this example (5), the version ID storage area 1
3 is newer than the version ID stored in the version ID storage unit 25.
It is determined that the version has been upgraded, and the version upgrade process shown in FIG. 4 is executed (S9). When this version upgrade processing is executed, the ID number input / output means 22 performs the processing of S21 to S24 shown in FIG. In this example (5), since the installation ID is not stored in the installation ID storage area 14, it is determined in S21 that the installation ID is not stored in the installation ID storage area 14, and the installation ID is registered in the installation ID storage area 14 in S22. Execute the processing to be performed.

Here, the ID number input / output means 22 newly assigns the installation ID to the installation ID number generation means 21.
The installation ID stored in the installation ID storage unit 23 of the computer system 2 is read and stored in the installation ID storage area 14 corresponding to the software 11 in the software installation medium 1. Store. Next, in S23, a version ID is acquired from the software installation medium 1, and the version ID in the version ID storage device paired with the software ID in the software ID storage unit 24 acquired in S2 is updated. After that, the installation unit 3 is started in S25, and the software 11 is installed in the secondary storage device 28.

In this example (5), the above processing updates the version ID storage unit 25 using the same version ID as the version ID stored in the software 29 installed in the secondary storage device 28, and , Software ID,
Since it is known that D exists, the verification of the coincidence of the IDs in S42 has the same result, and the process proceeds to S44.
The software 29 can be executed.

(6) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25,
Each ID is stored in the installation ID storage area 14 and the software ID in the software ID storage area 12
Exists in the software ID storage unit 24,
The version ID stored in the version ID storage area 13 is newer than the version ID in the version ID storage unit 25, and the combination of the combination in which the contents of the installation ID storage area 14 and the contents of the installation ID storage unit 23 match. Case. That is, once the software 11 in the software installation medium 1 is once installed in the computer system 2, the old version of the same software is intentionally installed for some reason, and then the software installation medium 1 stored for backup is used. And then again software 1
1 is installed.

In this case, the process proceeds from S3 shown in FIG. 2 to S5. In S5 and S6, the respective version IDs are acquired, and in S7, the new and old relations are verified. In this example (6), the version ID stored in the version ID storage area 13 is the version ID storage. Since the version ID is newer than the version ID in the unit 25, it is determined that the version is upgraded, and the version upgrade process shown in FIG. 4 is executed. When this version upgrade process is executed, since the ID is stored in the installation ID storage area 14, S
After step S21, the process of S24 is executed. In S24, it is verified whether the install ID in the install ID storage area 14 matches the install ID in the install ID storage unit 23. In this example (6), since both installation IDs match, the process proceeds to S23, where the version ID
After the update, the installation means 3 is started in S25, and the software 11 is installed in the secondary storage device 28.

In this example (6), the above processing procedure
The ID of the version ID storage unit 25 is updated using the same ID as the version ID stored in the secondary storage device 28.
Since it is known that a matching ID already exists, the verification of the matching of each ID in S42 has the same result, and S44 is executed, so that the software 29 can be executed.

(7) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25,
Each ID is stored in the installation ID storage area 14 and the software ID in the software ID storage area 12
Exists in the software ID storage unit 24,
Although the version ID stored in the version ID storage area 13 is newer than the version ID in the version ID storage unit 25,
And the contents of the installation ID storage unit 23 do not match. In other words, software 11
This is a case where the software 11 is illegally upgraded with respect to the computer system 2 on which the same type of software is already installed, for example, by using the software installation medium 1 provided for another computer system. . This situation is fully anticipated.

In this case, in S3 shown in FIG. 2, since the same software ID as the software ID in the software ID storage area 12 exists in the software ID storage unit 24, they match, and the process proceeds to S5. In S5 and S6, the respective version IDs are acquired, and in S7, the respective new and old relations are verified. In this example (7), the version I stored in the version ID storage area 13 is used.
D is the version I in the version ID storage unit 25
Since it is newer than D, it is determined to be a version upgrade, and the version upgrade process shown in FIG. 4 is executed. When this version upgrade process is executed, the ID is stored in the installation ID storage area 14, so that the process goes through S21 to S2.
Proceed to 4. In S24 of this example (7), the process ends because both installation IDs do not match. Therefore, the software 11 is not installed in the secondary storage device 28. However, the software 11 of the software installation medium 1 is stored in the secondary storage device 28 by some method.
To the installation ID storage area 14
Is also copied to the secondary storage device 28, the installation IDs do not match, and the
Is determined as mismatch, the software ends abnormally in S43, and the illegally copied software cannot be used.

(8) Each ID is stored in the installation ID storage unit 23, the software ID storage unit 24, and the version ID storage unit 25. A case where the same ID as the software ID in the storage area 12 is present in the software ID storage unit 24 and the version ID stored in the version ID storage area 13 is equal to the version ID in the version ID storage unit 25. That is, the software 11 in the software installation medium 1 is accidentally double-installed on the computer system 2 in which the software 11 has been already installed, by using the software installation medium 1 provided properly. This is the case.

In this case, as in the case of the example (1), S
The software IDs are acquired in S1 and S2, and S3
In this example (8), since the same software ID as the software ID in the software ID storage area 12 exists in the software ID storage unit 24, the two are matched. , Next S5
The processing moves to In S5 and S6, as in the case of the example (5), the respective version IDs are acquired, and in S7, each new / old relationship is verified. In this example (8),
The version ID stored in the version ID storage area 13 and the version I in the version ID storage unit 25
Since D is equal, it is determined that the backup medium is to be re-registered, and the backup medium registration processing shown in FIG. 5 is executed. When this backup medium registration process is executed, the ID
The number input / output means 22 performs the processing of S31 to S33 shown in FIG. As described above, in this example (8), the installation ID is stored in the installation ID storage unit 23,
Since the installation ID is not stored in the installation ID storage area 14, it is determined in S31 that the installation ID is stored, and in S32, it is determined that the installation ID is not stored. To end. Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 28.

Also, in this example (8), the software 29 in the secondary storage device 28 was destroyed by some accident, and the software installation medium stored for backup was also damaged. It may be unavoidable that the software installation medium 1 has been newly provided. Therefore, instead of completing the process immediately after ending S32, after ending S32,
"Double registration of new software / installation medium 1"
May be displayed to prompt the operator whether to perform the installation process by the installation unit 3 in S34.

In this example (8), the same software that is to be installed in the secondary storage device 28 has already been installed as the software 29 by the above processing, and processing such as updating each ID has not been executed. Therefore, the verification of each ID in S42 is the same, and when the loader 26 is executed, S44 is executed and the software 2
9 can be executed.

(9) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25,
Each ID is stored in the installation ID storage area 14 and the software ID in the software ID storage area 12
Exists in the software ID storage unit 24,
The version ID stored in the version ID storage area 13 and the version I in the version ID storage unit 25
D are equal, the contents of the installation ID storage area 14 are:
In the case of a combination in which the contents of the installation ID storage unit 23 match. That is, with the software installation medium 1 provided to the computer system 2 properly,
This is a case where the software 11 has been installed, but the software 29 of the secondary storage device 28 has been destroyed or the like, and the software 11 has been reinstalled using the same software installation medium 1 used for backup.

In this case, the respective software IDs are acquired in S1 and S2 shown in FIG. 2, and it is verified in S3 whether or not they match. In this example (9), the software ID in the software ID storage area 12 is Since the same software ID exists in the software ID storage unit 24, they match, and the process proceeds to S5. And
At S5 and S6, the respective version IDs are obtained, and at S7
In this example (9), the version ID stored in the version ID storage area 13 is equal to the version ID in the version ID storage unit 25. The registration processing is determined, and the backup medium registration processing shown in FIG. 5 is executed. When this backup medium registration process is executed,
Since the installation ID is stored in the installation ID storage unit 23 and the installation ID storage area 14,
31 and S32, and in S33, both installation IDs
Is compared. In S33, it is verified whether or not the install ID in the install ID storage area 14 matches the install ID in the install ID storage unit 23. In this example (9), since both installation IDs match, the process proceeds to S34, where the installation unit 3 is started, and the software 11 is installed in the secondary storage device 28.

In this example (9), by the above processing, the installation ID, software ID, and version ID for the software 11 in the software installation medium 1 are all stored in the installation ID storage unit 23, the software ID storage unit 24, and the version ID storage device. 15 are found to match the IDs stored in the respective IDs, the verification of the matching of the IDs in S42 has the same result. When the loader 26 is executed, S44 is executed.
The software 29 can be executed. (10) Install ID storage unit 23, software I
Each ID is stored in the D storage unit 24, the version ID storage unit 25, and the installation ID storage area 14, and is the same ID as the software ID in the software ID storage area 12.
Exists in the software ID storage unit 24 and is stored in the version ID storage area 13;
A combination in which the version IDs in the version ID storage unit 25 are equal and the contents of the installation ID storage area 14 and the contents of the installation ID storage unit 23 do not match. That is, the same software as the software 11 in the software installation medium 1 is provided to the computer system 2 already installed in the secondary storage device 28 of the computer system 2, for example, for another computer system. Using the software installation medium 1, the software 11
Is to be restored from the backup medium.

In this case, the respective software IDs are acquired in S1 and S2, and whether or not they match each other is verified in S3. In this example (10), the software ID is obtained.
The same software I as the software ID of the storage area 12
Since D exists in the software ID storage unit 24, they match, and the process proceeds to S5. In S5 and S6, each version ID is set in the same manner as in the case shown in the example (5).
Is acquired, and each new and old relationship is verified in S7.
In this example (10), since the version ID stored in the version ID storage area 13 is equal to the version ID in the version ID storage unit 25, it is determined that the backup medium is to be re-registered, and the backup shown in FIG. Execute the medium registration process. When this backup medium registration processing is executed, it can be determined through S31 and S32 that both installation IDs do not match in S33, so that the processing is terminated without activating the installation means 3. Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 28.

Even if the software 11 of the software installation medium 1 is copied to the secondary storage device 28 by any method, the installation ID of the installation ID storage area 14 is also transferred from the software installation medium 1 to the secondary storage device 28. Since the installation IDs are copied, the installation IDs do not match, which is determined in the processing of S42 of the loader 26, and the software ends abnormally in the processing of S43, so that the illegally copied software cannot be used.

(11) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 25
Each ID is stored in the installation ID storage area 14, and the same ID as the software ID in the software ID storage area 12 exists in the software ID storage unit 24 in a combination where no ID is stored.
The case where the version ID stored in the D storage area 13 is a combination older than the version ID in the version ID storage unit 25. In other words, although the software installation medium 1 is provided for the new installation, the installation destination computer system is incorrect, and the already installed software 29 is installed in the computer system 2 in which the same type of software is already installed. You are trying to install an older version of the software.

In this case, the respective software IDs are acquired in S1 and S2, and it is verified whether or not they match each other in S3. In this example (11), the same software ID as the software ID in the software ID storage area 12 is used. Are present in the software ID storage unit 24, the two match, and the process proceeds to S5. In S5 and S6, the respective version IDs are acquired, and in S7, each new / old relationship is verified. In this example (11), the version ID stored in the version ID storage area 13 is the version ID. Since it is older than the version ID in the storage unit 25, it is determined that there is no need to install,
The process ends without activating the installation means 3.

Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 28. Further, in such a case, despite the fact that the software version is outdated, the installation process is performed using the software installation medium 1 provided in a formal manner. It is possible that the software 29 in the file 28 needs to be returned to an older version.
Therefore, instead of completing the process immediately after ending S7, a warning message stating that "the software version in the secondary storage device is outdated" is displayed after S7 is completed, and the installation means 3 performs the installation process. The operator may be prompted to determine whether or not this is the case. The installation process at this time is equivalent to the version upgrade process shown in FIG. If the upgrade process shown in FIG. 4 is performed, the installation process is performed by the installation unit 3 in S25 through S21, S22, and S23.

(12) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 2
5, each ID is stored in the installation ID storage area 14, and the same ID as the software ID in the software ID storage area 12 exists in the software ID storage unit 24, and the version ID stored in the version ID storage area 13 Is a combination older than the version ID in the version ID storage unit 25. That is, the software 29 in the secondary storage device 28 of the computer system 2 is subjected to the version upgrade process, and the software installation medium 1 is stored as a backup medium for the computer system 2.
Because the software 29 of the secondary storage device 28 was destroyed,
When the software 11 is reinstalled using the software installation medium 1 used for backup, an old version of the backup medium may be used by mistake.

In this case, the respective software IDs are acquired in S1 and S2, and it is verified in S3 whether or not they match. In this example (12), the software ID in the software ID storage area 12 is the same as the software ID. Since they exist in the ID storage unit 24, they match, and the process proceeds to S5. At S5 and S6, the respective version IDs are acquired, and at S7, the new and old relations are verified. The version ID stored in the version ID storage area 13 is higher than the version ID in the version ID storage unit 25. , It is determined that there is no need for installation, and the process ends without activating the installation means 3.

Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 28. In such a case, since the installation process is performed using the backup software installation medium 1, it is necessary to return the software 29 in the secondary storage device 28 to an older version for some reason. It is possible that a situation has occurred. Therefore, instead of completing the process immediately after ending S7,
After the end of step S7, a warning message indicating that "the software version in the secondary storage device is outdated" may be displayed, and the operator may be prompted to determine whether or not to perform the installation process using the installation procedure 7. The installation process at this time is equivalent to the version upgrade process shown in FIG. If the upgrade process shown in FIG. 4 is performed, the installation process is performed by the installation unit 3 in S25 through S21, S22, and S23.

(13) Install ID storage unit 23, software ID storage unit 24, version ID storage unit 2
5, each ID is stored in the installation ID storage area 14, and the same ID as the software ID in the software ID storage area 12 exists in the software ID storage unit 24, and the version ID stored in the version ID storage area 13 Is older than the version ID in the version ID storage unit 25, but the content of the installation ID storage area 14 does not match the content of the installation ID storage unit 23. That is, since the software 29 of the secondary storage device 28 of the computer system 2 has been destroyed or the like, when the software 11 is reinstalled using the software installation medium 1 used as a backup, another computer system Accidentally using an old version of backup media stored as

In this case, in S1 and S2 shown in FIG. 2, respective software IDs are acquired, and in S3, it is verified whether or not the respective software IDs match.
In 3), since the same software ID as the software ID in the software ID storage area 12 is present in the software ID storage unit 24, they match, and the process proceeds to S5.
Move to At S5 and S6, the respective version IDs are acquired, and at S7, each new / old relationship is verified. The version ID stored in the version ID storage area 13 is the version ID stored in the version ID storage unit 25. Therefore, it is determined that there is no need for installation, and the process ends without activating the installation unit 3.

Therefore, the software 11 of the software installation medium 1 is not installed in the secondary storage device 28. Also, as in Examples (11) and (12),
Even if the version upgrade process shown in FIG.
After that, since the installation IDs do not match in S24, the process ends without activating the installation unit 3. Therefore, even if the software 11 of the software installation medium 1 can be copied to the secondary storage device 28, the installation ID of the installation ID storage area 14
Is also copied from the software installation medium 1 to the secondary storage device 28, in this example (13), the installation ID does not match, and this is determined in the processing of S42 of the loader 26, and the software is determined in the processing of S43. The program ends abnormally, and you cannot use illegally copied software.

The embodiment of the present invention has been described above. However, the present invention is not limited to this, and various other modifications can be made. For example, in the present embodiment, the number of software stored in the software installation medium 1 is one, but since a software ID indicating a type of software and a version ID indicating a version are provided, It is also possible to store a plurality of software on a large capacity medium.

When a medium that cannot be rewritten, such as a CD-ROM medium, is used, software itself that does not need to be written is stored in the CD-ROM medium, and an installation ID for performing a writing process is stored. Provides an installation common medium using a writable medium, for example, an FD medium, and installs the installation ID there.
Provision can be made by providing a storage area.

FIG. 7 shows such an embodiment. The installation method in this case is as follows.
Activate the OM access hand throw 410 and start the CD-ROM medium 1
The software ID and the version ID are read from the software ID storage area 111 and the version ID storage area 112 in 00, a list of registered software in the CD-ROM medium 100 is displayed, and an operator is prompted for an instruction as to which software to install.

When it is determined what software is to be installed, the software ID and the version ID of the selected software are stored in the CD-ROM access means 410 in order to identify the selected software. deep. The ID number input / output means 220 confirms that the install ID for another computer system is not stored in the install ID storage area 411, and then the install ID number generating means 210 sends the install ID from the install ID storage unit 221. Obtain,
It is stored in the installation ID storage area 411 in the installation common medium 400.

Thereafter, the software ID storage area 111 of the software 110 and the version ID storage area 112
ID and version ID stored in
Is stored in the software ID storage unit 222 formed in the BUM in the computer system 200,
The storage means 223 respectively stores the information in the installation unit 30
Start 0. Upon receiving this request, the installation means 300 stores the software in the CD-ROM medium 100
To install in the secondary storage device 280 from C
The D-ROM access unit 410 is started. CD-RO
When the M access unit 410 receives the activation from the installation unit 300, the M access unit 410
D and the version ID, the CD-ROM medium 10
0 is copied to the secondary storage device 280.

When the copying of the software 110 is completed, the installation means 300 stores the contents of the installation ID storage area 411 in the installation common medium 400 into the installation ID storage area 283 in the secondary storage device 280.
Copy to 0. As a result, even if it is not possible to directly write the installation ID on the CD-ROM medium 100 used as the software installation medium, the software 11 storing the IDs in the secondary storage device 280 can be used.
0 etc. can be installed. When an installation common medium provided for another computer system is used, the ID number input / output unit 220 verifies the inside of the installation ID storage area 411 during the installation initial processing, and
It can be determined that they do not match, so that unauthorized copying can be prevented. Even if the software can be maliciously copied from the CD-ROM medium 100, the software cannot be executed because the installation ID storage area 2830 is blank.

[0061]

As is apparent from the above description, according to the present invention, even if a software installation medium provided for a certain computer system is left, the software installation medium is installed in another computer system. Since installation cannot be performed using a medium, it is possible to prevent software from being illegally copied while securing a backup. In addition, there is an effect that it is possible to prevent the same software from being installed twice in a computer system by mistake and becoming unusable in another system.

Further, by registering a plurality of software using a large capacity medium, it is not necessary to generate a medium for each type of software, and it is possible to perform mass production in a lump, thereby realizing a reduction in production cost. be able to.

[Brief description of the drawings]

FIG. 1 is a block diagram of one embodiment of the present invention.

FIG. 2 is an explanatory view of a procedure of common processing at the time of software installation.

FIG. 3 is an explanatory diagram of a processing procedure when newly registering software.

FIG. 4 is an explanatory diagram of a processing procedure when software is upgraded.

FIG. 5 is an explanatory diagram of a processing procedure when software is installed from a backup medium.

FIG. 6 is an explanatory diagram of a processing procedure in a software execution stage.

FIG. 7 is a block diagram when a plurality of software are registered in one medium.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Software installation medium 2,200 Computer system 11,29,290 Software 3,300 Installation means 12,111 Software ID storage area 13,112 Version ID storage area 14,113,411 Installation ID storage area 21,210 Installation ID number Generation means 22, 220 Installation ID number input / output means 23, 221 Installation ID storage unit 24, 222 Software ID storage unit 25, 223 Version ID storage unit 26, 226 Loader 27, 227 ID number comparison unit 28, 280 Secondary storage device 100 CD-ROM media 281, 2810 Software ID storage area 282, 2820 Version ID storage area 283, 2830 Installation ID storage area 400 Installation Common media 410 CD-ROM access means

Claims (5)

[Claims] 1. A method for installing software stored in a storage medium into a storage device of a computer system having a non-volatile memory, wherein an installation ID indicating whether the software is installed is stored in the storage medium. Install I
D storage area, software I indicating the type of software
D, and a version ID storage area for storing a version ID indicating the version of the software. A non-volatile memory stores the installation ID, the software ID, and the version ID. Form a storage area,
Further, in the computer system, an installation ID generating means for generating the installation ID at the time of the first installation of the software, and storing the generated installation ID in an installation ID storage area of the storage medium and an installation ID of the nonvolatile memory.
D storage area and the software ID
Means for reading the corresponding software ID from the storage area and writing the same in the software ID storage area of the non-volatile memory, and reading the corresponding version ID from the version ID storage area and writing the same in the version ID storage area of the non-volatile memory And a software installation method characterized in that: 2. A storage area for the installation ID, the software ID, and the version ID is formed in a storage device of the computer system,
When the software is installed, it verifies the matching between each ID stored in the storage medium and each ID stored in each storage area, and determines whether the installation can be performed based on the verification result. 2. The installation method according to claim 1, further comprising means for determining 3. The computer system further comprises:
2. The apparatus according to claim 1, further comprising: an interface unit that displays a predetermined message at the time of installing the software and receives a response result to the message, and determines whether to execute the installation based on the received response result. Or the installation method described in 2. 4. A method for installing software stored in a storage medium into a storage device of a computer system having a non-volatile memory, comprising: a rewritable common medium accessible to the storage medium. At least an installation ID storage area for storing an installation ID indicating whether or not the software has been installed is formed. A software ID storage area for storing a software ID indicating the type of the software in the storage medium and a version of the software are defined. A storage area for the installation ID, the software ID, and the version ID in the nonvolatile memory, and a storage area for the installation ID, the software ID, and the version ID. Sof And installing ID generating means for generating the install ID during the initial installation of the wear, the installation of the installation ID generated installation ID storage area of said common medium said non-volatile memory I
D storage area and the software ID
Means for reading the corresponding software ID from the storage area and writing the same in the software ID storage area of the non-volatile memory, and reading the corresponding version ID from the version ID storage area and writing the same in the version ID storage area of the non-volatile memory And a software installation method characterized in that: 5. An execution method of software installed in a storage device of a computer system having a non-volatile memory, the installation method storing an installation ID indicating whether or not the software is installed in the storage device. An ID storage area, a software ID storage area for storing a software ID indicating a type of software, and a version ID storage area for storing a version ID indicating a version of the software, and the software Forming a storage area of the installation ID, the software ID, and the version ID input at the time of installation of
Further, the computer system verifies the matching between each ID stored in each storage area and each ID stored in the nonvolatile memory, and determines whether to execute the software based on the verification result. A software execution method characterized by providing a means for executing software.