JPH10199136A - Recording or reproducing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve efficiency of a disk driver and an entire data system. SOLUTION: This device is provided with a holding means 29, 30 which can hold a file manager in a state in which at least a disk is loaded, an external interface means 31-34 which can perform desired data communication to an external device other than a host device by a system such as, for example, data communication of an infrared ray system, LAM communication, and the like, and a control means 28 which can perform recording or reproducing operation for a disk using the file manager held in the holding means in accordance with request from external devices used for communication through the external interface means.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a recording or reproducing apparatus suitable for a disk drive for recording and reproducing data on a recording medium in, for example, a computer system, a multimedia system, and a data communication system. .

[0002]

2. Description of the Related Art Various kinds of software and data used in computer systems are transferred to optical disks, magneto-optical disks,
In general, a recording medium such as a magnetic disk, a memory card, and a magnetic tape is provided, and a user stores data and the like in these recording media. In these cases, usually, a disk drive that performs a recording / reproducing operation on a recording medium such as an optical disk or a magneto-optical disk is connected to a host computer, and the disk drive writes or writes data to the disk under the control of the host computer. Data is read from the disk.

[0003]

However, as described above,
In a system that performs recording / reproduction on a recording medium, usually, a host computer manages data files and the like on the recording medium. For this reason, file management for the loaded disc, that is, data read /
Management data and management software (hereinafter, referred to as a file manager) for managing writing are held by a host computer, and the host computer uses the file manager to make a write request to a disk drive at a required address. Issue a read request.

[0004] In other words, if only the device as a disk drive is used, the information as a file manager for the disk is not held. Therefore, a necessary operation is executed only by a write request and a read request from the host computer. Become. In other words, the disk drive could not be used as a recording / reproducing device when not connected to a specific host computer.

[0005] Of course, even if a file read request is issued from another device, such as by designating the file name, the disk drive does not manage the file name or the like on its own.
I can't answer that request. The same applies when data and a file name are transmitted and a write request is made.

That is, a disk drive is incorporated in a network file system independently of a host computer, and other information devices such as a notebook personal computer and a PDA (Personal Digital Assembler) are used.
istants) It cannot be used for data access and data storage from devices. For these reasons, the function as a disk drive is limited, and a more effective use form is required.

[0007]

SUMMARY OF THE INVENTION In view of the above problems, the present invention enables a disk drive, that is, a recording or reproducing apparatus, to respond to a recording / reproducing request from a source other than a specific host computer, thereby enabling recording. Another object of the present invention is to improve the efficiency of the reproducing apparatus and thus the entire data system.

For this reason, in the recording or reproducing apparatus, holding means capable of holding file management information relating to at least a recording medium in a state where the recording medium is loaded, and an infrared device such as an infrared ray for external devices other than the host device. Interface means capable of performing required data communication by a system such as a system data communication or LAN communication, and a file held by the holding means in response to a request from an external device communicated via the external interface means A control unit that can execute a recording or reproducing operation on a recording medium using the management information is provided.

That is, the recording or reproducing apparatus has file management information for the recording medium, so that it is possible to cope with direct access from an external device by a file name or the like. The file management information is recorded on a recording medium, and the file management information read from the recording medium may be stored in a holding unit, or one or a plurality of loaded recording media may be used as the holding unit. A storage unit for storing each file management information may be provided for the medium.

[0010] The control means may not respond to a recording or reproduction request for a recording medium from an external device at least during a period of recording or reproducing data on the recording medium in response to a request from the host device. During the period of recording or reproducing data on the recording medium in response to a request from the external device, by not responding to the recording or reproducing request from the host device for the recording medium, a recording / reproducing operation, a transfer operation, etc. Is performed properly.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A disk drive (recording / reproducing apparatus) in a data storage system (for example, an HS (Hyper Storage) system) which is an embodiment of the recording / reproducing apparatus of the present invention will be described below. The description will be made in the following order, and a ROM disk, a RAM disk, a partial ROM
I will give you a disk. 1. 1. Area structure of various discs 2. User area of partial ROM disk and RAM disk Control information 4. 4. System configuration example 5. Configuration of disk drive 6. Operation when loading disc Operation when requesting recording / playback

1. 1A to 1D show various disk media, and FIG. 1A shows a main data area whose entirety is a read-only area (ROM area) AE such as embossed pits.
ROM disk. FIG. 1B shows that the entire main data area is recorded / recorded by, for example, a magneto-optical area.
RAM that is a rewritable area ARW that can be reproduced
It is a disk. The partial ROM disk has a structure as shown in FIG. 1 (c) or (d), for example. That is, the ROM area AE and the rewritable area ARW are provided in the main data area of one disk.

FIG. 2 shows an area configuration from the outer peripheral side to the inner peripheral side, which is common to the disks of FIGS. 1 (a) to 1 (d). A GCP (Gray Code Part) zone for 736 tracks is provided on the outermost circumference side of the disc, and a buffer zone for 2 tracks, an outer control SFP zone for 5 tracks, a buffer zone for 2 tracks, A test zone for five tracks is provided. Subsequent to the test zone, a user area is formed as a main data area including a rewritable area ARW in which a user can record desired data and a read-only ROM area AE. The user area is divided into 16 bands of bands 0 to 15.

The ROM disk shown in FIG. 1A has an R area in which all user areas are recorded with embossed pits.
This is the OM area AE. In the RAM disk shown in FIG. 1B, the entire user area is a rewritable area ARW.

In the partial ROM disks shown in FIGS. 1C and 1D, a part of bands 0 to 15
E, a part thereof becomes the rewritable area ARW. Some of the 16 bands are rewritable area ARW and some are R
The OM area AE can be arbitrarily set by the manufacturer.

A test zone for 5 tracks and a buffer zone for 2 tracks, 5
Inner control SFP zone for tracks, buffer zone for 2 tracks, GCP for 820 tracks
A zone is provided.

GCP zone, outer control SF
The P zone and the inner control SFP zone are areas where predetermined control information is recorded.

In this disk, the number of rotations of the disk is constant, and the recording / reproducing clock is varied for each zone.
It is a so-called zone CAV disc, and 16 bands from band 0 to band 15 in the user area are each a zone corresponding to a specific recording / reproducing clock.

2. Partial ROM disk and RAM
FIG. 3 shows a detailed structure of a rewritable area ARW for a user area formed by 16 bands.
(A), (b) and FIG. FIG. 3A shows a partial ROM disc in which a rewritable area ARW is provided on the outer peripheral side of the disc in the user area.
FIG. 3B shows a partial ROM disk in which a rewritable area ARW is provided on the inner peripheral side of the disk.
FIG. 4 shows the case of a RAM disk.

In the case of FIG. 3A, bands 0 to M in the user area are rewritable areas ARW, and bands (M + 1) to 15 are ROM areas AE.
It has been. In the case of FIG. 3B, bands 0 to N in the user area are the ROM area AE, and bands (N + 1) to 15 are the rewritable area ARW. In the RAM disk of FIG. 4, all of the bands 1 to 15 are in the rewritable area A.
RW.

As can be seen from FIGS. 3 and 4, defect management areas DMA1 and DMA2 are provided in the head area of the band which is the head of the rewritable area ARW, and the defect management area is provided in the last area of the band which is the end of the rewritable area ARW. Management area DMA
3, DMA4. Also, the partial RO shown in FIG.
In the case of the M disk, an area adjacent to the ROM area AE is a buffer area.

