JP2002259145A - Method for executing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that the securing of resources is not achieved in succeeding program start and a program may not be executed when the resources are released at the end of the program in an architecture in which the securing of resources is limited only in a physical memory. SOLUTION: After starting an operating system, resources are secured and the resources are not released even when a program ends. By once succeeding is securing the resources by the method, the securing of the resources is maintained even when the start/end of the program is repeated.

Description

DETAILED DESCRIPTION OF THE INVENTION

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for operating a program requiring a large memory space on an architecture having a limited memory area when securing resources.

2. Description of the Related Art When a normal program is executed, an area of a predetermined size is required in a memory space to store input data, data being processed, output data, and the like.
This area is called a resource. If the resource reservation fails, the program cannot be executed. The resources of the conventional program are secured at least at the time of starting the program and released at the end of the program so as not to hinder execution of other programs. Further, there is a case where the resource is secured when it becomes necessary in the program, and released when it becomes unnecessary. At this time, areas not used simultaneously in the program can be allocated to the same memory space, and the memory space can be saved. Also, when a normal computer executes a program, when resources cannot be secured in a physical memory such as a RAM, resources can be secured as virtual memory in an external recording medium such as an HDD. The capacity of the RAM is usually 100 to 300 megabytes, whereas the capacity of the HDD is generally several tens of gigabytes at present. Therefore, even a program such as an image processing program which needs to secure resources in a continuous large memory space is required. The program can be executed without any practical problems.

However, in an architecture in which the securing of resources is limited in the physical memory, when a program that requires securing resources in a continuous large-capacity memory space is executed by a conventional method. However, the following problem occurs. If the resources are released at the same time as the termination of the program, there is a high possibility that the resources or data of another program will use the memory space to which the released resources have been allocated. After that, even if the program is started again to secure resources, the necessary resources cannot be secured, and there is a possibility that the program itself cannot be executed.

According to a first aspect of the present invention, there is provided a method for executing a program which needs to secure resources in a continuous large-capacity memory space. A resource securing step for securing resources, a program activating step for activating the program, and a program ending step for ending the program, wherein the resource securing step is executed after the operating system is activated, and when the program is requested to be activated, Executing the program starting step, and executing the program ending step when a request to end the program is issued. Further, a second invention is a method for executing a program which needs to secure resources in a continuous large-capacity memory space, comprising: a resource securing step for securing resources of the program; and a program starting step for activating the program. And a program termination step of terminating the program. Upon activation of the operating system, at the time of the first request for activation of the program, execute the memory securing step and the program activation step, and activate the program for the second time and thereafter. When requested, the program start step is executed, and when the program end request is made, the program end step is executed. Further, it is characterized in that the securing of resources is restricted within the physical memory space, and the release of resources is performed when the operating system ends.

