Commutative storage medium, control method and computer system

Description: TECHNICAL FIELD [Detailed description of the invention]

【0001】

[Technical field to which the invention belongs]

The present invention relates to a data file and a convertible storage medium for storing the data file in association with a program for processing the data file so that the data file can be used in a computer system, a method for writing / reading the data file to the convertible storage medium, and a method for writing / reading the data file. The present invention relates to a computer system using the convertible storage medium as a data input / output medium.

【0002】

[Conventional technology]

Conventionally, in order to make a data file recorded on a replaceable storage medium (portable and replaceable storage medium) such as a floppy disk or an optical disk available in a computer system, the data file is stored in the replaceable storage medium in advance. It is necessary to store the software for using the existing data in the computer system.

【0003】

[Problems to be Solved by the Invention]

For this reason, conventionally, a user who intends to use the data recorded in the convertible storage medium is software (program) for using the data according to the format of the data stored in the convertible storage medium and the storage method thereof. It is necessary to register the data in the computer system before using the data, the operation performance is poor, and if the software cannot be registered, there is a problem that the data stored in the replaceable storage medium cannot be used. In particular, one computer system or operation system may be able to use the data stored in the convertible storage medium, but another computer system or operation system may not be able to use the data, and the data may not be available between computer systems of different architectures or different operations. There was a problem that data could not be exchanged between systems.

【0004】

In addition, there are cases where it is desired to limit the computer system (operation system) and users who can use the data stored in the commutative storage medium, or when it is possible to read only the data and prohibit writing. There was a problem that control could not be done easily. Furthermore, since the data file is read by specifying the file name in the past, the data file can be easily read by using the search keyword, or a plurality of data files can be read at once by using the search keyword. There was no problem. Furthermore, since the conventional operation system (OS) defines a fixed data length unit (cluster) and its arrangement to access the data file, if the cluster length is short, long size data such as video data is used. Then, it becomes a shredded state, and the performance related to reading and writing deteriorates. On the contrary, if the cluster length is lengthened, an unused area is generated when relatively small data such as text data is recorded, and there is a problem that space efficiency is lowered.

【0005】

From the above, an object of the present invention is to prevent the user from having to register software corresponding to the data format and the storage method in the computer system one by one in order to use the data file stored in the convertible storage medium. It is to be. An object of the present invention is to enable computer systems having different operating systems to commonly use data files stored in a commutative storage medium. An object of the present invention is to easily limit the computer system (operation system) and users who can use the data file stored in the commutative storage medium, and to easily set the read / write conditions. That is. An object of the present invention is to be able to read a desired data file by inputting a search keyword. An object of the present invention is to enable recording of a data file in a data size unit and data arrangement suitable for the data file.

【0006】

[Means for solving problems]

FIG. 1 is an explanatory diagram of the principle of the present invention. In the figure, 1 is a portable and interchangeable storage medium, for example, an optical disk, 2 is an optical disk drive device, 3 is a computer system, and 3a is a processing device (CPU). Data management information 30, program management information 40, multiple data files (DATA A to DATA C) 31 to 33, and processing to make the data files available in the computer system are processed on the convertible storage medium 1. The programs to be applied (DATA DRIVER 1 to DATA DRIVER 3) 41 to 43 are stored. The data management information 30 is the name of each data file, (1) the file name 30a, (2) the location position 30b of the data file, and (3) the name of the program that processes the data file so that it can be used in the computer system. It maintains a correspondence with 30c. The program management information 40 maintains the correspondence between (1) the program name 40a, (2) the program location 40b, and (3) the name of the operating system in which the program can be used (OS information) for each program. ing. The operating system name does not necessarily have to be stored. ... Claims 1 and 2 [0007]

When writing a data file, the processing device 3a of the computer system associates the data file to be written with a processing program for making the computer system 3 available later and writes it to the convertible storage medium 1. Then, when the data file is read, the processing device 3a is subjected to processing such as conversion so that the data file can be used by the computer system 3 by a program corresponding to the data file to be read, and thereafter, the processing is performed. Performs a predetermined process using the data file. For example, a data file is compressed and written to a convertible storage medium 1, and when the data file is read, the data file can be restored (decompressed) using a program corresponding to the data file and processed by the computer system 3. Convert to data format. ... Claims 8, 9, 20 [0008]

When writing a data file, the processing device 3a associates the data file to be written with a processing program for making the computer system available later and an operating system name capable of executing the program, and stores the data file in a convertible manner. Write to medium 1. Then, when the data file is read, the processing device 3a is a program corresponding to the data file to be read, and a program that can be executed by the computer system 3 is used to convert the data file into a data file that can be used by the computer system. After that, a predetermined process is executed using the processed data file. For example, a data file is recorded in the convertible storage medium 1 in a data format independent of the operation system, and a processing program for making the data file available to the computer system is stored according to each OS. deep. Then, when a computer system equipped with a predetermined OS reads a data file, a data format capable of processing the data file by using a program corresponding to the data file to be read and corresponding to the OS of the own computer system. Convert to. ... Claims 3, 10, 11, 21 [0009]

In addition to the program management information 40, (1) program name 40a, (2) program location 40b, (3) name of operating system OS that can use the program 40c, and (4) reading of data files by the OS. And to include information that identifies whether it is writable or not, or read and write conditions, and that information allows both read / write or only read, or prohibits both read / write. Instruct. This makes it possible to limit the operating system OS and users who can use the data stored in the commutative storage medium. ... Claims 4, 12 to 15 The program management information 40 is specified by including (1) the program name 40a, (2) the program location 40b, and a keyword for data file search, and specifying the search keyword when reading the data file. Read the data file with the search keyword. ... Claims 7, 16, 17 When recording a data file in a predetermined data size unit, the data management information 30 includes (1) file name and (2). In addition to the name of the program for determining the data size and the data arrangement, the data arrangement information indicating the start position of the data file and the data position where the data of each data size unit is recorded is included, and the data file is read when the data file is read. Read the data file using the start position and placement information. ... Claims 8, 18, 19 [0010]

BEST MODE FOR CARRYING OUT THE INVENTION

(A) First Example (a) System configuration FIG. 2 is a configuration diagram of a computer system of the present invention, in which 1 is a portable and interchangeable storage medium, for example, an optical disk, and 2 is an optical disk drive device that reads data (data file, program) from the optical disk and writes data. , 3 are computer systems. In computer system 3, 3a is a processing unit (CPU), 3b is a bus line (BUS), 3c is RAM, 3d is ROM, 4a is a CRT control device, 4b is a display device (for example, CRT), and 5a is a keyboard control device. 5b is a keyboard, 6a is a mouse control unit, 6b is a mouse, 7a is a printer control unit, 7b is a printer, 8a is an external storage device such as a hard disk, 8b is a hard disk drive device, and 9a is an external storage control that controls each drive device. The device, 9b, is a BUS for an external storage device. The optical disk 1 has N tracks, each track is composed of, for example, 24 sectors, and logical sector addresses are sequentially assigned from the first sector of the first track to the 24th sector of the Nth track, and the sector position is determined by the sector address. Has come to be identified.

