CN112328328A

CN112328328A - Method, device, equipment and storage medium for overloading equipment drive

Info

Publication number: CN112328328A
Application number: CN202011332811.3A
Authority: CN
Inventors: 张佗
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2020-11-24
Filing date: 2020-11-24
Publication date: 2021-02-05
Anticipated expiration: 2040-11-24
Also published as: CN112328328B

Abstract

The embodiment of the application discloses a method, a device, equipment and a storage medium for overloading a device driver, and relates to the technical field of the internet such as cloud computing and cloud service. The method comprises the following steps: acquiring an instance identifier of target equipment; acquiring a drive guide file storage path of the target equipment according to the instance identifier; acquiring a hardware identifier corresponding to the target equipment according to the example identifier; and updating the driver of the target equipment according to the driver instruction file storage path and the hardware identifier, solving the problem that the driver cannot be loaded when the system of the target equipment is deployed, and reducing the manpower requirement and the deployment time of the system for deploying the target equipment in batches.

Description

Method, device, equipment and storage medium for overloading equipment drive

Technical Field

The application relates to the technical field of computers, in particular to the technical field of internet such as cloud computing and cloud service, and particularly relates to a method, a device, equipment and a storage medium for device driver overloading.

Background

When the same Windows system needs to be installed in batches, the Windows system mirror images which are manufactured in advance can be used, and the deployment mode is easy to operate, simple and fast.

With the development of technologies such as artificial intelligence, more and more image Processing Unit (GPU) servers are put into a production environment, and a large number of GPU servers also face the problem of batch deployment. The GPU server is provided with a new hardware device image processing chip, which requires integrating corresponding driver software in the manufactured system image. However, when the system image with the integrated driver is used for batch deployment, often the deployed GPU device driver of the Windows server cannot be loaded correctly due to the difference between the servers.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for reloading a device driver.

In a first aspect, an embodiment of the present application provides a method for overloading a device driver, including: acquiring an instance identifier of target equipment; acquiring a drive guide file storage path of the target equipment according to the instance identifier; acquiring a hardware identifier corresponding to the target equipment according to the example identifier; and updating the drive of the target equipment according to the drive instruction file storage path and the hardware identifier.

In a second aspect, an embodiment of the present application provides an apparatus for driving a heavy load by a device, including: an instance identifier obtaining module configured to obtain an instance identifier of a target device; the instruction file acquisition module is configured to acquire a drive instruction file storage path of the target device according to the instance identifier; the hardware identification acquisition module is configured to acquire a hardware identification corresponding to the target device according to the instance identification; and the drive updating module is configured to update the drive of the target device according to the drive instruction file storage path and the hardware identifier.

In a third aspect, an embodiment of the present application provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as described in any one of the implementations of the first aspect.

In a fourth aspect, embodiments of the present application propose a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method as described in any one of the implementations of the first aspect.

According to the method, the device, the equipment and the storage medium for reloading the equipment driver, the example identification of the target equipment is firstly obtained; then, according to the instance identifier, obtaining a drive guide file storage path of the target device; then, acquiring a hardware identifier corresponding to the target equipment according to the example identifier; and finally, updating the driver of the target equipment according to the storage path of the driver instruction file and the hardware identifier, thereby solving the problem that the driver cannot be loaded when a system of the target equipment is deployed.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings. The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:

FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;

FIG. 2 is a schematic flow chart diagram illustrating one embodiment of a method for device driver reloading according to the present application;

FIG. 3 is a schematic flow chart diagram illustrating another embodiment of a method for device driver reloading according to the present application;

FIG. 4 is a schematic diagram illustrating an application scenario of an embodiment of a method for device driver reloading according to the present application;

FIG. 5 is a schematic block diagram of an embodiment of the apparatus of the present application driving a reloading mechanism;

fig. 6 is a block diagram of an electronic device for implementing a method for overloading a device driver according to an embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.

Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the method of device driver reloading or apparatus for device driver reloading of the present application may be applied.

