JPH07200491A - Virtual drive name setting system - Google Patents

Abstract

PURPOSE:To calculate and display a virtual drive name by referring to local drive constitution information on a client, to set the virtual drive name by automatic input, and to actualize the use of the virtual drive by the client by activating a network OS without being aware of local drive constitution. CONSTITUTION:Each client 11 is provided with the local drive constitution information 15 where resource names are registered corresponding to drive names and a drive name calculating process 16 which calculates the virtual drive name by referring to the local drive constitution information 15; and the system is provided with a server 3 which receives the virtual drive name, calculated by the drive name calculating process 16, through a network at login time and registers it in a virtual drive name table 33 and each client 11 accesses a resource of the server 31 through the network by using the drive name and performs processes.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a virtual drive name setting system for setting / displaying a virtual drive name.

[0002]

2. Description of the Related Art A network OS has a concept of a virtual drive so that a client as a personal terminal can use the resources of a server having a large-capacity storage device (drive).

A client in a stand-alone state performs business processing by using a local drive which is a unique resource. When the client boots the network OS, the drive (virtual drive) existing in the server can be used as if it were a local drive via the network. For example, when the client has local drives A to E, when the network OS is started, the virtual drives F, G, H, ... Which the server has can be accessed by the same operation as the local drive.

At this time, the virtual drive name must be a drive name that is not used by the local drive. Therefore, in order to notify the network OS of the virtual drive name used by the client, the local drive owned by the client itself is used. Information needs to be entered into the network OS.

Conventionally, at the time of login, the user manually inputs the first virtual drive name (the drive name next to the last local drive name) to notify the network OS.

[0006]

Conventionally, as described above, when the network OS logs in, the final local
Since the user had to manually enter the drive name next to the drive name as the virtual drive name,
There was a problem that manual input was forced. Also, the local drive letter is A for some clients.
The local drive letters of .about.G exist, the local drive letters of A to E exist in other clients, and so on. Therefore, in the client set by another person, it is necessary to check the environment of the local drive before inputting the virtual drive name, and then input the virtual drive name, which is a problem.

As one solution, a method of programming a preset virtual drive name so that a specific business program is automatically input at the time of startup can be considered. In this method, a local drive of a client is used. There is a problem in that the virtual drive name must be changed every time the environment is changed.

The present invention solves these problems by
The local drive configuration information of the client is referenced to calculate and display the virtual drive name, or the virtual drive name is automatically entered to set the virtual drive name.
The purpose is to start the network OS and realize the use of the virtual drive without being aware of the drive configuration.

[0009]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the client 11 accesses a drive (local drive, virtual drive) to perform various processes, and is composed of the local drive configuration information 15 and the drive name calculation process 16.

The local drive configuration information 15 is one in which a resource name to be accessed is registered in advance in association with a drive name. The drive name calculation process 16 refers to the local drive configuration information 15 and calculates the drive name next to the final drive name as a virtual drive name.

The server 31 manages the virtual drive used by each client 11 and comprises a virtual drive name table 33 and a virtual drive 36.

The virtual drive name table 33 is a table in which the virtual drive 36 is registered in association with the virtual drive name of each client 11. The virtual drive 36 is a resource on the server 31 used by the client 11.

[0013]

According to the present invention, as shown in FIG.
At the time of login of 1, etc., the drive name calculation process 16 refers to the local drive configuration information 15 and calculates the drive name next to the final drive name as a virtual drive name,
The server 31 receiving the calculated virtual drive name via the network registers the resource name to be accessed in association with the virtual drive name in the virtual drive name table 33, and the client 11 uses the drive name to access the network. The resources of the server 31 are accessed through the processing.

Further, in response to the start instruction of each client 11 or the display instruction of the virtual drive name in each client 11, the drive name calculation process 16 refers to the local drive configuration information 15 and drives next to the final drive name. The name is calculated as a virtual drive name, and the calculated virtual drive name is displayed.

Therefore, by referring to the local drive configuration information 15 of the client 11 and calculating and displaying the virtual drive name or automatically inputting and setting the virtual drive name in the virtual drive name table 33, the client 11 It becomes possible for 11 to use the virtual drive 36 of the server 31 without being aware of the local drive configuration.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 1 shows an overall block diagram of the present invention.
In FIG. 1, the client 11 is connected to the server 31 via the network, and its own local drive 22
And a virtual drive 36 of the server 31 to perform various business processes.
2, OS 13, login process 14, local drive configuration information 15, drive name calculation process 16, buffer 17, final drive setting information 18, business program 19, and the like.

The network OS 12 is an OS (operating system) for using the virtual drive 36 of the server 31 via the network. OS13
Is an operating system, which controls the entire client 11, for example, MS-D.
OS and the like.

