Control device and computer-readable recording medium

Abstract

The control device of the present disclosure has: a driver information acquisition section that acquires a string for identifying each of a plurality of accessible drives; a virtual label generation section that, for the string for identifying each of the drives, removes a drive number and generates a virtual volume label obtained by replacing a predetermined prohibited use character that cannot be used as a path name on a file system with a predetermined usable character that can be used as a path name on the file system; a same label determination section that determines whether the same virtual volume label exists in the virtual volume labels; a same label change section that, in order to be able to distinguish between virtual volume labels that have been determined to be the same, appends an identification string containing at least the prohibited use character to the virtual volume labels that have been determined to be the same; a conversion section that performs mutual conversion between a drive number and a virtual volume label based on a string for identifying the drive; and a drive access section that provides an interface for accessing the drive by the virtual volume label using the mutual conversion of the conversion section.

Description

Technical Field

[0001] This disclosure relates to control devices and computer-readable recording media. Background Technology

[0002] Control devices for industrial machinery use an operating system (OS) based on Windows (registered trademark) to implement HMI functions, etc. Within such an OS, drives are managed, each assigned a drive letter to an external device such as a non-volatile memory (SSD), USB storage, CompactFlash (CF card) (registered trademark), or SD card. In reference to this, each drive is represented by a volume label containing its drive letter (e.g., Patent Document 1, etc.).

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2010-198112 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] Displaying drive letters when referring to drives poses a risk of revealing the OS type or folder structure. However, simply displaying fixed names associated with drive letters makes it difficult to identify the correspondence between devices and display names. Furthermore, removing drive letters from volume labels leaves the correspondence between external devices and display names unclear when volume labels are repeated. Moreover, a simple substitution of volume labels and drive letters makes it easy to infer the relationship between drive letters and substitution characters.

[0008] Technical means for solving the problem

[0009] The control device for industrial machinery disclosed herein solves the aforementioned problem by omitting the drive letter and only appending an identification string to the volume label with the same name, thereby generating and displaying a virtual volume label with a uniquely identifiable name.

[0010] Furthermore, one embodiment of this disclosure includes: a drive information acquisition unit that acquires a string for identifying each of a plurality of accessible drives; a virtual label generation unit that removes the drive letter from the string used to identify each of the drives and generates a virtual volume label by replacing predetermined prohibited characters that cannot be used as pathnames on the file system with predetermined usable characters that can be used as pathnames on the file system; a same label determination unit that determines whether the same virtual volume label exists among the virtual volume labels; a same label modification unit that, in order to distinguish virtual volume labels determined to be the same, appends an identification string containing at least the prohibited characters to the virtual volume label; a conversion unit that performs mutual conversion between the drive letter and the virtual volume label based on the string used to identify the drive; and a drive access unit that uses the mutual conversion of the conversion unit to provide an interface for accessing the drive through the virtual volume label. Attached Figure Description

[0011] Figure 1 This is a schematic hardware structure diagram of the control device according to the first embodiment.

[0012] Figure 2 This is a block diagram illustrating the general functions of the control device in the first embodiment.

[0013] Figure 3 This is a schematic diagram illustrating an example of a driver overview display in the context of existing technologies.

[0014] Figure 4 This is a diagram illustrating an example of associating a drive letter with a virtual volume label.

[0015] Figure 5 This is a schematic diagram showing an example of a list of drivers for the control device of the first embodiment. Detailed Implementation

[0016] The following is related to the appendix. Figure 1 The embodiments of this disclosure will be described below. Furthermore, in the following description, structures having the same or similar functions will be labeled with the same reference numerals. Also, repeated descriptions of these structures will sometimes be omitted.

[0017] In this application, "based on XX" means "at least based on XX," but also includes cases based on other elements besides XX. Furthermore, "based on XX" is not limited to directly using XX, but also includes cases based on information obtained through operations or processing of XX. "XX" can be any element (e.g., any information).