As shown in fig. 1, the system architecture 100 may include a terminal device 101, a server 102. The terminal device 102 may be installed on the terminal device 101, and may include a computer, a mobile communication terminal, a tablet computer, a multimedia playing device, and the like. The system image file of the template computer can be made on the terminal device 102 by using a system image file making tool (e.g., Ghost). The server 102 may be a Windows server, a GPU server, or other device servers for deploying the system.

The server 102 may be hardware or software. When the server 102 is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server. When the server 102 is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.

It should be noted that the method for reloading the device driver provided in the embodiment of the present application is generally executed by the terminal device 101, and accordingly, the apparatus for reloading the device driver is generally disposed in the terminal device 101.

It should be understood that the number of terminal devices and servers in fig. 1 is merely illustrative. There may be any number of terminal devices and servers, as desired for implementation.

With continued reference to FIG. 2, a flow diagram of one embodiment of a method of device driver reloading according to the present application is shown. The method comprises the following steps:

step 201, obtaining an instance identifier of a target device.

In this embodiment, an execution subject (for example, the terminal device 101 shown in fig. 1) of the method for reloading the device driver may acquire the instance identifier of the target device.

The target device refers to a device used for deploying the system. The target device may have a specific functional purpose, and the target device may be deployed with a system to utilize the functional purpose. For example, the GPU device has a computation or rendering function, and by deploying the system for the GPU device, normal use of the computation or rendering function of the GPU device can be ensured.

Generally speaking, the driver of the target device may be integrated into the operating system, and the function of the target device may be utilized by correctly loading the driver. The operating system herein includes, but is not limited to, a Windows system.

Wherein, the instance identifier is an identification character string of the target device provided by the operating system and is used for uniquely identifying the target device in the operating system. The target device may be identified in the operating system by its instance identification.

Step 202, according to the instance identifier, obtaining a drive instruction file storage path of the target device.

In this embodiment, the execution subject may obtain a drive instruction file storage path of the target device according to the instance identifier.

The driver instruction file is used for finding the driver program file when the operating system does not correctly load the driver of the target equipment, and reloading the driver, so that the target equipment can be normally used. Illustratively, for the Windows operating system, the storage path of the driver guidance files of various devices is Windows \ INF \ folder. The storage path of the drive instruction file of the target device is in one-to-one correspondence with the instance identifier of the target device. For example, the storage path of the driver instruction file of the GPU device in the Windows operating system is: windows \ INF \ oEM6. INF.

And step 203, acquiring a hardware identifier corresponding to the target device according to the instance identifier.

In this embodiment, the execution subject may obtain a hardware identifier corresponding to the target device according to the instance identifier.

The hardware identification is an identification character string defined by a target equipment manufacturer for the target equipment, and the operating system matches the target equipment with the corresponding drive instruction file by using the character string. The corresponding driving instruction file can be matched in the operating system through the hardware identification of the target device.

And step 204, updating the drive of the target equipment according to the drive instruction file storage path and the hardware identifier.

In this embodiment, the execution subject may update the driver of the target device according to the driver instruction file storage path and the hardware identifier.

The two parameters of the drive instruction file storage path and the hardware identifier can be transmitted into an update instruction, so that the drive of the target device is updated or reloaded.

It is worth mentioning that the driver instruction files and hardware identifications of the same device definition by the operating system are the same. Therefore, the embodiment can reduce the manpower requirement and the deployment time of the system for deploying the target devices in batches.

The method for overloading the device driver provided by the embodiment of the application solves the problem that the driver cannot be loaded when a system of the target device is deployed, and reduces the manpower requirement and the deployment time of the system for deploying the target device in batches.

In some optional implementations of this embodiment, the step 201 includes: and searching the instance identification of the target device by executing the searching command of the predetermined tool.

The predetermined tool refers to a tool which is installed in the operating system in advance and can perform a lookup operation in the operating system and find an instance identifier of the target device, for example, devcon. Illustratively, using the find command "find" of the devcon tool, the list of instance identifications of all devices can be viewed, and thus the instance identification of the target device can be found through the list.

In some optional implementations of this embodiment, the step 202 includes: and searching a drive instruction file storage path of the target equipment by executing a device driver node listing command of a preset tool.