A data area and a replacement area corresponding to the data area are prepared for each band. Therefore, when the rewritable area ARW is n bands out of 16 bands, an n-unit data area and an n-unit replacement area are provided. The replacement area is an area that provides a part to be used in place of the defective part when there is a defective part that cannot be recorded / reproduced due to a scratch or the like in the data area.

For example, if a defect site exists in the data area as shown by "x" in FIG.
A recording area replacing the “x” part is set in an area within the replacement area as indicated by an arrow. In the defect management areas DMA1 to DMA4, information for managing such a replacement situation and recording / reproducing appropriately without a defect portion is recorded.

It is to be noted that a search for a defective part in the data area, a specification of a part in the replacement area in place of the defective part, a defect management area DMA1 to DMAD.
Creation of information as MA4 and rewritable area ARW
The recording or the like is performed in the physical format processing of the disk, that is, by setting the state of FIG. 3A or 3B or FIG. 4 by the physical format, the rewritable area ARW is physically recorded. / Reproducible state.

However, in order to actually write a file to the rewritable area ARW, a logically formatted disk is further subjected to a logical format.
A file system for managing recording / reproduction in the rewritable area ARW must be written. That is, by performing the physical format and the logical format,
Actually, the user can use RAM disk or partial ROM
The disc can be used as a recording medium.
Although detailed explanation about the logical format is omitted,
This logical format mainly means the rewritable area A
A process of writing a file system capable of managing files in the rewritable area ARW (in the case of a partial ROM disc, the rewritable area ARW and the ROM area AE) at the head position of the RW. In the case of a partial ROM disk, a setup system serving as a tool for the logical format processing can be recorded in the ROM area AE in advance.

3. Control Information In the disc of this example, various types of control information are recorded at predetermined positions on the disc. The predetermined position in this case refers to an SFP zone (outer control SFP zone, inner control SFP zone) and a GCP zone. In the GCP zone, physical information of the medium (such as MO / ROM), media type, and location information of the SFP zone are recorded.

Each sector (204) in the SFP zone
8 bytes), information roughly shown in FIG. 5 is recorded.

Bytes 0 to 19 record the same data as the 20-byte data portion of the sector in the GCP zone. For example, physical information of media (MO / ROM, etc.), media type (type of ROM media by emboss / type of RAM media / partial ROM media by all MO area), format descriptor, start track number of SFP zone, maximum read Physical management information such as power and clock ratio in the control track is recorded.

In bytes 20 to 29, data as media information is recorded. For example, it is data such as a laser wavelength, a reflectance, and a track pitch.

In bytes 30 to 99, data as system information is recorded. For example, the maximum track number, maximum physical block address, DDS (Disc D
efinition Sector) start physical block address,
The number of tracks in the test zone, the number of bytes in the user area, and control information of 16 units of bands (band 0 to band 15) in the case of a partial ROM disk or ROM disk are recorded.

In bytes 100 to 419, detailed information on each of the 16-unit bands (band 0 to band 15) is recorded. That is, the start track address, the total number of tracks, the total number of sectors,
The number of sectors as a user area, the number of parity sectors, the number of preceding and following buffer sectors, the number of segments in the sector, the clock ratio, and the like are recorded. Byte 42
0 to 2047 are reserved.

Such information is roughly recorded in the SFP zone. Among them, the media type serving as disc type identification information is the position of byte 1 (second byte) in the sector of the SFP zone. Will be recorded.
In this one byte, information as shown in FIG. 6 is recorded. The fact that the byte 1 is “00h” (the number appended with h is in hexadecimal), that is, the eight bits are “00000000” indicates that the disk is a ROM medium. "20h" and "A0h" are RAM
Media and partial ROM media.

4. System Configuration Example FIG. 7 shows a system configuration example having the disk drive (recording / reproducing device) 1 of the present embodiment corresponding to the above ROM disk, RAM disk, and partial ROM disk.

The disk drive 1 normally performs a recording / reproducing operation under management and control from a host computer. FIG. 7 shows two disk drives 1A and 1B as the disk drive 1 of the present embodiment.
They are connected by CSI (SMALL COMPUTER SYSTEM INTERFACE), and perform recording / reproducing operations according to read / write requests from the host computer 3A. The disk drive 1B is a LAN (Local Area N)
(Etwork).

In the figure, a disk drive 2 is a conventional disk drive which does not correspond to the present invention.
Connected by SI, read from host computer 3B /
The recording / reproducing operation is performed only by the write request. The host computer 3B holds a file manager for managing a disk in the disk drive 2.

The disk drives 1A and 1B of this embodiment are different from the conventional disk drive 2 in that they are provided with an interface for performing infrared data communication and an interface for directly connecting to a network as a LAN. Will be. And furthermore,
As will be described later, a file manager for recording / reproducing a disk in the disk drives 1A and 1B has a configuration that the disk drives 1A and 1B hold therein.

Of course, the file manager relating to the disk drive 1A also has the host computer 3A, and the host computer 3A can execute a required recording / reproducing operation by transmitting a command as a read request / write request to the disk drive 1A. However, the disk drive 1A can also respond to an access request specifying a file name from an external device other than the host computer 3A, for example, a PDA device 5 or a notebook personal computer 6 (hereinafter referred to as a notebook computer). For example, if it is assumed that the PDA device 5 and the notebook computer 6 are equipped with an infrared interface means, a command or data for recording / reproducing a file or data for reproducing / recording a file is provided between the external device and the disk drive 1 by an interface using an infrared signal. Transmission and reception will be performed.

That is, the disk drive 1A has its own file manager and an infrared interface, so that the PDA device 5 and the notebook computer 6 can operate without the intervention of the host computer 3A.
The required recording / reproducing operation and data communication can be performed with an external device having an infrared interface.

Such an operation can be similarly performed in the disk drive 1B, and direct data communication between the disk drive 1A and the disk drive 1B is also possible. Further, the disk drive 1B can be accessed via the LAN transmission path 4 by the LAN interface. For example, when considering an information device 7 such as a personal computer or a PDA device configuring a LAN, the information device 7 can request a disk drive 1B to perform a recording / reproducing operation by designating a file name or the like. The same applies to the host computers 3A and 3B. Other communication interfaces include wireless LAN and R
Although various examples such as S-232C are conceivable, this example will be described with respect to a LAN and infrared rays.

5. Configuration of Disk Drive FIG. 8 shows the configuration of the disk drive 1 (1A, 1B) of this example.
Shown in The disk drive 1 is configured to be able to exchange commands and data with a host computer 3A (for example, a personal computer) connected by SCSI, and to supply commands and data from the host computer 3A to the disk 90. Data is recorded, and data is read from the disk 90 in response to a command from the host computer 3A.
The operation of supplying the data to the host computer 3A is performed. Here, the disk 90 is the ROM disk, R
It is an AM disk or a partial ROM disk.

The disk drive controller 10 (hereinafter, controller) controls communication with the host computer 3A and controls the entire recording operation and reproduction operation of the disk drive 1. The controller 10 executes actual recording / reproduction driving via a DSP (Digital Signal Processor) 19 communicable with the bus 27.
The DSP 19 has a function as a so-called servo driver, supplies a spindle drive control signal to the spindle driver 21 according to the servo information supplied from the A / D converter 18, and causes the spindle motor 22 to apply a drive signal. Thus, the CAV drive of the disk 90 is executed.