【0011】

(b) Data structure of commutative storage medium As shown in FIG. 3, the optical disk 1 which is a replaceable storage medium includes volume management information 20, user data management information 30, data driver management information (program management information) 40, and a plurality of data files (DATA A ~. DATA C) 31 to 33 and data drivers (DATA DRIVER 1 to DATA DRIVER 3) 41 to 43 that process the data file so that it can be used in the computer system are stored. The volume management information 20 is written in a predetermined location on the optical disk 1, and (1) data 20a indicating the start position of the user data management information 30 and (2) data indicating the start position of the data driver management information 40. Has 20b. User data management information 30 is provided in (1) file name (DATA A to DATA C) 30a, (2) data file start position (file first sector position) 30b, and (3) data file for each data file. Name of data driver (program) to be processed so that it can be used in a computer system (DATA DRIVER 1 ~ DATA DRIVER 3) Maintains a correspondence with 30c. The data driver management information 40 includes (1) a data driver name (DATA DRIVER 1 to DATA DRIVER 3) 40a and (2) a data driver start position (data driver first sector) 40b for each data driver.

【0012】

(c) Outline of operation The computer system 3 is operated by a program included in any of an external storage device such as ROM 3d, a commutative storage medium 1, or a hard disk 8a, or an operating system OS configured by cooperating with each program. When a request to acquire a data file from the convertible storage medium 1 (for example, a data file read command) occurs from the program or from the keyboard 5b, the CPU 3a refers to the user data management information 30 recorded on the medium and the target data. The start position 30b of the file and the name 30c of the data driver that processes the data file so that it can be used in the computer system are acquired and stored in RAM3c. Next, the CPU 3a refers to the data driver management information 40, obtains the start position of the data driver having the acquired data driver name, and stores it in the RAM 3c. After that, the data driver is read into RAM3c, the data file is read from the start position of the acquired target data file, and the data file is processed into the data file in a format that can be used by the computer system. After that, the CPU 3a performs a separately instructed process on the processed data file.

【0013】

(d) Data file reading process FIG. 4 shows a processing flow of the first embodiment when a predetermined data file is read from the commutative storage medium 1. When the CPU3a issues a command to read a predetermined data file, the CPU3a reads the user data management information 30 into the RAM3c (step 101). Then, from the user data management information 30, a file name (data name) that matches the file name (data name) specified by the read command is obtained (steps 102 to 104). If the file name specified by the read command does not exist in the user data management information 30, it means that the file name is not recorded in the commutative storage medium 1, and the process ends (abend).

【0014】

On the other hand, when the file name corresponding to the user data management information 30 exists, the data file start position and the name of the data driver stored corresponding to the file name are acquired (step 105). For example, when trying to acquire a data file named Data A, if the data management information as shown in FIG. 3 is recorded in the convertible storage medium 1, the start sector position is "1" and the data driver name. "Data Driver 1" is acquired as. After that, the CPU 3a reads the data driver management information 40 into the RAM 3c (step 106), and acquires the data driver management information having the data driver name obtained in step 105 from the data driver management information 40 (steps 107 to 109). If the data driver name obtained in step 105 does not exist in the data driver management information 40, it means that the corresponding data driver is not recorded in the commutative storage medium 1, and the process ends (abend). ..

【0015】

On the other hand, if the data driver name obtained in step 105 exists in the data driver management information 40, the recording start position of the data driver stored corresponding to the data driver name is acquired and stored in RAM3c. (Step 110). In the previous example, the start position "10" of "Data Driver 1" is acquired. After that, the CPU 3a reads the data driver into the RAM 3c from the start position, and also reads the data file into the RAM 3c from the start position obtained in step 105 (steps 111 to 112). After that, CPU3a performs predetermined processing on the data file by the read data driver so that it can be used in the computer system (step 113). For example, the data file is compressed and written to the convertible storage medium 1, and when the data file is read, the data file is restored (decompressed) using the data driver corresponding to the data file, and the computer system 3 Convert to a processable data format.

【0016】

(e) Data file writing process When writing a data file, there are three ways to select a data driver to process the data file. The first method is the method selected by the user, the second method is the method selected by the application, and the third method is the method selected by the data driver itself. (e-1) Process of selecting a data driver by the first method FIG. 5 is a write processing flow of the first embodiment in which the data driver is selected by the first method and the data file is written to the commutative storage medium 1. At the start of writing the data file, the user enters the data driver name or information that identifies the equivalent data driver (step 151). For example, the data driver can be explicitly specified by sending a command such as "Set Data Driver = Driver 1" from an input device such as a keyboard.

【0017】

After that, the CPU 3a determines whether or not the specified data driver name exists in the data driver management information 40 (steps 152 to 154), and if it exists, performs the writing process after step 155. On the other hand, if the specified data driver name does not exist in the data driver management information 40, the process ends because the corresponding data driver does not exist in the commutative storage medium 1 (abend end abnormally). If a data driver exists, the recording start position of the data driver specified from the data driver management information 40 is acquired and stored in RAM3c (step 155). After that, the CPU 3a reads the data driver into the RAM 3c from the start position (step 156), and performs a predetermined processing process on the data file by the data driver (step 157).

【0018】

After the processing is completed, the CPU 3a reads the user data management information 30 from the commutative storage medium 1 (step 158), acquires a position for recording the data file (step 159), and writes the processed data file to the recording position. (Step 160). After that, the CPU3a generates user data management information indicating the correspondence between the file name of the data file, the name of the data driver, and the writing position of the data file, and writes the user data management information to the convertible storage medium (step 161). The first method for the user to select a data driver is used in the following cases. For example, if the first data Driver 1 that does not restrict users and the second data driver data Driver 2 that prompts password input and restricts the use of others exist on the convertible storage medium 1, the user created it. Select data Driver 1 if you do not want to restrict the use of the text data when recording the text data file, and select data Driver 2 if you want to restrict the users.

【0019】

(e-2) Process of selecting a data driver by the second method The second way to select a data driver is for the application to select a data driver. The data formats handled by various applications are predetermined, such as text data for word processors and spreadsheet data for spreadsheet software. Therefore, when writing the created data file, the application automatically issues a command such as "Set data Driver = Driver 1" to select a data driver that matches its data format. The data file writing processing flow by this second method is almost the same as that in FIG. The difference is that in step 151, the application inputs the data driver name or the information for identifying the data driver by the above instruction prior to writing the data, and the processing after step 152 is exactly the same as that in FIG. ..

【0020】

(e-3) Process of selecting a data driver by the third method The third method of selecting a data driver is to determine whether or not the data driver itself can handle the data to be written, and if it is determined that the data driver can handle the data, the data driver is used. When writing data, for example, specify a file name on the medium such as "data A.txt" in the command "Write" that instructs writing, such as "Write date A.txt". The period after the period "." In this file name is called the extension. For example, the contents of the file are specified as "txt" for text files, "bmp" for image data, and "wav" for music data. doing. Therefore, the extension is defined when the data driver is created, and as shown in FIG. 6, in the data driver management information 40, the data driver name 40a is associated with the data driver start position 40b and the extension 40c to be the convertible storage medium 1. Remember. In this way, when the above write command is generated, the data driver can be selected from the data driver management information 40 using the extension of the file name as a key.

