JP7289940B2 - Program set, storage medium, and information processing method - Google Patents

Description

The present invention relates to a program, an information processing apparatus, and a control method for installing application software.

In recent years, as application software has become larger and more complex, there has been an increase in the number of products that require multiple installers to be executed in the correct order in order to operate one piece of application software. However, it is not necessarily easy for users with low IT literacy to execute the installer in the correct order.

Therefore, Japanese Patent Application Laid-Open No. 2002-200000 describes that a server computer performs a conflict check (consistency check) according to the installation order when installing a plurality of pieces of software. According to Patent Document 1, a user can install desired application software without being aware of the execution order of installers.

JP 2012-48410 A

However, if the user activates the application software being installed while executing multiple installers in succession, the installation process may fail.

For example, if a user purchases application software that includes a service pack, the product may come with a base installer and a service pack installer. In general, installers with such a configuration often start the service pack installation process automatically after the base installation process is completed. In this case, a shortcut is created on the desktop screen of the OS (Operating System) when the base installation process is completed. Therefore, the user can easily start the application software from the shortcut during installation of the service pack.

Here, when the user starts the application software being installed, the OS loads and locks the modules necessary for executing the application software. As a result, the service pack installer cannot update the service pack module, resulting in a failure of the service pack installation process.

It is also possible to update modules that could not be updated by the service pack installer after restarting the software. However, even though the user has purchased the application software including the service pack, the user temporarily uses the "product with no bug-fix applied" or "the product with only the base function that does not yet have new functions". I don't like doing it.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to prevent a process for starting the installed application software before starting an installer for additionally installing the already installed application software.

In order to solve the above problems, a program set of the present invention is a program set including at least a first installer executable by an information processing device, the first installer for installing application software. The program set includes a second installer for causing the information processing apparatus to perform a first installation process of and further to perform a second installation process for updating the application software and causing the information processing apparatus to execute the second installer, and if the second installer is not included in the set of programs, the shortcut of the application software is installed in the first installation process. is created after the completion of the first installation process, while if the set of programs includes the second installer, the shortcut for the application software is not created after the first installation process is completed and the second installation process is completed. is created after the installation process is completed.

According to the present invention, the process for starting the installed application software can be prevented from being executed before starting the installer for additionally installing the already installed application software.

Diagram showing hardware configuration example Diagram showing software configuration example Diagram showing an example of setup information related to the installer Flowchart showing processing of the first embodiment Flowchart showing processing of the second embodiment Flowchart showing processing of the third embodiment

The present invention realizes a shortcut creation method for preventing application software from being started while the user is executing the installer.

BEST MODE FOR CARRYING OUT THE INVENTION The best mode for carrying out the present invention will be described below with reference to the drawings.

[Hardware configuration]
FIG. 1 is a diagram showing a hardware configuration example in one embodiment of the present invention. FIG. 1 shows a hardware configuration example of an information processing apparatus 100, which is a computer. The information processing apparatus 100 is provided with a keyboard 105 and a pointing device 106 which are input devices for receiving user operation inputs.

A keyboard 105 is a device for inputting information such as characters and numbers to the information processing apparatus 100 . The keyboard includes, for example, keys for inputting kana and English letters, ten keys for inputting numbers, various function keys, cursor keys, and other keys.

The pointing device 106 includes, for example, a mouse. When a user operates the information processing apparatus 100 using a GUI (Graphical User Interface) or the like, the user can input predetermined information by clicking buttons or icons displayed on the display device with a mouse. can. For example, the information processing apparatus 100 displays an icon representing installed application software on the display unit 102, and the CPU 101 activates the application software in response to the user clicking the icon with a mouse. Additionally, a display 102 is provided to provide visual output information feedback to the user.

The display unit 102 displays various information on a screen including, for example, a CRT (Cathode Ray Tube) display, a liquid crystal display, or a plasma display. The display unit 102 displays keyboard and mouse input results, screens (for example, user interfaces) provided by installers and application software, and the like.

