JP5040694B2 - Communication support program and communication support method - Google Patents

Description

  The present invention relates to a communication support program and a communication support method, and in particular, a communication support program and a communication support method that support communication when there is no network driver corresponding to a communication device.

  In recent years, a personal computer system environment (such as an OS image) is normally copied to a portable device such as a USB memory (portable device) and carried on the other computer by USB booting. Can be reproduced.

FIG. 1 is a diagram showing how the system environment is carried by a portable device. In the figure, an OS 411 (OS image) of a normally used PC is recorded in the portable device 401. In this state, the portable device 401 is connected to the PCs 501, 502, 503, or 504 by USB and the USB boot is executed, so that the OS 411 can be loaded in each PC and the system environment that is normally used can be reproduced. .
JP 2007-293780 A

  In FIG. 1, a PC 501 includes a communication device A, a PC 502 includes a communication device B, a PC 503 includes a communication device C, and a communication device D 504 includes a communication device D. The communication device is hardware for realizing wired or wireless communication, such as a network card.

  Normally, in order to make a communication device connected to a PC available, driver software (network driver) corresponding to the communication device is required. In the portable device 401, driver A, driver B, and driver C are recorded as such driver software. Driver A corresponds to communication device A, driver B corresponds to communication device B, and driver C corresponds to communication device C.

  Assume that the portable device 401 is connected to the PC 501 in such a state, for example. FIG. 2 is a diagram illustrating an example in which the environment of the portable device 401 is loaded on the PC 501. In this case, the environment loaded into the memory area of the PC 501 includes a driver A corresponding to the communication device A included in the PC 501. Therefore, the PC 501 can perform communication using the driver A and the communication device A.

  On the other hand, FIG. 3 is a diagram illustrating an example in which the environment of the portable device 401 is loaded on the PC 504. In this case, the environment loaded into the memory area of the PC 504 does not include driver software (for example, driver D) corresponding to the communication device D included in the PC 504. Therefore, the PC 504 cannot use the communication device D (cannot perform communication). In addition, since the communication cannot be performed, the driver D cannot be downloaded via the network.

  Note that portable devices have capacity limitations, and it is not realistic to record driver software corresponding to all hardware in advance.

  The present invention has been made in view of the above points, and is a communication support program and a communication support method that can appropriately support the construction of a communicable state in an environment where there is no network driver corresponding to the communication device. The purpose is to provide.

  In order to solve the above problems, the present invention provides a communication support program stored in a portable device including a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded. A device detection procedure for detecting a second communication device included in the computer to a computer to which the portable device is connected, and a network driver corresponding to the detected second communication device are the computer and the When the portable device does not exist, a driver acquisition procedure for acquiring the network driver by network communication using the first communication device is executed.

  Such a communication support program can appropriately support the establishment of a communicable state in an environment where there is no network driver corresponding to the communication device.

  ADVANTAGE OF THE INVENTION According to this invention, the communication assistance program and communication assistance method which can support appropriately the construction | assembly of the state which can communicate in the environment where the network driver corresponding to a communication device does not exist can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 4 is a diagram for explaining an apparatus used in the embodiment of the present invention. In the figure, a portable device 10, a PC (Personal Computer) 20, and a server 30 are shown.

  The portable device 10 is a portable or portable device for carrying a system environment in a normally used PC or the like, and includes hardware such as a recording medium 11, a USB interface 12, a USB hub 13, and a communication device Z15. . The system environment carried by the portable device 10 is hereinafter referred to as “portable environment”.

  The USB interface 12 is a connector for connecting a USB cable, and is used as an interface for connecting to the PC 20 in this embodiment. The USB hub 13 branches the USB connection path between the recording medium 11 and the communication device Z15. The communication device Z15 may be a detachable device such as a network card that is required for wireless or wired communication, and may be a fixed type incorporated in the apparatus in advance, for example, in the case of a mobile phone. It can be a device.

  The recording medium 11 is a nonvolatile memory, and in this embodiment, software programs such as a driver A41, a driver B42, a driver C43, a driver Z45, a monitoring application 47, and an OS 48 are statically recorded. These are copied from a PC that is normally used.

  The driver A41, the driver B42, the driver C43, the driver C43, and the driver Z45 are driver software (network driver) for so-called network communication, and control communication devices. Each driver corresponds to a different communication device. The driver A41, the driver 42, and the driver C43 correspond to a communication device A, a communication device B, and a communication device C (not shown), respectively. The driver Z45 corresponds to the communication device Z15.

  The monitoring application 47 supports the construction of a communication environment in the PC 20. Specifically, when the mobile environment is loaded on the PC 20, the monitoring application 47 executes processing for enabling communication with the communication device D24 included in the PC 20. The OS 48 is an OS image copied from a normally used PC. The OS 48 includes a driver management table 481. The driver management table 481 is information for managing associations between communication devices and network drivers. Here, the contents set in advance in the normally used PC are copied as they are.

  FIG. 5 is a diagram illustrating a configuration example of the driver management table. In the figure, a driver management table 481 manages information such as a usage flag, a device identifier, and a driver identifier for each network driver installed in a portable environment.

  The driver identifier is identification information for the OS 48 or the like to identify each network driver installed on the OS 48 (in the portable environment). The device identifier is identification information for the OS 48 or the like to identify a communication device corresponding to the network driver, and is configured by, for example, a manufacturer ID, a product ID, or the like. That is, the network driver corresponding to each communication device is identified by the combination of the device identifier and the driver identifier. The use flag is flag information indicating whether or not the communication device according to the record can be used. A communication device having a usage flag value of “0” cannot be used and is not used.

  Note that a portable phone 401 or a PC having a wireless or wired communication function may be used as the portable device 401. Further, the portable device 401 may be realized by installing a communication function in a portable memory such as a USB memory. That is, the portable device 401 is not limited to a predetermined device as long as it includes a communication function, a recording medium for recording a system environment, and an interface for connecting (communication) with a computer. Moreover, although the portable device 10 in this Embodiment communicates with PC20 via the USB interface 12, the communication interface with PC20 does not need to be limited to a USB interface. The portable device 10 only needs to have an interface capable of communicating with the PC 20 by other means, whether wired or wireless.

  The PC 20 is a so-called PC, and includes a RAM 21, a USB interface 22, a CPU 23, a communication device D 24, and the like connected by a bus B. The communication device D24 is a device such as a network card required for performing communication by wireless or wired communication. In addition to the hardware shown in the figure, the PC 20 also has hardware such as a ROM and an HDD, which is included in a general PC, but is omitted for convenience in the present embodiment.

  The server 30 is a computer in which a network driver download site is constructed. In this embodiment, the server 30 manages the driver D44 corresponding to the communication device D24 of the PC 20 in a downloadable state.

  When the portable device 10 shown in FIG. 4 is USB-connected to the PC 20 and a USB boot is performed on the PC 20, the portable environment recorded in the portable device 10 is loaded on the PC 20.

  FIG. 6 is a diagram illustrating a state where the portable environment is loaded on the PC. In the figure, in order to avoid confusion, the code “a” is added to the software loaded on the PC 20 after the original reference number. In the figure, an OS 48 a is loaded on the RAM 21 of the PC 20. As a method of loading the OS 48 recorded in the portable device 10 onto the PC 20, there is a USB bootable method. In this case, the BIOS mounted on the PC 20 recognizes the USB connection, recognizes the OS image (OS 48) recorded in the connected device, and boots. Note that, when the PC 20 and the portable device 10 are connected by USB, the PC 20 can transparently handle the recording medium 11 and the communication device Z15 (similar to the hardware included in the PC 20).

  In the figure, the monitoring application 47a is also loaded in the RAM 21. This shows how the monitoring application 47a is activated on the OS 48a. The activation of the monitoring application 47a may be performed automatically following the loading of the OS 48a, or may be manually performed by the operator of the PC 20 after the loading of the OS 48a.

  Hereinafter, a processing procedure executed by the PC 20 or the like in the state shown in FIG. 6 will be described. 7 and 8 are sequence diagrams for explaining the processing procedure in the present embodiment. In the figure, processing related to the monitoring application 47a and the OS 48a is executed by the CPU 23 of the PC 20.

  When activated, the monitoring application 47a sets the usage flag in the driver management table 481a to 0 (unusable) for the communication device Z15 included in the portable device 10 (S101). FIG. 5 shows an example in which the use flag of the communication device Z15 is set to 0.

  Subsequently, the monitoring application 47a requests the OS 48a to execute a scan of the communication device (S102). In response to the request, the OS 48a scans the communication device provided in the PC 20. Here, scanning of a communication device refers to a communication device that is connected, and when the use flag is set to 1 (available) in the driver management table 481a for the detected communication device, the communication device. A process for enabling network communication by loading a network driver corresponding to the above.

  Here, the PC 20 includes a communication device D24. Therefore, the communication device D24 is detected by scanning, and the device identifier is acquired by the OS 48a (S103a). Further, the communication device Z15 included in the portable device 10 also appears transparent from the PC 20. Therefore, the communication device Z15 is also detected by scanning, and the device identifier is acquired by the OS 48a (S103b).

  However, as shown in FIG. 5, the communication device D24 is not registered in the driver management table 481a. Therefore, the OS 48a cannot determine the corresponding network driver, and the network driver corresponding to the communication device 24 is not loaded. The communication device Z15 is registered in the driver management table 481a, and the corresponding network driver (driver Z45) can be determined, but the usage flag is set to 0. Therefore, the OS 48a does not load the driver 45. As a result, communication by the communication device Z15 is not possible.

  Subsequently, the monitoring application 47a inquires of the OS 48a whether or not network communication is enabled as a result of the scan (that is, whether or not the network driver is loaded) (S104). The OS 48a responds that it is valid or invalid according to the scan result (S105). Here, since the network driver is not loaded, a response that it is invalid is returned. If the response is valid, the subsequent processing is not executed, and communication is performed using the loaded network driver and the corresponding communication device.

  That is, the use flag of the communication device Z15 is set to 0 in step S101 in order to prevent the driver Z45 corresponding to the communication device Z15 from being loaded by the scan at this timing. This is because if the driver Z45 is loaded at this timing and communication by the communication device Z15 becomes possible, the network communication invalid state (communication impossible state) cannot be detected in the next step (S106). This is because, in a later step, the process for making the communication device D24 available is not executed, and the communication state may be maintained while using the communication device Z15. Generally, the communication band by the communication device Z15 that can be connected to the portable device 10 or the like is narrower than the communication band by the communication device D24 that can be connected to the PC 20. In view of such a point, it is more likely that a higher-speed communication environment is realized if communication is performed using the communication device D24 if possible, than communication is maintained by the communication device Z15.

  When the response indicating that it is invalid is returned in step S105, the monitoring application 47a inquires whether the PC 20 has a communication device in the first place (S106). The OS 48a responds based on the scan result (S107). Here, two communication devices are detected by scanning. Therefore, a response indicating that the communication device is included is returned.

  When a response indicating that the communication device is included is received, the monitoring application 47a inquires the OS 48a about the device identifier of the communication device (S108). The OS 48a returns the device identifiers of the communication device D24 and the communication device Z15 based on the scan result (S109). The monitoring application 47a registers a device identifier that is not registered in the driver management table 481a among the returned device identifiers in the driver management table 481a, and sets its use flag to 1 (S110). Therefore, here, a record relating to the communication device D is registered in the driver management table 481a.

  FIG. 9 is a diagram illustrating an example of a driver management table in which the communication device D is registered. As shown in the figure, the device identifier and the usage flag of the communication device D24 are registered in the driver management table 481a. However, the network driver corresponding to the communication device D24 is not installed at this point.

  Subsequently, the monitoring application 47a sets the use flag of the communication device Z to 1 (S121 (FIG. 8)). FIG. 10 is a diagram illustrating an example of a driver management table in which the use flag of the communication device Z is set to 1.

  In this state, the monitoring application 47a requests the OS 48a to rescan the communication device (S122). Similarly to steps S103a and S103b, the OS 48a detects the communication device D24 and the communication device Z15 by scanning (S123a, S123b). Here, as for the communication device D24, the corresponding network driver is still not installed (see FIG. 10). On the other hand, for the communication device Z15, the use flag is set to 1 (available). Therefore, the OS 48a loads the driver Z45 associated with the communication device Z15 in the driver management table 481a (S124). As a result, the PC 20 can perform network communication via the communication device Z15 (validated).

  Therefore, the monitoring application 47a starts network communication with the server 30 using the driver Z45 and the communication device Z15 (S125). The monitoring application 47a refers to the driver management table 481a, specifies a record in which only the device identifier is recorded and no driver identifier is recorded, and assigns the device identifier (communication device D in this example) of the record to the server 30. (S126). For example, the server 30 refers to a driver management table in which a device identifier and a driver identifier are associated and managed for each network driver that can be provided by the server 30, and a driver identifier corresponding to the device identifier received from the portable device 10. And the network driver (driver D44 in this example) indicated by the driver identifier is transmitted to the portable device 10. As described above, the portable device 10 downloads the necessary network driver. In the portable environment, the IP address or host name of the server 30 is recorded at a position (for example, a predetermined file on the file system) that can be recognized by the monitoring application 47a. Therefore, the monitoring application 47a communicates with the server 30 based on the IP address or the like when the communication device Z15 is set to the available state (use flag is 1).

  After downloading, the monitoring application 47a registers the driver identifier of the driver D44 in the driver management table 481a (S128).

  FIG. 11 is a diagram illustrating an example of a driver management table in which the driver D is registered. As shown in the figure, the driver identifier of the driver D44 is registered in the record of the communication device D24. As a result, the communication device D24 can be used.

  Therefore, when the monitoring application 47a performs the network driver download process, the monitoring application 47a thereafter performs a process for performing communication using the communication device D24 of the PC 20 instead of the communication device Z15 of the portable device 10 (that is, communication to be used) Execute the device switching process. First, the monitoring application 47a unloads the currently loaded driver Z45 (S129). Thereby, the communication by the communication device Z15 is invalidated. Subsequently, the monitoring application 47a disables the communication device Z15 by setting the use flag of the communication device Z15 to 0 (S130).

  FIG. 12 is a diagram illustrating an example of a driver management table in which the use flag of the communication device Z of the communication device Z is set to 0.

  In this state, the monitoring application 47a requests the OS 48a to rescan the communication device (S132). The OS 48a detects the communication device D24 by scanning (S133). Here, the driver D44 corresponding to the communication device D24 has been downloaded, and the use flag of the communication device D24 is 1 (see FIG. 12). Therefore, the OS 48a loads the driver D44 (S134).

  FIG. 13 is a diagram illustrating a state in which the driver D is loaded on the PC. As shown in the figure, a driver D44a is loaded in the RAM 44a of the PC 20. Thereby, communication by the communication device D24 is validated. Although the communication device Z15 is also detected by rescanning, the use flag is set to 0, so the driver Z45 is not loaded. Therefore, the communication device Z15 is not used by mistake.

  Thereafter, the environment loaded in the RAM 21 of the PC 20 may be written back to the recording medium 11 of the portable device 10 before the connection between the portable device 10 and the PC 20 is released. In this case, the communication device D44 is newly recorded on the recording medium 11, and the device management table 481 is updated to the state shown in FIG. Therefore, when the portable device 10 is connected to the PC 20 next time, it is possible to quickly start communication using the driver D44 recorded in the portable device 10 and the communication device 24 of the PC 20.

  As described above, according to the present embodiment, even when the driver D44 corresponding to the communication device D24 included in the PC 20 to which the portable device 10 is connected does not exist in the portable environment, the communication device Z15 included in the portable device 10. Can be used to download the driver D44, and communication by the communication device D24 can be validated.

  Further, by switching the use flag at an appropriate timing, avoidance of interference by the communication device Z15 when detecting the communication device D24, downloading of the communication device D24 using the communication device Z15, and communication by the communication device D24 after downloading. Can be appropriately realized.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