In addition, a drive control signal is output to the laser driver 16 to execute the laser emission operation from the laser diode 15a in the optical head 15, and the laser emission control is performed. The laser beam from the laser diode 15a passes through an optical system (not shown) and is applied to the disk 90 via the objective lens 15b. The reflected light from the disk 90 passes through an optical system (not shown) and passes through the photodetector 15.
c, and is extracted as an electric signal.

The electric signal obtained by the photodetector 15c is supplied to the IV / matrix amplifier 17 and the electric current /
After the voltage conversion, various signals are extracted by the matrix operation amplifier. That is, the ROM area A of the disk 90
RF signal to be reproduced data from E, disk 9
An MO signal, a focus error signal, a tracking error signal, a front APC signal, and the like to be reproduced data from the 0 rewritable area ARW are extracted.

A focus error signal serving as servo information;
Tracking error signal and front APC signal are A / D
The data is converted into digital data by the converter 18 and supplied to the DSP 19. The DSP 19 generates a servo drive signal according to the focus error signal and the tracking error signal,
It is supplied to the PWM driver 20. The PWM driver 20 supplies drive power to a focus coil, a galvano motor, and a slide motor in the optical head 15.

That is, the PWM driver 20 applies drive power to the focus coil by the focus servo drive signal based on the focus error signal, so that the objective lens is driven in the direction of coming and going to the disk, thereby performing focus control, and tracking. The tracking control and the sled movement control are performed by applying the driving power to the galvano motor and the slide motor by the PWM driver 20 based on the tracking servo drive signal and the slide servo drive signal based on the error signal. The DSP 19 controls the laser driver 16 according to the front APC signal so as to keep the laser output level at an appropriate level.

Data read at the time of reproduction from the disk 90 is obtained from the IV / matrix amplifier 17 as an RF signal or an MO signal. The output from the IV / matrix amplifier 17 is set to an appropriate potential level by the gain / offset control unit 23, and is converted into digital data by the A / D converter 24. Then, the signal converted into digital data is supplied to the encoder / decoder section 12, where the digital filter processing, the Viterbi decoding processing, and the NRZ
Decoding processing, descrambling processing and the like are performed, and the reproduced data is obtained. After the reproduced data is stored in the buffer memory 11, the data is sent to the SCSI processing unit 26 by the controller 10 at a predetermined timing, and the host computer 3
A.

Note that the A / D converter is used to generate various timings synchronized with a reproduction clock and a reproduction signal for the reproduction process.
The output of the converter 24 is a PLL timing generator 25
The reproduction clock and various timing signals based on the reproduction clock are formed by a so-called PLL operation.

When a recording request command and data to be recorded are supplied from the host computer 3A via the SCSI processing unit 26, the controller 10 accumulates the data in the buffer memory 11 and then stores the data at a predetermined transfer rate. The data is supplied to the decoder unit 12 and is encoded into a data form used when recording is actually performed on the disk 90. Then, the encoded data is supplied to the magnetic head driver 13, and the magnetic head driver 13 executes a magnetic field application operation from the magnetic head 14 to the disk 90 according to the recording data. During recording, a high-level laser output for recording is executed from the laser diode 15a.

In the disk drive 1 of this embodiment, as described above, the disk drive 1 itself has a file manager for the disk 90, and the disk manager 1 is required to use the file manager without control from the host computer 3A. A recording / reproducing operation can be performed. Therefore, the CPU 27 and the RA
M29 and flash memory 30 are connected. Further, there are provided an infrared controller 31 and a transmission / reception section 32 which constitute an infrared interface, a network controller 33 which constitutes a LAN interface, and a LAN communication section 34 connected to the transmission path 4 in FIG.

In FIG. 10, the disk drive controller 10 is divided into blocks so as to include functions as a buffer memory controller for controlling the buffer memory 11 and a SCSI controller for controlling the SCSI processing unit 26. The infrared controller 31 controls a control signal SG for data transfer with the buffer memory controller in the disk drive controller 10.
By exchanging (for example, a transfer request signal or a transfer clock), data can be exchanged with the buffer memory 11. Similarly, the network controller 33 also exchanges a control signal SG (for example, a transfer request signal or a transfer clock) for data transfer with the buffer memory controller in the disk drive controller 10 to exchange data with the buffer memory 11. It is possible to exchange data between.

In this example, the functions as the controller include four control functions of disk drive control, buffer memory control (memory manager), SCSI control, infrared interface control, and network interface control, and one memory manager. Although these functions are required, all of these parts can be integrated as a one-chip controller.

The RAM 29 or the flash memory 30 is used to hold a file manager serving as management information unique to the disk. As a method of holding the file manager in the disk drive 1, data (software) as the file manager is stored on the disk 9.
0, and when the disc is loaded, it is read and expanded in the RAM 29.
0 file manager for flash memory 30
For example, a method of storing the data in a solid-state memory such as the above is conceivable.

When the method of reading from the disk 90 is adopted, it is not necessary to always keep the file manager in the flash memory 30. That is, in this case, there is no need to provide the flash memory 30.
When the method of holding the file manager in the flash memory 30 is adopted, the file manager must be recorded on the disk 90, and
R to expand the file manager read from
There is no need to prepare AM29. Of course, the memory for holding the file manager does not always need to be a flash memory, and another type of memory may be used. In addition, although an operation mode of reading from a disk is used, as a method having a function equivalent to the case of using the flash memory 30, a file manager may be held in the ROM area of the partial ROM disk.

The CPU 28 uses the file manager stored in the RAM 29 or the flash memory 30 to instruct the controller 10 to perform a recording / reproducing operation of a required data file. That is, necessary recording / reproducing operation control is performed by communication with an external device via the infrared controller 31 or the network controller 33, and data transmission / reception operation control with the infrared controller 31 or the network controller 33 is performed.

The infrared controller 31 decodes commands and data transmitted from an external device by infrared rays and received by the transmission / reception unit 32, and decodes the commands and data.
(Buffer memory 11). The communication information from the CPU 28 and the controller 10 (the buffer memory 1
The reproduction data supplied from 1) is encoded as necessary as an infrared signal, and the transmission / reception unit 32 transmits the data to an external device. Similarly, the network controller 33 sets the LAN transmission path 4 to the LAN communication unit 3
4 decodes the command or data received in
28 and the controller 10 (buffer memory 11). Also, communication information from the CPU 28 and the controller 1
0 (buffer memory 11), necessary encoding is performed on the reproduced data as an infrared signal,
An operation of transmitting data from the LAN communication unit 34 to the LAN network is performed. It is also conceivable to provide a wireless LAN communication unit 34a so as to support wireless LAN.