Further, the information processing apparatus 100 includes a CPU 101, a RAM 103, a ROM 104, and an HDD 107, which are means for controlling operations. As operations specific to this embodiment, the CPU 101 controls operations of the plurality of installers 200 and 210 shown in FIG. The CPU 101 executes each installer of the information processing apparatus 100 and performs various calculations, information processing, and control processing of the entire information processing apparatus 100 according to a predetermined program.

The RAM 103, ROM 104, and HDD 107 store various programs and execution information in this embodiment. A DVD/CD-ROM driver 108 is also provided for reading data recorded on a DVD/CD. The RAM 103 is loaded and executed by the CPU 101 with an OS (Operating System) and other control programs including a control program for realizing this embodiment. It also functions as various work areas and temporary save areas used to execute control programs. In this embodiment, an area is reserved in the RAM 103 for the CPU 101 to start the installer and perform internal processing of the system. The ROM 104 is a storage device that stores various control programs for executing various controls of the CPU 101, data, parameters, and the like.

The HDD 107 includes a readable/writable storage medium and a drive device for reading/writing programs and data from/to the storage medium. In this embodiment, the HDD 107 is a local disk with a hard disk. Note that the storage medium included in the HDD 107 may be a magneto-optical disk, a magnetic disk, a semiconductor memory, or the like. The HDD 107 stores a plurality of installers 200 and 210 shown in FIG. The HDD 107 also stores a communication program that controls the interface device I/O 109 and maintains communication via the network. The HDD 107 also stores an OS, which is basic application software for operating the client such as memory management and file input/output management.

Furthermore, it has an interface device I/O 109 that communicates with an external device, and a CPU 101 that executes a program. The form of connection with the peripheral device may be wired or wireless. The interface device I/O 109 connects to other terminals (web server, mail server, etc.) via a network (eg, LAN or Internet). For example, a protocol such as TCP/IP is used for communication via the Internet.

The processing described in this embodiment is realized by loading programs, execution information, and temporary data stored in the ROM 104 or HDD 107 into the RAM 103 and executing them by the CPU 101 .

[Software configuration]
FIG. 2 is a diagram showing a configuration example of software.

The information processing apparatus 100 includes a plurality of installers (first installer 200, second installer 210). Note that, in this embodiment, the installer 210 has the same configuration as the installer 200, and redundant information will be omitted.

Here, the first installer 200 and the second installer 210 are generally stored on a DVD, CD, or the like by the creator of the application software, or converted into an archive file and uploaded to a Web page or the like. . There are two patterns of installer distribution methods: a single installer format in which a single installer is distributed separately, and a multiple installer format in which a plurality of installers are distributed together. For example, when a service pack for application software is released and two installers for the base and the service pack are distributed as one, the multiple installer format is used. If the base has already been installed on the user's PC, and a later released service pack is to be additionally installed, the service pack installer will be distributed in the form of a single installer. It can be said that the first installer 200 and the second installer 210 as shown in FIG. 2 are an installer set distributed in a multiple installer format.

Each configuration included in the information processing apparatus 100 will be described.

The installer 200 has various user interfaces for installing and executing application software, receives requests from users on the desktop of the information processing apparatus 100, and comprehensively manages the execution of each function process.

Installer 200 has display unit 201 and control unit 202 . The components that make up each installer are explained.

The display unit 201 constructs the user interface of the installer 200 . It also processes acceptance of various input operations from the user via the GUI.

The control unit 202 has functions for overall processing related to installer control. For example, on the basis of receiving various input operations from the user, application software (not shown) is installed, uninstalled, or repaired, and application settings and construction are performed. Also, the control unit 202 analyzes setting information regarding the installer of the information processing apparatus 100 . The setting information indicates, for example, installer information 300 and registry information 320 managed by each installer. Details of the setting information will be described later with reference to FIG.

Furthermore, when installing the application software, the control unit 202 executes a process of enabling acceptance of user input for starting the already installed application software. As an example of the processing, the control unit 202 creates a shortcut for receiving user input for starting application software on the desktop screen provided by the OS of the information processing apparatus. As another example of processing, the control unit 202 may display application software in a list on the menu screen, or associate extensions with files.