[0018] [First Implementation Method]

[0019] Figure 1 This is a schematic hardware structure diagram showing the main parts of a control device according to an embodiment of the present disclosure. The control device 1 of the present disclosure can be installed as a control device for controlling industrial machinery such as machine tools and robots. Hereinafter, the control device 1 for controlling a machine tool will be described as an example, wherein the machine tool performs workpiece machining by controlling the relative position of the tool and the workpiece.

[0020] The CPU 11 of the control device 1 disclosed herein is the processor that controls the entire control device 1. The CPU 11 reads the system program stored in the ROM 12 via the bus 22 and controls the entire control device 1 according to the system program. Temporary calculation data, display data, and various data input from external sources are temporarily stored in the RAM 13.

[0021] The non-volatile memory 14 is configured, for example, a memory backed up by a battery (not shown), an SSD, etc., and maintains its storage state even when the power supply to the control device 1 is disconnected. The non-volatile memory 14 stores control programs and data read from the external device 72 via the interface 15, data and control programs input via the input device 71, and various data obtained from the industrial machinery 3. The control programs and data stored in the non-volatile memory 14 can be expanded in the RAM 13 during execution / use. Furthermore, various system programs, such as known parsing programs, are pre-written into the ROM 12.

[0022] Interface 15 is used to connect the CPU 11 of the control device 1 to external devices 72 such as USB memory, CompactFlash (CF card) (registered trademark), and SD card. It can read control programs and various data used for controlling industrial machinery 3 from the external device 72. Furthermore, it allows the external device 72 to store edited control programs and various data within the control device 1.

[0023] The PLC (Programmable Logic Controller) 16 controls the industrial machine 3 and its control panel and peripheral devices (e.g., tool changers, robot actuators, sensors mounted on the industrial machine 3) via the I / O unit 17 through a timing program built into the control device 1. Additionally, the PLC 16 receives signals from various buttons, dials, switches, peripheral devices, and other industrial machinery operating in cooperation with the industrial machine 3 from the control panel mounted on the main body of the industrial machine 3, performs necessary signal processing, and then transmits the signals to the CPU 11.

[0024] In the display device 70, data read into the memory, as well as data obtained as a result of executing control programs or system programs, are output and displayed via interface 18. Additionally, the input device 71, consisting of pointing devices such as a keyboard, mouse, and touch panel, transmits instructions and data based on the operator's actions to the CPU 11 via interface 19. The display device 70 and input device 71 may also be, for example, a hanging console or a tablet terminal.

[0025] Interface 20 is used to connect the CPU 11 of the control device 1 to a wired or wireless network 5. Network 5 can communicate using technologies such as RS-485 serial communication, Ethernet, optical communication, wireless LAN, Wi-Fi, and Bluetooth. Other industrial machinery 4, fog computers 6, cloud servers 7, and PCs (Personal Computers) 8 are connected to network 5, exchanging data with the control device 1.

[0026] The axis control circuit 30, used to control the control axes of the industrial machinery 3, receives position commands for the control axes from the CPU 11 and outputs the commands for those control axes to the servo amplifier 40. The servo amplifier 40 receives these commands to drive the servo motors 50 of the control axes, causing the various parts of the industrial machinery 3 to move along their respective axes. Each servo motor 50 has a built-in position detector, and feeds back position feedback signals from these detectors to the axis control circuit 30. The axis control circuit 30 performs feedback control of the servo motors 50 based on these position feedback signals. Furthermore, in... Figure 1 In the hardware structure diagram, one axis control circuit 30, one servo amplifier 40, and one servo motor 50 are shown, but in reality, they are prepared according to the number of control axes of the industrial machine 3 that is being controlled. For example, in the case of controlling a typical machine tool with three linear axes and two rotary axes, five sets of axis control circuits 30, servo amplifiers 40, and servo motors 50 are prepared to move the spindle on which the tool is mounted and the workpiece relative to each other in the directions of the three linear axes and the two rotary axes (X-axis, Y-axis, Z-axis, A-axis, and C-axis).