FIG. 9 shows a functional block configuration of software in such a disk drive 1. That is, LAN interface processing, infrared interface processing, SCSI interface processing, drive processing, file manager processing, cache processing, and background processing are configured based on hardware processing such as the CPU 28 and monitoring processing. L
The AN interface process is a process related to control of the network controller 33 and data transmission / reception / command transmission / reception via the LAN network. The infrared interface processing is processing relating to control of the infrared controller 31 and data transmission / reception / command transmission / reception with an external device by infrared communication. The file manager process is performed in the RAM 29 or the flash memory 3
This is processing relating to management of recording / reproducing operations on the disk 90 using the file manager holding 0. S
The CSI interface processing is performed by the host computer 3
Processing related to communication with A, drive processing is the actual recording /
This is processing related to playback control. Further, a caching process related to data reading and a background process are also configured.

In this embodiment, an infrared interface configuration and a LAN interface configuration are used as interfaces to external devices other than the host computer 3A, but it is not always necessary to provide both.

6. Operation when loading a disk As described above, as a method of holding a file manager inside the disk drive 1, data as a file manager is recorded on each disk 90, and when the disk is loaded, the file manager is read and the RAM is read.
29 and a method of providing a flash memory 30 in which a file manager is recorded.

Here, regarding the operation at the time of loading the disk when the method of reading the file manager from the disk 90 and expanding it to the RAM 29 is adopted,
28 and the processing performed by the controller 10 are shown in FIGS.
3 will be described. Then, a processing example of a method of providing a flash memory 30 in which a file manager is recorded will be described with reference to FIG.

As shown in FIG.
When the disk 90 is loaded in the CPU 90, the CPU 28 first determines the type of the disk 90 in step F101. That is, it is determined whether the disk 90 is a RAM disk, a ROM disk, or a partial ROM disk. This determination process is a process of reading the data of the SFP zone on the disk described with reference to FIGS. 5 and 6, for example, and confirming the media type code in the data.

If it is determined that the disk is a RAM disk, the process proceeds to step F102, and a process of reading the last sector of the relable area is performed. If it is determined that the disk is a ROM disk or a partial ROM disk (partial ROM with a physical format), the process proceeds to step F103 to read the last sector of the ROM area.

The file manager is recorded in a certain area on the disk 90. File system information for managing the recording position of the file manager on the disk 90 is the last file in the rewritable area in the case of a RAM disk. In the case of a ROM disk or a partial ROM disk, the data is recorded in the last sector of the ROM area.

Accordingly, the processing in step F102 or F103 is processing for reading file system information. Note that the recording position of the file system information is not necessarily RA
The last sector of the rewritable area of the M disk, or the R sector of the ROM disk or partial ROM disk
It is not necessary to set to record in the last sector of the OM area. Therefore, the processing of steps F102 and F103 may be read processing of the sector in accordance with the setting of the sector in which the file system information is recorded.

In the case of this example, the last sector of the rewritable area of the RAM disk or the ROM disk,
File system information recorded in the last sector of the ROM area on the partial ROM disk is, for example, as shown in FIG.
Information such as 2 (a) to 2 (d) is obtained. FIG. 12A shows a partial R in a state where the logical format is not performed.
This shows an example of file system information as the last sector of the ROM area in the OM disk, for example.

In this case, the first 24 bytes are used as the header of the file system information.
A code corresponding to the character "LE PROM SYSTEM" is recorded. And the next 6 bytes are file I
D is recorded. The file ID is an identification code indicating a file format. For example, FAT12, FAT1
6. Information indicating the type of file system such as HFS. (FAT; File Allocation Table, HFS; Hi
erarchy File System)

Two bytes following the file ID record the number of bytes per sector, and the next one byte records the number of sectors per allocation. The next 8 bytes describe the start sector of the file manager, that is, the recording position of the file manager, and the next 4 bytes describe the total number of sectors of the load file as the file manager.

Thus, the portion of the disk 90 where the file manager is recorded (the area corresponding to the number of sectors from the start sector) is shown. The location of the file manager may be in the ROM area or in the rewritable area. However, in a partial ROM having a rewritable area where recording, rewriting, and erasing are performed at any time, it is conceivable that the file manager is set in the rewritable area from the beginning to cope with data update required for the file manager. Can be

In the following 1 byte, “FF” is used as the end ID.
h ”is recorded, indicating the end of the actual data as a sector of the file system information.

FIG. 12B shows an example of file system information recorded as, for example, the last sector of a rewritable area on a partial ROM disk in a state in which a logical format has been performed. In this case, the first 24 bytes as a header of the file system information are recorded with a code corresponding to the character "HS FILE PRAM SYSTEM", for example, as shown in FIG.
Is distinguished from Subsequent data is the same as in FIG.

In step F101 in FIG.
If it is determined that the disc is an OM disc, the RO is determined in step F103.
File system information as the last sector of the M area,
That is, although the sector shown in FIG. 12A is read, if the disk is a logically formatted partial ROM disk, the process proceeds to step F102, where the file system information shown in FIG. It is also conceivable to read sectors.

FIG. 12 shows the logical format.
When the file system information shown in FIG. 12B is formed, the two file system information shown in FIGS. 12A and 12B coexist on the disk. In this case, the file system information shown in FIG. (The processing after step F104 described later). This is because FIG.
The two file system information items (b) may have the same contents, but may not necessarily be the same.
In particular, since the file system information in FIG. 12B can be freely set later, it is preferable to give priority to the file system information in FIG. However, if the file manager cannot be recognized as a process in step F106 described below even if access is performed using the file system information in FIG.
What is necessary is just to use the file system information of (a). In this case, it is appropriate to prohibit the writing operation to the rewritable area.

Further, when the two file system information shown in FIGS. 12A and 12B coexist, it is possible to adopt a mode in which different file managers are shown. For example, R
A file manager that manages files in the OM area and a file manager that manages files in the rewritable area are formed separately, and each file manager is as shown by the file system information in FIGS. It may be.

FIG. 12C shows an example of file system information formed in the last sector of the rewritable area in the case of a RAM disk. In this case, the first 24 bytes as the header of the file system information are, for example, “HS FILE RAM SYSTEM”.
The code corresponding to the character
(A) and (b) are distinguished. The following data is shown in Fig. 1.
This is the same as 2 (a) and 2 (b).

FIG. 12D shows an example of file system information formed in the last sector of the ROM area in the case of a ROM disk. In this case, in the first 24 bytes as the header of the file system information, for example, a code corresponding to the character "HS FILE ROM SYSTEM" is recorded.
(B) It is distinguished from (c). The following data is shown in Fig. 1.
2 (a), (b), and (c).

When a sector in which file system information is likely to be recorded is read in the processing of step F102 or F103, the header of the first 24 bytes of file system information in each of FIGS. It is determined whether or not it exists (F104).

If the header of the file system information does not exist, it means that the disc cannot support the operation of the present example, that is, the operation of expanding the file manager inside the disk drive 1, and the process directly proceeds to step F116. The process ends with the file system recognition flag turned off. That is, in this case, since the file manager does not exist in the disk drive 1 itself, the recording / reproducing operation on the disk 90 can be performed only by using the file manager in the host computer 3A. It is not possible to directly access from external devices such as.

However, if the header of the file system information exists, it means that the file manager is recorded on the disk 90. Therefore, in step F105, the recording sector of the file manager is determined. That is, information such as the start sector of the file manager and the number of sectors of the file manager in the file system information of FIG. 12 is read. Then, in step F106, the actual file manager is read and activated. In other words, the file manager is read from the disk 90 and expanded in the RAM 29, and the CPU 28 can start a required file recording / reproducing operation on the disk 90 without the intervention of the host computer 3A by being started by the file manager.