【0021】

FIG. 7 is a write processing flow of the first embodiment in which the data driver is specified by the third method and the data file is written to the commutative storage medium 1. When the write command "Write date A.txt" occurs (step 181), CPU3a cuts out the extension "txt" (step 182). Then, the extensions that can be handled by each data driver are extracted from the beginning of the data driver management information 40 (steps 183 to 185). In the example of the data driver management information 40 in FIG. 6, the extensions that can be handled by the first and second data drivers Data Driver 1 and Data Driver 2 are "wav" and "bmp", respectively. Not selected. However, the extension that the third data driver, Data Driver 3, can handle is "txt", which matches the extension included in the write command. Therefore, the data driver Data Driver 3 is selected, and the subsequent writing process is performed. However, if there is no data driver that can handle the extension of the data file included in the write command, it will end abnormally.

【0022】

After that, the same processing as in FIG. 5 is performed to write the data file specified by the write command to the commutative storage medium 1. That is, the recording start position of the data driver is acquired from the data driver management information 40 and stored in RAM3c (step 186). After that, the CPU 3a reads the data driver into the RAM 3c from the start position (step 187), and performs a predetermined processing process on the data file by the data driver (step 188). After the processing is completed, the CPU 3a reads the user data management information 30 from the commutative storage medium 1 (step 189), acquires a position for recording the data file (step 190), and writes the processed data file to the recording position. (Step 191). After that, the CPU3a generates data management information indicating the correspondence between the file name of the data file, the name of the data driver, and the writing position of the data file, and writes the data management information to the convertible storage medium (step 192).

【0023】

In the above, an example of selecting a data driver according to the extension has been shown, but in many cases, an ascii character string or the like for specifying the data format is embedded in the data file. Therefore, in such a case, in the data driver management information 40, the data driver start position 40b and the above ascii character string are associated with the data driver name 40a, and when a data file write command is issued, the data file is displayed. It can be configured to refer to the included ascii string to select a data driver. Of course, the extension and this method may be used together.

【0024】

As described above, in the description of the first embodiment, the reading / writing of the data file and the processing of the data file are separated, but the reading / writing may be performed while sequentially processing. When using an image data file as the data file of the first embodiment, record it on the convertible storage medium 1 in a format such as JPEG, TIFF, etc., and register the conversion program to the data format that is good at a certain OS as a data driver. To do. In this way, the OS does not care what the format of the recorded image data file is, reads the data as a pair with the data driver, and processes (converts) the data file with the data driver. The image data can be used by. Also, when recording a data file on the convertible storage medium 1, the data file can be written by the procedure of reading the data driver, processing the data file, and writing the processed data file. Therefore, when using a data file with a special data format or a new data format, you can use it without changing the OS by simply creating a data driver.

【0025】

(B) Second Example (a) Outline of the second embodiment The second embodiment makes it possible to use the data files in common even in different OSs, and the system configuration is the same as the configuration of the first embodiment shown in FIG. As shown in FIG. 8, the optical disk 1 which is a commutative storage medium has a data storage configuration substantially similar to that of the first embodiment of FIG. The first difference is that the data driver management information 40 is for each data driver: (1) data driver name (DATA DRIVER 1 to DATA DRIVER 3) 40a and (2) data driver start position (data driver first sector). In addition to 40b, (3) it has the name of the operating system OS that can use the data driver. The second difference is that there are two or more data driver management information having the same data driver name, and each operating system name is different. That is, two data drivers for operation systems A and B are registered as data driver Data Driver 1, and two data drivers for operation systems A and B are registered as data driver Data Driver 2.

【0026】

A data file is recorded in the convertible storage medium 1 in a data format independent of the operation system, and a processing program for making the data file available to the computer system is stored according to each operation system OS. Keep it. Then, when a computer system equipped with a predetermined operating system OS reads a data file, the data driver is operated by using a data driver corresponding to the data file to be read and corresponding to its own operating system OS. Convert to a data format that can be processed by the system OS.

【0027】

(b) Data file reading process of the second embodiment FIG. 9 is a data file reading processing flow of the second embodiment. When the data file read command is issued, CPU3a reads the user data management information 30 into RAM3c (step 201). Then, from the user data management information 30, a file name (data name) that matches the file name specified by the read command is obtained (steps 202 to 204). If the file name specified by the read command does not exist in the user data management information 30, the process ends (abend abnormally). On the other hand, when the file name corresponding to the user data management information 30 exists, the data file start position and the name of the data driver stored corresponding to the file name are acquired from the data management information 30 (step 205). ). Next, CPU3a reads the data driver management information 40 into RAM3c (step 206), and is a data driver with the data driver name obtained in step 205, and can execute its own operating system OS (use). (Available) Acquires the data driver management information of the data driver (steps 207 to 210), and then executes the reading process from step 211 onward.

【0028】

On the other hand, if there is no data driver that has the data driver name obtained in step 205 and can be executed (can be used) in its own operating system OS, the process ends (abend). After step 210, CPU3a acquires the recording start position of the data driver and stores it in RAM3c (step 211). After that, the CPU 3a reads the data driver into the RAM 3c from the start position, and also reads the data file into the RAM 3c from the start position obtained in step 205 (steps 212 to 213). After that, CPU3a uses the read data driver to perform predetermined processing on the data file so that it can be used in the computer system (step 214). As described above, when the data file Data A is read when the user data management information 30 and the data driver management information 40 are recorded on the replaceable recording medium 1 as shown in FIG. 8, the data is obtained from the user data management information 30. "Data Driver 1" is required as a data driver for processing files. Then, referring to the data driver management information 40 in Fig. 8, Data Driver Two types of "1" are recorded depending on the OS. If the operating system used in computer system 3 is OS / B, the start position of the data driver can be specified as "12", and from that start position. Data driver Data Driver 1 is read, and the data driver performs predetermined processing on the data file Data A.

【0029】

(c) Data file writing process of the second embodiment FIG. 10 shows a data file writing processing flow of the second embodiment, and is a case where the user selects a data driver. At the start of writing the data file, the user enters the data driver name or information that identifies the equivalent data driver (step 251). For example, the data driver can be explicitly specified by sending a command such as "Set data Driver = Driver 1" from an input device such as a keyboard. After that, CPU3a is a data driver having the specified data driver name in the data driver management information 40, and determines whether or not there is a data driver that can be used by its own operating system OS (steps 252 to 255). ), If it exists, the writing process after step 256 is performed. On the other hand, if the data driver name specified in the data driver management information 40 does not exist, the corresponding data driver does not exist in the commutative storage medium 1, and the process ends (abend abnormally).

【0030】