[0027] The spindle control circuit 60 receives a spindle rotation command and outputs a spindle speed signal to the spindle amplifier 61. The spindle amplifier 61 receives this spindle speed signal and causes the spindle motor 62 of the industrial machine 3 to rotate at the indicated speed, thereby driving the spindle. A position encoder 63 is connected to the spindle motor 62. The position encoder 63 outputs feedback pulses synchronously with the spindle rotation, and these feedback pulses are read by the CPU 11.

[0028] Figure 2The functions of the control device 1 according to the first embodiment of this disclosure are shown in a schematic block diagram. The functions of the control device 1 according to this embodiment are illustrated by... Figure 1 The control device 1 shown is equipped with a CPU 11 that executes system programs to control the actions of each part of the control device 1.

[0029] The control device 1 of this embodiment includes a driver information acquisition unit 100, a virtual tag generation unit 110, a same tag determination unit 120, a same tag change unit 130, a conversion unit 140, and a driver access unit 150.

[0030] The drive information acquisition unit 100 acquires a string for identifying each of the multiple drives accessible in the control device 1. Drives accessible in the control device 1 include, for example, an SSD used as non-volatile memory 14, a USB memory connected as an external device 72, a CompactFlash (CF card) (registered trademark), an SD card, etc. These drives are managed by assigning drive letters to each drive using OS functions. Drive letters are, for example, any letter from A to Z. Drive letters are used by appending a colon (:) to these letters. A volume label is assigned to each drive. The volume label is a name that the user can freely add to identify the drive. For each drive, the drive information acquisition unit 100 acquires a string that combines the drive letter and the volume label string as a string for identifying the drive. For example, for a drive with a drive letter of "E" and a volume label of "SD", the drive information acquisition unit 100 acquires the string "SD (E:)" as a string for identifying the drive. Such a string for identifying the drive can be acquired using OS system calls, etc. The driver information acquisition unit 100 outputs the string used to identify the driver obtained for each driver to the virtual tag generation unit 110.

[0031] The virtual label generation unit 110 removes the drive letter from the string used to identify each drive and replaces predetermined prohibited characters that cannot be used as pathnames on the file system with predetermined usable characters that can be used as pathnames on the file system, thereby generating virtual volume labels. Virtual volume labels are used to access each drive and do not actually assign a drive name. The prohibited characters that cannot be used on the file system vary depending on the file system. In Windows NTSF, for example, a half-width " "?", "?" "", "", ", ", " Characters such as '|' and ' " are prohibited. When such characters are included in a string defining a drive, the virtual label generation unit 110 replaces these characters with usable characters (e.g., whitespace characters, hyphens, etc.) that can be used as pathnames on the file system. The usable character for this replacement can be predefined individually for each prohibited character, or all prohibited characters can be converted to a single usable character. An empty string (a string of length 0) can also be used as a usable character. In this case, the prohibited character is removed from the virtual volume label. The virtual label generation unit 110 outputs the generated virtual volume label to the same label determination unit 120.

[0032] The same label determination unit 120 determines whether the same virtual volume label exists among the multiple virtual volume labels generated by the virtual label generation unit 110. The same label determination unit 120 determines whether the same virtual volume label exists among the multiple virtual volume labels by simply comparing the strings of the virtual volume labels with each other. The same label determination unit 120 outputs the determination result to the same label modification unit 130.

[0033] The same label modification unit 130 appends an identification string containing at least prohibited characters of the file system to virtual volume labels determined to be the same by the same label determination unit 120, enabling the identification of these identified virtual volume labels. The identification string must be different for each identified virtual volume label. Therefore, it is preferable to include appended serial numbers such as 1, 2, 3, etc., and English letters such as A, B, C, etc. The prohibited characters in the identification string can be any characters. For example, the same label modification unit 130 can append strings such as ":1", ":2", ":3", etc., to identified virtual volume labels. The same label modification unit 130 does not need to apply any changes to virtual volume labels that are not identified as the same. The same label modification unit 130 outputs both modified and unmodified virtual volume labels to the conversion unit 140.