The predetermined tool refers to a tool which is installed in the operating system in advance and can execute the operation of the listed device driver nodes in the operating system and find the storage path of the driver guidance file of the target device, for example, devcon. Illustratively, the device driver node using the devcon tool lists a command "drivers + instance ids", which may look at the drive instruction file used by the target device corresponding to the instance ids and look up the storage path of the drive instruction file of the target device. For example, the storage path of the driver installation instruction file of the GPU device in the Windows operating system is Windows \ INF \ oem6. INF.

In some optional implementations of this embodiment, the step 203 further includes: the hardware identification corresponding to the target device is looked up by executing the machine code query command of the predetermined tool.

The predetermined tool refers to a tool which is installed in the operating system in advance and can execute a machine code query operation in the operating system and find the hardware identifier of the target device, for example, devcon. Illustratively, the machine code query command "hwids + instance id" of the devcon tool is used to find the hardware id corresponding to the instance id of the target device.

In some optional implementations of this embodiment, the step 204 further includes: the driving of the target device is updated by executing an update command of a predetermined tool.

The predetermined tool refers to a tool which is installed in the operating system in advance and can perform an update operation in the operating system and update the driver of the target device, for example, devcon. Illustratively, the update or reload of the driver of the GPU device may be done using the update command "update \ Windows \ INF \ oem6.INF + hardware identification" of the devcon tool.

In some optional implementation manners of this embodiment, the method is applied to a start script, the start script is integrated in a Windows system image file, and the Windows system image file is integrated with a driver of the target device.

Scripts (scripts) are executable files written according to a certain format, also called macros or batch files, using a specific descriptive language. Scripts can typically be temporarily called and executed by an application, and the start-up script can run an executable file of the software. The method for reloading the device driver provided by the above embodiment of the present application may be called by the start script.

The mirror image file is a file similar to a rar or zip compressed file, a specific series of files are made into a single file according to a certain format for a user to download, such as an operating system mirror image and a game mirror image, and the mirror image file can be identified by specific software and recorded on an optical disc. The system image file contains operating system files, boot files, partition table information, etc. for system installation and repair, and the system image file may be understood as a clone file for installing all data of the optical disc to the whole system, such as a microsoft original edition system, or a backup file for operating system partitions, such as a ghost system image.

Illustratively, the process of making the Windows system image file is as follows: installing a version corresponding to a Windows system to be deployed on a server provided with GPU equipment, and then manually installing a GPU equipment driver according to the requirement of an application party, wherein the driver can be correctly loaded, and the corresponding GPU is normal in calculation or rendering function; then generating a system mirror image for the environment, and taking the mirror image as a template for deploying GPU servers in batches in a machine room; finally, a start script is designed to call the method for reloading the device driver provided according to the above embodiment of the present application.

By adopting the Windows system image file provided by the embodiment to carry out batch deployment on the target equipment server, the manpower requirement and the deployment time of batch deployment can be greatly reduced.

In some optional implementations of this embodiment, the method further includes stopping execution of the start script in response to a successful driver update of the target device.

Wherein, the start script can judge whether the driver of the target device is successfully updated or reloaded through the return value of the predetermined tool. Where the predetermined tool can return success or failure, as well as information related to the failure. When the parameters transmitted to the predetermined tool, including command parameters, instance identifiers, driving guide file paths, etc., have errors, the predetermined tool fails to execute and returns a failure result. And when the drive of the target equipment is updated or reloaded successfully, stopping executing the start script, and ensuring that the start script is not executed any more when the target equipment is started next time, so that the speed of restarting is improved.

With further reference to FIG. 3, there is shown a flow chart of another embodiment of a method of device driver reloading, the method comprising the steps of:

step 301, searching the instance identifier of the target device by executing the search command of the predetermined tool.

Step 302, searching a drive instruction file storage path of the target device by executing a device driver node listing command of a predetermined tool.

Step 303, the hardware identifier corresponding to the target device is found by executing the machine code query command of the predetermined tool.

Step 304, updating the driver of the target device by executing the update command of the predetermined tool.

