JP2008171352A - Copy device for data, copy method for data, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent data which has not been completed in copying from being deleted from a storage medium of a copy source. <P>SOLUTION: This copy device for data has: a copy part copying data stored in a first storage medium to a second storage medium; and an attribute change part changing an attribute of the data stored in the first storage medium into read only before copying the data to the second storage medium, and changing the attribute of the data stored in the first storage medium into an erasable attribute after the copy of the data to the second storage medium is completed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a data copying apparatus, a data copying method, and a program.

In some cases, image data is copied from a memory card storing image data taken by a digital camera or the like to a large-capacity storage device. In recent years, an increasing number of large capacity storage devices can be carried by battery drive.
JP 2005-111943 A

  When the data copy destination storage device is battery-powered, for example, the battery may run out before all the data of the copy source storage device is stored in the copy destination storage device. However, even when the battery runs out in this way, the user may recognize that all data has been copied.

  By the way, the user uses the memory card which is the copy source storage medium again. At this time, since data is still left in the copy source storage medium, the user often uses the data after deleting the data. However, the copy source storage medium also includes data that has not been copied to the copy destination storage medium. Since the user recognizes that copying of all data has been properly completed, when deleting the data on the copy source storage medium, even the data that has not been copied to the copy destination storage medium is deleted. May end up.

  The present invention has been made in view of such circumstances, and an object thereof is to prevent data that has not been copied from being deleted from a copy-source storage medium.

The main invention for achieving the above object is:
(A) a copy unit that copies data stored in the first storage medium to the second storage medium;
(B) Before copying the data to the second storage medium, change the attribute of the data stored in the first storage medium to read-only,
An attribute changing unit that changes the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
Is a data copying apparatus.
Other features of the present invention will become apparent from the description of the present specification and the accompanying drawings.

  At least the following matters will become clear from the description of the present specification and the accompanying drawings.

(A) a copy unit that copies data stored in the first storage medium to the second storage medium;
(B) Before copying the data to the second storage medium, change the attribute of the data stored in the first storage medium to read-only,
An attribute changing unit that changes the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A data copying apparatus comprising:
In this way, it is possible to prevent data that has not been copied from being deleted from the copy source storage medium.

  In such a data copying device, the second storage medium is preferably controlled by a battery-powered device. The first storage medium is preferably detachable from the data copy device. In the first storage medium, it is preferable that the data is managed by a file system managed in units of files, and the file system has an area for storing an attribute for making each file read-only. Further, it is desirable that the data is divided into a plurality of sessions according to the capacity of the second storage medium.

In addition, it is preferable that a file in which the data is collected in a session unit is created before the data is copied to the second storage medium. The second storage medium is preferably an optically readable storage medium. The second storage medium is preferably a storage medium in which data is written in session units. In the second storage medium, the data may be managed by a file system that is managed in file units. Further, it is desirable that the copying unit further deletes the data for which the copying has been completed from the first storage medium.
In this way, it is possible to prevent data that has not been copied from being deleted from the copy source storage medium.

(A) a connection unit for connecting the first storage medium;
(B) a second storage medium;
(C) a controller that copies data stored in the first storage medium to the second storage medium,
Before copying the data to the second storage medium, change the attribute of the data stored in the first storage medium to read-only,
A controller that changes the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A data copying apparatus comprising:
In this way, it is possible to prevent data that has not been copied from being deleted from the copy source storage medium.

Changing the attribute of the data stored in the first storage medium to read only;
Copying the data stored in the first storage medium to a second storage medium after changing the attribute of the data to read only;
Changing the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
To copy data including
In this way, it is possible to prevent data that has not been copied from being deleted from the copy source storage medium.

A program for operating a data copying device,
Changing the attribute of the data stored in the first storage medium to read only;
Copying the data stored in the first storage medium to a second storage medium after changing the attribute of the data to read only;
Changing the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A program for causing the data copying apparatus to execute
In this way, it is possible to prevent data that has not been copied from being deleted from the copy source storage medium.