[0034] The conversion unit 140 stores the virtual volume label input from the same label change unit 130 in association with the drive letter of the drive to which the virtual volume label relates. Then, when there is a query for the virtual volume label, the drive letter associated with it is output as a response to the query. In addition, when there is a query for the drive letter, the virtual volume label associated with it is output.

[0035] The drive access unit 150 provides an interface for users to access individual drives via virtual volume labels. The drive access unit 150 is used, for example, when displaying a drive list to the user or accessing files on individual drives via the drive list. For example, when requested to obtain a drive list, the drive access unit 150 obtains the drive letters for each of the multiple drives accessible in the control device 1. Then, it queries the conversion unit 140 for each drive letter to obtain the virtual volume label for each drive. Then, it responds with the obtained list of virtual volume labels. Additionally, when requested to access a path containing a virtual volume label, the drive access unit 150 queries the conversion unit 140 to obtain the drive letter associated with that virtual volume label. Then, it converts the virtual volume label contained in the path to the access destination into a drive letter. Then, it accesses the converted path and returns the result as a response to the request source. The drive access unit 150 may also provide an API (Application Programming Interface) for other functions. Furthermore, the drive access unit 150 may also provide a user-friendly interface.

[0036] use Figures 3-5 The operation of the control device 1 in this embodiment will be explained.

[0037] Figure 3 This is a schematic diagram illustrating an example of a driver overview display using existing technology. Figure 3 In this example, five drives, C through H, are connected to the control unit. Drive C is, for example, an SSD volume, labeled with the string "FA_SYS". Drive E is, for example, a CompactFlash (CF card) volume (registered trademark), labeled with the string "CF".

[0038] In this embodiment, when the control device 1 has this driver structure, firstly, the driver information acquisition unit 100 acquires strings used to determine each driver. Figure 3 In that drive configuration, the string that identifies drive C is “FA_SYS (C:)”, the string that identifies drive D is “FA_DATA (D:)”, the string that identifies drive E is “CF (E:)”, the string that identifies drive F is “CF (F:)”, the string that identifies drive G is “CF:2 (G:)”, and the string that identifies drive H is “HMI_DATA (H:)”.

[0039] The virtual label generation unit 110 removes the portion equivalent to the drive letter from the string used to identify these drives. Furthermore, strings prohibited from being used as pathnames are deleted. Figure 3In the example, the volume name of the CompactFlash (CF card) (registered trademark) connected to the G drive contains a colon (:) as a prohibited character. Therefore, the virtual label generation unit 110 replaces this character with a character that can be used as a path name. For example, if it is replaced with a hyphen (-) as a usable character, the virtual volume label of the G drive becomes "CF-2".

[0040] The same label determination unit 120 determines whether the same label exists in the virtual volume labels created in this way. Figure 3 In the example, both the virtual volume labels for drive E and drive F are "CF". Therefore, the same label determination unit 120 outputs the determination result that the virtual volume labels for drive E and drive F are the same virtual volume label.

[0041] The same label change unit 130 adds an identification string to virtual volume labels that are determined to be the same. For example, by adding a colon (":") as a prohibited character and an appended number, the virtual volume label for drive E becomes "CF:1". Similarly, the virtual volume label for drive F becomes "CF:2".

[0042] The conversion unit 140 stores the virtual volume label generated in this way in association with the drive letter. Figure 4 This is a diagram illustrating an example of associating a drive letter with a virtual volume label. Figure 4 The example shown is that the control device 1 in this embodiment is Figure 3 In the case of the illustrated drive structure, the conversion unit 140 stores the association between the drive letter and the virtual volume label.