Next, at step F107, the first sector of the user area (so-called sector of logical block address 0) is read. In other words, it is the head part where the actual file structure is recorded. The processing after step F107 is processing for checking the consistency between the file system information and the file manager and the actual data file, and setting a flag (setting a file system recognition flag) according to the type of the confirmed file system. .

The file system recognition flag indicates whether or not the file manager corresponding to the loaded disk 90 can be held in the RAM 29 (including the flash memory 30 in FIGS. 15 and 16 described later). This is information that can be identified and indicate the type of the file management information. As will be described later with reference to FIG. 18, when there is a disk access request from an external device, the CPU 28 determines execution / non-execution of access processing according to the request based on the state of the file system recognition flag. .

The type of the file system is assumed to be FAT12, FAT16, HFS for explanation. Of course, the file system applicable to this example is not limited to these.

First, in the file system information shown in FIG. 11, the file ID is FAT12 or FAT1.
If it is 6, the actual file structure from logical block address 0 should be as shown in FIG. IPL (Initial program Loarde)
r) An area is formed, and the version name, the number of bytes per sector,
File system management information such as the number of sectors per allocation, the number of FATs, and the number of entries in a root directory is recorded.

In addition to the IPL area, FAT1 area, FAT area
An AT2 area, a root directory area, a data area, and the like are provided, and a FAT system is constructed. FIG.
If the file ID is FAT12 or FAT16 in the file system information shown in (1), the IPL area is first read in the process of step F107, and the FAT-ID in the IPL area must be confirmed as shown in FIG. become. FAT-ID is FAT12, FA
Although a code corresponding to T16 or the like is described, if the FAT-ID is correctly confirmed, the process proceeds to step F108.
To F109. And FAT according to FAT-ID.
Check the header of the 1 area and the FAT2 area.

Here, if the headers of the FAT1 area and the FAT2 area cannot be confirmed correctly, it means that the FAT system has not been properly constructed for some reason. In this case, the process proceeds to step F116, where the file system recognition flag is turned off and the process ends.

In this case, the file manager developed on the RAM 29 does not correctly correspond to the file configuration of the disk 90. Therefore, by turning off the file system recognition flag, it is considered that no file manager exists in the disk drive 1, and the recording / reproducing operation on the disk 90 can be performed only by using the file manager in the host computer 3A. It is assumed that the recording / reproducing operation on the disk 90 by direct access from an external device such as the notebook personal computer 6 cannot be performed.

If the headers of the FAT1 area and the FAT2 area have been correctly confirmed, the process proceeds to step F110, where the FAT-
The existence of the root directory is confirmed according to the ID. If the existence of the root directory cannot be confirmed, this also means that the FAT system has not been properly constructed. Therefore, also at this time, the process proceeds to step F116, the file system recognition flag is turned off, and the process ends.

If the existence of the header and the root directory of the FAT1 area and the FAT2 area is confirmed, that is, if the FAT file is confirmed as the actual file, the CPU 28
The process proceeds to step F114, where the file system recognition flag is set to a value corresponding to FAT (FAT12 or FAT16), and the process ends. In this case, the CPU 28
Corresponds to the FAT12 or FAT16 file system on the disk 90, and it is confirmed that the file manager is expanded in the RAM 29. Accordingly, when an external device such as the PDA device 5 or the notebook computer 6 makes an access request specifying a file name, the CPU 28 uses the file manager stored in the RAM 29 (to control the host computer 3A). (Not based on this), it is possible to execute recording / reproduction of a file on / from the disk 90.

If the file ID is HFS in the file system information shown in FIG. 12, step F1
At the head of logical block address 0 (sector 0) read at 07, a code (magic key) serving as an ID indicating an HFS file system should be recorded.

If the HFS-ID does not exist, it means that no file system is constructed on the disk as HFS, that is, the file manager expanded on the RAM 29 correctly corresponds to the file configuration of the disk 90. You will not. Therefore, the process proceeds from step F111 to F116, in which the file system recognition flag is turned off, and it is considered that no file manager exists in the disk drive 1, and the recording / reproducing operation on the disk 90 is performed by using the file manager in the host computer 3A. Recording / reproducing operation on the disk 90 by direct access from an external device such as the PDA device 5 or the notebook personal computer 6 cannot be performed.

On the other hand, if the HFS-ID exists, the process proceeds from step F111 to F112. Here, the information of the partition map is confirmed from the information of the sector 0, and further, a drive map is searched to confirm whether or not the magic number (magic key) of the partition map is an appropriate value. If not confirmed correctly, go to step F1
Proceeding from 13 to F116, the file system recognition flag is turned off.

If the confirmation is successful, the HFS file has been confirmed as an actual file, and the CPU 28
The process proceeds to step F115, where the file system recognition flag is set to a value corresponding to HFS, and the process ends.
In this case, the CPU 28 has confirmed that the file manager has been expanded in the RAM 29 in correspondence with the file system as the HFS on the disk 90. That is, thereafter, the CPU 28 operates the PDA device 5, the notebook personal computer 6, and the like. When there is an access request specifying a file name from an external device, the CPU 28
9 (without being controlled by the host computer 3A), a file can be recorded / reproduced on / from the disk 90.

FIG. 11 specifically shows the processing of steps F107 → F111 → F112 → F113 when the actual file is an HFS file. That is, in step F107, the information of the sector 0 (logical block address 0) is read as described above. However, in the case of an HFS file, the reading of the sector 0 means the sector and the size in which the device driver is recorded. Is read processing. The first two bytes of sector 0 are called a magic key, and if this value is "4552h", it is considered appropriate. If the first two bytes are not "4552h", it is determined that the file is not an appropriate HFS file, and the process proceeds to step F111.
From step F116 to step F116 in FIG.

If the first two bytes are "4552h",
The read data of sector 0 is regarded as appropriate data, and the process proceeds from step F111 to F112. Then, the information of sector 1 (logical block address 1) is read. The reading of the sector 1 is reading of the partition map. In the partition map, a start position, an end position, information contents (information type such as a driver and a file system) of the partition are written. Also,
The first two bytes of sector 1 are also called a magic key, and if this value is "504Dh", it is considered appropriate.

The first two bytes of sector 1 are "504D
h ", it is not a proper HFS file,
The process proceeds from step F113 to step F116 in FIG. If the first two bytes of sector 1 are “504Dh”, the file is determined to be a proper HFS file, that is, it is determined that the confirmation is OK, and the process proceeds to step F115, where the file system recognition flag is set to a value corresponding to HFS as described above. And finish the process.

The operation at the time of loading the disk in the case of employing the method of reading the file manager from the disk 90 and expanding it in the RAM 29 has been described above. However, in the case of employing the method of providing the flash memory 30 recording the file manager, Then, it is determined whether or not the real file of the loaded disk 90 correctly corresponds to a certain file manager in the flash memory 30, and a process of setting a file system recognition flag is performed.