Step 305, in response to the driver update of the target device being successful, deleting the predetermined tool.

Wherein, when the driver update or reload of the target device is successful, a file which is not necessary to be used in the future, such as a predetermined tool, can be deleted, thereby increasing the speed at the time of restart.

In some optional implementations of this embodiment, the target device is a GPU device, such as an NVIDIA GPU device.

In some optional implementations of the embodiment, the Windows system image file is installed in a variety of image processor servers. The hardware of each image processor may be the same or different. By adopting the Windows system image file to deploy various image processor servers, the problem of GPU drive loading failure in batch Windows system deployment can be solved, and the deployed GPU servers do not need manual operation to repair.

For ease of understanding, fig. 4 shows a schematic application scenario of an embodiment of a method of device driver reloading according to the application.

As shown in fig. 4, firstly, a Windows system image file is made, which includes the steps of: starting a Windows server, installing an NVIDIA driver and deploying a heavy-load starting script of the driver. The method for reloading the device driver provided by the embodiment of the application can be called by the starting script; then generating a system mirror image based on the environment, and taking the mirror image as a template for deploying GPU servers in batches in a machine room; and finally, deploying the generated system images to a GPU equipment server in batches.

With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of device driver overloading, which corresponds to the embodiment of the method shown in fig. 2, and which can be applied in various electronic devices.

As shown in fig. 5, the apparatus 500 for driving a heavy load of a device of the present embodiment may include: an instance identifier obtaining module 501, a guidance file obtaining module 502, a hardware identifier obtaining module 503, and a driver updating module 504. The instance identifier obtaining module 501 is configured to obtain an instance identifier of a target device; a guide file obtaining module 502 configured to obtain a drive guide file storage path of the target device according to the instance identifier; a hardware identifier obtaining module 503 configured to obtain a hardware identifier corresponding to the target device according to the instance identifier; and the driver updating module 504 is configured to update the driver of the target device according to the driver instruction file storage path and the hardware identifier.

In the present embodiment, in the apparatus 500 for device driving reloading: the specific processing and the technical effects thereof of the example identifier obtaining module 501, the instruction file obtaining module 502, the hardware identifier obtaining module 503, and the driver updating module 504 can refer to the related descriptions of step 201 and step 204 in the corresponding embodiment of fig. 2, which are not described herein again.

In some optional implementations of this embodiment, the instance identification acquisition module is further configured to: and searching the instance identification of the target device by executing the searching command of the predetermined tool.

In some optional implementations of this embodiment, the instruction file obtaining module is further configured to: the hardware identification corresponding to the target device is looked up by executing the machine code query command of the predetermined tool.

In some optional implementations of this embodiment, the hardware identification acquisition module is further configured to: the hardware identification corresponding to the target device is looked up by executing the machine code query command of the predetermined tool.

In some optional implementations of this embodiment, the driver update module is further configured to: the driving of the target device is updated by executing an update command of a predetermined tool.

In some optional implementations of this embodiment, the apparatus is configured to configure the start script, and the start script is integrated in a Windows system image file, and the Windows system image file is integrated with a driver of the target device.

In some optional implementations of this embodiment, the apparatus further includes: and the termination module is configured to stop executing the start script in response to the drive update success of the target device.

In some optional implementations of this embodiment, the apparatus further includes: a deletion module configured to delete the predetermined tool in response to the drive update of the target device being successful.

In some alternative implementations of this embodiment, the target device is an image processor.

In some optional implementations of the embodiment, the Windows system image file is installed in a variety of image processor servers.

Fig. 6 is a block diagram of an electronic device according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.

As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 6, one processor 601 is taken as an example.

The memory 602 is a non-transitory computer readable storage medium as provided herein. Wherein the memory stores instructions executable by at least one processor to cause the at least one processor to perform the method of device driver reloading provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the method of device driver reloading provided herein.

The memory 602, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the method for device driver reloading in the embodiments of the present application (for example, the example identifier obtaining module 501, the instruction file obtaining module 502, the hardware identifier obtaining module 503, and the driver updating module 504 shown in fig. 5). The processor 601 executes various functional applications of the server and data processing by running non-transitory software programs, instructions and modules stored in the memory 602, that is, implementing the method of device driver reloading in the above method embodiments.