[0043] Figure 5 This is a schematic diagram showing an example of a list of drivers in the control device 1 of this embodiment. Figure 5 An example is that the drive structure of the control device 1 in this embodiment is configured to be similar to... Figure 3 Examples of the same driving structure. For example... Figure 5 As illustrated, the virtual volume labels processed in the control device 1 of this embodiment do not contain drive letters, thus making it difficult for users to deduce the type of OS or folder structure. Furthermore, the virtual volume labels associated with each drive are different for each drive, allowing for unique identification. This effect is achieved by generating virtual volume labels that temporarily do not contain prohibited characters in the virtual label generation unit 110, and then appending an identification string containing prohibited characters in the same label changing unit.

[0044] The control device 1 of this embodiment, which has the above-described structure, hides the drive letter and can access each drive through virtual volume labels that are easy for the user to understand, thereby hiding the drive structure of the OS and improving operability.

[0045] As a variation of the control device 1 in this embodiment, when an identification string is attached to a virtual volume label, the user can be asked whether to change the volume label set for the actual drive to the virtual volume label with the attached identification string. Then, upon receiving a response from the user indicating their intention to change, the volume label set for the actual drive is changed to the virtual volume label. By setting up such a structure, external devices 72 that are connected to or detached from the control device 1 can be managed by being set to volume labels with identification strings, thus making it easier for the user to identify the external devices 72.

[0046] [Second Implementation]

[0047] The control device according to the second embodiment of this disclosure will be described below.

[0048] The control device 1 of this embodiment has the same hardware structure as the control device 1 of the first embodiment. Furthermore, the control device 1 of this embodiment has the same functions as the control device 1 of the first embodiment, and is used via… Figure 1 The control device 1 shown has a CPU 11 that executes system programs to control the actions of each part of the control device 1.

[0049] The control device 1 of the second embodiment of this disclosure is similar to the control device 1 of the first embodiment, and includes a driver information acquisition unit 100, a virtual tag generation unit 110, a same tag determination unit 120, a same tag change unit 130, a conversion unit 140, and a driver access unit 150.

[0050] In the control device 1 of this embodiment, the functions of the virtual tag generation unit 110, the same tag determination unit 120, the same tag change unit 130, the conversion unit 140, and the driver access unit 150 are the same as those of the first embodiment.

[0051] In this embodiment, the driver information acquisition unit 100 filters out (removes) system-specific drivers such as the OS from among the multiple drives accessible in the control device 1, and obtains a string used to identify the driver. Therefore, the driver information acquisition unit 100 only outputs information about drivers that can be accessed without issue by the user to the virtual tag generation unit 110. As a result, the dedicated areas used by the OS can be hidden from the user.

[0052] The control device 1 of this embodiment, equipped with the above-described structure, hides drive letters and allows access to each drive via virtual volume labels that are easily understood by the user. This hides the OS's drive structure and improves operability. In particular, drives that are private areas of the OS are not displayed to the user, enabling more reliable hiding.

[0053] [Third Implementation Method]

[0054] The control device of the third embodiment of this disclosure will now be described.

[0055] The control device 1 of this embodiment has the same hardware structure as the control device 1 of the first embodiment. Furthermore, the control device 1 of this embodiment has the same functions as the control device 1 of the first embodiment, and is used via… Figure 1 The control device 1 shown has a CPU 11 that executes system programs to control the actions of each part of the control device 1.

[0056] The control device 1 of the third embodiment of this disclosure is similar to the control device 1 of the first embodiment, and includes a driver information acquisition unit 100, a virtual tag generation unit 110, a same tag determination unit 120, a same tag change unit 130, a conversion unit 140, and a driver access unit 150.

[0057] In the control device 1 of this embodiment, the functions of the virtual tag generation unit 110, the same tag determination unit 120, the same tag change unit 130, the conversion unit 140, and the driver access unit 150 are the same as those of the first embodiment.