FIG. 14 shows a processing example in this case. In addition,
Steps having the same processing content as the processing in FIG. 10 are denoted by the same step numbers, and description thereof is omitted. FIG.
As described in the case of the processing example, the file system information recorded in, for example, the last sector of the disk 90 includes:
The information as the start sector of the file manager is recorded. However, when the flash memory 30 is provided to hold the file manager, it is not always necessary to hold the file manager in the disk 90. If the file is not stored, the information as the start sector of the file manager may not be recorded, or information for identifying a specific file (file as a file manager) in the flash memory may be recorded. . Note that the flash memory 3
Needless to say, when the file manager is held by setting 0, the same file manager may be held in the disk 90.

When the file manager held in the flash memory 30 is used, the correspondence between the loaded disk 90 and a certain file manager in the flash memory 30 may be checked.
For this comparison, the file system information recorded on the disk 90 may be used.
In the case where a file manager is recorded in 0, the contents of the file manager may be compared with a certain file manager in the flash memory 30 to perform collation.

The processing in FIG. 14 is performed in step F105 in FIG.
The processing of F106 is different in that the processing of steps F130 and F131 shown in FIG. 14 is performed. That is, when the header of the file system information is confirmed in step F104, it is determined whether or not the file manager corresponding to the loaded disk 90 is stored in the flash memory 30 based on, for example, the file system information. If the file manager corresponding to the disk 90 is not stored in the flash memory 30, the process proceeds to step F116, and the file system recognition flag is turned off. That is, in this case, since the file manager does not exist in the disk drive 1 itself, the recording / reproducing operation on the disk 90 is performed by the host computer 3.
A becomes possible only by using the file manager in A, and cannot be directly accessed from external devices such as the PDA device 5 and the notebook computer 6.

On the other hand, if the file manager corresponding to the disk 90 is stored in the flash memory 30,
In step F131, the file manager is read from the flash memory 30. Then, from step F107, the same processing as in the case of FIG. 10 is performed to set the file system recognition flag.

When the file manager is held in the flash memory 30, such processing may be employed. However, considering that the file manager is also recorded on the disk 90, the processing shown in FIG. Is also conceivable. In FIG. 15, steps having the same processing content as the processing in FIG. 10 are denoted by the same step numbers, and description thereof is omitted.

The processing in FIG. 15 is performed between the processing in step F106 and step F107 in FIG. 10 and the processing in step F14 shown in FIG.
The difference is that the processes of 0, F141, and F142 are added.
That is, when the header of the file system information is confirmed in step F104, the recording sector of the file manager is determined in step F105 as in the case of FIG. 10, and the file manager is read in step F106. If the file manager can read the data into the RAM 29 well, the process proceeds to step F140.
To F107. However, there are cases where the file manager cannot be read for some reason. For example, a case where no file manager is formed on the disk 90 or a case where the data portion as the file manager is damaged due to some accident and cannot be read.

Then, if the reading becomes NG, step
The process proceeds from F140 to F141 to determine whether or not a file manager corresponding to the disk 90 is stored in the flash memory 30. If the file manager corresponding to the disk 90 is not stored in the flash memory 30, that is, if the file manager cannot be read from the disk 90 or the flash memory 30, the process proceeds to step F116 to turn off the file system recognition flag. In this case, there is no file manager in the disk drive 1 itself, so that the recording / reproducing operation on the disk 90 can be performed only by using the file manager in the host computer 3A, and the PDA device 5, the notebook personal computer 6, etc. Direct access from external devices will not be possible.

On the other hand, if the file manager corresponding to the disk 90 is stored in the flash memory 30,
The process proceeds from step F141 to F142 to read the file manager from the flash memory 30. And step F107
Proceed to. After reading the file manager from the disk 90 or the flash memory 30 and proceeding to step F107, the same processing as in FIG. 10 is performed to set the file system recognition flag.

In the case of the process shown in FIG. 15, the available width for a disk on which a file manager is recorded and a disk on which a file manager is not recorded (a disk in which the file manager is held in the flash memory 30) is widened. If the file manager is also stored in the flash memory 30 even if the disk has a manager recorded thereon, even if an accident or the like that causes the file manager to be unable to be read from the disk 90 occurs, normal operation can be performed. Will be able to respond.

In the process of FIG. 15, the flash memory 30 may be checked first, and if there is no file manager in the flash memory 30, the file manager may be read from the disk 90.

7. Operation at the time of recording / reproducing request Next, the operation when there is a recording / reproducing request from the host computer 3A, and the recording / reproducing request of the file by the infrared interface from the external device such as the PDA device 5 or the notebook computer 6 The operation in the case of the above will be described. Note that, for example, regarding an operation (an interface by the network controller 33 and the LAN communication unit 34) when a recording / reproduction request is made via the LAN from the external device 7 in FIG. 7, a file recording / reproduction request is made through the infrared interface. The operation in this case is only the difference in the input / output method according to the interface mode, and the operation of the disk drive 1 is substantially the same, so that the description is omitted.

FIG. 16 shows the processing by the CPU 28 and the controller 10 when there is a recording / reproducing request from the host computer 3A, that is, when a SCSI selection occurs. As a recording / reproducing request from the host computer 3A to the disk drive 1, S
When a selection on the CSI occurs, the CPU 28 first checks the state of the command processing flag for another interface in step F201.

The command processing flag is SCS in this example.
An I processing flag, an infrared IF processing flag, and a LAN-IF processing flag. These command processing flags are shown in FIG.
6. This flag is set in the process set in FIG. 18, and is a flag for identifying the communication execution state of each interface.

The command processing flags relating to other interfaces in step F201 are an infrared IF processing flag and a LAN-IF processing flag. FIG.
6. In FIG. 18, the LAN-IF processing flag is not considered for the sake of simplicity of explanation, but the LAN-IF processing flag is not considered.
The processing flag is turned on during execution of processing by the LAN interface, similarly to the case where an infrared IF processing flag described later is turned on during execution of processing by the infrared interface.

