JPH03167642A - File memory device - Google Patents

Abstract

PURPOSE:To write the same file names on each other as long as the difference of capacity between an uncorrected file and the corrected one is smaller than the prescribed value and to inquire the propriety for execution of the duplicate writing of the same file names when said difference of capacity is larger than the prescribed value. CONSTITUTION:A main disk 6 stores the programs turned into a file, and a subdisk 7 stores the same programs respectively. A CPU 1 obtains the capacity of a file for corrected programs stored in the disk 6 and that for uncorrected programs stored in the subdisk 7. Then the CPU 1 writes the uncorrected programs on each other onto the disk 7 in the same file name as the uncorrected one when the capacity difference is kept within + or -20% and then writes the capacity of the file for corrected programs and that for uncorrected programs on each other to inquire the propriety for back-up after displaying them on a display device 9 if the capacity difference is kept over + or -20%. When a back-up operation is instructed via the key 8 again, the uncorrected programs are written on each other onto the subdisk 7 in the same file name. If this writing operation is not required, the due process ends as it is. In such a constitution, it is possible to inhibit the abnormal duplicate writing operations, to protect the file of uncorrected programs, and to surely write only the normal files on each other.

Description

[Detailed description of the invention] (Industrial application field) The present invention relates to a file memory device.

(Prior Art) For example, a created program is stored as a file on a main disk, and is also stored on a sub-disk serving as a backup memory for file backup. Here, if the contents of such a program need to be modified and are modified, this modified program is stored again in the main disk and sub disk. By the way, the backup of this file is MS-D
This is done using the OS's copy command, and at this time, the modified program stored in the subdisk is overwritten with the same file name as the file name of the program before modification.

(Problem to be Solved by the Invention) By the way, most programs are modified by correcting key points, and rarely by major modifications. Therefore, the size of the modified program and the program before modification are not significantly different.

However, when a program is modified, for example, if a part that does not need to be deleted is deleted by mistake, the size of the modified program and the program before modification are significantly different. If the program is incorrectly modified in this way, and the operator is not aware of the error, the incorrectly modified program will be overwritten on the subdisk with the same file name as the modified program file name. Therefore, an abnormal backup file is created and the backup is not effective.

SUMMARY OF THE INVENTION Therefore, it is an object of the present invention to provide a file memory device that can prevent overwriting of abnormal files to protect unmodified files, and can reliably overwrite only normal files.

(Means for Solving the Problems) The present invention provides a file memory device that overwrites a modified file in memory with the same file name as the file name before modification, in which the capacity of the modified file and the file before modification is The above purpose is achieved by calculating the difference, overwriting the modified file in memory if the difference in capacity is less than a predetermined capacity, and notifying whether or not to overwrite if the difference in capacity is greater than a predetermined capacity. This is the file memory device that you are trying to access.

(Function) By providing such a means, when overwriting with the same file name, the difference in capacity between the modified file and the file before modification is determined, and if this difference in capacity is less than the predetermined capacity, the modification is performed. overwrite the file into memory,
If the capacity difference is greater than or equal to a predetermined capacity, notification is made as to whether or not to overwrite.

(Example) Hereinafter, an example of the present invention will be described with reference to the drawings.

FIG. 1 is a configuration diagram of a computer system to which a file memory device is applied. A CPU (Central Processing Unit) 1 is connected to a RAM (Random Access Memory) 3, a ROM (Read Only Memory) 4, and an I/O memory via a bus 2.
An O (input/output) boat 5, a main disk 6, and a sub disk 7 as a backup memory are connected. A keyboard 8 and a display device 9 are connected to the I/O port 5. The ROM 4 stores a backup flowchart program shown in FIG. Therefore, by executing this program, the CPUI calculates the difference in capacity between the modified file and the unmodified file when backing up the file.
If this capacity difference is less than a predetermined capacity, overwrite the modified file on subdisk 7 with the same file name as the file before modification, and if the capacity difference is greater than or equal to a predetermined capacity, whether to overwrite and back up. It will have the function of notifying.

Next, the operation of the apparatus configured as described above will be explained with reference to the backup flowchart shown in FIG.

The main disk 6 stores programs in the form of files, and the sub disk 7 stores the same programs as the programs stored in the main disk 6 in the form of files.

Here, when the program stored on the main disk 6C is modified manually using keys from the keyboard 8, the modified program is backed up. Therefore, when a backup command is entered from the keyboard 8, the CPU 1 moves from step s1 to step s2 to find the capacity of the modification program file stored in the main disk 6, and also calculates the capacity of the modification program file stored in the sub disk 7. Find the file size of the program before modification. Next, in step s3, the CPUI compares the file capacity of the modified program with the file capacity of the program before modification, and determines whether the difference in these capacities is ±20% or more. As a result of this judgment, if the capacity difference is within ±20%, the CPUI moves to step s4 and overwrites the modified program onto the subdisk 7 with the same file name as the file name of the program before modification.

However, if the difference in capacity between the file size of the modified program and the file capacity of the program before modification is ±20% or more, the CPU 1 moves to step s5 and calculates the file size of the modified program and the file capacity of the program before modification. The data is displayed on the display device 9, and a message asking whether to overwrite and back up the data is displayed on the display device 9. In this case, an alarm sound may be emitted along with the message. Here, when an instruction to back up is entered from the keyboard 8, the CPU moves to step S4 and overwrites the modified program in the sub-disk 7 with the same file name as the file name of the program before modification. Note that if you do not want to back up, the program will exit.

In this way, in the above embodiment, when backing up a file, the difference in capacity between the modified program and the program before modification is determined, and if this difference in capacity is less than ±20%, the modified program is saved as a file on the subdisk 7. If the difference in capacity is more than ±20%, a message will be displayed asking whether to overwrite and back up the program.If there is no error in the modified program, subdisk 7 will be used for backup. If there is a capacity difference of ±20% or more and there is a possibility that there is an error in the modified program, backup can be prohibited. Therefore, a program with an error is not overwritten with the same file name as the program before modification, and the program before modification can be protected. Further, if the difference in capacity is ±2096 or more and there is no error in the modified program, it can be overwritten with the same file name as the program before modification.

It should be noted that the present invention is not limited to the above-mentioned embodiment, and may be modified without departing from the spirit thereof.

For example, the difference in capacity between a modified program and a program before modification is not ±20%, but may be set arbitrarily depending on the content of program modification. Moreover, it can be applied not only when storing on the sub-disk 7 for backup, but also when rewriting a modified program with an unmodified program stored on the main disk 6.

(Effects of the Invention) As described in detail above, according to the present invention, it is possible to provide a file memory device that can protect unmodified files by prohibiting backup of abnormal files, and can reliably back up only normal files.

[Brief explanation of the drawing]

1 and 2 are diagrams for explaining one embodiment of a file memory device according to the present invention, in which FIG. 1 is a configuration diagram and FIG. 2 is a backup flowchart. 1...CPU, 2...Bus, 3...RAM
, 4... ROM, 5... 1/0 port, 6... Main disk, 7... Sub disk, 8... Keyboard, 9... Display device.

Claims (1)

[Claims] In a file memory device that overwrites a modified file into memory with the same file name as the file name before modification, the difference in capacity between the modified file and the file before modification is calculated, and the difference in capacity is determined to be less than or equal to a predetermined capacity. If so, the modified file is overwritten in the memory, and if the capacity difference is greater than or equal to a predetermined capacity, a notification is made as to whether to overwrite or not.