[0058] In this embodiment, the drive information acquisition unit 100 filters out (removes) internal drives such as SSDs built into the control device 1 from among multiple drives accessible in the control device 1 to obtain a string for identifying the drive. Examples of drives other than these internal drives include the drive for external device 72 and network drives. At this time, the drive information acquisition unit 100 can also confirm the removability attribute and file system type of each drive. Then, it can obtain a string only for identifying drives with removability attributes, or it can obtain a string only for identifying drives with specific file systems such as FAT and FAT32. In addition, drives with pre-set specific drive letters can also be filtered out (removed). As a result, the drive information acquisition unit 100 outputs only the information for identifying the drive for external device 72 and network drives to the virtual tag generation unit 110. As a result, it is possible to access areas stored in the non-volatile memory 14 or the like within the control device 1.

[0059] The control device 1 of this embodiment, equipped with the above-described structure, hides drive letters and allows access to each drive via virtual volume labels that are easily understood by the user. This hides the OS's drive structure and improves operability. In particular, the internal storage area of ​​the control device 1 is not displayed to the user, enabling more reliable hiding.

[0060] The embodiments of this disclosure have been described in detail above, but this disclosure is not limited to the various embodiments described above. Various additions, substitutions, modifications, and partial deletions can be made to these embodiments without departing from the spirit of the invention, or without departing from the idea and spirit of this disclosure derived from the content described in the patent protection scope and its equivalents. For example, in the embodiments described above, the order of each action and the order of each process are shown as an example and are not limited thereto. The same applies to the use of numerical values ​​or mathematical formulas in the description of the embodiments described above.

[0061] The following are notes regarding embodiments of this disclosure.

[0062] (Note 1)

[0063] One aspect of the control device (1) disclosed herein includes: a drive information acquisition unit (100) that acquires a string for identifying each of a plurality of accessible drives; a virtual label generation unit (110) that removes the drive letter from the string used to identify each of the drives and generates a virtual volume label by replacing a predetermined prohibited character that cannot be used as a pathname on the file system with a predetermined usable character that can be used as a pathname on the file system; a same label determination unit (120) that determines whether the same virtual volume label exists among the virtual volume labels; a same label changing unit (130) that, in order to distinguish the virtual volume labels determined to be the same, attaches an identification string containing at least the prohibited character to the virtual volume label; a conversion unit (140) that performs mutual conversion between the drive letter and the virtual volume label based on the string used to identify the drive; and a drive access unit (150) that uses the mutual conversion of the conversion unit (140) to provide an interface for accessing the drive through the virtual volume label.

[0064] (Note 2)

[0065] The driver information acquisition unit (100) of the control device (1) of other embodiments of this disclosure filters out system-specific drivers and acquires a string for determining the driver.

[0066] (Note 3)

[0067] The driver information acquisition unit (100) of the control device (1) of other embodiments of the present disclosure filters out internal drivers and acquires a string for determining the driver.

[0068] (Note 4)

[0069] The drive information acquisition unit (100) of the control device (1) of other embodiments of the present disclosure filters out drives based on at least one of the presence or absence of the drive's removability attribute, the type of file system, and a specific drive letter, and obtains a string for identifying the drive.

[0070] (Note 5)

[0071] In other embodiments of the present disclosure, the control device (1) queries whether to change the actual drive's volume label when the identification string is attached to the virtual volume label.

[0072] (Note 6)