Infrared IF processing flag (or LAN-IF
If the (processing flag) is on, it means that communication on those interfaces is being executed. Then, the process proceeds from step F202 to F203, and returns “BUSY” as status information to the SCSI, that is, the host computer 3A. That is, a process indicating that the request from the host computer 3A cannot be handled is performed.

However, depending on the model of the host computer 3A (that is, the type of the operating system),
When "BUSY" is returned by SCSI, there are some cases in which good operation is not possible. In such a case, upon receiving a command from the host computer 3A, it is preferable to perform a process of causing the host computer 3A to wait as it is (for example, a situation where a disk is not loaded in a pseudo manner). An example of processing in such a case will be described later with reference to FIG.

If the infrared IF processing flag (and the LAN-IF processing flag) is off at the time of step F202, communication is not currently being performed on those interfaces, and a request from the host computer 3A is received. It will be able to respond. Therefore, the process proceeds from step F202 to F204, and first, it is determined whether a cartridge lock command has been transmitted from the host computer 3A. If it has been transmitted, a cartridge lock process is performed.
(F205).

The cartridge lock is a process in which the host computer 3A sets the operation of the disk drive 1 in a state dedicated to the host computer 3A for recording / reproducing on / from the disk 90. Note that, for example, when the host computer 3A sends a command to the disk drive 1 to perform a device check when the host computer 3A is powered on to start up the system, recording / reproduction to / from the disk 90 is not involved. In this case, the cartridge is not locked. That is, the cartridge lock command is not transmitted from the host computer 3A.

The actual read / write request etc.
Will occur intermittently through step F20
In the state of waiting in the loop of F207 and F207, each time those actual commands are transmitted, the process proceeds to step F206.
Then, the process proceeds to F208 to turn on the SCSI processing flag. Then, processing such as data reading / writing is executed according to the command (F209). When the processing is completed, the process proceeds from step F210 to F211 to turn off the SCSI processing flag and return to the loop of steps F206 and F207.

The host computer 3A requests the disk drive 1 for a necessary operation, and terminates the selection when a series of data transmission or reception is completed.
Then, the process of the CPU 28 proceeds from step F207 to F212. If a cartridge lock release command has been sent at the same time, the cartridge lock is released in step F213, and the process ends. The host computer 3A
Claims that it has its own file manager for the disk 90,
It is not necessary to use the file manager 29 or the file manager held in the flash memory 30, but, for example, the host computer 3A requests access by a file name or the like as in the case of the external device using the infrared interface described in FIG. It is also possible to execute the disk access operation by using the file manager held by the drive 1.

As described above, depending on the model of the host computer 3A, a process as shown in FIG. 17 may be performed instead of step F203 in FIG. That is, step F2
Even if it is determined in 02 that the infrared IF processing flag (or the LAN-IF processing flag) is ON, a response to the selection by SCSI is made in step F220, and the process proceeds to step F221.
Receives a command from the host computer 3A. Then, in step F222, it is determined whether or not the received command is a drive access command for recording and reproduction. If the received command is not a drive access command, it is possible to respond even if drive access by an infrared interface is performed, for example. Therefore, the process corresponding to the command is executed in Step F223, and Step F224
Returns the good status as the processing result, and ends the processing.

If the received command is a drive access command, since the flag-on period cannot be handled, the process proceeds to step F225, where the host computer 3A
It is determined whether or not disconnection is possible.
If disconnection is not possible, the process proceeds from step F225 to F226, and returns “error” or “BUSY” to the SCSI, that is, the host computer 3A. The value returned depends on the system.

If it is determined in step F225 that disconnection is possible, disconnection processing is performed in step F227, and the process waits in step F228. That is, it waits until the flag-on state is released in the disconnected state (that is, the drive access by the infrared interface is terminated). When the flag is turned off, it is possible to respond to a drive access command as a selection generated in SCSI. Therefore, after performing a reconnect process in step F229, the process proceeds to step F204 in FIG.

Next, a process when the CPU 28 detects a command input through the infrared interface via the transmission / reception unit 32 and the infrared controller 31 will be described with reference to FIG. First, in step F301, the file system recognition flag is checked. As described above, the case where the file system recognition flag is off is the case where no file manager exists in the RAM 29 (or the flash memory 30) for the current disk 90. Therefore, in this case, normally, it is not possible to respond to the command input through the infrared interface.
Thus, the transmission / reception unit 32 returns to the external device that the file system cannot be recognized.

However, as an exception, if the input command is a command for instructing a formatting process for the disc 90, a file system is to be formed from now on. is there. Therefore, if the command is a format execution command, the process proceeds from step F307 to F308 to execute a format process on the disk 90. That is, the controller 10 instructs the controller 10 to execute formatting according to the file system type (FAT, HFS) specified by the format execution command. Set a flag. For example, when the HFS format is performed, the file system recognition flag is set to a value corresponding to HFS.

If the file recognition flag is ON in step F301, the disk drive 1 can respond to an access request through the infrared interface. In this case, the CPU 28 checks the state of the command processing flag relating to another interface as Step F302. Here, the SCSI processing flag (and LAN-I
F processing flag).

When the SCSI processing flag (or the LAN-IF processing flag) is on, it means that communication on those interfaces is being executed. Then, the process proceeds from step F302 to step F311 to return "BUSY" as status information from the infrared interface, that is, the transmitting / receiving unit 32 to an external device such as the PDA device 5 or the notebook computer 6. That is, processing is performed assuming that it cannot respond to a file recording / reproducing request from an external device.

In some cases, the cartridge lock is on even if the SCSI processing flag is off.
If it is determined in step F303 that the cartridge lock is ON, since the logical connection between the disk drive 1 and the host computer 3A by SCSI is ongoing at this time, the process also proceeds to step F311 and the external device is connected to the external device. Will return "BUSY".

When the SCSI processing flag (and the LAN-IF processing flag) and the cartridge lock are off, communication is not currently being performed on those interfaces, and an external device generated by the infrared interface is not connected. It will be able to respond to requests. So step
The process proceeds from F303 to F304, and first, the infrared IF processing flag is turned on. And read / write data according to the received command according to the protocol of the infrared interface,
A process such as infrared transmission is executed (F309). When the process is completed, the infrared IF processing flag is turned off in step F306, and the process ends.

Since the interface with the host computer 3A and the interface with the external device are performed as described above, communication on a plurality of interfaces is not overlapped, and the operation of the system is not confused. FIG. 19 shows this state. As shown in FIGS. 19A and 19B, during the period in which the cartridge lock or the SCSI processing flag is ON, even if a request by the infrared interface is generated, the infrared IF non-permission period, which cannot respond to the request, BUSY ”is returned.

On the other hand, as shown in FIG. 19C, while the infrared IF flag is on, the host computer 3
A is a SCSI non-permission period that cannot respond to an access request from the host computer 3A, that is, the host computer 3A.
"BUSY" is returned.

During the period in which the cartridge lock is on, the portion in which the SCSI flag is on is a period in which processing accompanying a series of intermittent commands for drive access is normally performed. The portion where the SCSI flag is ON during the period in which the cartridge lock is OFF is a period during which processing corresponding to some command other than the drive access command is being executed.

By the way, depending on the model of the host computer 3A, for example, on / off control of the cartridge lock is not performed before and after the access request to the disk drive 1 is made. For example, this is a method of setting a state of mount / unmount for the connected disk drive 1 and turning on / off a state in which the host computer 3A and the disk drive 1 logically form a system according to the setting. In this case, while the host computer 3A “mounts” the disk drive 1 as a logically connected device, the disk drive 1 is dedicated to the host computer 3A. On the other hand, in the “unmounted” state, the host computer 3A does not regard the disk drive 1 as a logically connected device.

In the host computer 3A, the mount /
A process as shown in FIG. 20 is performed according to a user operation for unmounting. First, when an application for mounting / unmounting is started (F401), it is determined whether the user operation is a mount setting operation or an unmount setting operation (F402). An internal mounting process, that is, a setting process for setting the disk drive 1 as a logical connection device is performed (F403), and a cartridge lock command is output to the disk drive 1 (F404). In the disk drive 1, the cartridge is locked accordingly. Then, the application used for the processing is started (F405).

If the user's operation is an unmount setting operation, the application that has been started at that time is terminated (F406). Then, internal unmount processing, that is, setting processing for releasing the disk drive 1 from the logical connection device is performed (F40).
7) Output a cartridge lock release command to the disk drive 1 (F408). In the disk drive 1, the cartridge lock is released accordingly.

In the case of such a mount / unmount system, when a file access request is received from an external device through the infrared interface, the unmount (that is, the cartridge lock is released in the disk drive 1) is performed. There must be. Therefore, when the user uses the disk drive 1 from an external device such as the PDA device 5 or the notebook computer 6, it is necessary to perform an unmount setting operation in the host computer 3A in advance.