If the data driver exists, the recording start position of the data driver is acquired from the data driver management information 40 and stored in RAM3c (step 256). After that, the CPU 3a reads the data driver into the RAM 3c from the start position (step 257), and performs a predetermined processing process on the data file by the data driver (step 258). After the processing is completed, the CPU 3a reads the user data management information 30 from the commutative storage medium 1 (step 259), acquires a position for recording the data file (step 260), and writes the processed data file to the recording position. (Step 261). After that, the CPU3a generates data management information indicating the correspondence between the file name of the data file, the name of the data driver, and the writing position of the data file, and writes the data management information to the convertible storage medium (step 262).

【0031】

(d) Application example of the second embodiment (d-1) First application example According to the second embodiment, each operation operates a processing program for recording the data file on the convertible storage medium 1 in a data format independent of the operating system and making the data file available to the computer system. When a computer system equipped with a predetermined operating system OS reads a data file, it is a data driver of the data file to be read and is a data driver corresponding to its own operating system OS. Convert the data file into a data format that can be processed by the operating system OS. FIG. 11 is an explanatory diagram of the first application example of the second embodiment, FIG. 11 (a) is a partial character string of the text data file Data A created by the ascii code, and FIG. 11 (b) is the operation system OS. A character string expressed in shift JIS format that can be handled by / A, and Fig. 11 (c) is a character string expressed in JIS format that can be handled by the operation system OS / B.

【0032】

OS / A can handle text data in the character code format called shift JIS format, OS / B can handle text data in the character code format called JIS format, and the convertible storage medium 1 has a text data file Data A in ASCII code. It shall be recorded. In such a case, in order to read the data file Data A recorded in the convertible storage medium 1 into the memory by the OS / A, the OS / A refers to the user data management information 30 and describes the data file Data A. Search for. By this search, the OS / A gets the starting position of the data file Data A and the name of the data driver (Data Driver 1). Next, the OS / A refers to the data driver management information 40 and the information about the data driver Data Driver 1. In the example of Fig. 8, the description about the data driver Data Driver 1 can be found for OS / A and for OS / B, but since it is referenced by OS / A, the data driver for OS / A Data Driver It is possible to acquire the start position information (start sector 10) regarding 1. Therefore, the data driver Data Driver 1 related to OS / A is read into the memory. The data driver Data Driver 1 for this OS / A has a function of converting text data in ascii format recorded in the commutative storage medium 1 into shift JIS format. Therefore, at the same time as reading the data file Data A from the convertible storage medium 1 or once storing it in the memory, the data file Data A is changed from the ascii format to the shiftJIS format by the data driver Data Driver 1 for the OS / A. Data conversion becomes possible, and it becomes a data format that can be used by OS / A.

【0033】

In the case of OS / B, the data driver Data Driver 1 for OS / B is selected and loaded into the memory when the data driver management status 40 in Fig. 8 is referenced. This Dedriver Data Driver 1 for OS / B has a function to convert text data in ascii format to JIS format, so it can be used in OS / B by performing the same conversion as in the case of OS / A. It can be a data format. When writing data, if you want to record shift JIS format text data on the medium in OS / A, select the data driver Data Driver 1 for OS / A from the data driver management information 30 and select this data driver for OS / A. Data Driver 1 converts the shift JIS format to the ascii format, and records the data file in the ascii format on the convertible storage medium 1. If you want to record JIS format text data on a medium in OS / B, select Data Driver 1 for OS / B and Data Driver for this OS / B. 1 converts the data format from JIS format to ascii format, and records the data file in ascii format on the commutative storage medium 1.

【0034】

In the above example, the example of data format conversion in text data has been shown, but the same applies to various data files such as image data files, music data files, and table calculation data files. That is, the operating system OS supports one of the most suitable formats for each data type within the limits based on the resources available to the OS, and uses a data driver to follow the data file. By processing the data, data can be easily exchanged between different OSs.

【0035】

(d-2) Second application example FIG. 12 is an explanatory diagram of the second application example, in which OS / A can handle images in the bitmap method, OS / B can handle image data in Raw format, and the convertible storage medium 1 is a JPEG that does not depend on the operation system. This is the case when recording the data file Data A in the format. As shown in Fig. 12 (a), it is assumed that the user creates image data expressed in 1 byte / pixel for 8 × 8 pixels on OS / B. In OS / B, the data format is as shown in Fig. 12 (b) because it is simply an image-only data format called RAW format. To record this on a commutative storage medium, the data driver for OS / B converts the above RAW format image data into JPEG format and records it. That is, first, the RAW format image data is converted into the data in the spatial frequency domain by using a method called DCT (discrete cosine transform). Then, each frequency component is quantized using a quantization table such as a Huffman table, then entropy-encoded to convert it into JPEG format image data shown in FIG. 12 (c), and the JPEG obtained by the conversion. The image data in the format is recorded in the convertible storage medium 1.

【0036】

After that, when the JPEG format image data recorded in the convertible storage medium 1 is used in OS / A, the data driver for OS / A once performs entropy decoding of the JPEG image data on the memory. , Inverse quantization is performed in the quantization table, and then inverse DCT transform is performed to reproduce the image data in RAW format. After that, the arrangement of the data is exchanged, and it is converted into a bitmap format that can be executed by the OS / A as shown in Fig. 12 (d). In this example, the conversion from OS / B to OS / A is shown, but the reverse is also true. The same applies to formats called TIFF other than RAW, JPEG, and bitmaps. The same applies to a moving image composed of a plurality of image data.

【0037】

(d-3) Third application example By using the data driver as a program for compressing and decompressing data, the size of the data file recorded on the commutative storage medium can be reduced. When such a data driver is used, in the data processing process of step 214 in FIG. 9, decompression processing (compression data restoration processing) is performed by the data driver, and data compression processing is performed in the data processing process of step 258 in FIG. Will be.

【0038】

Various methods have been proposed as compression / decompression methods. For example, FIG. 13 shows the flow of data compression processing when the run length method is used. run The length method compresses 0 or 1 data by recording the continuous amount when the data is continuous. In the data processing (compression process) of step 258 in FIG. 10, the CPU 3a sets the first register variable C to 0, and then n bits (for example, 8 bits) of data from the memory in which the data to be compressed is stored. To the register (steps 258a to 258b). Then, after setting the second register variable I to 0 (step 258c), each bit is checked to see if it is the same as the previous bit, and if they are the same, C is counted up and I is counted up, and I = 8. Check (steps 258d ~ 258h). If I <8, the processing after step 258d is repeated. If I = 8, the end of the data is checked (step 258i), and if not, the process returns to step 258b, reads the next 8-bit data, and continues the subsequent processing. On the other hand, if it differs from the previous data in step 258d, the register variable C (the number of consecutive "1" or "0") is output (step 258j), and then the register variable is cleared to 0 (step 258k). ), After that, the processing after step 258g is repeated.

【0039】

In the above compression processing example, the data to be read from the memory into the register is set to 8 bits. However, depending on the CPU and OS of the computer system used, the amount of data n that can be captured at one time differs, such as 8bit, 16bit, 32bit, 64bit, and the larger n, the better the processing efficiency. Therefore, for example, a data driver that compresses / decompresses data with a data amount of n = 16 is used for OS / A, and a data driver that compresses / decompresses data with a data amount of n = 64 is used for OS / B. It is possible to achieve maximum performance by registering in and using different data drivers depending on the OS. Although the run length method has been used as the data compression method, the present invention is not limited to this method.

