JP2001142685A - Program correcting method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform a program editing work by using an information file in a simple form. SOLUTION: This method is provided with a process to create the information file to express a name of a file (folder name) to be a correcting object and the correction contents (contents information) in a text form when a prescribed program is corrected and a process to analyze the information file and to correct the file to be the correcting object based on the correction contents.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program correction method for changing a program such as an application used in a general-purpose terminal system.

[0002]

2. Description of the Related Art Generally, a general-purpose terminal system having a medium-sized stand-alone configuration (for example, Windows as a general-purpose OS).
In wsNT (with a registered trademark of Microsoft Corporation in the United States), a commercially available program change package is used to change or delete a part of a program such as an application program. For example, when a part of a program is changed, a file (module) to be changed is newly created using a commercially available program change package, and the file is replaced.

[0003]

SUMMARY OF THE INVENTION However, Win
A commercially available program change package that operates on a general-purpose OS such as dowsNT cannot be used unless a special language or the like is understood, and it is very difficult for anyone to easily create a change program.

[0004]

SUMMARY OF THE INVENTION The present invention is a program editing method for solving such a problem. In other words, according to the present invention, when a predetermined program is modified, a step of creating an information file representing the name of the file to be modified and the contents of the modification in a text format, interpreting the information file, and modifying the file to be modified And performing a correction based on the details of the correction.

In the present invention, when a predetermined program is modified, the name of the file to be modified and the contents of the modification are described in text format as an information file, and the file to be modified is written based on the information file. It has been corrected. As a result, the user who corrects the program only needs to create an information file indicating the details of the correction with a simple description in a text format, and can correct the program without understanding a special language. .

[0006]

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an embodiment of a program correcting method according to the present invention. The program correction method according to the present embodiment mainly has a function of transferring a module stored in a medium (eg, a floppy disk or a CD-ROM) to a specific location (eg, a directory);
This is a program modification method with limited functions, such as deleting a module at a specific location. As a result, anyone can easily perform the program correction work.

FIG. 1 is a diagram for explaining a file format used when a program is changed. In the present embodiment, when a program is corrected, the name of a file (module) to be corrected and the details of the correction are created in advance as an information file representing the text format. In the present embodiment, as a text format information file,
CSV format (Comma Separated Value: data is separated by comma) is applied. The information file in the text format is not limited to the CSV format, but may be another format (for example, a format delimited by tabs).

As shown in FIG. 1, when a module is changed as a modification of a program, an information file in which folder names, content information, and transfer destination directories are separated by commas is created. For example, the module with the folder name “data” stored in the medium is transferred to the transfer destination directory p.
The transfer to rg1 is as follows.

Data, 1, \ temp \ prg1, or data, 2, \ temp \ prg1,

Here, when the content information is 1, the transfer destination directory is not created, and when the content information is 2, the transfer destination directory is created. That is, when the content information is 1, the module stored in the folder name data of the medium is transferred to \ temp \ prg1. At this time, if the transfer destination directory does not exist, the error or the processing proceeds. When the content information is 2, after the transfer destination directory $ temp \ prg1 is automatically created, the module stored in the folder name data of the medium is transferred to the directory \ temp \ prg1. If the transfer destination directory \ temp \ prg1 already exists, the module is transferred as it is.

By interpreting such a CSV format information file by a predetermined program, the user can transfer a desired module to a designated directory simply by creating a simple CSV format information file.

FIG. 2 is a diagram for explaining a file format used when deleting a program. That is, as shown in FIG. 2, when a module is to be deleted as a modification of a program, an information file in which the program to be deleted and the directory where the program to be deleted exists is separated by commas. For example, an information file for performing deletion is as follows.

Aaa1. exe, \ temp \ prg
1, aaa2. exe, aaa3. exe ,, bbb
1, {temp} prg2, ccc1 ,,

The first line of the information file is aaa1.
exe in the folder \ temp \ pr
g1. Also, the second line, 3
In the line, the target directory is omitted. In this case, the modules aaa2... Respectively specified from the target directory set immediately before (in this example, \ temp \ prg1). exe, aaa3. exe will be deleted.

Similarly, the fourth line of the information file is b
bb1. exe in the folder \ tem
This indicates that p @ prg2 is deleted. Also, 5
In the line, since the target directory is omitted, the target directory set immediately before (in this example, ￥
module c specified from temp @ prg2)
cc1. exe will be deleted.

By interpreting such a CSV format information file by a predetermined program, a user can delete a desired module from a specified directory by simply creating a simple CSV format information file.