A communication support program stored in a portable device comprising a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded,
A computer to which the portable device is connected;
A device detection procedure for detecting a second communication device included in the computer;
A driver acquisition procedure for acquiring the network driver by network communication using the first communication device when a network driver corresponding to the detected second communication device does not exist in the computer and the portable device; Communication support program to execute
(Appendix 2)
The device detection procedure includes:
A procedure for recording information indicating that the first communication device cannot be used in the availability management unit in which the availability information indicating availability for each communication device is recorded;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by a communication device indicating availability, and
In the driver acquisition procedure, when communication by the second communication device is not valid, communication by the one communication device is validated and a network driver corresponding to the second communication device is obtained. The communication support program according to attachment 1.
(Appendix 3)
The driver acquisition procedure includes:
A procedure for recording information indicating that the first communication device is usable in the availability management unit when communication by the second communication device is not valid;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by the first communication device indicating availability; and
The communication support program according to claim 2, further comprising a procedure for acquiring a network driver corresponding to the second communication device by network communication using the first communication device.
(Appendix 4)
Supplementary notes 1 to 3, further comprising: a communication procedure for invalidating communication by the first communication device and enabling network communication by the second communication device using the network driver acquired in the driver acquisition procedure. 4. The communication support program according to any one of 3.
(Appendix 5)
The communication procedure is:
Disabling communication by the first communication device;
A procedure for recording information indicating that the first communication device is unusable in the usability management unit;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is The communication support program according to claim 4, further comprising a procedure for validating communication by the second communication device indicating that the second communication device can be used.
(Appendix 6)
A communication support method executed by a computer connected to a portable device including a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded,
A device detection procedure for detecting a second communication device included in the computer;
A driver acquisition procedure for acquiring the network driver by network communication using the first communication device when a network driver corresponding to the detected second communication device does not exist in the computer and the portable device; A communication support method characterized by comprising:
(Appendix 7)
The device detection procedure includes:
A procedure for recording information indicating that the first communication device cannot be used in the availability management unit in which the availability information indicating availability for each communication device is recorded;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by a communication device indicating availability, and
In the driver acquisition procedure, when communication by the second communication device is not valid, communication by the one communication device is validated and a network driver corresponding to the second communication device is obtained. The communication support method according to attachment 6.
(Appendix 8)
The driver acquisition procedure includes:
A procedure for recording information indicating that the first communication device is usable in the availability management unit when communication by the second communication device is not valid;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by the first communication device indicating availability; and
The communication support method according to claim 2, further comprising a procedure of acquiring a network driver corresponding to the second communication device by network communication using the first communication device.
(Appendix 9)
Supplementary notes 6 to 6, further comprising: a communication procedure for invalidating communication by the first communication device and enabling network communication by the second communication device using the network driver acquired in the driver acquisition procedure. The communication support method according to any one of claims 8 to 9.
(Appendix 10)
The communication procedure is:
Disabling communication by the first communication device;
A procedure for recording information indicating that the first communication device is unusable in the usability management unit;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is The communication support method according to claim 9, further comprising a procedure for validating communication by the second communication device indicating that the second communication device can be used.
(Appendix 11)
A portable device comprising a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded,
To the computer to which the portable device is connected,
A device detection procedure for detecting a second communication device included in the computer;
A driver acquisition procedure for acquiring the network driver by network communication using the first communication device when a network driver corresponding to the detected second communication device does not exist in the computer and the portable device; A portable device in which a portable device for executing is recorded.
(Appendix 12)
The device detection procedure includes:
A procedure for recording information indicating that the first communication device cannot be used in the availability management unit in which the availability information indicating availability for each communication device is recorded;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by a communication device indicating availability, and
In the driver acquisition procedure, when communication by the second communication device is not valid, communication by the one communication device is validated and a network driver corresponding to the second communication device is obtained. The portable device according to appendix 11.
(Appendix 13)
The driver acquisition procedure includes:
A procedure for recording information indicating that the first communication device is usable in the availability management unit when communication by the second communication device is not valid;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by the first communication device indicating availability; and
The portable device according to claim 12, further comprising a procedure for acquiring a network driver corresponding to the second communication device by network communication using the first communication device.
(Appendix 14)
Additional remarks 11 to 11, further comprising: a communication procedure for invalidating communication by the first communication device and enabling network communication by the second communication device by using the network driver acquired in the driver acquisition procedure. The portable device according to claim 13.
(Appendix 15)
The communication procedure is:
Disabling communication by the first communication device;
A procedure for recording information indicating that the first communication device is unusable in the usability management unit;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is The portable device according to claim 14, further comprising a procedure for validating communication by the second communication device indicating that the second communication device can be used.