【0040】

(C) Third Example The third embodiment is an example of limiting the usage environment and users of the data file stored in the commutative storage medium, and the system configuration is the same as that of the first embodiment of FIG. (a) Data structure in commutative storage medium FIG. 14 is an explanatory diagram of the data structure of the commutative storage medium according to the third embodiment, and has almost the same data structure as that of FIG. The difference is that the data driver management information 40 is for each data driver, (1) data driver name (DATA DRIVER 1 to DATA DRIVER 3) 40a, and (2) data driver start position (data driver first sector) 40b. (3) In addition to the name 40d of the operating system OS that can use the data driver, (4) the usage environment of the data file stored in the convertible storage medium and the condition 40e that limits the user are provided. .. According to condition 40e, (1) whether the operating system can read and write data files unconditionally using the data driver, and (2) Terms of use are specified to enable reading and writing. The usage conditions are described using the type of OS, the type and size of data, and user information, and it is possible to describe one or a combination of these pieces of information. The condition may always be fixed, or the user may be prompted to enter data such as a password, which may be a condition. Moreover, those conditions do not have to be the same at the time of writing and at the time of reading. Further, the conditions may be the same for the entire commutative storage medium, or may be specified for each data file.

【0041】

In FIG. 14, the data file Data A using Data Driver 1 can be accessed only by Read Only in OS / A, but can be read / written in OS / B. In addition, the data file Data B that uses "Data Driver 2" requires the password password to be entered in OS / A, and can be accessed only when "abc" is entered, whereas in OS / B it is accessible. Unconditionally inaccessible.

【0042】

(b) Data file reading process FIG. 15 is a data file reading processing flow in the third embodiment. When the data file read command is issued, CPU3a reads the user data management information 30 into RAM3c (step 301). Then, from the user data management information 30, a file name (data name) that matches the file name specified by the read command is obtained (steps 302 to 304). If the file name specified by the read command does not exist in the user data management information 30, the process ends (abend abnormally). On the other hand, when the file name corresponding to the user data management information 30 exists, the data file start position and the name of the data driver corresponding to the file name are acquired from the data management information 30 (step 305). Next, CPU3a reads the data driver management information 40 into RAM3c (step 306), and is a data driver with the data driver name obtained in step 305, and can execute its own operating system OS (use). (Available) Acquires the data driver management information of the data driver (steps 307 to 310), and then executes the reading process from step 311 onward.

【0043】

On the other hand, if there is no data driver that has the data driver name obtained in step 305 and can be executed (can be used) by its own operating system OS, the process ends (abend). After step 310, CPU3a acquires the recording start position of the data driver and stores it in RAM3c (step 311). After that, CPU3a reads the data driver into RAM3c from the start position (step 312). When the reading of the data driver is completed, CPU3a acquires the reading condition (available environment condition) 40e from the data driver management information 40 (step 313), and determines whether the reading condition is satisfied (step 314). If the reading conditions are not satisfied, the data file ends abnormally, and if it is satisfied, the data file is read into RAM3c from the start position obtained in step 305, and the read data driver is used to convert the data file into a computer system. Perform the prescribed processing so that it can be used in (step 315).

【0044】

In step 313, if the usage condition is "read only" or "full access", the data file is unconditionally allowed to be read, and if it is "disabled", the data file is unconditionally prohibited from being read. , In the case of "passward abc", a message prompting the password input is displayed on the display screen, and the data file is allowed to be read only when the password "abc" is input.

【0045】

(c) Data file writing process FIG. 16 shows a data file writing processing flow of the third embodiment, and is a case where the user selects a data driver. At the start of writing a data file, the user enters the data driver name or information that identifies the equivalent data driver. For example, by sending a command such as "Set data Driver = Driver 1" from an input device such as a keyboard, the data driver is explicitly specified. After the above command is input, CPU3a determines whether or not there is a data driver having the specified data driver name in the data driver management information 40 and which can be used by its own operating system OS. (Steps 351 to 354), and if it exists, the processing after step 255 is performed. On the other hand, if the data driver name specified by the above command does not exist in the data driver management information 40, the process ends (abend abnormal termination).

【0046】

If the data driver exists, the recording start position of the data driver is acquired from the data driver management information 40 and stored in RAM3c (step 355). After that, CPU3a reads the data driver into RAM3c from the start position (step 356), acquires the write condition (available environment condition) 40e from the data driver management information 40 (step 357), and determines whether the write condition is satisfied. (Step 358). If the writing conditions are not satisfied, the process terminates abnormally, and if the writing conditions are satisfied, the user data management information 30 is read from the commutative storage medium 1 (step 359), and a position for recording the data file is acquired (step 359). 360). After that, CPU3a performs a predetermined processing process on the data file to be written using the data driver read in step 356, and writes the processed data file to the recording position obtained in step 360 ( Step 361). Finally, the CPU3a generates data management information indicating the correspondence between the file name of the data file, the name of the data driver, and the writing position of the data file, and writes the data management information to the convertible storage medium (step 362).

【0047】

In step 358, if the usage condition is "full access", the data file is unconditionally allowed to be written, and if it is "read only" or "disable", the data file is unconditionally prohibited from being written. , In the case of "passward abc", a message prompting the password input is displayed on the display screen, and the writing of the data file is permitted only when the password "abc" is input. As described above, by realizing the function to limit the usage environment with the data driver, for example, full access in the data file authoring environment, Read Only in the user's usage environment, and only users who satisfy the usage conditions can use it. It becomes possible to use it widely while protecting the rights of data.

【0048】

(d) A modified example of the third embodiment The above is a case where the usage conditions (data file access conditions) are added to the data driver management information 40 and the reading and writing of the data file are permitted or prohibited based on the usage conditions. However, the data file is added to the data driver. It is also possible to have a function to manage the user's access to. FIG. 17 shows a flow of reading processing in such a case, and the same steps as the processing flow of FIG. 15 are assigned the same step numbers. The data driver only manages the access of the data file, and does not perform any processing such as conversion on the data file.

【0049】

In FIG. 17, the difference from the process of FIG. 15 is the process after loading the data driver into RAM3c in step 312. When the CPU3a reads the data driver, it immediately executes the data driver (step 321), and determines whether or not to continue the subsequent data file reading process based on the execution result of the data driver (step 322). .. If the return value obtained by executing the data driver is FALSE, it ends abnormally, and if it is TRU, the data file is read into RAM3c from the start position obtained in step 305 (step 315). FIG. 18 shows a flow of writing processing, and the same steps as the processing flow of FIG. 16 are assigned the same step numbers. The data driver only manages the access of the data file, and does not perform any processing such as conversion on the data file.

【0050】