Note that the installer 200 is an installer for installing the basic functions of the application software in the information processing apparatus. An installer 210 having a display unit 211 and a control unit 212 is a service pack installer for additionally installing application software. Additional installation in the service pack installer includes, for example, bug fixes and security enhancements for basic functions in the base installer, and addition of functions that are upgraded versions of the base functions. On the other hand, the installer 210 in the second embodiment, which will be described later with reference to FIG. 5, is treated as an installer for installing optional functions as additional installation of application software. In the optional function installer, additional functions that are not included in the base function and can be customized and added by the user are installed. The control unit 212 of the service pack installer, like the control unit 202 of the base installer, is capable of executing a process of enabling acceptance of user input for starting already installed application software. For example, the control unit 212 has a shortcut creation function. On the other hand, the optional function installer control unit 212 does not have a function of executing a process of enabling acceptance of user input for starting already installed application software, and therefore cannot create a shortcut.

The processing described in this embodiment is implemented by loading a program stored in the ROM 104 or HDD 107 into the RAM 103 and executing it by the CPU 101 .

[Installer setting information]
FIG. 3 shows an example of setting information about the installer.

The setting information about the installer includes installer information held by the installer and registry information held by the OS. These pieces of information are used together in the installation process of each installer.

First, the installer information 300 shown in FIG. 3A will be described. The installer information 300 is setting information necessary for installation processing of the installer 200 and is information held by the installer 200 . The setting information includes, for example, InstallerVersion 301, ProductCode 302, UpgradeCode, and the like. Similarly, the installer information 310 shown in FIG. 3B is setting information necessary for the installation process of the installer 210 and is information held by the installer 210 . Note that, in this embodiment, the installer information 310 has the same configuration as the installer information 300, and redundant description of the information will be omitted.

Each item of the installer information 300 will be described. InstallerVersion 301 indicates the version of application software that can be installed by the installer 210 . Generally, the version of application software consists of three values: major version, minor version, and revision (service pack version). For example, if the major version value is "3", the minor version value is "0", and the revision value is "0", the application software version is "3.0.0". Since the value of InstallerVersion 301 in this embodiment is "3.0.0", the installer 200 installs version 3.0.0 of the application software. Also, since the value of InstallerVersion 311 of the installer information 310 is "3.0.1", the installer 210 installs version 3.0.1 of the application software.

ProductCode 302 is a unique number or character string used for identifying application software. This value is written by installer 200 to ProductCode 322 of registry information 320 . Generally, when releasing a service pack applicable to released application software, the ProductCode 302 and UpgradeCode are not changed. That is, when a service pack is installed, the value of ProductCode 322 and the value of UpgradeCode written in registry information 320 are not changed. If the second installer 210 is an optional function installer, the ProductCode and UpgradeCode are different from the values held by the first installer 200 (not shown). If the values are different, the application software installed by the first installer 200 and the second installer 210 respectively have no upgrade dependencies. The ProductVersion 323 and ProductCode 324 will be described in the second embodiment.

Taking FIG. 3 as an example, the installer 200 with the installer information 300 is the base, and the installer 210 with the installer information 310 is the service pack for the base.

Next, the registry information 320 shown in FIG. 3(c) will be described. Registry information 320 indicates an example of a registry information list held by the OS of the information processing apparatus 100 .

The registry information 320 is information on application software installed in the information processing apparatus 100 and is stored in the ROM 104 . For example, the registry information 320 includes Application Software ProductVersion 321, ProductCode 322, UpgradeCode, installation path, and the like. Also, the registry information 320 manages a plurality of application software. Taking FIG. 3 as an example, the registry information 320 includes two pieces of application software: base application software and optional function application software for the base. Specifically, ProductVersion 321 and ProductCode 322 are information relating to the registry information of the base application software. ProductVersion 323 and ProductCode 324 are information on the registry information of application software for optional functions for the base. Note that redundant description of the two ProductVersions and ProductCodes included in the registry information 320 will be omitted.

Each item of the registry information 320 will be described. ProductVersion 321 indicates the version of the base application software installed in the information processing apparatus 100 . For example, if the value of ProductVersion321 is "3.0.0", it means that version 3.0.0 of the application software is installed.

Here, when the service pack is installed, the revision value is "1" or more. Therefore, in the example shown in FIG. 3C, since the revision value is "0", it can be determined that the service pack has not been installed.