=== Embodiment ===
<Printer configuration>
FIG. 1 is a perspective view for explaining the overall configuration of the printer 1. FIG. 2 is a block diagram of the overall configuration of the printer 1. Hereinafter, a basic configuration of the printer 1 will be described.

  The printer 1 includes a controller 11, a memory card reader / writer 12, a CD reader / writer 13, a printing unit 14, an interface 15, a hard disk drive 16, a liquid crystal display 17, and an operation panel 18. The printer 1 writes the image data stored in the memory card read from the memory card reader / writer 12 to the CD3 (CD-R) or the hard disk drive 16 using the CD reader / writer 13, or the printing unit. 14 can be printed.

  The controller 11 controls a memory card reader / writer 12, a CD reader / writer 13, a printing unit 14, an interface 15, a hard disk drive 16, a liquid crystal display 17, and an operation panel 18, which will be described later. The controller 11 is equipped with a processing device for processing a program and a memory for storing the program and data. The controller 11 executes a program stored in this memory. By executing the program, for example, the backup target data stored in the memory card 2 as described later is backed up to the CD 3.

  A memory card can be inserted into the memory card reader / writer 12, and data can be read and written from the memory card 2. The file system of the memory card 2 used here is a FAT file system. The FAT file system reserves an area for storing attributes for making each file read-only. And, in directory unit and file unit, the file attribute is read-only (read-only attribute, file cannot be deleted) or read-only attribute is canceled (writeable attribute, file can be deleted) Attributes).

  The CD reader / writer 13 writes data to the CD3 and reads data from the CD3. At this time, data can be written to and read from the CD 3 in accordance with a CD-ROM file system conforming to ISO9660 level 1.

  The printing unit 14 forms an image on a medium based on the image data under the control of the controller 11. For example, an image can be printed on paper by ejecting ink droplets.

  The interface 15 is an interface for connecting to a computer 19 such as a USB interface. By connecting to a computer, data such as image data can be transmitted and received from the computer 19.

  The hard disk drive 16 can write and read data read from the memory card 2 or the CD 3. The file system of the hard disk drive 16 used here is a FAT file system.

  The liquid crystal display 17 provides visual information to the user under the control of the controller 11. For example, an image file stored in the memory card 2 is displayed or processing options are shown to the user.

  The operation panel 18 is for receiving instructions from the user. By using this, for example, the user selects an image file to be copied from the memory card 2 to the hard disk drive 16.

  FIG. 3 is a circuit diagram showing a power supply system of the printer 1. The printer 1 in this embodiment is a battery-driven printer.

  The power line Vcc is supplied with power from an external AC adapter 110 as an external power source of the printer 1 and a lithium ion battery pack 120 (hereinafter referred to as a battery pack 120) as a “battery” detachably built in the printer 1. The The AC adapter 110 performs AC-DC conversion of AC power (such as AC100V) to DC power (DC20V). The DC power output from the AC adapter 110 is supplied to the power supply line Vcc via the diode D1. The battery pack 120 includes a plurality of lithium ion batteries. The DC power output from the battery pack 120 is supplied to the power supply line Vcc via the diode D2.

  The power supply line Vcc is provided with a power switch 135, and the power supply line Vcc is directly connected / disconnected at the contact point of the power switch 135 to turn on / off the electronic device.

  The charging circuit 121 performs charging of the battery pack 120 using the DC 20V power supplied from the AC adapter 110 via the diode D3.

  The A / D conversion circuit 122 that can acquire information for estimating the remaining amount of power of the battery pack 120 divides the output voltage of the battery pack 120 by a predetermined voltage division ratio, and then converts the voltage to a digital signal voltage value. And output to the controller 11.

  The power supply detection circuit 123 detects the presence / absence of power supply from the battery pack 120 from the presence / absence of power supply from the AC adapter 110 and the attachment / detachment state of the battery pack 120, and detects the respective detection states (power supply detection signals). Is output.

  The controller 11 determines whether the supplied power is the AC adapter 110 or the battery pack 120 based on the detection state (power supply detection signal) of the power supply from the AC adapter 110 and the power supply from the battery pack 120 in the power supply detection circuit 123. Judging. In addition, the controller 11 estimates the remaining power of the battery pack 120 based on the output signal of the A / D conversion circuit 122.