Conversely, when connecting the disk drive 1 as a logical connection device from the host computer 3A,
Must be mounted. Therefore, when using the disk drive 1 from the host computer 3A after using the disk drive 1 from the external device, the mount setting operation is performed in the host computer 3A before that.

Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described system configuration, disk drive 1 configuration, and processing method, and it can be said that various various examples can be considered. Not even.

In the above description, a removable disk (ROM disk, RAM disk, partial ROM disk) is given as an example of a recording medium. However, even if the disk is irremovably mounted in the disk drive 1, the same applies. The present invention can be applied to

[0134]

As described above, the recording or reproducing apparatus of the present invention has a holding means capable of holding file management information (file manager) relating to a recording medium at least in a state where the recording medium is loaded, External interface means capable of performing required data communication by a system such as infrared data communication or LAN communication with external equipment other than the host equipment, and requests from external equipment communicated via the external interface means And control means for executing a recording or reproducing operation on a recording medium using the file management information held in the holding means. That is, since the recording or reproducing apparatus has the file management information and control function for the recording medium inside the recording or reproducing apparatus, not only the operation by the command from the host computer having the file management information but also the direct operation from the external device by the file name or the like. It can operate in response to access. As a result, there is an effect that the versatility and efficiency of use as a recording or reproducing device can be realized. In particular, by enabling data transfer without a host device, a network file system can be formed. Specifically, the above effects can be exhibited as a wired or wireless network file system using a LAN, a wireless LAN, an infrared interface, or the like.

[0135] Further, the control means does not respond to the recording or reproduction request for the recording medium from the external device at least during the period of recording or reproducing the data on the recording medium in response to the request from the host device. During the period of recording or reproducing data on the recording medium in response to a request from the external device, by not responding to the recording or reproducing request from the host device for the recording medium, a recording / reproducing operation, a transfer operation, etc. Is performed properly, and the operation is prevented from being complicated among a plurality of interfaces.

Further, the control means identifies whether or not the file management information corresponding to the loaded recording medium can be held in the holding means and also indicates the type of the file management information as information. The file management information recognition information (file system recognition flag) is set, and when an external device communicated via the external interface unit requests recording or reproducing operation on the recording medium, the file management information recognition information is set. In accordance with the setting result, the execution / non-execution of the process according to the request is determined, so that an appropriate operation according to the holding status of the file manager in the holding unit and the type of the file management information is realized. .

When a request for a format operation on a recording medium is made from an external device, the control means determines execution of a format process in accordance with the request, regardless of the setting result of the file management information recognition information. By executing the format operation, it is also possible to format the recording medium from the external device, and it is possible to widen the usage of the system.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram of various disks.

FIG. 2 is an explanatory diagram of an area structure of each disk.

FIG. 3 is an explanatory diagram of a structure of a user area of a partial ROM disk.

FIG. 4 is an explanatory diagram of a structure of a user area of a RAM disk.

FIG. 5 is an explanatory diagram of data of an SFP zone of a disk according to the embodiment;

FIG. 6 is an explanatory diagram of a media type code of a disk according to the embodiment.

FIG. 7 is an explanatory diagram of an example of a system including the disk drive according to the embodiment;

FIG. 8 is a block diagram of a recording / reproducing apparatus according to the embodiment.

FIG. 9 is an explanatory diagram of a software configuration of the recording / reproducing device in the embodiment.

FIG. 10 is a flowchart of a processing example when a disc is inserted in the embodiment.

FIG. 11 is a flowchart of an example of an HFS-compatible process according to the embodiment.

FIG. 12 is an explanatory diagram of file system information of a disk according to the embodiment.

FIG. 13 is an explanatory diagram of a FAT file on a disk in the embodiment.

FIG. 14 is a flowchart of another processing example when a disc is inserted in the embodiment.

FIG. 15 is a flowchart of still another processing example when a disc is inserted in the embodiment.

FIG. 16 is a flowchart of a processing example when a recording / reproducing request is made from a host computer in the embodiment.

FIG. 17 is a flowchart of another processing example when a recording / reproducing request is made from a host computer in the embodiment.

FIG. 18 is a flowchart of a processing example at the time of a recording / reproduction request from an external device in the embodiment.

FIG. 19 is an explanatory diagram of operation timing in the embodiment.

FIG. 20 is a flowchart of mount processing and unmount processing for the disk drive according to the embodiment.

[Explanation of symbols]

1, 1A, 1B disk drive, 3A host computer, 5 PDA device, 6 notebook computer, 7
External equipment 10 controller, 12 encoder / decoder, 14 magnetic head, 15 optical head, 19
DSP, 26 SCSI processing unit 28 CPU, 29 R
AM, 30 flash memory, 31 infrared controller, 32 transmitting / receiving unit, 33 network controller, 34 LAN communication unit

Claims (12)

[Claims] An apparatus according to claim 1, wherein recording or reproduction of data is performed on a loaded recording medium in accordance with a control based on the file management information from a specific host device which holds the file management information on the recording medium. A recording / reproducing apparatus capable of performing, at least in a state in which a recording medium is loaded, holding means capable of retaining file management information relating to the recording medium, and data communication with an external device other than the host device And a recording or reproducing operation on a recording medium using file management information held in the holding means in response to a request from an external device communicated via the external interface means. And a control means capable of executing 2. The recording or reproducing apparatus according to claim 1, wherein the recording medium is irremovably mounted in the recording or reproducing apparatus. 3. The recording or reproducing apparatus according to claim 1, wherein the recording medium is a portable medium, and is loaded when inserted into the recording or reproducing apparatus. 4. The file management information for a loaded recording medium is recorded on the recording medium, and the file management information read from the recording medium is stored in the storage unit. The recording or reproducing apparatus according to claim 1, wherein 5. The recording or reproducing apparatus according to claim 1, wherein a storage unit that stores file management information for one or a plurality of recording media is provided as the holding unit. 6. The control unit does not respond to a recording or reproducing request for a recording medium from the external device at least during a period when recording or reproducing data on a recording medium in response to a request from the host device. In addition, at least during a period in which data recording or reproduction on a recording medium is being performed in response to a request from the external device, the host device is not made to respond to a recording or reproduction request for the recording medium from the host device. The recording or reproducing device according to claim 1. 7. The recording or reproducing apparatus according to claim 1, wherein said external interface means is an infrared signal interface means. 8. The recording or reproducing apparatus according to claim 1, wherein said external interface means is an interface means for a local area network. 9. The recording or reproducing apparatus according to claim 1, wherein said external interface means is an interface means in a wired transmission mode. 10. The recording or reproducing apparatus according to claim 1, wherein said external interface means is an interface means using a wireless transmission mode. 11. The control means can identify whether or not the file management information corresponding to the loaded recording medium can be held in the holding means and can indicate the type of the file management information. File management information recognition information is set as information, and when there is a request for a recording or reproduction operation on a recording medium from an external device communicated via the external interface means, the file management information recognition information 2. The recording or reproducing apparatus according to claim 1, wherein the execution / non-execution of the processing according to the request is determined according to the setting result of (1). 12. The control means, when receiving a format operation request for a recording medium from an external device communicated via the external interface means, regardless of a setting result of the file management information recognition information. 12. The recording or reproducing apparatus according to claim 11, wherein the execution of the format processing according to the request is determined.