The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the electronic device of the method of device driver reloading, and the like. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory located remotely from the processor 601, and these remote memories may be connected over a network to the electronic device of the method of device driver reloading. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The electronic device of the method of device driver reloading may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected by a bus or other means, and fig. 6 illustrates the connection by a bus as an example.

The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device of the method of device driving override, such as a touch screen, keypad, mouse, track pad, touch pad, pointer stick, one or more mouse buttons, track ball, joystick, or like input device. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

According to the technical scheme of the application, firstly, an instance identifier of target equipment is obtained; then, according to the instance identifier, obtaining a drive instruction file storage path of the target device; then, acquiring a hardware identifier corresponding to the target equipment according to the instance identifier; and finally, updating the driver of the target equipment according to the storage path of the driver instruction file and the hardware identifier, thereby solving the problem that the driver cannot be loaded when a system of the target equipment is deployed.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.

The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method of device driver overloading, comprising:

acquiring an instance identifier of target equipment;

acquiring a drive guide file storage path of the target equipment according to the instance identifier;

acquiring a hardware identifier corresponding to the target equipment according to the instance identifier;

and updating the drive of the target equipment according to the drive instruction file storage path and the hardware identifier.

2. The method of claim 1, wherein the obtaining an instance identification of a target device comprises:

and searching the instance identification of the target equipment by executing a search command of a preset tool.

3. The method according to claim 1 or 2, wherein the obtaining of the drive instruction file storage path of the target device according to the instance identifier comprises:

and searching a drive instruction file storage path of the target equipment by executing a device driver node listing command of a preset tool.

4. The method of claim 1, wherein the obtaining a hardware identifier corresponding to the target device according to the instance identifier comprises:

and searching the hardware identification corresponding to the target device by executing a machine code query command of a predetermined tool.

5. The method of claim 1, wherein the updating the driver of the target device according to the driver guideline file storage path and the hardware identification comprises:

updating the driving of the target device by executing an update command of a predetermined tool.

6. The method of claim 1, wherein the method is applied to a boot script integrated into a Windows system image file integrated with a driver of a target device.

7. The method of claim 6, wherein the method further comprises:

and stopping executing the start script in response to the drive update success of the target device.

8. The method of claim 7, wherein the method further comprises:

and deleting the predetermined tool in response to the drive update success of the target device.

9. The method of claim 1, wherein the target device is an image processor.

10. The method of claim 9, wherein the Windows system image file is installed on a plurality of image processor servers.

11. An apparatus for driving a heavy load with a device, the apparatus comprising:

an instance identifier obtaining module configured to obtain an instance identifier of a target device;

the instruction file acquisition module is configured to acquire a drive instruction file storage path of the target device according to the instance identifier;

a hardware identifier obtaining module configured to obtain a hardware identifier corresponding to the target device according to the instance identifier;

and the drive updating module is configured to update the drive of the target device according to the drive instruction file storage path and the hardware identifier.

12. The apparatus of claim 11, wherein the instance identification acquisition module is further configured to:

13. The apparatus of claim 11 or 12, wherein the guideline file obtaining module is further configured to:

14. The apparatus of claim 11, wherein the hardware identification acquisition module is further configured to:

15. The apparatus of claim 11, wherein the drive update module is further configured to:

16. The apparatus of claim 11, wherein the apparatus is configured with a boot script integrated into a Windows system image file integrated with a driver of a target device.

17. The apparatus of claim 16, wherein the apparatus further comprises:

a termination module configured to stop executing the start script in response to a drive update success of the target device.

18. The apparatus of claim 16, wherein the apparatus further comprises:

a deletion module configured to delete a predetermined tool in response to a drive update success of the target device.

19. The apparatus of any of claims 11, wherein the target device is an image processor.

20. The apparatus of claim 19, wherein the Windows system image file is installed on a plurality of image processor servers.

21. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-10.

22. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-10.