<Directory structure>
FIG. 4 is an example of a directory structure stored in the memory card 2.
As shown in the figure, the memory card 2 has a “DCIM” directory 211 and a “MISC” directory 212 as subdirectories in the first hierarchy 21 immediately below the root directory 200. In the second hierarchy 22 under the “DCIM” directory 211, there are further subdirectories “100ABCDE” directory 211 and “101ABCDE” directory 222. Then, five image files 251 exist in the “100ABCDE” directory 221, and two image files 252 exist in the “101ABCDE” directory 222. Furthermore, one text file (“AUTOPRINT.MRK”) 253 exists in the “MISC” directory 212.

  FIG. 5 is a diagram showing a data structure of the backup data 30 when the backup target data shown in FIG. 4 is backed up to the CD 3 in one session. Here, the data structure of CD3 when data included in the directory structure shown in FIG. 4 is backed up to CD3 as backup target data will be described.

  CD3 has a structure according to the CD-ROM file system. Therefore, management areas 301 and 302 according to the CD-ROM file system are provided at the beginning and end of the backup data 30. As shown in FIG. 5, an area in which the three storage parts of lead-in, data, and lead-out are combined is called a session.

  In the present embodiment, a CD conforming to ISO9660 level 1 will be described as an example. However, the present invention can be applied to other expanded standards (for example, ISO9660 level 2, Joliet).

  The backup data 30 is provided with a root directory entry 310, subdirectories “DCIM” directory 211, and “MISC” directory 212 directory entries 311 and 312 following the top management area 301. Since there is no subdirectory in the “MISC” directory 212, the data body 353 of the text file 253 is stored following the directory entry 312.

  Subsequently, the directory entry 321 of the “100ABCDE” directory 221 and the data body 351 of the image file 251 in the “100ABCDE” directory 221, the directory entry 322 of the “101ABCDE” directory 222, and the “101ABCDE” directory 222 The data body 352 of the image file 252 is stored.

  In the range described above, all of the directory and data body of the backup target data are included. In the case of the CD-ROM file system, a path table 330 indicating the directory structure of all data stored in the CD 3 is further provided.

  The path table 330 is for representing all data included in the CD3 in a tree structure as shown in FIG. 4 when the backup data 30 is stored in the CD3. Therefore, for example, when the backup data 30 is written on a new CD 3, the path table 330 represents the tree structure shown in FIG.

  7 to 11 are diagrams showing the data structures of the directory entries 310, 311, 312, 321, and 322 of the root directory, “DCIM” directory, “MISC” directory, “100ABCDE” directory, and “101ABCDE” directory.

  Each directory entry 310, 311, 312, 321, 322 has pointer records 3101, 3111, 3121, 3211, 3221 pointing to its own sector and pointer records 3102, 3112, 3122, 3212 pointing to the parent directory sector. , 3222 are included, and the data length of each is fixed to 34 bytes.

  Furthermore, when each directory entry 310, 311, 312, 321, 322 includes a subdirectory directly under each directory, subdirectory records 3103, 3113 are included, and a file immediately below each directory is included. When there is, file records 3123 and 3224 are included.

  Each of the subdirectory records 3103 and 3113 includes a pointer and a subdirectory name indicating a sector in which the directory entry of the subdirectory is stored. The record length is variable, and the maximum length is 46 bytes. The file records 3124, 3214, and 3224 include a pointer and a file name that point to the sector in which the file body is stored, and the record length is variable and has a maximum length of 46 bytes.

  For example, the root directory entry 310 shown in FIG. 7 includes a directory record 3103 of the “DCIM” directory 211 and a “MISC” directory 221 directory record 3103. The directory entry 312 of the “MISC” directory shown in FIG. 9 includes a file record 3124 of the text file 253.

  FIG. 12 shows the data structure of the path table. The path table 330 includes a root directory record 3301 and a subdirectory record 3303 including a pointer and a directory name indicating each parent directory for each subdirectory record. The root directory record 3301 is fixed to 10 bytes, and the subdirectory record 3303 has a variable length and a maximum of 18 bytes.

  Here, one sector of CD3 is 2048 bytes. Therefore, even when the amount of data to be stored in each directory entry 310, 311, 312, 321, 322 and path table 330 is less than 2048 bytes, when storing one directory entry or path table, it is a multiple of 2048 bytes. Storage space is consumed. This also applies to the case where the data body is stored. That is, when the data body is stored in the CD3, the storage area is consumed in units of 2048 bytes according to the size of the data body.

  FIG. 6 is a diagram showing the data structure of backup data 30a and 30b when the backup target data shown in FIG. 4 is divided into two sessions and backed up to CD3. Here, it is divided into a first session including the “DCIM” directory 211 of the first hierarchy 21 and its subdirectories and files, and a second session including the “MISC” directory 212 and its subordinate files. The data structure of the backup data 30a and 30b when backup is performed separately is shown.

  FIG. 6A shows the backup data 30a after the backup of the first session. The backup data 31 is configured by removing the “MISC” directory entry 312 and the text file body 353 from the backup data 30 shown in FIG. However, the contents of the path table 330 a are different from the path table 330 of the backup data 30. That is, since the “MISC” directory 212 is not copied, the path table 330a includes information indicating the directory structure excluding the “MISC” directory 212 and its subordinate text file 353 in the directory structure shown in FIG. It is.

  FIG. 6B is a diagram showing the backup data 30b when the backup of the second session is executed following the first session. The backup data 30b includes directory entries 312b and 302b, a root directory 310b, and a path table 330b of the “MISC” directory 212 to be backed up in this session.

  Here, the path table 330b includes information indicating the directory structure shown in FIG. This is because the “DCIM” directory 211 was backed up in the first session and the “MISC” directory 212 was copied in the second session, so that all the data shown in FIG. Because.

  As a result, even when the same data is backed up, it can be seen that the required capacity varies depending on the session. That is, if the session is divided into a plurality of as shown in FIG. 6, only the capacity of the management areas 301b and 302b, the root directory entry 310b, and the path table 330b is compared with the case where the backup is performed without dividing the session as shown in FIG. A lot is needed.