Embodiments of the present invention will be described below with reference to the drawings. In the following description,
The operating system is referred to as OS. (First Embodiment) FIG. 1 is a flowchart for explaining a first embodiment of the present invention. In FIG. 1, 1
01 is an OS start step, 102 is a resource securing step, 103 is a start determination step, 104 is a program start step, 105 is an end determination step, 106 is a program end step, 107 is an OS end request detection step, and 108 is an OS end step. is there. The variable bPO
n is a variable that is TRUE during execution of the program and FALSE during other periods. Hereinafter, a first embodiment of the present invention will be described with reference to FIG. When the OS is started in the OS start step 101, FALS is set to bPOn.
E is set, and the process proceeds to the resource securing step 102. The resource securing step 102 secures all resources necessary for the program. In the start determination step 103,
When bPOn is FALSE and a program start request is made, the process proceeds to a program start step 104, otherwise, the process proceeds to an end determination step 105. In the program starting step 104, the program is started and the bP
After setting TRUE to On, the process returns to the beginning of the loop. In the end determination step 105, when bPOn is TRUE and a program end request is made, the process proceeds to the program end step 106, and otherwise, the process proceeds to the OS end request detection step 107. Program end step 10
At 6, the program is terminated, FALSE is set to bPOn, and the process returns to the beginning of the loop. The OS termination request detection step 107 returns to the beginning of the loop if an OS termination request is not made, and if an OS termination request is made, proceeds to the OS termination step 108, where the OS is terminated and resources are automatically released. You. As described above, the first aspect of the present invention
In the embodiment, when a program that requires a continuous large-capacity memory space as a resource is operated in an architecture in which resource reservation is limited to physical memory, the necessary resource reservation is performed immediately after the OS is started. Then, by continuing to secure resources until the OS ends, the resources are not eroded by other programs or data. Therefore, it is possible to always start the program if there is a program start request. (Second Embodiment) FIG. 2 is a flowchart for explaining a second embodiment of the present invention. In FIG. 2, 2
01 is an OS boot step, 202 is a boot determination step,
203 is a first determination step, 204 is a resource securing step, 205 is a program start step, 206 is an end determination step, 207 is a program end step, 20
8 is an OS termination request detection step, and 209 is an OS termination step. The variable bFirst is TRUE when the resource is not secured, and is FALSE when the resource is secured. BPOn is a variable similar to that of the first embodiment. Hereinafter, a second embodiment of the present invention will be described with reference to FIG. When the OS is started in the OS start step 201, FALS is added to bPOn.
TRUE is set to E and bFirst. In the start determination step 202, when bPOn is FALSE and a program start request is made, the first determination step 203
Otherwise, the process proceeds to the end determination step 206. In the first determination step 203, bFirst is set to TR
If it is a UE, proceed to the resource securing step 204,
All resources required for program execution are secured and bF
After setting rst to FALSE, the process proceeds to the program starting step 205. On the other hand, if bFirst is FALSE, it indicates that resources have already been secured, and the process directly proceeds to the program starting step 205.
In the program starting step 205, the program is started, bPOn is set to TRUE, and the process returns to the beginning of the loop. Termination determination step 206, program termination step 207, OS termination request detection step 208, and O
The operation of S end step 209 is exactly the same as in the first embodiment. As described above, according to the second embodiment of the present invention, when a program that requires a continuous large-capacity memory space as a resource is operated in an architecture in which the securing of resources is limited in the physical memory, Necessary resources are secured at the time of the first program startup, and thereafter, resources are continuously secured until the OS is terminated. Once the resources are successfully secured, the resources are not eroded by other programs or data. If there is a program start request, it can always be started. In this embodiment, since the resources of the program are not secured immediately after the OS is started, there is an advantage that the execution of another program is not hindered before the execution of the program. On the other hand, only after the OS is started and before the program is executed, the memory space is used by executing another program or storing data, and there is a possibility that resources cannot be secured in the resource securing step 204. In this case, the user may be prompted to cut out the memory space or to turn off the power by deleting unnecessary data. In the description of the first and second embodiments, it has been described that all resources are secured in the resource securing step, but it is also possible to adopt a configuration in which not all resources are secured. Also, in the description of the embodiment of the present invention, the start of the flowchart is referred to as OS
Although this is at the time of startup, this may be at the time of power-on. Although the flowchart ends when the OS ends, the same effect can be obtained even when the power is turned off. The present invention is particularly effective when the possibility that resources of other programs are released or the possibility that stored data is erased is extremely small.

As described above, according to the present invention,
When executing a program that requires securing resources in a continuous large-capacity memory space in an architecture where the securing of resources is limited in the physical memory, once the securing of the resources of the program is successful, the program starts,
In response to the termination request, the activation and termination of the program can be repeated.

[Brief description of the drawings]

FIG. 1 is a flowchart for explaining the operation of a first embodiment of the present invention;

FIG. 2 is a flowchart for explaining the operation of the second embodiment of the present invention;

[Explanation of symbols]

 101, 201, OS start steps 102, 204, resource securing steps 103, 202, start determination steps 104, 205, program start steps 105, 206, end determination steps 106, 207, program end steps 107, 208, OS end request detection Steps 108 and 209, OS termination step 203, initial determination step

Claims (7)

[Claims] 1. A method for executing a program which needs to secure resources in a continuous large-capacity memory space,
A resource securing step for securing resources of the program, a program launching step for launching the program, and a program terminating step for terminating the program. A program execution method, comprising: executing the program start step when a start request is made; and executing the program end step when a program end request is made. 2. A method for executing a program which needs to secure resources in a continuous large-capacity memory space,
A resource securing step for securing resources of the program, a program activating step for activating the program, and a program ending step for ending the program. Executing a memory securing step and the program starting step,
A program execution method, comprising: executing the program start step when the program is requested to be started after the first time; and executing the program end step when the program end request is made. 3. The system according to claim 1, wherein the release of the resource is performed when the operating system is terminated.
The method for executing a program according to item 1. 4. The program execution method according to claim 1, wherein the securing of resources is restricted in the physical memory space for programs other than the programs in addition to the programs. 5. The program execution method according to claim 1, wherein even if there is a program start request, if the program has already been started, the program start step is not executed. 6. The program execution method according to claim 1, wherein the program ending step is not performed if the program has not been started even if a program ending request is issued. 7. The program execution method according to claim 1, wherein in the resource securing step, when the resource securing fails, the power supply or the release of the resources of another program is urged.