JP4556285B2 - Recording / playback device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a recording / reproducing apparatus.
[0002]
[Prior art]
Recently, a semiconductor memory (memory card) that can be small and have a large capacity can be configured at low cost. When recording / reproducing data using such a memory card as a recording medium, for example, a device for reading / writing data such as a disk rotation mechanism or an optical pickup configured in a disk drive device for recording / reproducing an optical disk is required. Therefore, the recording / reproducing apparatus can be configured at low cost, and stable data recording / reproducing can be performed.
[0003]
[Problems to be solved by the invention]
By the way, the memory card described above is configured to record data in a required format format corresponding to the memory card. That is, when recording and playing back this memory card in the same manner as a recording medium having a different format, application software or driver software or dedicated application software compatible with the memory card is required for compatibility between formats. Driver software is required.
[0004]
That is, when the data recorded on the memory card is used for general purposes, the cost for providing the various software described above is required. In addition, the provision of the above software may cause a state in which each software cannot operate normally due to competition with other software in the same operating environment or compatibility.
[0005]
[Means for Solving the Problems]
In order to solve such a problem, the present invention provides a peripheral device for a computer apparatus that includes the second recording medium, and receives data from the first recording medium based on a request from the computer apparatus. Readout means that can be read out and management information of the first recording medium read out by the reading means are processed so that the computer device can handle the same as the data of the second recording medium. The recording / reproducing apparatus includes data processing means and data output means for transferring the management information processed by the data processing means to the computer device.
[0006]
Further, as a peripheral device of a computer device configured to include the second recording medium, a data capturing unit capable of capturing data read from the second recording medium based on a request from the computer device Data processing means for processing the management information of the second recording medium captured by the capturing means into management information corresponding to the first recording medium, and the management information processed by the data processing means. A recording / reproducing apparatus is provided with data output means for outputting to the first recording medium.
[0007]
According to the present invention, at the time of data reproduction of the first recording medium in the recording / reproducing apparatus, the data processing is performed so as to correspond the management information to the second recording medium and output to the computer apparatus. Further, when data from the computer device is recorded on the first recording medium, data processing is performed so that the management information corresponds to the first recording medium.
Therefore, in the computer apparatus, when data communication (recording / reproduction) with the first recording medium is performed, the data can be handled in the same manner as the data of the second recording medium.
[0008]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the recording / reproducing apparatus of the present invention will be described below.
The recording / reproducing apparatus of the present embodiment is capable of recording / reproducing corresponding to, for example, CD-R, CD-RW, DVD-R, DVD-RW, etc. as a disk drive device. Further, reproduction corresponding to reproduction-only media such as CD-DA, CD-ROM, or DVD-ROM is also possible. In addition, the disk drive device according to the present embodiment can be loaded with a memory card, and can perform recording / reproduction with respect to the memory card.
[0009]
First, the part related to the recording / reproducing operation of the disk 90 will be described.
The disc 90 is rotated and driven at a constant linear velocity (CLV) or a constant angular velocity (CAV) by the spindle motor 6 during the recording / reproducing operation in a state of being stacked and chucked on the turntable 7. The optical pickup 1 reads pit data (phase change pits or pits due to organic dye changes (reflectance changes)) on the disk 90. In the case of CD-DA or CD-ROM, the pit is an embossed pit.
[0010]
In the pickup 1, a laser diode 4 serving as a laser light source, a photodetector 5 for detecting reflected light, an objective lens 2 serving as an output end of the laser light, and a laser recording light are irradiated onto the disk recording surface via the objective lens 2. In addition, an optical system (not shown) for guiding the reflected light to the photodetector 5 is formed.
A monitor detector 22 for receiving a part of the output light from the laser diode 4 is also provided.
[0011]
The objective lens 2 is held by a biaxial mechanism 3 so as to be movable in the tracking direction and the focus direction.
The entire pickup 1 can be moved in the radial direction of the disk by a thread mechanism 8.
The laser diode 4 in the pickup 1 is driven to emit laser light by a drive signal (drive current) from a laser driver 18.
[0012]
Reflected light information from the disk 90 is detected by the photodetector 5, converted into an electrical signal corresponding to the amount of received light, and supplied to the RF amplifier 9.
The RF amplifier 9 includes a current-voltage conversion circuit, a matrix calculation / amplification circuit, and the like corresponding to output currents from a plurality of light receiving elements as the photodetector 5, and generates necessary signals by matrix calculation processing. For example, an RF signal as reproduction data, a focus error signal FE for servo control, a tracking error signal TE, and the like are generated.
The reproduction RF signal output from the RF amplifier 9 is supplied to the binarization circuit 11, and the focus error signal FE and tracking error signal TE are supplied to the servo processor 14.
[0013]
In addition, for example, a CD-R, a CD-RW, or the like, in which a groove (groove) serving as a guide for a recording track is formed in advance, time information indicating the absolute address on the disk is FM modulated. The signal is wobbled (meandered). Accordingly, at the time of recording operation, tracking servo can be applied from the groove information, and an absolute address can be obtained from the groove wobble information. The RF amplifier 9 extracts wobble information WOB (ATIP signal) by matrix calculation processing and supplies it to the address decoder 24.
The address decoder 24 demodulates the supplied wobble information WOB (ATIP signal) to obtain absolute address information and outputs it to the system controller 10. The address decoder 24 can also extract various control information included in the wobble information WOB (ATIP signal) and output it to the system controller 10.
Further, by injecting the groove information into the PLL circuit, the rotational speed information of the spindle motor 6 is obtained and further compared with the reference speed information, thereby generating and outputting a spindle error signal SPE.
[0014]
The reproduction RF signal obtained by the RF amplifier 9 is binarized by the binarization circuit 11 to be a so-called EFM signal (8-14 modulation signal) and supplied to the encoding / decoding unit 12. The DVD-R, DVD-RW, or DVD-ROM is converted into an EFM + signal and supplied to the encode / decode unit 12.
[0015]
The encoding / decoding unit 12 includes a functional part as a decoder during reproduction and a recording part as an encoder during recording.
During reproduction, as decoding processing, processing such as EFM demodulation, CIRC error correction, deinterleaving, and CD-ROM decoding is performed to obtain reproduction data converted into CD-ROM format data.
The encode / decode unit 12 also performs subcode extraction processing on the data read from the disk 90 and supplies the TOC, address information, and the like as subcode (Q data) to the system controller 10.
Further, the encode / decode unit 12 generates a reproduction clock synchronized with the EFM signal by the PLL process, and executes the decoding process based on the reproduction clock. The rotation speed information of the spindle motor 6 is obtained from the reproduction clock. And the spindle error signal SPE can be generated and output by comparing with the reference speed information.
[0016]
At the time of reproduction, the encode / decode unit 12 accumulates the data decoded as described above in the buffer memory 20.
As the reproduction output from this drive device, the data buffered in the buffer memory 20 is read out and transferred and output.
[0017]
The interface unit 13 is connected to an external host computer 80 and communicates recording data, reproduction data, various commands, and the like with the host computer 80. Actually, SCSI and ATAPI interfaces are adopted. At the time of reproduction, the reproduction data decoded and stored in the buffer memory 20 is transferred and output to the host computer 80 via the interface unit 13.
Note that a read command, a write command, and other signals from the host computer 80 are supplied to the system controller 10 via the interface unit 13.
The host computer 80 includes a hard disk device 80a serving as a first recording medium. The hard disk device 80a includes start management information (master boot record, partition boot record), which is management information for operating the host computer 80, an operation system, a file system, application software used by the user, or the application. An area for recording various files created by software is formed.
[0018]
On the other hand, during recording, recording data (audio data or CD-ROM data) is transferred from the host computer 80. The recording data is sent from the interface unit 13 to the buffer memory 20 and buffered.
In this case, the encoding / decoding unit 12 encodes CD-ROM format data into CD format data (when the supplied data is CD-ROM data), CIRC encoding, and encoding processing of the buffered recording data. Interleaving, subcode addition, EFM modulation, etc. are executed.
[0019]
The EFM signal obtained by the encoding process in the encoding / decoding unit 12 is subjected to a process called “write equalization” by the equalizer 21, then sent to the laser driver 18 as write data WDATA, and written to the disk. That is, the laser driver 18 applies a laser drive pulse modulated by the write data WDATA to the laser diode 4 and performs laser light emission driving, whereby pits (phase change pits and dye change pits) corresponding to the write data WDATA are formed on the disk 90. Will be formed.
[0020]
The APC circuit (Auto Power Control) 19 is a circuit unit for controlling the laser output power to be constant regardless of temperature or the like while monitoring the laser output power by the output of the monitor detector 22. The target value of the laser output is given from the system controller 10, and the laser driver 18 is controlled so that the laser output level becomes the target value.
[0021]
The servo processor 14 performs various focus, tracking, thread, and spindle servo drives from the focus error signal FE and tracking error signal TE from the RF amplifier 9 and the spindle error signal SPE from the encoding / decoding unit 12 or the address decoder 24. Generate a signal and execute servo operation.
That is, the focus drive signal FD and the tracking drive signal TD are generated according to the focus error signal FE and the tracking error signal TE and supplied to the biaxial driver 16. The biaxial driver 16 drives the focus coil and tracking coil of the biaxial mechanism 3 in the pickup 1. Thus, a tracking servo loop and a focus servo loop are formed by the pickup 1, the RF amplifier 9, the servo processor 14, the biaxial driver 16, and the biaxial mechanism 3.
[0022]
Further, in response to a track jump command from the system controller 10, the tracking servo loop is turned off and a jump drive signal is output to the biaxial driver 16 to execute a track jump operation.
[0023]
The servo processor 14 further supplies a spindle drive signal generated in accordance with the spindle error signal SPE to the spindle motor driver 17.
The spindle motor driver 17 applies, for example, a three-phase drive signal to the spindle motor 6 according to the spindle drive signal, and causes the spindle motor 6 to perform CLV rotation. The servo processor 14 also generates a spindle drive signal in response to the spindle kick / brake control signal from the system controller 10 and causes the spindle motor driver 17 to perform operations such as starting, stopping, accelerating and decelerating the spindle motor 6.
[0024]
Further, the servo processor 14 generates a thread drive signal based on, for example, a thread error signal obtained as a low frequency component of the tracking error signal TE, an access execution control from the system controller 10, and supplies the thread drive signal to the thread driver 15. The thread driver 15 drives the thread mechanism 8 according to the thread drive signal. Although not shown, the sled mechanism 8 has a mechanism including a main shaft that holds the pickup 1, a sled motor, a transmission gear, and the like, and the sled driver 15 drives the sled motor 8 according to a sled drive signal. The required slide movement is performed.
[0025]
Various operations of the servo system and the recording / reproducing system related to the disk 90 as described above are controlled by the system controller 10 formed by a microcomputer.
The system controller 10 executes various processes in accordance with commands from the host computer 80.
For example, when a reproduction command for requesting transfer of certain data recorded on the disk 90 is supplied from the host computer 80, seek operation control is first performed for the designated address. That is, a command is issued to the servo processor 14 to cause the pickup 1 to access the address specified by the seek command.
Thereafter, operation control necessary for transferring the data in the designated data section to the host computer 80 is performed. That is, data requested from the disk 90 is read / decoded / buffered and the requested data is transferred.
[0026]
When a write command (record command) is issued from the host computer 80, the system controller 10 first moves the pickup 1 to an address to be written. Then, the encoding / decoding unit 12 performs the encoding process on the data transferred from the host computer 80 as described above to generate an EFM signal.
Then, the write data WDATA that has been equalized as described above is supplied to the laser driver 18 to perform recording.
[0027]
Here, the system controller 10 can set the reference speed information for the servo processor 14, and the servo processor 14 compares the set reference speed information with the rotation speed information from the decoder 12 to generate the spindle error signal SPE. Generate. Furthermore, it is possible to change and set the disk rotational drive speed by changing the setting of the reference speed information. That is, in the case of reproduction, it is possible to reproduce at a predetermined double speed that is higher than the disk rotational drive speed. At this time, the reproduction clock obtained by operating the PLL circuit in the encoding / decoding unit 12 is also set to a frequency corresponding to the set double speed, so that signal processing corresponding to double speed reproduction is executed. The
In addition, when the disk rotational drive speed is set to a double speed higher than the single speed during recording, a frequency corresponding to the set double speed is set as a clock for recording. The encoding process in the encoding / decoding unit 12 and the signal processing in the equalizer 21 are executed according to this clock. Then, the data WDATA processed in this way is supplied to the laser driver 18, whereby recording on the disk is performed at a writing rate corresponding to the set disk rotation driving speed.
[0028]
Further, a ROM 26 and a RAM 27 are provided for the system controller 10.
The ROM 26 stores information necessary for the system controller 10 to perform various operation controls in addition to programs to be executed by the system controller 10, for example.
The RAM 27 holds various information obtained according to various control processes executed by the system controller 10. In addition, the RAM 27 is provided with a work area for performing data processing described later.
[0029]
In addition, the disk drive device 0 of the present embodiment is loaded with a memory card 40 as a first recording medium, and data can be recorded / reproduced using the memory card 40 as a recording medium. ing.
The memory card 40 includes a memory control unit 40a that performs processing such as serial / parallel conversion of recorded data / reproduced data, and a memory unit 40b that forms a recording area of the memory card 40, for example. In the disk drive device 0, data supplied from the host computer 80 by the system controller 10 or data requested from the host computer 80 can be read and output. In this case, data communication with the host computer 80 is performed via the system controller 10 and the serial interface unit 30.
That is, when a command for executing recording on the memory card 40 is supplied from the host computer 80 to the disk drive device 0, the system controller 10 stores the serial data transferred from the host computer 80 via the serial interface unit 30. Supply to the card 40. In the memory card 40, the serial data supplied from the serial interface unit 30 is converted into parallel data corresponding to the bus width of the memory unit 40b in the memory controller unit 40a and written to the memory unit 40b.
Even when data recorded in the memory card 40 is read, the read operation is executed based on a command for executing reproduction supplied from the host computer 80 to the disk drive device 0. In other words, the system controller 10 requests data from the memory card 40 via the serial interface unit 30 to perform reading, and transfers the read data to the host computer 80.
[0030]
As described above, in the disk drive device 0, the memory card 40 can be used as a recording medium together with the disk 90. In this embodiment, in order to be able to handle the data recorded in the memory card 40 in the same manner as the data recorded in the hard disk device 80a in the host computer 80, the data is recorded in the disk drive device 0. Necessary data processing is performed when transferring. This data processing is performed in the work area of the RAM 27. That is, data transfer performed between the host computer 80 and the memory card 40 is performed via the RAM 27.
For example, when the data transferred from the host computer 80 is recorded in the memory card 40, if the transferred management information is included in the transferred data, the processing is performed so that the startup management information corresponds to the memory card 40. Then, the data is transferred to the memory card 40 via the serial interface unit 30.
Also, when the requested data is read from the memory card 40 and transferred to the host computer 80 when the requested management data is included in the requested data, the activation management information is stored in the hard disk. After processing so as to correspond to the device 80 a, it is transferred to the host computer 80 via the interface unit 13.
[0031]
As described above, since the disk drive device 0 processes the startup management information, when the host computer 80 performs data communication (recording / reproduction) with the memory card 40, a dedicated memory card 40-compatible memory card 40 is used. There is no need to use driver software or the like, and the hard disk device 80a and the memory card 40 are handled in the same way so that data can be recorded / reproduced.
[0032]
FIG. 2 is a diagram schematically illustrating the start management information recorded in the hard disk device 80a.
When the hard disk device 80a is set as a startup disk in the host computer 80, a master boot record (hereinafter referred to simply as MBR) is recorded at a predetermined position of the hard disk device 80a. ing. The master boot record records position information and size information of partitions formed in the hard disk device 80a, a program for starting the host computer 80, and the like.
In addition, when a plurality of the above partitions are formed, a partition boot record (Partition Boot Record) is used as a program for starting the operation system at the beginning of the partition that is a basic partition Is simply recorded as PBR).
In addition to the location where MBR and PBR are recorded, the above-mentioned operation system, file system, application software used by the user, and various files created by the application software are recorded. become.
[0033]
When the host computer 80 is activated, a control program called BIOS (Basic Input / Output System) recorded in a required recording means inside the host computer 80 first executes the activation program recorded in the MBR, and the basic partition. And the startup control is taken over by the PBR recorded in the basic partition. As a result, the PBR activates the operation system recorded in the basic partition, and the host computer 80 shifts to a normal operating state.
[0034]
Next, a part of the logical format of the memory card 40 will be described with reference to FIG. In this figure, the main part related to the description of the present embodiment in the logical format will be described.
As shown in the figure, the logical format in the memory card 40 is such that the data contents recorded in the memory unit 40b can be referred to using the values of the cylinder, head (track), and sector.
MBR is recorded in LBA sector “0” (cylinder 0 / head 0 / sector 0), and PBR is recorded in LBA sector “27” (cylinder 0 / head 1 / sector 12). MBR and PBR will be described later.
[0035]
After PBR, in order to form a partition in the memory unit 40a, data having the following contents is recorded.
A FAT entry is recorded in the LBA sector “28” (cylinder 0 / head 1 / sector 13). In the FAT entry, the connection state of clusters handled in the data area is recorded. The FAT is usually created with 12 bits for each cluster (FAT12). However, if the maximum number of clusters formed in the data area exceeds 4085, it is created with 16 bits (FAT16). Also, FAT entry backup information is recorded in the LBA sector “30” (cylinder 0 / head 1 / sector 15).
A root directory entry is recorded in the LBA sector “32” (cylinder 1 / head 0 / sector 1). This root directory entry is, for example, file name information, extension information, attribute information, reservation information, and last editing time information. Information such as last edit date information, start cluster number information, file size information (in bytes) is recorded.
From the LBA sector “64” (cylinder 2 / head 0 / sector 1), a data area is formed so that user data can be recorded.
[0036]
In FIG. 3, for example, the contents of one partition have been described as partition # 1, but in the memory unit 40b, only one partition can be formed in this way, or, for example, partition # 1. It is also possible to form a plurality of partitions such as 2, partition # 3.
[0037]
FIG. 4 is a diagram showing an example of the contents of the MBR recorded from the LBA sector “0” shown in FIG. 3, and shows an area where each information is recorded based on the offset amount from the head of the MBR. Yes. Note that the contents of the MBR shown in this figure indicate a state in which only partition # 1 is defined.
In the MBR, for example, a boot command related to the activation of the host computer 80 is recorded from “0x000h” to “0x1BDh”.
Various information corresponding to partition # 1 is recorded in 16 bits from “0x1BEh” to “0x1CDh”.
In one byte of “0x1BEh”, “0x80h” is recorded as boot identification information. This “0x80h” is information indicating that the partition # 1 is a basic partition (Default Boot Partition).
The start head number is recorded in 1 byte of “0x1BFh”, the start sector number is recorded in 1 byte of “0x1C0h”, the start cylinder number is recorded in 1 byte of “0x1C1h”, and the system identification information is recorded in 1 byte of “0x1C2h” The
The system identification information is “0x01h” for FAT12, “0x04h” when the capacity of FAT16 and the memory card 40 is 32 MB or less, and “0x06h” when the capacity of the FAT16 and memory card 40 is 32 MB or more. To be recorded.
Further, following the system information, 1 byte of “0x1C3h” has final head number information, 1 byte of “0x1C4h” has final sector number information, 1 byte of “0x1C5h” has final cylinder number information, and “0x1C6h” 4 bytes from the start logical sector number information, and 4 bytes from “0x1CAh” record partition size information.
[0038]
From “0x1CEh”, various information corresponding to partition # 2 to partition # 4 can be recorded in the same manner as described above. However, as described above, in FIG. Since the state up to # 4 is not used, “0x00h” indicating the unused state is recorded.
Then, in the 2 bytes from “0x1FEh”, “0x55AAh” is recorded as information indicating the end portion of the recording area.
[0039]
FIG. 5 shows an example of actual data constituting the MBR, and shows a state in which necessary information is arranged corresponding to the offset amount from “0x000h” shown in FIG.
As described with reference to FIG. 4, “0x000h” to “0x1BDh” are boot instruction information. In the present embodiment, “00h” is used because it is unused as described above. As indicated by the underline, the partition information is from the boot identification information indicated as “80h” in “0x1BEh” to the termination information indicated as “55AAh” from “0x1FEh”. The
In the present embodiment, among the boot instruction information from “0x000h” to “0x1BDh”, the information from “0x000h” to “0x0DFh” is processed into information corresponding to the hard disk device 80a, whereby the host computer 80 The data recorded on the memory card 40 can be handled in the same manner as the data recorded on the hard disk device 80a.
[0040]
FIG. 6 is a diagram showing an example in which a part of the contents of the MBR corresponding to the memory card 40 shown in FIG. 5 is processed to correspond to the MBR of the hard disk device 80a.
For example, in the state recorded in the memory card 40, as shown in FIG. 5, “00h” is recorded as boot command information from “0x000h” to “0x1BDh”, but is surrounded by a wavy line in FIG. As shown, the data recorded from “0x000h” to “0x0DFh”, which is a part of the boot instruction information, is processed into the contents as shown. That is, the information indicated by the wavy line from “0x000h” to “0x0DFh” corresponds to the MBR shown in FIG. 2 in the hard disk device 80a.
[0041]
Therefore, in the disk drive device 0, when the data recorded in the memory card 40 is requested from the host computer 80, and the MBR is included in the requested data, the MBR read from the memory card 40 is shown in FIG. After processing into such data, it may be transferred to the host computer 80. The MBR recorded in the hard disk device 80a is transferred from the host computer 80 in the state shown in FIG. 6, for example. In this case, the MBR shown in FIG. 6 is shown in FIG. As described above, the data processing is performed so that a part of the boot command information becomes “00h” and is recorded in the memory card 40.
[0042]
FIG. 7 is a diagram showing an example of the contents of the PBR recorded from the LBA sector “27” shown in FIG. 3, and shows the area where each information is recorded based on the offset amount from the head of the PBR. Yes.
A value of “0xE900000h” is recorded as a jump code in 3 bytes from “0x000h”, and OEM name information and version information are recorded in ASCII code in 8 bytes from “0x003h”.
In two bytes from “0x00Bh”, “0200h” is recorded as a fixed number as the number of bytes per sector. In one byte “0x00Dh”, the number of sectors per cluster is recorded based on the capacity of the memory card 40.
In one byte of “0x00Eh”, “1” is recorded as the number of reserved sectors.
The number of FAT is recorded in 1 byte of “0x010h”, the number of entries of the root directory entry is recorded in 2 bytes of “0x011h”, and values “2” and “512” are recorded as fixed values, respectively. The number of logical sectors is recorded in 2 bytes from “0x013h”, and a value of 65536 or less is recorded based on the capacity of the memory card 40.
[0043]
In one byte of “0x015h”, for example, a value “0xF8h” is recorded as the media ID. In 2 bytes of “0x016h”, the number of sectors per 1 FAT is recorded based on the capacity of the memory card 40.
In two bytes from “0x018h”, “16”, in which the number of sectors per head (track) is a fixed value, is recorded. The number of heads is recorded in 2 bytes from “0x01Ah” based on the capacity of the memory card 40.
In the 4 bytes from “0x01Ch”, the number of hidden sectors is recorded based on the capacity of the memory card 40. Furthermore, in 4 bytes from “0x020h”, a value of 65536 or more is recorded based on the capacity of the memory card 40.
[0044]
In one byte from “0x024h”, for example, a value “0x00h” is recorded as a physical drive number. One byte from “0x025h” is reserved, and “0x29h” is recorded as an extended boot identification code in the subsequent one byte from “0x026h”. In 4 bytes from “0x027h”, for example, “0x00h” is recorded as a volume serial number.
In 11 bytes from “0x02Bh”, volume label information is recorded by ASCII code.
In 8 bytes from “0x036h”, file system type information is recorded by ASCII code.
[0045]
In the “0x1C0h” byte from “0x03Eh”, a boot record is recorded, and in this embodiment, “0x00h” indicating unused is set.
Then, “0x55AAh” is recorded in the 2 bytes from “0x1FEh” as PBR termination information.
[0046]
FIG. 8 shows an example of actual data constituting the PBR, and shows a state in which necessary information is arranged corresponding to the offset amount from “0x000h” shown in FIG.
Also in the PBR shown in FIG. 8, data processing is performed at the time of data transfer. In the example shown in FIG. 8, for example, the data shown by being surrounded by a wavy line is processed.
When the contents of the data surrounded by the wavy line are associated with FIG. 7, jump code (3 bytes from “0x000h”), OEM name information / version information (8 bytes from “0x003h”), physical drive number information (“0x024h”) 1 byte), volume label information (11 bytes from “0x02Bh”), and boot code information (from “0x03Eh” to “0x1C0” bytes).
That is, when the PBR recorded on the memory card 40 shown in FIG. 8 is processed so as to correspond to the PBR of the hard disk device 80a, for example, as shown in FIG.
[0047]
Next, a transition when processing data (MBR, PBR) recorded in the memory card 40 will be schematically described.
First, MBR data processing will be described with reference to FIG. In FIG. 10, the MBR corresponding to the hard disk device 80a is indicated as “MBR ′”.
As shown in FIG. 10A, when there is a data read request from the host computer 80 and it is determined that MBR is included in the requested data, the disk drive device 0 uses the memory card 40. To read out the MBR. Then, the MBR is read and stored in the RAM 27. The MBR immediately after being read from the memory card 40 has all the boot command information “00h” as shown in FIG. Then, through the processing, a part of the boot command information is processed so as to correspond to the hard disk device 80a as shown in FIG. 6, and transferred to the host computer 80 as MBR ′. As a result, the host computer 80 can handle data transferred from the memory card 40 via the disk drive device 0 in the same manner as data recorded on the hard disk device 80a.
[0048]
Further, as shown in FIG. 10B, when the data transferred from the host computer 80 is recorded in the memory card 40, if it is determined that the transferred data includes the MBR, The boot command information has contents corresponding to the hard disk device 80a as shown in FIG. 6, for example. That is, it is transferred from the host computer 80 as MBR ′. Also in this case, the transferred MBR is stored in the RAM 27. In this RAM 27, data processing is performed, and a part of the boot command information is processed into contents corresponding to the memory card 40 as shown in FIG. And transferred to the memory card 40 as MBR. Therefore, even when MBR ′ having contents corresponding to the hard disk device 80a is transferred from the host computer 80, data can be recorded in the memory card 40 as MBR by performing data processing in the disk drive device 0.
[0049]
Next, the data processing of the PBR will be described with reference to FIGS. 11A and 11B. In this case as well as the MBR described above, the data processing is performed at the time of data reading or recording.
That is, as shown in FIG. 11A, when there is a data read request from the host computer 80 and the requested data includes PBR, the disk drive device 0 uses the memory card 40. PBR read processing is performed and stored in the RAM 27. In this state, the PBR is as shown in FIG. Then, through the processing, it is processed so as to correspond to the hard disk device 80a as shown in FIG. 9, and transferred to the host computer 80 as PBR ′. In FIG. 11, the PBR corresponding to the hard disk device 80a is indicated as “PBR ′”.
[0050]
Further, as shown in FIG. 11B, when the PBR ′ transferred from the host computer 80 is recorded on the memory card 40, the transferred PBR is stored in the RAM 27, and the RAM 27 stores the data Processing is performed. Then, as shown in FIG. 8, PBR ′ is processed so as to correspond to the memory card 40 and transferred to the memory card 40 as PBR.
[0051]
By performing such data processing, the host computer 80 can handle the data transferred from the memory card 40 via the disk drive device 0 in the same manner as the data of the hard disk device 80a.
Even when MBR ′ or PBR ′ having contents corresponding to the hard disk device 80a is transferred from the host computer 80, data processing can be performed to record the data on the memory card 40 as MBR or PBR.
That is, when data is transferred between the memory card 40 and the hard disk device 80a, the memory card 40 data can be handled in the same manner as the data of the hard disk device 80a without using dedicated software in the host computer 80, for example. I am doing so.
[0052]
FIG. 12 is a flowchart showing an example of processing steps when the host computer 80 reads data from the memory card 40 loaded in the disk drive device 0.
For example, when requesting data recorded in the memory card 40 loaded in the disk drive device 0, it is first determined whether or not the disk drive device 0 is in an operating state (S001). When it is determined that the disk drive device 0 is in an operating state and data communication can be executed, a command for requesting data in the memory card 40 is issued (S002). Next, it is determined whether or not a reply to the command in step S002 has been detected from the disk drive device 0 (S003). If it is determined that a reply has been detected, the content of the reply is determined (S004). If it is determined that the reply content is communicable, the data transferred from the memory card 40 via the disk drive device 0 is fetched (S005). When it is determined that the content of the reply is an error, a required error process is performed (S006).
In this case, the MBR or PBR transferred from the disk drive device 0 in step S004 is processed into contents corresponding to the hard disk device 80a, and the host computer 80 handles the same as the data recorded in the hard disk device 80a. Will be able to.
[0053]
FIG. 13 shows an example of processing steps when the disk drive device 0 reads data recorded on the memory card 40 based on a request from the host computer 80 and transfers the read data to the host computer 80. It is a flowchart to show.
First, the disk drive device 0 determines whether a command has been received from the host computer 80 (S101). If it is determined that the command has been received, it is determined whether or not the received command is a request for data recorded in the memory card 40 (S102), and the received command is stored in the memory card 40. If it is determined that the data is requested, it is determined whether or not the memory card 40 is loaded by performing a required communication process on the memory card 40 (S103). If it is determined that the received command does not request data of the memory card 40, the process proceeds to another processing step (S104) corresponding to the command. If it is determined in step S103 that the memory card 40 is loaded, a reply is sent to the host computer 80 that communication with the memory card 40 is possible (S105). If it is determined that the memory card 40 is not loaded, it is determined that communication with the memory card 40 is impossible, and error information is returned as a reply to the host computer 80 (S106).
[0054]
When the state shifts to a state where communication with the memory card 40 is possible, it is determined whether or not the address of the data requested from the host computer 80 is CHS (Cylinder / Head / Sector) (S107). If it is determined that the address is CHS, the address is converted to LBA (S108), and reading of data corresponding to the address is started (S109). The data read here is stored in the RAM 27.
After the address conversion process, for example, it is determined whether or not MBR is requested from the host computer 80 based on the address or the like (S110), and if it is determined that MBR is requested, FIG. As described above, MBR data processing is performed (S111). Further, similarly to step S110, it is determined whether or not PBR is requested from the host computer 80 (S112), and when it is determined that PBR is requested, as described with reference to FIG. PBR data processing is performed (S113).
Then, the requested data is transferred to the host computer 80 (S114).
[0055]
FIG. 14 is a flowchart showing an example of processing steps in the case where data is recorded in the memory card 40 loaded in the disk drive device 0 in the host computer 80.
For example, when data is recorded on the memory card 40 loaded in the disk drive device 0, it is first determined whether or not the disk drive device 0 is in operation (S201). When it is determined that the disk drive device 0 is in an operating state and data communication can be executed, a command for recording data in the memory card 40 is issued (S202). Then, it is determined whether or not a reply to the command in step S202 is detected from the disk drive device 0 (S203). If it is determined that a reply is detected, the content of the reply is determined (S204). If it is determined that the reply content is communicable, the data recorded in the memory card 40 is transferred to the disk drive device 0 (S205). When it is determined that the content of the reply is an error, a required error process is performed (S206).
In this case, the MBR or PBR transferred in step S205 is processed into content corresponding to the memory card 40 in the disk drive device 0. Therefore, the host computer 80 can handle the data recorded on the memory card 40 in the same manner as the data recorded on the hard disk device 80a.
[0056]
FIG. 15 is a flowchart illustrating an example of processing steps in the case where data transferred from the host computer 80 is recorded in the memory card 40 based on a request from the host computer 80 in the disk drive device 0.
First, it is determined whether or not a command has been received from the host computer 80 (S301). If it is determined that a command has been received, whether or not the received command is to record data in the memory card 40 is determined. A determination is made (S302).
If it is determined that the received command is a command for recording data in the memory card 40, it is determined whether or not the memory card 40 is loaded by performing a required communication process on the memory card 40. It performs (S303). If it is determined that the received command does not request data of the memory card 40, the process proceeds to another processing step (S304) corresponding to the command.
If it is determined in step S303 that the memory card 40 is loaded, a reply is sent to the host computer 80 that communication with the memory card 40 is possible (S305). If it is determined that the memory card 40 is not loaded, it is determined that communication with the memory card 40 is impossible, and error information is returned as a reply to the host computer 80 (S306).
[0057]
When a transition is made to a state in which communication with the memory card 40 is possible, fetching of data transferred from the host computer 80 is started (S307). The data read here is stored in the RAM 27.
Then, for example, based on the address or the like, it is determined whether or not the MBR has been transferred from the host computer 80 (S310). Data processing is performed (S311). Further, similarly to step S310, it is determined whether or not the PBR is transferred from the host computer 80 (S312). If it is determined that the PBR is transferred, as described with reference to FIG. The PBR data is processed (S313).
Then, the data transferred from the host computer 80 is transferred to the memory card 40 (S314).
[0058]
As described above, when the MBR and PBR transferred from the host computer 80 are recorded on the memory card 40, the disk drive device 0 according to the present embodiment is processed into the contents corresponding to the memory card 40 and then transferred to the memory card 40. I am doing so. Therefore, the host computer 80 can perform recording on the memory card 40 in the same manner as recording data on the hard disk device 80a, for example.
That is, necessary processing is performed on the management information (MBR, PBR) of the first recording medium serving as the memory card 40 and the management information (MBR, PBR) of the second recording medium serving as the hard disk device 80a. Thus, the host computer 80 does not need to include driver software or application software for handling the data in the memory card 40 in the same manner as the data in the hard disk device 80a. Therefore, it is possible to suppress adverse effects on operation due to competition with other software in the operating environment of the host computer 80 or compatibility.
[0059]
In the present embodiment, an example in which the hard disk device 80a built in the host computer 80 in the disk drive device 0 and the MBR and PBR of the memory card 40 loaded in the disk drive device 0 are matched will be described. However, the first and second recording media are not limited to the memory card 40 and the hard disk device 80a.
[0060]
【The invention's effect】
As described above, when the recording / reproducing apparatus of the present invention outputs the management information recorded on the first recording medium to the computer apparatus, the computer apparatus is similar to the data on the second recording medium. It is processed so that it can be handled.
Further, when the management information of the second recording medium transferred from the computer device is recorded on the first recording medium, the management information is processed into the management information corresponding to the first recording medium.
As a result, the computer apparatus can record and reproduce the management information by handling the data recorded on the first recording medium in the same manner as the data on the second recording medium.
In addition, since the computer device does not require software for processing the management information on the first recording medium and the management information on the second recording medium, it reduces software contention in the operating environment of the computer device. In addition, it is possible to suppress malfunctions due to software compatibility and the like.
[Brief description of the drawings]
FIG. 1 is a block diagram illustrating a configuration example of a disk drive device according to an embodiment of this invention.
2 is a diagram for explaining start management information (MBR, PBR) recorded in a hard disk device of a host computer shown in FIG. 1; FIG.
FIG. 3 is a diagram illustrating a part of a logical format of a memory card.
4 is a diagram for explaining the contents of the MBR shown in FIG. 3; FIG.
FIG. 5 is a diagram illustrating an example of the MBR illustrated in FIG. 3;
6 is a diagram showing an example in which the MBR shown in FIG. 5 is processed in correspondence with a hard disk device.
7 is a diagram for explaining the contents of the PBR shown in FIG. 3; FIG.
8 is a diagram showing an example of the PBR shown in FIG.
9 is a diagram showing an example in which the PBR shown in FIG. 8 is processed so as to correspond to a hard disk device.
FIG. 10 is a schematic diagram for explaining a process transition when processing an MBR.
FIG. 11 is a schematic diagram for explaining processing transition when processing PBR.
FIG. 12 is a diagram illustrating processing steps performed by a host computer when requesting data recorded on a memory card.
FIG. 13 is a diagram for explaining processing steps performed in the disk drive device when data recorded in a memory card is read.
FIG. 14 is a diagram illustrating processing steps performed by a host computer when data is recorded on a memory card.
FIG. 15 is a diagram illustrating processing steps performed by the disk drive device when data is recorded on a memory card.
[Explanation of symbols]
1 pickup, 2 objective lens, 3 biaxial mechanism, 4 laser diode, 9 RF amplifier, 10 system controller, 12 encode / decode unit, 13 interface unit, 14 servo processor, 16 biaxial driver, 20 buffer memory, 26 ROM, 27 RAM, 80 host computer, 80a hard disk drive, 30 serial interface unit, 40 memory card, 90 disk