<When backing up to CD3>
13 and 14 are flowcharts showing the procedure of the backup process for backing up the data in the memory card 2 to the CD3. FIG. 15 is a diagram showing the relationship between the directory structure and the division pattern.

  First, the controller 11 sets the division number 0 as the division pattern A (S502). That is, consider a case where backup is performed in one session without dividing the backup target data.

  Here, the controller 11 determines whether or not the total capacity of the backup target data is larger than the free capacity of the CD3 that is the backup destination medium (S504). If the total capacity of the data to be backed up is larger than the free capacity of the CD3 (S504: Yes), the CD3 capacity is insufficient and cannot be backed up.

  When the total capacity of the backup target data is not larger than the free capacity of the CD (S504: No), the controller 11 uses the division pattern B as the CD3 necessary for dividing the session into subdirectory units of the first hierarchy. The capacity is calculated (S506). In the example of FIG. 15, the division at this time is a division in which the “DCIM” directory 211 is the first session and the “MISC” directory 212 is the second session.

  As described above, when a session is divided, the management area and the like increase, so that the capacity required for backup as a whole increases. Furthermore, the required number of sectors may differ depending on the number of directories or files, the size of the file, and the like. Therefore, the controller 11 calculates the total capacity required for backup according to the directory structure and the number of directories included in each session.

  Next, the controller 11 determines whether or not the total capacity required for the division pattern B is larger than the free capacity of the CD 3 as the backup destination medium (S508). When the total capacity required for the division pattern B is larger than the free capacity of the CD3 (S508: Yes), the division pattern A is selected (S510).

  If the total capacity required for the division pattern B is not larger than the free capacity of the CD3 (S508: No), the controller 11 uses the CD3 necessary for dividing the session into sub-directory units in the second hierarchy as the division pattern C. The capacity is calculated (S512). In the example of FIG. 15, the division at this time is a division in which the “100ABCDE” directory 221 and the “101ABCDE” directory 222 are further divided into sessions.

  The controller 11 determines whether or not the total capacity required for the division pattern C is larger than the free capacity of the CD3 that is the backup destination medium (S514). When the total capacity required for the division pattern C is larger than the free capacity of the CD3 (S514: Yes), the division pattern B is selected (S516).

  When the total capacity required for the division pattern C is not larger than the free capacity of the CD3 (S514: No), the controller 11 divides a plurality of files in the second hierarchy subdirectory into two groups as the division pattern D. Dividing and calculating the capacity of CD3 required at this time (S518).

  Here, when there are subdirectories below the third hierarchy, they may be further divided into subdirectories. Here, since there are no sub-directories below the third layer, a large number of files existing in the sub-directory of the second layer which is the lowest layer are divided into a plurality of groups.

  The controller 11 determines whether or not the total capacity required for the division pattern D is larger than the free capacity of the CD3 (S520). When the total capacity required for the division pattern D is larger than the free capacity of the CD3 (S520: Yes), the division pattern C is selected (S522).

  When the total capacity required for the division pattern D is not larger than the free capacity of the CD3 (S520: No), the division pattern D is selected (S524).

  Note that, when divided by any of the above-described division patterns, an image file for each session is created in the hard disk drive 16. In this image file, data written to the CD 3 is provisionally collected into one file. For example, when the data of FIG. 6A is written to the CD 3, a file in which these data are collected into one is created. By reading this data and writing it to CD3, continuous data can be written without delaying the CD writing speed.

  Further, when divided by any of the above-described division patterns, the remaining number N of write sessions indicating how many times to write to CD3 is determined.

  Next, data to be written to CD3 is set to a read-only attribute (S526). Specifically, the attribute of the file to be written to the CD 3 in the memory card 2 is set to the read only attribute. The attribute is also set to the read-only attribute for the image file written to the CD 3 created in session units in the hard disk drive 16.

  Next, the controller 11 creates a file in which “write end information” is recorded (S528). The write end information includes the remaining number N of write sessions, information on files in each divided session, and information on whether or not writing to the CD 3 has been completed for each session. This “write end information” is a text file or binary file and is created in the hard disk drive 16 with a predetermined file name.

  Next, the image file of one session among the divided sessions is written to CD3 (S530). When the writing for one session is completed on the CD 3 and the session is closed, the controller 11 cancels the read-only attribute of the memory card 2 for the file included in the written session (S532). In addition, the read-only attribute of the image file of the written session is also released. Then, the controller 11 deletes the image file of the session written on CD3.

  Next, among the plurality of sessions, the write end information is updated in order to distinguish between the sessions for which writing to CD3 has been completed and the sessions for which writing has not been completed (S534). Specifically, information indicating that writing has been completed is added to a session for which writing has been completed.

  Next, the write session remaining number N of the write end information is decremented (S536). Then, the controller 11 determines whether or not the remaining number N of write sessions is greater than 0 (S538). Here, when the remaining number N of write sessions is not larger than 0 (that is, when N = 0) (S538: No), since there are no more sessions to be written, this backup processing is terminated.

  On the other hand, when the remaining number N of write sessions is greater than 0 (S538: Yes), the controller 11 acquires the remaining battery level (S540). The memory in the controller 11 stores the remaining battery level corresponding to the output voltage signal sent from the A / D conversion circuit 122. Therefore, the controller 11 can obtain the remaining battery level based on the output voltage signal from the A / D conversion circuit. Then, the controller 11 determines whether or not the remaining battery capacity is sufficient to write an image file for one session on the CD (S542).

  If the remaining battery level is sufficient (S542: Yes), the process returns to step S530 to write the image file of another session to the CD3. On the other hand, when the remaining battery level is not sufficient (S542: No), the controller 11 displays to the user that the remaining session cannot be written to the CD 3 because the remaining battery level is not sufficient, to the user. Notification is made (S544). Then, this backup process is terminated.

  When it is determined in step S538 that writing for all sessions has been completed, the selected file in the memory card 2 may be deleted. In this case, the file is safely “moved” from the memory card 2 to the CD 3.

  As described above, the attribute of the data to be copied is rewritten to read-only in the memory card 2 before writing to the CD 3 is performed. Then, in the memory card 2, the read-only attribute for the file included in the session for which copying has been completed is cancelled. By doing so, it is possible to delete the file of the session that has been properly copied in the memory card 2, while the file of the session that has not been properly written to the CD 3 may be deleted. Can not be. In this case, it can be considered that the memory card 2 corresponds to the first storage medium and the CD 3 corresponds to the second storage medium.

  For example, it is assumed that a plurality of files are divided into three sessions in order to back up a plurality of files to CD3. These sessions are referred to as a first session, a second session, and a third session. It is assumed that the backup of the first session is completed and the battery runs out during the backup of the second session. In that case, the read-only attribute is canceled in the memory card 2 for the file included in the first session. On the other hand, for the files included in the second session and the third session, the attribute in the memory card 2 is a read-only attribute.

  Under such circumstances, the user may forget for some reason that only the backup of the first session was performed among the backups that were divided into these three sessions. In such a case, it is conceivable that the user tries to delete all the files on the memory card 2. If all the files can be deleted, the files included in the second session and the third session that are not backed up will be lost. However, in the present embodiment, the read-only attribute is maintained in the memory card 2 for files included in the second session and the third session that have not been backed up. Therefore, even if the user intends to delete the file by mistake, the files included in the second session and the third session that have not been backed up are protected without being deleted.

  Further, every time writing for each session is completed, the read-only attribute is canceled in the hard disk 16 for the image file of the session for which writing has been completed. In addition, “write end information” indicating which session has been written is updated. Therefore, the image file of the session for which the read-only attribute has been canceled can be deleted, but the image file of the session for which writing has not been properly completed is not deleted. In this way, after restarting the printer 1, by referring to the “writing end information” again, a session that has not been properly written can be used to record the CD using the image file left on the hard disk drive 16. Writing to can be resumed. In this case, it can be considered that the hard disk drive 16 corresponds to the first storage medium and the CD 3 corresponds to the second storage medium.

  In this example, the image file is used to write data to the CD 3, but the lead-in, file data, and lead-out may be directly written to the CD 3 without creating the image file. .

  In addition, before the memory card 2 is inserted into the memory card reader / writer 12, the file on the memory card 2 may have a read-only attribute. In this case, the file name having the read-only attribute is stored in the memory of the controller 11 before backup. Then, after the backup is completed, the files having the read-only attribute from the beginning are not deleted and are left in the memory card 2 with the read-only attribute.