Next, FIG. 3 is a view for explaining a file format used when setting registry information. That is, as shown in FIG. 3, when setting the registry information as a modification of the program, an information file in which a file storage information key for setting the registry information and a setting value are separated by a comma is created. For example, when setting the registry information, the information file is as follows.

HKEY_LOCAL_MACHINE,
PassWord: REG_SZ: 9999

In the above information file, HKEY_LOC
AL_MACHINE represents a file storage information key,
PassWord is the data name among the set values, REG_S
Z represents the data type name among the set values, and 9999 represents the write data among the set values.

With this information file, a password is set to the file storage information key HKEY_LOCAL_MACHINE. At this time, there are cases where this process cannot be executed depending on the operating authority.

By interpreting such a CSV format information file by a predetermined program, the user can set registry information only by creating a simple CSV format information file.

Further, the program can be modified by designating the date and time by using the same CSV format information file. FIG. 4 is a diagram illustrating a file format used when specifying a date and time. That is, as shown in FIG. 4, when specifying the date and time of the program correction, an information file is created in which the date and time are separated by commas.
For example, the information file is as follows.

1998/02/26, 18:30,

Based on this information file, it is determined whether or not the program can be edited. That is, when the program is edited, this information file is interpreted and the set date (in the above example, February 26, 1998)
It is determined whether the day has passed or the set time (18:30 in the above example) has passed. Only when the set date and time has passed, program editing can be executed.

When only one of the date and time is specified, the program can be edited only when the specified date or time has passed. If both are specified, the program can be edited only when both the date and time have passed.

By interpreting such a CSV format information file with a predetermined program, the user can specify the date and time conditions for program editing simply by creating a simple CSV format information file.

Next, a flow for realizing the program correction method of this embodiment by program processing will be described with reference to the flowcharts of FIGS. First, the overall flow of the processing will be described with reference to FIGS. When the program is started, FD (floppy disk), CD (CD-
(Step S10)
1).

Next, a button operation is determined (step S1).
02), if the FD button is selected, Start_
FD is displayed (step S103), and if the CD button is selected, Start_CD is displayed (step S104).

Further, it is determined whether or not the cancel button has been selected (step S105). If the cancel button has been selected, interruption confirmation processing is performed (step S106). The interruption confirmation processing will be described later.

Next, when the cancel button is not selected, the change information file is copied to a predetermined folder (step S107). Here, it is determined whether or not the change information file is unknown (step S108), and if unknown, Err_Media is displayed (step S10).
9). Thereafter, button selection is determined (step S11).
0), if it is cancelled, an interruption confirmation process is performed (step S111), and if it is OK, the process returns to step S107.

After copying the change information file, it is determined whether there is a date file (step S11).
2). If there is a date file, the date is checked (step S113). If the current date is not later than the date set in the date file, the date is checked as NG and Sup
_DataCheckNG is displayed (Step S11)
4). Thereafter, Sup_End is displayed (step S1).
15), and return to step S101. In the case of an error, Err_MotoDitFile is displayed (step S116), in the case of cancellation, interruption confirmation processing is performed (step S117), and when the continue button is selected (step S118), the process proceeds to the next step. move on.

Next, as shown in FIG. 6, the first line of the change information file is read (step S201), and it is determined whether or not there is a format error in the change information file (step S202). If there is an error, Sup
_End is displayed (step S203).

If there is no format error, it is determined whether or not the medium is the first medium (step S204). If the medium is not the first medium, it is determined whether or not the medium is replaced (step S20).
5) In the case of replacement, Sup_FDChange is displayed (step S206). Then, the selection of the button is determined (step S207), and in the case of cancellation, the interruption confirmation processing is performed (step S208). On the other hand, if OK, it is determined whether or not there is a volume name in the change information (step S209). If so, it is determined whether the volume names match or mismatch (step S210). If they do not match, Sup_FDChange is displayed (step S211), and the process returns to step S206.

If it is determined in step S204 that the medium is the first medium, it is determined whether or not there is a volume name in the change information (step S212). If so, it is determined whether or not the volume names match (step S213). . If they do not match, Err_VolName is displayed (step S214), and button selection is determined (step S21).
5). Then, in the case of cancellation, interruption confirmation processing is performed (step S216), and in the case of OK, step S2
Return to 12.

Next, as shown in FIG. 7, the contents of the change are determined (step S301). Here, if the change is a version file, a version file copy process is performed (step S302), and if it is copy / decompression, a copy / decompression process is performed (step S3).
03) If it is a registry, a registry change process is performed (step S304); if it is a delete, a file delete process is performed (step S305). Then, the processing from step S201 shown in FIG. 6 to step S305 shown in FIG. 7 is repeated until the last line of the change information file, and Sup_End is displayed (step S30).
6), end the process.