Claims (2)

As a peripheral device of a computer device configured to include the second recording medium,
Reading means capable of reading data from the first recording medium;
Data processing means for processing the management information of the first recording medium read by the reading means so that the computer device can handle the same as the data of the second recording medium;
A system controller for controlling the reading means and the data processing means based on a request from the computer device;
Bei to give a,
The system controller is
Determining that the request from the computer device requests data recorded in the first recording medium;
If it is determined that an MBR is requested from the computer device, the data processing means is controlled so that the MBR corresponding to the first recording medium becomes the MBR corresponding to the second recording medium. Process,
If it is determined that a PBR is requested from the computer device, the data processing means is controlled so that the PBR corresponding to the first recording medium becomes a PBR corresponding to the second recording medium. Process,
Transferring requested data from the second recording medium to the computer device;
Recording / playback device. As a peripheral device of a computer device configured to include the second recording medium,
Data capturing means capable of capturing data read from the second recording medium;
Data processing means for processing the management information of the second recording medium captured by the capturing means into management information corresponding to the first recording medium;
A system controller for controlling the reading means and the data processing means based on a request from the computer device;
Bei to give a,
The system controller is
Determining that the request from the computer device is to record data on the first recording medium;
If it is determined that the MBR has been transferred from the computer device, the data processing means is controlled so that the MBR corresponding to the second recording medium becomes the MBR corresponding to the first recording medium. Process,
If it is determined that the PBR is transferred from the computer device, the data processing means is controlled so that the PBR corresponding to the second recording medium becomes the PBR corresponding to the first recording medium. Process,
Transferring data from the computer device to the second recording medium;
Recording / playback device.

Images