<When copying to the hard disk drive 16>
FIG. 16 is a flowchart showing a copy processing procedure for copying data in the memory card 2 to the hard disk drive 16. Here, a process of copying a data file from the memory card 2 to the hard disk drive 16 will be described with reference to this flowchart.

  Here, the memory card 2 has already been inserted into the memory card reader / writer 12 of the printer 1. The memory card 2 stores a file that is image data. A list of images stored in the memory card 2 is displayed on the liquid crystal display 17 of the printer 1.

  First, the user operates the operation panel 18 to select a file to be copied from the memory card 2 to the hard disk drive 16 of the printer 1 (S601). When selection of a file to be copied is completed and copying is instructed, the controller 60 changes the attribute of the selected image file to read-only in the memory card 2 (S602).

  Next, the controller 60 copies one of the selected files from the memory card 2 to the hard disk drive 16 (S603). Then, it is determined whether or not copying of this file is completed (S604). When copying of one of the selected files is completed normally, the read-only attribute of the file in the memory card 2 is canceled (S605). In this way, a file that has been successfully copied can be subsequently deleted from the memory card 2.

  On the other hand, the file copy may not be completed normally due to the battery running out of the printer 1 during the copy. In such a case, this copy process ends without being completed normally (S604: No). However, the attribute of the file that has not been normally copied at this time is read-only in the memory 2. Therefore, a file that has not been normally copied can be prevented from being deleted from the memory card 2 by the user thereafter.

  In step S605, when the read-only attribute of the file whose copy has been normally completed is cancelled, the controller 11 determines whether or not the copy of all the selected files has been completed (S606). If all the selected files have not been copied, the process returns to step S603 to copy the remaining files. Thereafter, the same processing as described above is repeated.

  In step S606, when all the files have been copied, this copy process ends. Here, when the copy process is completed, the file selected in the memory card 2 may be deleted. In this case, the file is safely “moved” from the memory card 2 to the hard disk drive 16.

  As described above, the attribute of the file to be copied is set to read-only in the memory card 2, and thereafter, the read-only attribute is canceled for the file that has been normally copied. Therefore, since the attribute remains read-only for files that have not been successfully copied, it is possible to prevent files that have not been successfully copied from being accidentally deleted. .

  For example, consider a case where a plurality of files (“image1.jpg”, “image2.jpg”, “image3.jpg”) are copied to the hard disk drive 16. Assume that the copy of the “image1.jpg” file is completed and the battery runs out during the copy of “image2.jpg”. In this case, the read-only attribute is canceled in the memory card 2 for “image1.jpg”. On the other hand, for “image1.jpg” and “image2.jpg”, the attribute in the memory card 2 is a read-only attribute.

  Under such circumstances, the user may be notified for some reason that the copy of all the files was not completed due to the battery running out. In such a case, it is conceivable that the user tries to delete all the files on the memory card 2. If all the files can be deleted, “image2.jpg” and “image3.jpg” that have not been copied are lost. However, in the present embodiment, “image2.jpg” and “image3.jpg” whose copying has not been completed have the read-only attribute in the memory card 2. Therefore, even if the user intends to delete by mistake, “image2.jpg” and “image3.jpg” whose copying has not been completed are protected without being deleted.