In FIG. 18, the difference from the process of FIG. 16 is the process after loading the data driver into RAM3c in step 356. When the CPU3a reads the data driver, it immediately executes the data driver (step 371), and determines whether or not to continue the subsequent data file writing process based on the execution result of the data driver (step 372). .. If the return value obtained by executing the data driver is FALSE, it terminates abnormally, and if it is TRU, the user data management information 30 is read from the commutative storage medium 1 (step 359), and the data file is recorded. (Step 360). After that, CPU3a writes the data file to be written to the recording position obtained in step 360 (step 361), and finally, the correspondence between the file name of the data file, the name of the data driver, and the writing position of the data file. The data management information indicating the above is generated and written to the convertible storage medium (step 362).

【0051】

Fig. 19 shows the processing flow of the data driver Data Driver 1 for OS / A, Fig. 20 shows the processing flow of the data driver Data Driver 1 for OS / B, and Fig. 21 shows the processing flow of the data driver Data Driver 2 for OS / A. , Fig. 22 shows the processing flow of the data driver Data Driver 2 for OS / B. As shown in Fig. 19, the data driver 1 for OS / A for specifying the access conditions of the data file Data A determines whether to write (step 401), and in the case of writing, sets the return value to FALSE (step 401). Step 402), set the return value to TRUE in the case of reading (step 403). As a result, when a computer system equipped with an OS / A reads the data file Data A, the return value becomes TRUE in step 322 (Fig. 17), and the data file Data A can be read. However, when writing the data file Data A, the return value becomes FALSE in step 372 (Fig. 18), and the writing of the data file Data A is prohibited. On the other hand, the data file Data As shown in Fig. 20, data Driver 1 for OS / B for specifying the access condition of A always sets the return value to TRUE regardless of reading or writing (step 410). As a result, a computer system equipped with OS / B can freely read / write the data file Data A.

【0052】

In addition, dataDriver 1 for OS / A for defining the access conditions of the data file Data B displays the password input screen as shown in Fig. 21 (step 421), and compares the password entered by the user with the set password. (Steps 422 and 423), when the set password is entered, the return value is set to TRUE (step 424), and when the set password is not entered, the return value is set to FALSE (step 425). As a result, when a computer system equipped with an OS / A reads or writes the data file DataB, the return value in step 322 (Fig. 17) and step 372 (Fig. 18) if the set password is entered. Becomes TRUE, and the data file Data B can be read and written. However, if the password is not entered correctly, the return value will be FALSE in steps 322 and 372, and reading and writing of the data file Data B will be prohibited. On the other hand, the data driver for OS / B for specifying the access conditions for the data file Data B. As shown in Figure 22, 2 always sets the return value to FALSE regardless of whether it is read or written (step 431). As a result, the computer system equipped with OS / B cannot read / write the data file Data B unconditionally.

【0053】

As described above, according to the third embodiment, it is possible to easily restrict the use of data files according to the data usage environment such as the OS and the user. For example, by changing the OS at the time of editing and the OS at the time of user use, it is possible to easily perform control such as making it impossible for the user to rewrite the data file or hiding the contents of the data file from the user. Will be.

【0054】

(D) Fourth Example The fourth embodiment reads and writes the data file by using the search keyword instead of the file name, and can be realized by the same configuration as the system of the first embodiment of FIG. The data storage structure of the commutative storage medium in the fourth embodiment is almost the same as that in the second embodiment of FIG. 8, and the differences are as shown in FIG. 23, the search keywords 30d-1 and 30d- are added to the user data management information 30. It is a point that has 2, ... That is, the user data management information 30 includes (1) a file name 30a and (2) a data driver name 30c that performs predetermined processing on the data file so that the data file can be used in the computer system. In addition to (3) the correspondence with the location position 30b of the data file, (4) it has the search keywords 30d-1, 30d-2, ... Used to search the data file.

【0055】

FIG. 24 shows a data file reading processing flow of the fourth embodiment, and the same steps as the processing flow of FIG. 9 are assigned the same step numbers. When reading a data file, enter the search keyword for the data file you want to read along with the read command (step 501). When the read command is generated, the CPU 3a reads the user data management data 30 from the commutative storage medium 1 and stores it in the RAM 3c (step 502). Then, CPU3a extracts a keyword from the user data management information 30 (step 503), and obtains user data management information having a keyword matching the search keyword specified by the read command (steps 504 and 505). If the user data management information that has a keyword that matches the search keyword specified by the read command does not exist, it terminates abnormally. If it exists, the start position of the data file and the data driver name are read from the user data management information. Then, it is stored in RAM3c (step 205), and thereafter, the same processing as in the second embodiment is performed to read the data file.

【0056】

A plurality of keywords may be given to one data file, or the same keyword may be given to the data file more than once. For example, in Fig. 23, when the keyword "mouse" is entered, only the data file Data C is read into the memory, but when the keyword "car" is entered, the data file Data A and the data file Data B are read into the memory. FIG. 25 shows a data file writing processing flow of the fourth embodiment, and the same steps as the processing flow of FIG. 10 are assigned the same step numbers. Steps 251 to 261 are the same as the writing process of the second embodiment.

【0057】

When the writing of the data file to the storage medium is completed in step 261, CPU3a prompts the user to input the search keyword of the data file or automatically creates the search keyword (step 271). After that, CPU3a creates user data management information with the name of the data file to be written, the name of the program that processes the data file, the storage location of the data file, and the search keyword, and records it on the storage medium. (Step 262). In the above, the case where the search key is a character string has been described, but it does not necessarily have to be character data as long as the data file can be specified. Further, in the case of character data, the search may be performed under conditions such as prefix match, suffix match, and partial match, even if the keywords do not completely match, and the patent publication number is used to automatically create the search keyword. The method disclosed in H07-113926 can be adopted. Further, the search means may be recorded in the computer system and a constant method may always be used, but as shown in FIG. 26, the data search program 50 is recorded on the convertible storage medium 1 as in the data driver. However, the search may be performed using the data search program. According to this embodiment, data and a data driver can be easily selected by inputting a search keyword.

【0058】

(E) Fifth Example In the fifth embodiment, the cluster length and its arrangement (arrangement) are not fixed by the drive, and the data file can be recorded and read in the replaceable storage medium 1 in the data size unit and the data arrangement suitable for the data file and the medium. A data driver is used for this, and it can be realized by the same configuration as the system of the first embodiment shown in FIG. (a) Data structure in storage medium FIG. 27 is an explanatory diagram of the data configuration of the replaceable storage medium in the fifth embodiment, 30 is user data management information, 40 is data driver management information, 31-1 to 31-5, 32-1, 33-1 to 33-2 are data files (DATA A to DATA C), and 41 to 43 are data drivers (DATA DRIVER 1 to DATA DRIVER 3) that specify the cluster length of data files and their arrangement (arrangement). Data file Data A is distributed and stored at sector addresses 11,17,21,25,30 in cluster units (1 cluster is 4 sectors), and data file Data B is stored at sector address 15 in cluster units (1 cluster is 1 sector). Stored in the data file Data C is distributed and stored at addresses 16 and 29 in cluster units (1 cluster is 1 sector).

【0059】