It is a figure which shows a mode that a system environment is carried by a portable device. 6 is a diagram illustrating an example in which an environment of a portable device 401 is loaded on a PC 501. FIG. 6 is a diagram illustrating an example in which an environment of a portable device 401 is loaded on a PC 504. FIG. It is a figure for demonstrating the apparatus utilized in embodiment of this invention. It is a figure which shows the structural example of a driver management table. It is a figure which shows the state by which portable environment was loaded by PC. It is a sequence diagram for demonstrating the process sequence in this Embodiment. It is a sequence diagram for demonstrating the process sequence in this Embodiment. It is a figure which shows the example of the driver management table in which the communication device D was registered. It is a figure which shows the example of the driver management table by which the utilization flag of the communication device Z was set to 1. It is a figure which shows the example of the driver management table in which the driver D was registered. It is a figure which shows the example of the driver management table by which the utilization flag of the communication device Z was set to 0. It is a figure which shows the state in which the driver D was loaded by PC.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Portable device 11 Recording medium 12 USB interface 13 USB hub 15 Communication device Z
20 PC
21 RAM
22 USB interface 23 CPU
24 Communication device D
30 Server 41 Driver A
42 Driver B
43 Driver C
44 Driver D
45 Driver Z
47 Monitoring application 48 OS
B bus