=== Other Embodiments ===
FIG. 17 is a perspective view for explaining the viewer. FIG. 18 is a block diagram for explaining the internal configuration of the viewer. The viewer is a portable terminal for storing image data captured by a digital camera or the like in the hard disk drive 16 and displaying the image by a user operation.

  The viewer 5 includes a controller 11 ′, a memory card reader / writer 12 ′, an interface 13 ′, a hard disk drive 16 ′, a liquid crystal display 17 ′, and an operation panel 18 ′. Here, the memory card reader / writer 12 ′, interface 13 ′, hard disk drive 16 ′, liquid crystal display 17 ′, and operation panel 18 ′ used have substantially the same functions as those of the printer 1 described above. is there. Therefore, with regard to the reference numerals, the same number is denoted by “′”, and the description is omitted. The viewer 5 is battery driven by a circuit similar to the circuit shown in FIG.

  The viewer 5 also copies files from the memory card 2 'to the hard disk drive 16' as described above. At this time, the copy process shown in FIG. 16 is performed. By doing so, the attribute remains read-only for files that have not been successfully copied, so that files that have not been successfully copied are not accidentally deleted. can do.

  The above-described embodiments are for facilitating the understanding of the present invention, and are not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and it is needless to say that the present invention includes equivalents thereof. In particular, the embodiments described below are also included in the present invention.