[0073] One aspect of this disclosure is a computer-readable recording medium containing a program that enables a computer to function as the following units: a drive information acquisition unit (100) that acquires a string for identifying each of a plurality of accessible drives; a virtual label generation unit (110) that removes the drive letter from the string used to identify each drive and generates a virtual volume label by replacing predetermined prohibited characters that cannot be used as pathnames on the file system with predetermined usable characters that can be used as pathnames on the file system; a same label determination unit (120) that determines whether the same virtual volume label exists among the virtual volume labels; a same label modification unit (130) that, in order to distinguish virtual volume labels determined to be the same, appends an identification string containing at least the prohibited characters to the virtual volume label; a conversion unit (140) that performs mutual conversion between the drive letter and the virtual volume label based on the string used to identify the drive; and a drive access unit (150) that uses the mutual conversion of the conversion unit (140) to provide an interface for accessing the drive through the virtual volume label.

[0074] Explanation of reference numerals in the attached figures

[0075] 1 Control device

[0076] 3, 4 Industrial Machinery

[0077] 5 Networks

[0078] 6 Fog Computer

[0079] 7 cloud servers

[0080] 8 PC

[0081] 11 CPU

[0082] 12 ROM

[0083] 13 RAM

[0084] 14 Non-volatile memory

[0085] Interfaces 15, 18, 19, and 20

[0086] 16 PLC

[0087] 17 I / O Units

[0088] 22 bus

[0089] 30-axis control circuit

[0090] 40 servo amplifier

[0091] 50 servo motors

[0092] 60 spindle control circuit

[0093] 61 spindle amplifier

[0094] 62 spindle motor

[0095] 63-position encoder

[0096] 70 display devices

[0097] 71 Input Device

[0098] 72 External Devices

[0099] 100 Drive Information Acquisition Department

[0100] 110 Virtual Tag Generation Department

[0101] 120 Same Label Judgment Department

[0102] 130 Same Label Change Department

[0103] 140 conversion unit

[0104] 150 Drive Access Department.

Claims

1. A control device, characterized in that, have: The drive information acquisition unit acquires strings used to identify each of the multiple accessible drives. The virtual label generation unit removes the drive letter from the string used to identify each of the drives and generates a virtual volume label by replacing predetermined prohibited characters that cannot be used as pathnames on the file system with predetermined usable characters that can be used as pathnames on the file system. The same label determination unit determines whether the same virtual volume label exists among the virtual volume labels; In order to distinguish between virtual volume labels that are determined to be the same, the same label change unit attaches an identification string containing at least the prohibited characters to the virtual volume label. A conversion unit that performs mutual conversion between the drive letter and a virtual volume label based on a string used to identify the drive; as well as The drive access unit, which uses the mutual conversion of the conversion unit, provides an interface for accessing the drive through the virtual volume label.

2. The control device according to claim 1, characterized in that, The driver information acquisition unit filters out system-specific drivers and obtains the string used to identify the driver.

3. The control device according to claim 1, characterized in that, The driver information acquisition unit filters out internal drivers and obtains a string used to identify the driver.

4. The control device according to claim 1, characterized in that, The drive information acquisition unit filters drives based on at least one of the following: the presence or absence of the drive's removability attribute, the type of file system, and a specific drive letter, and obtains a string used to identify the drive.

5. The control device according to claim 1, characterized in that, When the identification string is attached to the virtual volume label, the system prompts whether to change the actual drive's volume label.

6. A computer-readable recording medium containing a program, characterized in that, The program causes the computer to perform the following actions: The drive information acquisition unit acquires strings used to identify each of the multiple accessible drives. The virtual label generation unit removes the drive letter from the string used to identify each of the drives and generates a virtual volume label by replacing predetermined prohibited characters that cannot be used as pathnames on the file system with predetermined usable characters that can be used as pathnames on the file system. The same label determination unit determines whether the same virtual volume label exists among the virtual volume labels; In order to distinguish between virtual volume labels that are determined to be the same, the same label change unit attaches an identification string containing at least the prohibited characters to the virtual volume label. A conversion unit that performs mutual conversion between the drive letter and a virtual volume label based on a string used to identify the drive; as well as The drive access unit, which uses the mutual conversion of the conversion unit, provides an interface for accessing the drive through the virtual volume label.

Images