ProductCode 322 is a unique number or character string used for identification of application software. If the ProductCode 302 of the application software exists in the registry information 320, it means that the application software has been installed.

Information held by the installer information and the registry information is not limited to this embodiment.

[Processing of Each Installer in Embodiment 1]
In the first embodiment, a method for solving the problem when the first installer 200 and the second installer 210 are continuously executed will be described. In the first embodiment, the first installer 200 is treated as a base installer, and the second installer 210 is treated as a service pack installer.

First, problems in the first embodiment will be described. When the two installers for base and service pack are executed consecutively, the service pack installation process may fail. Specifically, when two installers are executed consecutively, the base installer first creates a shortcut on the desktop screen of the OS. After that, the service pack installer is executed, and when the execution of the base installer is completed, the user can give an instruction to start the application software from the shortcut created on the desktop screen of the OS. Here, if the application software is started while the service pack installer is running, the service pack installer may not be able to update the modules of the application software, and the installation process may fail.

Here, a method for dynamically changing the shortcut creation timing according to the installer configuration for solving the above-described problem will be described.

[Processing of Each Installer in Embodiment 1]
FIG. 4 is a flowchart of the base installer 200 and service pack installer 210 processing. The flow of processing will be described using the installers 200 and 210 operating on the information processing apparatus 100 in FIG. 1 as an example. The flow chart shown in FIG. 4 shows a technique for performing dynamic shortcut creation processing in the installer. Also, each step from S1001 to S1010 is processed by the installer 200, and each step from S1101 to S1103 is processed by the installer 210. FIG.

FIG. 4A is a flow chart showing the flow of processing by the installer 200, which is the base installer.

When the installer 200 is activated, in S1001, the control unit 202 determines whether application software installable by the installer 200 is not installed. If yes (not installed), go to S1002; if no (not installed), go to S1003.

The determination logic in S1001 will be specifically described. Control unit 202 acquires registry information 320 . Based on the registry information 320 and the installer information 300 , the control unit 202 analyzes whether the ProductCode 302 held by the installer information 300 exists in the registry information 320 . If the ProductCode 302 exists in the ProductCode 322 of the registry information 320, it is determined that the base application software is not installed, and the process proceeds to S1003. On the other hand, if the ProductCode 302 does not exist in the ProductCode 322 of the registry information 320, or if the registry information 320 does not exist, it is determined that the base application software has not been installed, and the process proceeds to S1002.

Next, in S1002, the control unit 202 turns ON the installation execution flag of the base application software.

Next, in S1003, it is determined whether or not there is an uninstalled service pack in the installer set of the multiple installer format. If yes (exists), proceed to S1004; otherwise, proceed to S1005.

The determination logic in S1003 will be specifically described. First, the control unit 202 acquires the service pack installer information 310 . If the installer information 310 cannot be obtained here, it is determined that the service pack installer 210 does not exist, and the process proceeds to S1005. Next, the control unit 202 acquires registry information 320 . Based on the service pack installer information 310 and the registry information 320 , the control unit 202 analyzes whether the ProductCode 312 held by the installer information 310 exists in the registry information 320 . If the ProductCode 302 does not exist in the ProductCode 322 of the registry information 320, or if the registry information 320 does not exist, it is determined that there is an uninstalled service pack, and the process proceeds to S1004. On the other hand, if the ProductCode 302 exists in the ProductCode 322 of the registry information 320, the InstallerVersion 311 and the ProductVersion 321 are further compared. Here, for example, each revision value is compared. As a result of the comparison, if the InstallerVersion 311 is greater, it is determined that there is an uninstalled service pack, and the process advances to S1004. On the other hand, if the InstallerVersion 311 is smaller or the same, it is determined that there is no uninstalled service pack, and the process advances to S1005.

Next, in S1004, the control unit 202 turns ON the installation execution flag of the application software of the service pack.

Next, in S1005, the control unit 202 determines whether there is one or more application software to be installed. Here, the "base application software installation execution flag" and the "service pack application software installation execution flag" are used for the determination logic in S1005. If at least one of the flags is ON, it is determined to install some application software. If yes (exists), the process advances to S1006; if no (does not exist), the processing of this flowchart ends.