=== Summary ===
(1) A printer 1 including a data copying apparatus in the present embodiment includes a memory card reader / writer 12, a CD reader / writer, a hard disk drive 16, and a controller 11 as a copy unit. The copy unit copies the data stored in the memory card 2 to the CD 3 or the hard disk drive 16.
The printer 1 also includes a controller 11 as an attribute changing unit that changes the attribute of the data stored in the memory card 2 to read-only before copying the data to the second storage medium. The controller 11 changes the attribute of the data stored in the memory card 2 to an erasable attribute after the copying of the data to the second storage medium is completed.
In this way, it is possible to prevent data that has not been properly copied from being deleted from the memory card 2.

(2) The second storage medium is included in and controlled by the battery-powered printer 1.
As described above, when the second storage medium as the copy destination is driven by a battery, data copy may not be properly completed due to a battery exhaustion. Even in such a case, it is possible to prevent data that has not been properly copied from being deleted from the memory card 2.

(3) The memory card 2 as the first storage medium is detachable from the printer 1 including a data copying device. Here, the first storage medium is the memory card 2, but it may be a small hard disk.
In this way, when data is copied from the removable medium, it is possible to prevent data that has not been properly copied from being deleted from the memory card 2.

(4) In the memory card 2, data is managed by a FAT file system which is a file system managed in units of files, and this FAT file system has an area for storing attributes for making each file read-only.
In this way, the file attribute can be changed to a read-only attribute.

(5) The above-mentioned data is obtained by dividing the session into a plurality of sessions according to the capacity of the CD3.
As described above, when data is written on a plurality of CDs by dividing a session into a plurality of sessions, the possibility of running out of the battery increases. Even in such a case, it is possible to prevent data that has not been properly written from being deleted from the memory card 2.

(6) Also, before data is copied to the CD3, an image file in which data is collected in units of sessions is created.
In this way, the image file is read and written to the CD3, so that continuous data can be written without delaying the CD writing speed.

(7) The second storage medium is an optically readable storage medium such as a CD.
As described above, when data is written to the CD, there is a possibility of running out of the battery. Even in such a case, data that has not been properly written is not deleted from the memory card 2. Can be.

(8) The second storage medium is a storage medium to which data is written in session units, and is, for example, a CD.
As described above, when data is written to the CD, there is a possibility of running out of the battery. Even in such a case, data that has not been properly written is not deleted from the memory card 2. Can be.

(9) In the second storage medium, the data is managed by a file system that is managed in file units.
In this way, even when copying to the hard disk drive 16 and the battery runs out during copying, data that has not been properly copied is deleted from the memory card 2. can do.

(10) Further, the copying unit further deletes the data for which the above-described copying has been completed from the memory card 2.
In this way, a file can be moved from the memory card 2 to the second storage medium. Even in such a case, it is possible to prevent data that has not been properly moved from being deleted from the memory card 2.

(11) The configuration of the printer 1 as a data copying apparatus in the present embodiment can also be disassembled as follows. That is, the printer 1 includes a memory card reader / writer 12 as a connection unit for connecting to the memory card 2 and a second storage medium (hard disk drive 16 or CD reader / writer 13).
The printer 1 also includes a controller 11 that copies the data stored in the memory card 2 to the second storage medium described above. The controller 11 changes the attribute of the data stored in the memory card 2 to read only before copying the data to the second storage medium. Further, the controller 11 changes the attribute of the data stored in the memory card 2 to an erasable attribute after the copying of the data to the second storage medium is completed.
In this way, it is possible to prevent data that has not been properly copied from being deleted from the memory card 2.