The user data management information 30 includes (1) file names (DATA A to DATA C) 30a, (2) data file start position (first sector position) 30b, and (3) data file cluster for each data file. It holds the correspondence between the data driver names (DATA DRIVER 1 to DATA DRIVER 3) 30c that determine the size and layout, and (4) data layout information 30e for each cluster of data files. Since the data file DataA stores sector addresses 11 to 1 cluster, sector addresses 17 to 3 clusters, and sector address 30 to 1 cluster, 11 (1), 17 (3), 30 (1) are stored as data allocation information 30e. ) (The number in parentheses is the number of consecutive clusters) is recorded. In other words, in the data file Data A with a large data size, 4 sectors are treated as one cluster, and the data expansion information is also data in the format of "start position (continuous length)" by a method that enables continuous reading with good data transfer efficiency. I manage the records of. On the other hand, data files with small data size Data B, Data In C, data is managed in a space-efficient manner by using one sector and one cluster. The data driver management information 40 includes (1) a data driver name (DATA DRIVER 1 to DATA DRIVER 3) 40a and (2) a data driver storage start position (data driver first sector) 40b for each data driver. ..

【0060】

(b) Reading process of the fifth embodiment FIG. 27 shows a data file reading processing flow of the fifth embodiment of the present invention, and the same steps as the reading processing flow of the first embodiment of FIG. 4 are assigned the same step numbers. The data driver determines the class length and data arrangement, and reads the data file based on the class length and data arrangement, and does not perform any processing such as conversion to the data file. When the CPU3a issues a command to read a predetermined data file, the CPU3a reads the user data management information 30 into the RAM3c (step 101). Then, from the user data management information 30, a file name (data name) that matches the file name specified by the read command is obtained (steps 102 to 104). If the file name specified by the read command does not exist in the user data management information 30, the process ends abnormally.

【0061】

On the other hand, if a file name corresponding to the user data management information 30 exists, the start position of the data file stored from the user data management information 30 corresponding to the file name, the name of the data driver, and the data expansion information Acquire (data placement information) (step 601). For example, when reading the data file Data A, if the data management information shown in FIG. 27 is recorded in the convertible storage medium 1, the start sector position is 11, the data driver name is Data Driver 1, and the data is arranged. Obtain 11 (1), 17 (3), 30 (1) as information. After that, the CPU 3a reads the data driver management information 40 into the RAM 3c (step 106), and acquires the data driver management information having the data driver name obtained in step 601 from the data driver management information 40 (steps 107 to 109). If the data driver name obtained in step 601 does not exist in the data driver management information 40, it means that the corresponding data driver is not recorded in the commutative storage medium 1, and the process ends (abend). ..

【0062】

On the other hand, if the data driver name obtained in step 601 exists in the data driver management information 40, the recording start position of the data driver is acquired and stored in RAM3c (step 110). In the example of FIG. 27, the start position 100 of Data Driver 1 is acquired. After that, CPU3a reads the data driver into RAM3c from the start position (step 111), and thereafter, data from the convertible storage medium 1 according to the start position and data arrangement information of the data file obtained in step 601 using the data driver. Read the file and store it in RAM3c (step 602).

【0063】

(c) Data file writing process FIG. 29 shows the flow of the data file writing process according to the fifth embodiment, and the same step number is assigned to the same step as the writing process of the first embodiment of FIG. The data driver determines the class length and data arrangement, and reads the data file based on the class length and data arrangement, and does not perform any processing such as conversion to the data file. At the start of writing the data file, the user enters the data driver name or information that identifies the equivalent data driver (step 151). For example, Set data Driver = Driver The data driver is specified by sending a command such as "1" from an input device such as a keyboard. When the above command is input, CPU3a determines whether or not the specified data driver name exists in the data driver management information 40. Judgment is performed (steps 152 to 154), and if it exists, the writing process after step 155 is performed. On the other hand, if the data driver name specified by the command does not exist in the data driver management information 40, the data driver is exchanged. Since the corresponding data driver does not exist on medium 1, the process ends (abend abnormally).

【0064】

If the data driver exists, the recording start position of the data driver is acquired from the data driver management information 40 and stored in RAM3c (step 155). After that, the CPU 3a reads the data driver into the RAM 3c from the start position (step 156), reads the user data management information 30 from the convertible storage medium 1 (step 158), and reads the data file recording position from the user data management information. Acquire (step 159). After that, CPU3a uses the data driver to sequentially write the data file to be written in cluster units of a predetermined length from the recording position, and from the data file name, the data driver name, the data writing start position, and the data arrangement information. Create data management information consisting of and write it to storage medium 1 (step 160).

【0065】

After the writing is completed, it is determined whether appropriate writing has been performed, and if the recording method (for example, cluster size) is not appropriate, the recording method (cluster size) is changed and the data arrangement information is rewritten. For example, when writing a data file with a large cluster size, if the actual file size of the data file is small, the cluster size is reduced and the data arrangement information is rewritten. As a result, according to the fifth embodiment, the data can be recorded in a format suitable for the size of the data file, so that the data can be written in a format that is efficient in performance and space. Moreover, by preparing each data driver for a plurality of OSs, data sharing becomes easy.

【0066】

(F) Sixth Example (a) Outline of the sixth embodiment In the above embodiment, one data driver that performs predetermined processing is associated with one data file and used, but in reality, one data file may be associated with a plurality of data drivers. it can. In the sixth embodiment, a plurality of data drivers can be used for one data file, and the system configuration is the same as the configuration of the first embodiment shown in FIG. As shown in FIG. 30, the optical disk 1 which is a commutative storage medium has a data storage configuration substantially similar to that of the first embodiment of FIG. The difference is that in the data management information 30, a plurality of data drivers can be registered corresponding to one data file. When the computer system reads a data file from the optical disk 1, a plurality of data drivers are sequentially read, and each data driver is used to apply a predetermined processing pressure to the data file.

【0067】

(b) Data file reading process of the sixth embodiment FIG. 31 is a data file reading processing flow of the sixth embodiment. When the data file read command is issued, CPU3a reads the user data management information 30 into RAM3c (step 601). Then, the file name (data name) that matches the file name specified by the read command is obtained from the user management information 30 (steps 602 to 604). If the file name specified by the read command does not exist in the user management information 30, the process is interrupted. On the other hand, when the file name corresponding to the user data management information 30 exists, the data file start position stored corresponding to the file name is acquired from the data management information 30, and the CPU 3a transfers the data file to RAM3c. Read (step 605). Then, the name of the data driver group to be used stored corresponding to the file name is read into RAM3c from the data management information 30 (step 606). After that, CPU3a reads the data driver management information 40 into RAM3c (step 607). Here, it is determined whether or not all the data drivers of the data driver group have been read and the processing for the data file has been executed (step 608), and if all have been completed, the processing is terminated.

【0068】