Next, in S1006, the control unit 202 determines whether the installation execution flag of the base application software is ON. If yes (the installation execution flag is ON), the process proceeds to S1007; if No (the installation execution flag is OFF), the process proceeds to S1008.

Next, in S1007, the control unit 202 installs the basic functions of the application software. The installation process executed in S1007 is file copying and registry registration of the application software. Note that the control unit 202 does not create a shortcut after the installation executed in S1007 is completed. The shortcut will be created after the installation of additional functions by the service pack installer, which will be described later, is completed.

Next, in S1008, the control unit 202 determines whether the installation execution flag of the application software of the service pack is ON. If yes (the installation execution flag is ON), the process advances to S1009, and if No (the installation execution flag is OFF), the process advances to S1010.

Next, in S1009, the control unit 202 activates the installer 210 for installing the service pack, and executes processing by the installer 210 (FIG. 4B). In other words, in S1009, when installing the application software, the control unit 202 activates the installer 210 without executing processing for enabling acceptance of user input for activation of the installed application software.

Next, in S1010, the control unit 202 creates a shortcut of the application software on the desktop screen of the OS, and the process of the installer 200 ends.

FIG. 4B is a flow chart showing the flow of processing by the installer 210, which is the service pack installer.

When the installer 210 is activated by the installer 200 in S1009, the controller 212 installs additional functions of the application software in S1101. The installation processing executed in S1101 is processing for copying application software files and registry registration processing, and does not include shortcut creation processing.

Next, in S1102, the control unit 212 determines whether there is a shortcut of the application software on the desktop screen of the OS. If yes (exists), the process of installer 210 ends. If no (does not exist), proceed to S1103.

Next, in S1103, the control unit 212 creates a shortcut of the application software on the desktop screen of the OS, and the process of the installer 210 ends.

Note that after the service pack installation process in S1101 is completed, the shortcut may be created by the base installer instead of the service pack installer.

Also, if only the base application software has been installed in advance, a shortcut of the application software has already been created on the desktop screen of the OS. However, the user may have deleted the shortcut from the desktop screen of the OS. Therefore, in the processing of S1102 and S1103 executed by the service pack installer, it may be determined whether or not the shortcut created by the base installer needs to be repaired, and repaired if necessary.

The method of dynamically changing shortcut creation timing according to the installer configuration has been described above. As a result, when the two installers for the base and service pack are executed consecutively, the service pack installer can create a shortcut without creating a shortcut with the base installer. Therefore, regardless of the configuration of the installer, shortcut creation is uniformly performed at the end of the installation process, and the user does not start the application software from the shortcut during installation. As a result, it is possible to prevent the activation operation of the application software during the installation.

[Processing of Each Installer in Second Embodiment]
In a second embodiment, a method for solving the problem when the first installer 200 and the second installer 210 are executed continuously will be described. In the second embodiment, the first installer 200 is treated as a base installer, and the second installer 210 is treated as an optional function installer.

A problem in the second embodiment will be described. An optional function installer is an installer that can install optional functions to the base application software. Generally, the optional function installer only installs the optional function for the base, and there is no processing for creating a shortcut of the base application software. Therefore, as with the problem of the first embodiment, if two installers for the base and optional functions are executed consecutively, the user may start the application software before the optional functions are enabled. .

In a second embodiment, a method for dynamically changing the shortcut creation timing according to the installer configuration for solving the above problem will be described.

[Processing of Each Installer in Second Embodiment]
FIG. 5 is a flow diagram of the processing of the base installer 200 and optional feature installer 210 . The flow of processing will be described using the installers 200 and 210 operating on the information processing apparatus 100 in FIG. 1 as an example. This flow shows a technique for dynamically creating shortcuts in the installer. Also, each step from S1001 to S1010 is processed by the installer 200, and each step from S1101 to S1103 is processed by the installer 210. FIG. Note that the description of the parts that overlap with the steps of the flowchart shown in FIG. 4 will be omitted.

FIG. 5(a) is a flow chart showing the flow of processing by the installer 200, which is the base installer.

In S2003, it is determined whether or not there is an optional function that has not been installed in the multiple-installer format installer set. If yes (exists), proceed to S2004; otherwise, proceed to S2005.