(12) Needless to say, there is the following data copy method. That is, the data copying method includes a step of changing the attribute of the data stored in the memory card 2 to read-only, and the data stored in the memory card 2 after changing the attribute of the data to read-only. Copying to two storage media. The data copying method includes a step of changing the attribute of the data stored in the memory card 2 to an erasable attribute after the copying of the data to the second storage medium is completed.
In this way, it is possible to prevent data that has not been properly copied from being deleted from the memory card 2.

(13) Needless to say, there is a program for causing the data copying apparatus to perform the above-described data copying method.

1 is a perspective view for explaining an overall configuration of a printer. FIG. 1 is a block diagram of an overall configuration of a printer 1. FIG. FIG. 2 is a circuit diagram illustrating a power supply system of the printer 1. 3 is an example of a directory structure stored in a memory card 2. 4 is a data structure of backup data 30 when the backup target data shown in FIG. 4 is backed up to CD3 in one session. FIG. 6A shows the backup data after the backup of the first session, and FIG. 6B shows the backup data when the backup of the second session is executed following the first session. 3 is a diagram illustrating a data structure of a root directory 310. FIG. FIG. 10 shows a data structure of a “DCIM” directory entry 311. FIG. 5 shows a data structure of a “MISC” directory entry 312. FIG. 5 shows a data structure of a “100ABCDE” directory entry 321. FIG. 10 shows a data structure of a “101ABCDE” directory entry 322. It is a figure which shows the data structure of a path table. It is a flowchart which shows the procedure of the backup process which backs up the data of the memory card 2 to CD3. It is a flowchart which shows the procedure of the backup process which backs up the data of the memory card 2 to CD3. It is a figure which shows the relationship between a directory structure and a division | segmentation pattern. 4 is a flowchart showing a copy processing procedure for copying data in the memory card 2 to the hard disk drive 16; It is a perspective view for demonstrating a viewer. It is a block diagram for demonstrating the internal structure of a viewer.

Explanation of symbols

1 Printer, 2 Memory card, 3 CD, 11 Controller,
12 memory card reader / writer, 13 CD reader / writer, 14 printing section,
15 interface, 16 hard disk drive, 17 liquid crystal display,
18 operation panel, 19 computer, 110 AC adapter,
120 lithium ion battery pack, 121 charging circuit, 122 A / D conversion circuit,
123 power detection circuit, 130 DC-DC converter, 135 switch

Claims (13)

(A) a copy unit that copies data stored in the first storage medium to the second storage medium;
(B) Before copying the data to the second storage medium, change the attribute of the data stored in the first storage medium to read-only,
An attribute changing unit that changes the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A data copying apparatus comprising:   The data copying device according to claim 1, wherein the second storage medium is controlled by a battery-powered device.   3. The data copying apparatus according to claim 1, wherein the first storage medium is detachable from the data copying apparatus.   The data in the first storage medium is managed by a file system managed in units of files, and the file system has an area for storing attributes for making each file read-only. A data copy device.   5. The data copying apparatus according to claim 1, wherein the data is divided into a plurality of sessions according to the capacity of the second storage medium.   6. The data copying apparatus according to claim 1, wherein a file in which the data is grouped in a session unit is created before the data is copied to the second storage medium.   The data copying apparatus according to claim 1, wherein the second storage medium is an optically readable storage medium.   8. The data copying apparatus according to claim 1, wherein the second storage medium is a storage medium in which data is written in session units.   5. The data copying apparatus according to claim 1, wherein the data is managed by a file system managed in file units in the second storage medium. 6.   The data copying apparatus according to claim 1, wherein the copying unit further deletes the data for which the copying has been completed from the first storage medium. (A) a connection unit for connecting the first storage medium;
(B) a second storage medium;
(C) a controller that copies data stored in the first storage medium to the second storage medium,
Before copying the data to the second storage medium, change the attribute of the data stored in the first storage medium to read-only,
A controller that changes the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A data copying apparatus comprising: Changing the attribute of the data stored in the first storage medium to read only;
Copying the data stored in the first storage medium to a second storage medium after changing the attribute of the data to read only;
Changing the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
To copy data including A program for operating a data copying device,
Changing the attribute of the data stored in the first storage medium to read only;
Copying the data stored in the first storage medium to a second storage medium after changing the attribute of the data to read only;
Changing the attribute of the data stored in the first storage medium to an erasable attribute after the copying of the data to the second storage medium is completed;
A program for causing the data copying apparatus to execute

Images