Claims (6)

A communication support program stored in a portable device comprising a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded,
A computer to which the portable device is connected;
A device detection procedure for detecting a second communication device included in the computer;
A driver acquisition procedure for acquiring the network driver by network communication using the first communication device when a network driver corresponding to the detected second communication device does not exist in the computer and the portable device; Communication support program to execute The device detection procedure includes:
A procedure for recording information indicating that the first communication device cannot be used in the availability management unit in which the availability information indicating availability for each communication device is recorded;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by a communication device indicating availability, and
In the driver acquisition procedure, when communication by the second communication device is not valid, communication by the one communication device is validated and a network driver corresponding to the second communication device is obtained. The communication support program according to claim 1. The driver acquisition procedure includes:
A procedure for recording information indicating that the first communication device is usable in the availability management unit when communication by the second communication device is not valid;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is Enabling communication by the first communication device indicating availability; and
The communication support program according to claim 2, further comprising: obtaining a network driver corresponding to the second communication device through network communication using the first communication device.   The communication procedure for disabling communication by the first communication device and enabling network communication by the second communication device by using the network driver acquired in the driver acquisition procedure. The communication support program as described in any one of thru | or 3. The communication procedure is:
Disabling communication by the first communication device;
A procedure for recording information indicating that the first communication device is unusable in the usability management unit;
The first communication device included in the portable device and the second communication device included in the computer are detected. Among the detected communication devices, a corresponding network driver exists, and the availability information is The communication support program according to claim 4, further comprising a procedure for validating communication by the second communication device indicating that the second communication device can be used. A communication support method executed by a computer connected to a portable device including a first communication device and a recording medium on which a network driver corresponding to the first communication device is recorded,
A device detection procedure for detecting a second communication device included in the computer;
A driver acquisition procedure for acquiring the network driver by network communication using the first communication device when a network driver corresponding to the detected second communication device does not exist in the computer and the portable device; A communication support method characterized by comprising:

Images