The determination logic in S2003 will be specifically described. First, the control unit 202 acquires the installer information 310 of optional functions. If the installer information 310 cannot be obtained here, it is determined that the optional function installer 210 does not exist, and the process proceeds to S2005. Next, the control unit 202 acquires registry information 320 . Based on the optional function installer information 310 and the registry information 320 , the control unit 202 analyzes whether the ProductCode 312 held by the installer information 310 exists in the registry information 320 .

If the ProductCode 302 does not exist in the ProductCode 324 of the registry information 320, or if the registry information 320 does not exist, it is determined that there is an uninstalled optional function, and the process proceeds to S2004. On the other hand, when the ProductCode 302 exists in the ProductCode 324 of the registry information 320, the InstallerVersion 311 of the installer information 310 and the ProductVersion 323 of the registry information 320 are compared. Here, for example, each revision value is compared. As a result of the comparison, if the InstallerVersion 311 is greater, it is determined that there is an optional function that has not been installed, and the process advances to S2004. On the other hand, if the InstallerVersion 311 is smaller or the same, it is determined that there is no uninstalled optional function, and the process advances to S2005.

Next, in S2004, the control unit 202 turns on the installation execution flag of the application software of the optional function.

Next, in S2005, the control unit 202 determines whether there is one or more application software to be installed. Here, the "installation execution flag of the base application software" and the "installation execution flag of the optional function application software" are used for the determination in S2005. If any flag is ON, it is determined to install some application software. If yes (exists), the process advances to S1006; if no (does not exist), the process of the installer 200 ends.

Next, in S2008, the control unit 202 determines whether the installation execution flag of the optional function application software is ON. If yes (the installation execution flag is ON), the process proceeds to S2009, and if No (the installation execution flag is OFF), the process proceeds to S2010.

Next, in S2009, the control unit 202 activates the installer 210 for installing the application software of the optional function, and executes the process by the installer 210 (FIG. 5B).

Next, in S2010, the control unit 202 creates a shortcut of the application software on the desktop screen of the OS, and the process of the installer 200 ends.

FIG. 5B is a flow chart showing the flow of processing by the installer 210, which is an installer of optional functions.

When the installer 210 is activated by the installer 200 in S2009, the controller 212 installs optional functions applicable to the base in S2101, and the process of the installer 210 ends. It is assumed that the installation processing executed in S2101 is processing for copying application software files and registering in the registry, and does not include shortcut creation processing. After completing the optional function installation process in S2101, the shortcut is created by the installer 200 in S2010.

The method of dynamically changing shortcut creation timing according to the installer configuration has been described above. As a result, when two installers, one for the base and one for the optional function, are executed consecutively, the shortcut can be created by the base installer after the installer for the optional function is finished. Therefore, regardless of the configuration of the installer, shortcut creation is uniformly performed at the end of the installation process, and the user does not start the application software from the shortcut during installation. As a result, it is possible to prevent the activation operation of the application software during the installation.

[Processing of Installer in Embodiment 3]
In a third embodiment, a method for solving the problem when the second installer 210 is executed alone will be described. In the third embodiment, the second installer 210 is treated as a service pack installer.

A problem in the third embodiment will be described. When the base application software is installed in advance, shortcuts are already created on the OS desktop screen. If only the service pack is installed alone in this state, the user can easily start the application software from the shortcut that exists on the desktop screen of the OS while the service pack installer is being executed. Therefore, as in the case of the first and second embodiments, when the service pack installer is executed alone, the user may start the application software before the service pack installation is completed.

In a third embodiment, a method of creating shortcuts according to the presence or absence of shortcuts for solving the above-described problem will be described.

[Processing of Each Installer in Embodiment 3]
FIG. 6 is a flow chart showing the processing flow of the service pack installer 210 . The flow of processing will be described using the installer 210 that operates on the information processing apparatus 100 in FIG. 1 as an example. This flow shows a method of executing shortcut creation processing according to the presence or absence of shortcuts in the installer.

When the boot process of the installer 210 is started, in S3001, the control unit 212 determines whether there is a shortcut of the application software on the desktop screen of the OS. If yes (exists), proceed to S3002; otherwise, proceed to S3003.