Next, the version file copy processing shown in step S302 will be described with reference to the flowchart of FIG. First, it is determined whether there is a copy source file (step S401). If there is no copy source file, Err_MotoDirFile is displayed (step S402). If there is a copy source file, it is determined whether the transfer destination directory is unknown (step S403). Err_SakiDi if unknown
r is displayed (step S404), the selection of the button is determined (step S405), and in the case of cancellation, an interruption confirmation process is performed (step S406).

If there is a transfer destination directory, Sup
_Copy is displayed (step S407), and processing for copying the version file to the transfer destination directory is performed (step S408).

Next, the copy / decompression processing shown in step S303 will be described with reference to the flowchart of FIG. First, it is determined whether there is a copy source directory (step S501). If there is no copy source directory, Err_MotoDirFile is displayed (step S502). If there is a copy source directory, the content information is determined (step S503).
If the content information is "2", it is determined whether or not there is a transfer destination directory (step S504). If not, a transfer destination directory is created (step S5).
05).

On the other hand, if the content information is "1", it is determined whether the transfer destination directory is unknown (step S5).
06). If unknown, Err_SakiDir is displayed (step S507), button selection is determined (step S508), and if canceled, interruption confirmation processing is performed (step S509).

If there is a transfer destination directory, a copy source file name is obtained (step S510), and the file is copied to the transfer destination directory (step S51).
1). The processing of steps S510 to S511 is repeated for directories in the target folder.

Next, the registry change processing shown in step S304 will be described with reference to the flowchart of FIG. First, it is determined whether a registry file is unknown (step S601). Err_Mo if unknown
ToFile is displayed (step S602), the selection of a button is determined (step S603), and in the case of cancellation, interruption confirmation processing is performed (step S604).

On the other hand, if there is a registry file, a key and a value are obtained (step S605). Here, it is determined whether or not the key is unknown. If the key is not unknown, registry writing is performed (step S607). The processing of steps S606 to S607 is repeated line by line of the registry file.

Next, the file deletion process shown in step S305 will be described with reference to the flowchart of FIG. First, it is determined whether the deleted file is unknown (step S701). Err_MotoFi if unknown
le is displayed (step S702), the selection of a button is determined (step S703), and in the case of cancellation, interruption confirmation processing is performed (step S704).

On the other hand, if there is a file to be deleted, the target file path is obtained (step S705), and processing for deleting the target file based on the obtained file path is performed (step S706). This step S705-
The processing of S706 is repeated line by line of the deletion file.

Finally, the interruption confirmation processing will be described with reference to the flowchart of FIG. First, Sup_Abort is displayed (step S801). Next, the selection of the button is determined (step S802), and in the case of cancellation, the process returns to the original process. On the other hand, in the case of OK, Sup_End
Is displayed (step S803), and the top of the main process is displayed.
That is, the process returns to step S101 shown in FIG.

[0046]

As described above, according to the program correcting method of the present invention, the following effects can be obtained. That is, limited to the minimum functions required for program modification,
By simply referring to the information file created by a simple text file, it is possible to perform the work of replacing programs and the like on the general-purpose OS. This allows anyone to easily edit a program without having to understand a special language.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a file format used when a program is changed.

FIG. 2 is a diagram illustrating a file format used when deleting a program.

FIG. 3 is a diagram illustrating a file format used for setting registry information.

FIG. 4 is a diagram illustrating a file format used when designating a date and time.

FIG. 5 is a flowchart (part 1) for explaining the overall flow of processing.

FIG. 6 is a flowchart (part 2) for explaining the overall flow of the processing;

FIG. 7 is a flowchart (part 3) for explaining the overall flow of the processing;

FIG. 8 is a flowchart illustrating a version file copy process.

FIG. 9 is a flowchart illustrating copy / decompression processing.

FIG. 10 is a flowchart illustrating a registry change process.

FIG. 11 is a flowchart illustrating a file deletion process.

FIG. 12 is a flowchart illustrating an interruption confirmation process.

Claims (5)

[Claims] 1. A step of creating an information file representing the name of a file to be corrected and the contents of the correction in a text format when correcting a predetermined program; interpreting the information file to be a target of the correction Modifying the file based on the content of the modification. 2. The method according to claim 1, wherein the information file includes correction contents for changing a file of the predetermined program. 3. The method according to claim 1, wherein the information file includes correction contents for deleting a file of the predetermined program. 4. The method according to claim 1, wherein the information file includes correction contents for changing registry information of the predetermined program. 5. The program correction method according to claim 1, wherein the information file includes a correction execution date and time in addition to a name and a correction content of a file to be corrected.