If there is a data driver that has not yet processed the data file, the data driver name is extracted in the order registered in the data management information (step 609), and the matching data driver name is in the data driver management information. Whether or not it is determined (steps 610 to 613). If the data driver to be used does not exist, the process ends (abend abend). If present, CPU3a acquires the recording start position of the data driver and reads it into RAM3c (steps 614, 615). Then, CPU3a performs a predetermined process on the data file using the read data driver (step 616). After that, the processing after step 608 is performed, and the processing for the next data driver specified in the data management information is repeated. As described above, when the data file DataA is read when the user data management information 30 and the data driver management information 40 are recorded on the convertible recording medium 1 as shown in FIG. 30, the user management information 30 is added to the data file. As a data driver to perform processing, "Data Driver" 1,2,3,4,7 is obtained. Therefore, first read the data driver of 1 , process Data A, then the data driver of 2 , and then all the data such as 3 . The drivers are read in sequence, and Data A is subjected to the specified processing.

【0069】

(c) Data file writing process of the sixth embodiment FIG. 32 is a data file writing processing flow of the sixth embodiment, and is a case where the user selects a data driver. At the start of writing the data file, the user enters the data driver name or information that identifies the equivalent data driver (step 701). For example, the data driver can be explicitly specified by sending a command such as "Set Data Driver = Driver 1,5,6,8" from an input device such as a keyboard. The CPU3a then reads the data driver management information 40 into RAM3c (step 702). Then, it is sequentially determined whether or not all the data drivers specified by the user exist (steps 703 to 707), and if they do not exist, the process is interrupted (abnormal termination).

【0070】

If the data driver exists, the recording start position of the data driver is acquired from the data driver management information 40, the data driver is read into RAM3c, and the data is subjected to a predetermined processing process by the data driver (steps 708 to 710). After that, the processing of step 703 and subsequent steps is performed, and the data file is subjected to predetermined processing by all the data drivers specified by the user. After that, the CPU 3a reads the user data management information 30 from the commutative storage medium 1 (step 711), acquires a position for recording the data, and writes the processed data to the recording position (steps 712 to 713). After that, CPU3a reverses the order of the data drivers specified by the user so that it matches the order at the time of reading (step 714). After that, data management information indicating the correspondence between the data file name, the name of the data driver group, and the writing position of the data file is generated and written to the convertible storage medium (step 715).

【0071】

(d) Application example of the sixth embodiment In the sixth embodiment, the data file can be processed by a plurality of data drivers. FIG. 33 is an explanatory diagram of an application example of the sixth embodiment, 30 is data management information, and 40 is data driver management information. Here, the data driver 1 is a data driver that converts the character code of the text data shown in the application example 1 of the second embodiment, and the data driver 2 compresses the data shown in the application example 3 of the second embodiment. It is assumed that the data driver to be performed and the data driver 3 are data drivers that specify the usage conditions of the data shown in the third embodiment. According to this application example, in addition to the data that is only compressed such as data B, the data that is subjected to data conversion such as data A and the use of data such as data C are specified. The data to be processed can also be compressed, and the capacity of the recording medium can be used to the maximum. In the above examples, data compression has been described as being shared by each data, but the present invention is not limited thereto. In addition, it may be combined with the method of using different data drivers depending on the OS as in the second embodiment. Although the present invention has been described above by way of examples, the present invention can be modified in various ways according to the gist of the present invention described in the claims, and the present invention does not exclude these.

【0072】

[Effect of the invention]

According to the present invention, when using a data file stored in a replaceable storage medium or the like, it is not necessary for the user to register software according to the data format and the storage method in the computer system one by one, and the operation performance can be improved. Can be improved. According to the present invention, computer systems having different operating systems can commonly use data files stored in a replaceable storage medium or the like, and therefore easily between computer systems having different architectures or between different operating systems. Data can be exchanged. According to the present invention, even if a data file is recorded on a commutative storage medium or the like in a new or special format, the data file can be used without changing the computer system or the operation system.

【0073】

According to the present invention, the computer system (operation system) and users who can use the data file stored in the commutative storage medium or the like can be easily limited, and the read / write conditions can be easily set. .. According to the present invention, a desired data file can be read by inputting a search keyword. According to the present invention, a data file can be written and read in a data size unit and data arrangement suitable for the data file, and performance and space efficiency can be improved.

[Simple explanation of drawings]

[Figure 1]

It is a principle explanatory drawing of this invention.

[Figure 2]

It is a block diagram of the computer system of this invention.

[Fig. 3]

It is a data structure diagram in a commutative storage medium.

[Fig. 4]

This is the data file reading processing flow of the first embodiment.

[Fig. 5]

This is the write processing flow of the first embodiment when the user selects the data driver.

[Fig. 6]

It is a data structure diagram of the commutative storage medium when the extension is included in the data driver management information.

[Fig. 7]

This is the write processing flow of the first embodiment when the data driver is selected using the extension of the file name.

[Fig. 8]

It is a data structure diagram of the commutative storage medium of the 2nd Example.

[Fig. 9]

This is the data file reading processing flow of the second embodiment.

[Fig. 10]

This is a data file writing process flow of the second embodiment.

[Fig. 11]

It is explanatory drawing of the 1st application example of 2nd Example.

[Fig. 12]

It is explanatory drawing of the 2nd application example of the 2nd Example.

[Fig. 13]

It is a flow chart of the processing process in a data driver.

[Fig. 14]

It is a data structure diagram of the commutative storage medium of the 3rd Example.

[Fig. 15]

It is a reading process flow of the data file of the 3rd Example.

[Fig. 16]

This is a data file write processing flow of the third embodiment.

[Fig. 17]

It is another reading processing flow of the data file of the 3rd Example.

[Fig. 18]

Another write processing flow of the data file of the third embodiment [Fig. 19]

This is the processing flow of Data Drivere 1 for OS / A.

[Fig. 20]

This is the processing flow of Data Driver 1 for OS / B.

[Fig. 21]

This is the processing flow of Data Driver 2 for OS / A.

[Fig. 22]

This is the processing flow of Data Driver 2 for OS / B.

[Fig. 23]

It is explanatory drawing of the user data management information of 4th Example.

[Fig. 24]

It is a reading processing flow of the data file of the 4th Example.

[Fig. 25]

This is a data file writing process flow of the fourth embodiment.

[Fig. 26]

It is a data structure diagram of a commutative storage medium provided with a data file search program.

[Fig. 27]

It is a data structure diagram in the commutative storage medium of the fifth embodiment.

[Fig. 28]

It is a reading processing flow of the data file of the 5th Example.

[Fig. 29]

This is a data file writing process flow of the fifth embodiment.

[Fig. 30]

It is a data structure diagram in the commutative storage medium of the sixth embodiment.

[Fig. 31]

It is a flow diagram (reading) of the process of the sixth embodiment.

[Fig. 32]

It is a process flow chart (writing) of the 6th Example.

[Fig. 33]

It is explanatory drawing of application example of 6th Example.

[Explanation of symbols]

1 ... Portable and interchangeable storage media, such as optical discs 2 ... Optical disk drive device 3 ... Computer system 3a ... Processing unit (CPU) 30 ... Data management information 30a ... File name 30b ... Location of data file 30c ... Program name 31 ~ 33 Multiple data files (DATA A ~ DATA C) 40 ... Program management information 40a ... Program name 40b ... Program location 40c ... Operation system name (OS information) 41 ~ 43 Program (DATA DRIVER 1 ~ DATA DRIVER 3)