Next, in S3002, the control unit 212 deletes the shortcut of the application software existing on the desktop screen of the OS.

Next, in S3003, the control unit 212 installs the application software of the service pack applicable to the base. The installation processing executed in S3003 is processing for copying application software files and registering in the registry, and does not include shortcut creation processing.

Next, in S3004, the control unit 212 creates a shortcut of the application software on the desktop screen of the OS, and the process of the installer 210 ends.

Instead of deleting the shortcut in S3002, the display of the shortcut may be temporarily changed to indicate that the application cannot be started.

Also, the installer 210 in the third embodiment is not limited to the service pack installer. Further, in the software configuration of the third embodiment, the information processing apparatus 100 may include only the second installer 210 without including the first installer 200 (not shown).

In the above, the shortcut creation method according to the presence or absence of the shortcut has been described. As a result, if the service pack installer is run alone, the shortcut will be deleted during the service pack installation and created at the end of the installation process. Therefore, the user will not start the application software from the shortcut during installation of the service pack. As a result, it is possible to prevent the activation operation of the application software during the installation.

(Other examples)
The present invention also includes an apparatus or system configured by appropriately combining the above-described embodiments, and a method therefor.

Here, the present invention is a main device or system that executes one or more software (programs) that realize the functions of the above-described embodiments. A method for realizing the above-described embodiments executed by the device or system is also one aspect of the present invention. Also, the program is supplied to a system or device via a network or various storage media, and is read and executed by one or more computers (CPU, MPU, etc.) of the system or device. In other words, one aspect of the present invention includes the program itself or various computer-readable storage media storing the program. The present invention can also be realized by a circuit (for example, an ASIC) that implements the functions of the above-described embodiments.

Claims (7)

A set of programs including at least a first installer executable by an information processing device,
The first installer causes the information processing apparatus to perform a first installation process for installing application software, and further causes the information processing apparatus to perform a second installation process for updating the application software. is included in the program set, causing the information processing device to execute the second installer,
if the set of programs does not include the second installer, a shortcut to the application software is created after the first installation process is completed;
If the set of programs includes the second installer, the application software shortcut is not created after the first installation process is completed, but is created after the second installation process is completed. Ru
A set of programs characterized by The first installer causes the information processing apparatus to perform a first installation process for installing application software, and the second installer causes the information processing apparatus to perform the second installation process that has not yet been executed. 2. The set of programs according to claim 1, wherein the second installer is caused to be executed by the information processing apparatus when included in the set of programs. In the second installation process for updating the application software, at least one of bug correction, security enhancement, and function addition is performed on the application software installed by the first installation process. 3. A set of programs according to claim 1 or 2, characterized by: if the set of programs does not include the second installer, causing the first installer to create a shortcut for the application software after the first installation process is completed;
If the set of programs includes the second installer, the first installer installs the second installer without creating a shortcut for the application software after the first installation process is completed. causing the information processing device to execute an installer, and causing the second installer to create a shortcut of the application software after the second installation process is completed;
4. A program set according to any one of claims 1 to 3, characterized in that: if the set of programs does not include the second installer, the first installer causes a shortcut of the application software to be created after the first installation process is completed;
If the set of programs includes the second installer, the first installer installs the second installer without creating a shortcut of the application software after the first installation process is completed. creating a shortcut of the application software after the second installation process is completed by causing the information processing device to execute an installer;
A set of programs according to claim 1, characterized in that: A computer-readable storage medium storing the program set according to any one of claims 1 to 5. An information processing method performed by an information processing device executing a set of programs including at least a first installer,
a step of performing a first installation process for installing application software by the information processing apparatus executing the first installer;
When the set of programs includes a second installer for performing a second installation process for updating the application software, the information processing device executes the second installer , performing a second installation process for updating the installed application software;
if the program set does not include the second installer, the information processing device creates a shortcut of the application software after the first installation process is completed;
When the set of programs includes the second installer, the information processing apparatus performs the second installation without creating a shortcut for the application software after the first installation process is completed. creating a shortcut of said application software after processing is completed;
An information processing method characterized by:

Images