The login process 14 is executed by the client 1
1 performs various processes for using the virtual drive 36 of the server 31. Local drive configuration information 1
Reference numeral 5 is a resource (disk device, floppy disk device, RAM disk device, etc.) registered (defined) in association with a drive name.

The drive name calculation process 16 refers to the local drive configuration information 15 and calculates the drive name next to the final local drive name to obtain the virtual drive name.

The buffer 17 temporarily stores various kinds of information. Here, the virtual drive name calculated by the drive name calculation process 16 is set.

The final drive setting information 18 is information in which the final drive name or the like found by referring to the local drive configuration information 15 is set. The business program 19 accesses the local drive 22 and the virtual drive 36 to perform various business processes.

The keyboard 20 is used to input various data and instructions. The display 21 displays various data. The local drive 22 is a resource (resource such as a disk device, a floppy disk device, a RAM disk) provided in the client 11.

The server 31 is connected to a plurality of clients 11 via a network and uses the virtual drive 36 in this case. The server 31 is composed of a network OS 32 and a virtual drive name table 33. Is.

The network OS 32 is for exchanging various data in collaboration with the network OS on the client 11 side via the network. Here, each client 11 uses the virtual drive 36 in the server 31. It is for doing.

The virtual drive name table 33 is a table in which the virtual drive 36 is registered in association with the virtual drive name notified from each client 11 (FIG. 4, FIG.
(See FIG. 5).

The keyboard 34 is used to input various data and instructions. The display 35 displays various data. The virtual drive 36 is a virtual drive to be accessed by the client 11, and is a disk device, a floppy disk device, a RAM disk device, or the like.

Next, the creation of the local drive configuration information 15 in the client 11 will be described in detail with reference to FIGS. 2 and 3. FIG. 2 shows a flowchart for setting a local drive according to the present invention.

In FIG. 2, S1 sets the local drive used for system setting and the LAST drive. Here, for example, the following settings described on the right side are set.

Local drive name: AE (drive name A to drive name E) LAST drive setting: final drive name E With the above, for example, the following settings are made as shown in FIG.

Drive Name Attribute A disk 1 (disk device 1) B disk 2 C disk 3 D floppy disk (floppy disk device) E RAM disk (RAM disk device) F NULL Here, drive names are A, B, and C. , D, E in this order. Last drive name (LAST drive name)
Is the drive name “E” here.

Next, referring to FIGS. 4 and 5, the server 31
The creation of the virtual drive name table 33 in FIG. FIG. 4 shows a setting flowchart of the virtual drive of the server of the present invention.

In FIG. 4, S11 sets the virtual drive used when setting the system of the server. This is because the virtual drive used when the system of the server 31 is set is, for example, the virtual drive name table 3 in FIG.
As shown in 3, virtual drives are set as ## 1, ## 2, and ## 3.

FIG. 5A shows an example of the virtual drive name table of the present invention. This is the virtual drive 36 of the server 31 sequentially from the virtual drive name (the drive name next to the last local drive name) notified from the client 11.
It is registered in association with. Here, since the virtual drive name "F" is notified from the client # 1 and the virtual drive name "D" is notified from the client # 2, the virtual drive name table 33 is set as shown below.

Client # 1 Client # 2 Virtual Drive F D ## 1 G E ## 2 H F ## 3 FIG. 5B shows an example of the virtual drive name table of the present invention. Here, the virtual drive name “F” is notified from the client # 1, the virtual drive name “D” is notified from the client # 2, and the client # 2 is set to be unusable for the virtual drive name “## 3”. Therefore, it is set in the virtual drive name table 33 as shown below.

Client # 1 Client # 2 Virtual Drive F D ## 1 G ## 2 H − ## 3 Here, − indicates that the virtual drive cannot be used.

Next, the operation of the configuration of FIG. 1 will be described in detail in the order shown in the flowchart of FIG. In FIG. 6, in S21, a connection command is input from the client.

In step S22, the connection is established (client-server). These S21 and S22 are executed by the client 11
To connect to the server 31 via the network.

In step S23, a network login input instruction is given. A step S24 decides whether or not the LAST drive name is set. This is the final drive setting information 1 in Figure 1.
It is determined whether the LAST drive name (final drive name) is set in 8. In the case of YES, since the LAST drive name has been set, the drive name next to the set LAST drive name is set in the buffer 17 as a virtual drive name in S25, and the process proceeds to S26. on the other hand,
In the case of NO in S24, since the LAST drive name has not been set, the local drive configuration information 15 is referred to in S29, and in S30, the extent to which the drive name is set is calculated. For example, in the case of the local drive configuration information 15 in FIG. 3, it is calculated that the drive name “E” is set. Then, in S25, the drive name next to the set final drive name is set in the buffer 17 as a virtual drive name.

In step S26, the top virtual drive name is input. In S27, the login process is executed. As a result, the client 11 can access the server 3 via the network.
The processing required to use the virtual drive 36 of No. 1 is executed.

In step S28, the operation is started. This allows
The business program 19 of the client 11 can access the resource by the drive name to perform business processing without being aware of the distinction between the virtual drive 36 of the server 31 via the local drive 22 and the network.

FIG. 7 shows an operation explanatory diagram of the present invention. This shows how the clients # 1 and # 2 notify the virtual drive name to the server 31 and use the virtual drive 36.

The client # 1 sets five drive names A, B, C, D and E in the local drive 22. The final drive name is calculated as the drive name "E". -The server 31 continues the virtual drive name "F" at the head of the client # 1, then "G", "H", and the virtual drives ## 1, ## 2, ## 3 in the server 31. Are sequentially associated as indicated by arrows.

Similarly, the client # 2 sets three drive names A, B and C in the local drive 22. The final drive name is
The drive name is calculated as "C".

The server 31 instructs the client # 2 to start the virtual drive name "D", then "E", "F"
Then, virtual drives ## 1, ## 2 in the server 31,
## 3 are sequentially associated as indicated by arrows.

As described above, the clients # 1 and # 2
Allows you to set the virtual drive name after the local drive name. FIG. 8 shows an operation explanatory diagram (at the time of inquiry) of the present invention. This is an operation explanatory diagram when a virtual drive name is displayed in response to a client start instruction or a virtual drive name inquiry.

In FIG. 8, S31 issues a client start instruction or a virtual drive name inquiry instruction.
In S32, it is determined whether the LAST drive name is set. This is LA in the final drive setting information 18 of FIG.
It is determined whether the ST drive name (final drive name) is set. In the case of YES, since the LAST drive name has been set, the LAS set in S33 is set.
The drive name next to the T drive name is set in the buffer 17 as a virtual drive name, and the drive name (virtual drive name) is displayed and notified in S34. On the other hand, in the case of NO in S32, since the LAST drive name has not been set, the local drive configuration information 15 is referenced in S35,
In S36, it is calculated to what extent the drive name is set. For example, in the case of the local drive configuration information 15 in FIG. 3, it is calculated that the drive name “E” is set. Then, in S33, the drive name next to the final drive name that has been set is set as the virtual drive name in the buffer 1
7, and the drive name (virtual drive name) is displayed and notified in S34.

As described above, the LAS is responded to in response to the client start instruction or the inquiry about the virtual drive name.
If the T drive name is set, the next drive name (virtual drive name) is displayed and notified. On the other hand, if it is not set, the local drive configuration information 15
To find the final drive letter and display the next drive letter (virtual drive letter) to inform you.

[0049]

As described above, according to the present invention,
Since the virtual drive name is calculated and displayed by referring to the local drive configuration information 15 of the client 11 or the virtual drive name is automatically input and set in the virtual drive name table 33, the client is used. Can use the virtual drive in the server 31 via the network without paying attention to the local drive configuration, and responds to the client start instruction or the virtual drive name inquiry, the virtual drive name (final local The drive name next to the drive name) can be displayed to notify the operator who uses the client 11.

[Brief description of drawings]

FIG. 1 is an overall block diagram of the present invention.

FIG. 2 is a flowchart for setting a local drive according to the present invention.

FIG. 3 is an example of local drive configuration information of the present invention.

FIG. 4 is a flowchart for setting a virtual drive of the server of the present invention.

FIG. 5 is an example of a virtual drive name table of the present invention.

FIG. 6 is an operation explanatory view (at the time of login) of the present invention.

FIG. 7 is an operation explanatory diagram of the present invention.

FIG. 8 is a diagram for explaining the operation of the present invention (when inquiring).

[Explanation of symbols]

 11: Client 12: Network OS 13: OS 14: Login process 15: Local drive configuration information 16: Drive calculation process 17: Buffer 18: Final drive setting information 19: Business program 20: Keyboard 21: Display 22: Local drive 31: Server 32: Network OS 33: Virtual drive name table 34: Keyboard 35: Display 36: Virtual drive

Claims (2)

[Claims] 1. Local drive configuration information (15) for pre-registering a resource name to be accessed in association with a drive name
And a drive name calculation process (16) for calculating the drive name next to the final drive name as a virtual drive name by referring to this local drive configuration information (15), and each client (11) At the time of login in 11), the virtual drive name calculated by the drive name calculation process (16) is received via the network, and the resource name to be accessed in association with the received virtual drive name is stored in the virtual drive name table (33). ), And each client (11) is configured to access the resource of the server (31) through the network using the drive name to perform processing. Drive name setting system. 2. The drive name calculation process (16) in response to an instruction to start each client (11) or an instruction to inquire a virtual drive name from each client (11).
A virtual drive name setting system characterized in that the virtual drive name calculated by is displayed on the screen.