Driver CD efficient production method and device

Abstract

The present invention discloses a method and device for efficiently producing a Driver CD, which is used to solve the problem of low testing efficiency and prone to errors in the existing bare board testing phase due to the need to manually install the driver to produce the test environment. The method comprises: obtaining the WIM file of the old version of the Driver CD and mounting the WIM file; identifying and modifying project information, and modifying the original project information in the WIM file based on the modified project information; obtaining a driver list, compiling a component package based on the driver list to obtain a configuration component package; automatically decompressing the configuration component package to obtain a configuration file, which includes the component package configuration information required when configuring a new project; automatically creating a component configuration path based on the configuration file, and placing the component package configuration information in the component configuration path; uninstalling the WIM file and performing hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

Description

Technical Field

[0001] The present invention relates to the technical field of computer testing, and in particular to a method for efficiently producing a Driver CD, a device for efficiently producing a Driver CD, an electronic device, and a storage medium. Background Art

[0002] A driver CD is a disc used to install and update hardware device drivers. It typically contains drivers for specific hardware devices. Users can complete driver installation by using the software on the installation CD.

[0003] However, during the bare board testing phase, customers typically don't provide a Driver CD containing drivers and applications. This forces the testing department to create a test environment based on a test platform (such as Pure OS) and manually install drivers, which is inefficient. This method also allows only one-to-one Driver CD production, which can easily lead to problems with some drivers not being properly installed due to human error. Furthermore, when providing drivers to customers, Driver CD production errors can occasionally occur, necessitating the re-supply of the correct driver version, impacting project progress and ratings. Furthermore, manual modifications to the Driver CD involve too many changes, and without a history of manual modifications in previous projects, testing efficiency is low. Summary of the Invention

[0004] The present invention provides a method for efficiently producing a driver CD, a device for efficiently producing a driver CD, an electronic device, and a storage medium, which are used to solve or partially solve the technical problem that in the existing bare board testing stage, the test environment needs to be manually installed to produce a driver, resulting in low testing efficiency and prone to errors.

[0005] The present invention provides a method for efficiently producing a Driver CD, the method comprising:

[0006] Obtain the WIM file of the old version of the Driver CD and mount the WIM file;

[0007] Identifying the modified project information input by the user, and modifying the original project information in the WIM file according to the modified project information;

[0008] Obtaining a driver list, compiling a component package according to the driver list, and obtaining a configuration component package;

[0009] Automatically decompressing the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required when configuring a new project;

[0010] Automatically create a component configuration path according to the configuration file, and place the component package configuration information into the component configuration path;

[0011] Uninstall the WIM file and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production.

[0012] Optionally, compiling a component package according to the driver list to obtain a configuration component package includes:

[0013] In response to a component selection operation, extracting information from the driver list to obtain component package extraction information, and automatically loading information based on the component package extraction information;

[0014] Capture the currently loaded component package information, and compare and verify the component package information with the component package extraction information;

[0015] If the information comparison and verification is successful, the component package extraction information is written into the configuration file as component package configuration information, and the configuration file is compressed to obtain a configuration component package.

[0016] Optionally, in response to the component selection operation, extracting information from the driver list to obtain component package extraction information includes:

[0017] In response to a component selection operation, extracting required component information according to a header of the driver list;

[0018] Identify and classify the extracted component information according to the component package type to obtain component package extraction information;

[0019] The component package extraction information is stored in a designated location according to a preset file format, so that when the information is automatically loaded, information is called in the designated location according to the component package type to obtain the component package information.

[0020] Optionally, the component package type includes a Driver Component class, a StoreAPP Component class, a Win32APP Component class, and a Component class, and the comparing and verifying the component package information with the component package extraction information includes:

[0021] Filtering target extraction information having the same component package type as the component package information from the component package extraction information;

[0022] In combination with the component package type, the component package information is compared and verified with the target extraction information; wherein, when performing the information comparison and verification:

[0023] For the Driver Component class package, the information compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information;

[0024] For StoreAPP Component packages, the information compared and verified includes the application version and manufacturer, installation script name, APPID information, HWID information, and Extension ID information;

[0025] For Win32APP Component class or Component class component package, the comparison and verification information includes application version and manufacturer, installation script name, and Version_Path.

[0026] Optionally, the method further includes:

[0027] If the information comparison and verification fails, the component package compilation will be stopped and an error message will be prompted.

[0028] Optionally, the project information includes Driver CD name, project name, platform information, Driver CD version, installation type and operating system version.

[0029] Optionally, after modifying the original project information in the WIM file according to the modified project information, the method further includes:

[0030] Delete the original WIM file in the Software folder and replace it with the modified WIM file required for the new project.

[0031] The present invention also provides a device for efficiently producing a Driver CD, comprising:

[0032] A file mounting module, used to obtain the WIM file of the old version of the Driver CD and mount the WIM file;

[0033] A project information modification module, configured to identify modified project information input by a user and modify the original project information in the WIM file according to the modified project information;

[0034] A component package compilation module is used to obtain a driver list, compile the component package according to the driver list, and obtain a configuration component package;

[0035] A component package decompression module, configured to automatically decompress the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required when configuring a new project;

[0036] A component configuration path creation module, configured to automatically create a component configuration path based on the configuration file, and place the component package configuration information into the component configuration path;

[0037] The file uninstallation module is used to uninstall the WIM file and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production.

[0038] The present invention further provides an electronic device, comprising a processor and a memory:

[0039] The memory is used to store program code and transmit the program code to the processor;

[0040] The processor is configured to execute any one of the above methods for efficiently producing a Driver CD according to instructions in the program code.

[0041] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store program code, and the program code is used to execute any of the above methods for efficiently producing a Driver CD.

[0042] It can be seen from the above technical solutions that the present invention has the following advantages:

[0043] This paper provides an efficient method for creating a Driver CD. The method involves obtaining a WIM file from an older version of the Driver CD and mounting the WIM file. The method identifies and modifies project information, and based on the modified project information, modifies the original project information in the WIM file. The method obtains a driver list and compiles component packages based on the driver list to obtain a configuration component package. The configuration component package is then automatically decompressed to obtain a configuration file, which contains the component package configuration information required for configuring a new project. Based on the configuration file, a component configuration path is automatically created and the component package configuration information is placed there. The method then unmounts the WIM file and calculates hash values ​​for all files in the newly configured Driver CD. This method automatically and quickly completes Driver CD creation, improving testing efficiency and reducing errors caused by human operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] Figure 1This is a flowchart of the steps of an efficient method for making a Driver CD;

[0046] Figure 2 A diagram of the UI design interface for mounting a Driver CD WIM file;

[0047] Figure 3 A flowchart of the Driver CD customization process;

[0048] Figure 4 A diagram of a customized UI design for Driver CD;

[0049] Figure 5 A schematic diagram of the steps for compiling a component package;

[0050] Figure 6 A flowchart of the steps for extracting driver list information is shown below;

[0051] Figure 7 A schematic diagram of a process for comparing and verifying component package information;

[0052] Figure 8 A UI design interface diagram compiled for a component package;

[0053] Figure 9 This is a schematic diagram of the overall process of an efficient method for producing a Driver CD;

[0054] Figure 10 The structure diagram of a device for efficiently producing Driver CDs is shown in FIG. DETAILED DESCRIPTION

[0055] The embodiments of the present invention provide a method for efficiently producing a Driver CD, a device for efficiently producing a Driver CD, an electronic device, and a storage medium, which are used to solve or partially solve the technical problem that in the existing bare board testing stage, the test environment needs to be manually installed to produce a driver, resulting in low testing efficiency and prone to errors.

[0056] In order to make the purpose, features, and advantages of the present invention more obvious and easy to understand, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described below are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0057] For example, during the bare-board testing phase, customers typically don't provide a DriverCD containing drivers and applications. The testing department can only create a test environment based on a test platform (such as Pure OS) and manually install drivers, which is inefficient. This method also allows only one-to-one Driver CDs to be created, which can easily lead to problems with some drivers not being properly installed due to human error. Furthermore, when providing drivers to customers, Driver CD production errors can occasionally occur, necessitating the re-supply of the correct driver version, impacting project progress and scoring. Furthermore, manual modifications to the Driver CD involve too many changes, and without a history of manual modifications in previous projects, testing efficiency is low.

[0058] Therefore, one of the core invention points of the embodiment of the present invention is to provide an efficient method for producing the first version of the Driver CD in the bare board testing stage: obtain the WIM (Windows Imaging Format, an image file format) file of the old version of the Driver CD and mount the WIM file; identify the modified project information, and modify the original project information in the WIM file according to the modified project information; obtain the driver list, compile the component package according to the driver list, and obtain the configuration component package; then automatically decompress the configuration component package to obtain the configuration file, which includes the component package configuration information required when configuring the new project; according to the configuration file, automatically create a component configuration path and place the component package configuration information in the component configuration path; uninstall the WIM file, and calculate the hash value of all files in the newly configured Driver CD to complete the Driver CD production.

[0059] By adopting the technical solution provided by the present invention, on the one hand, customized content modification of the Driver CD file and component package compilation can be automatically and efficiently completed, enabling automated installation methods for bare board stage image USB disk deployment and PXE (Preboot Execution Environment) server deployment. This not only improves testing efficiency but also reduces errors caused by manual operation, allowing non-professionals to complete Driver CD production, thereby providing a batch installation solution for testing and significantly saving time and development costs. On the other hand, by matching the driver list with each component package, component package information errors can be avoided in advance, ensuring that the correct first version of the Driver CD is provided to customers, thereby improving customer satisfaction.

[0060] Reference Figure 1 , shows a flowchart of a method for efficiently producing a Driver CD provided by an embodiment of the present invention, which may specifically include the following steps:

[0061] Step 101: Obtain the WIM file of the old version of the Driver CD and mount the WIM file;

[0062] WIM files are used to store complete copies of Windows operating systems, applications, and their configurations. WIM files are commonly used in scenarios such as operating system deployment, system backup, and recovery.

[0063] In the embodiment of the present invention, project information is modified based on the WIM file of any old version of the Driver CD to achieve Driver CD customization to meet the needs of the new project.

[0064] Customization (or Customisation) refers to the process of tailoring products or services to the specific needs and preferences of customers. Customization generally means that products or services are not universal, but are personalized according to the specific requirements of customers.

[0065] Therefore, in a specific implementation, a graphical interface (GUI) can be designed to facilitate the creation of a Driver CD. This graphical interface can provide multiple selectable older Driver CD versions. The user can select one of these older Driver CD versions. Based on the user's selection of the older Driver CD version, the system loads the corresponding WIM file and automatically mounts the WIM file.

[0066] For example, Figure 2 A schematic diagram of a UI design interface for mounting a Driver CD WIM file provided by an embodiment of the present invention is shown.

[0067] Step 102: identifying the modified project information input by the user, and modifying the original project information in the WIM file according to the modified project information;

[0068] After mounting the WIM file, load the path to the Driver CD directory file that needs to be modified. Users can use the graphical interface to enter or select the project information to be modified (that is, write the Driver CD customization information required for the new project). The system will then recognize and automatically modify the corresponding project information to adapt to the new project.

[0069] The project information mainly includes Driver CD Name, Project Name (ModelName), Platform Information (Platform Name), Driver CD Version (DCD Version), Installation Type (SystemType) and Operating System Version (OS_Version).

[0070] Furthermore, after modifying the original project information in the WIM file, delete the original WIM file in the Software folder (a directory on the PXE server that stores operating system images, boot files, and other software resources) and replace it with the modified WIM file required by the new project.

[0071] Combined with the relevant content in step 101, Figure 3 A schematic diagram of a Driver CD customization process provided by an embodiment of the present invention is shown.

[0072] Step S01: Determine the old version Driver CD that needs to be customized and mount the WIM file.

[0073] Step S02: Identify the modified project information input by the user.

[0074] Step S03: confirm whether the WIM file is mounted successfully; if not, jump to step S04; if so, jump to steps S05 to S06.

[0075] Step S04: Try to mount the WIM file again until the mounting is successful.

[0076] Step S05: Modify the original project information in the WIM file according to the modified project information.

[0077] Step S06: Delete the original WIM file in the Software folder and replace it with the modified WIM file required for the new project to complete the Driver CD customization.

[0078] For example, Figure 4 A schematic diagram of a Driver CD customized UI design interface provided by an embodiment of the present invention is shown.

[0079] Step 103: Obtain a driver list, compile a component package according to the driver list, and obtain a configuration component package;

[0080] Next is the component package compilation process. Component package compilation mainly includes three steps: driver list information processing, loading component package information and comparing it with the driver list information extracted, and entering component package information.

[0081] Component packages can be divided into four categories according to different types: Driver Component class (corresponding to driver), StoreAPP Component class (corresponding to APP application), Win32APP Component class and Component class (corresponding to customer customization).

[0082] Component package compilation primarily compiles the aforementioned four types of component package information into an inst.ini file (configuration file). This process primarily checks whether the version and date of the inf file in the driver match those in the Driver List. It also verifies whether the installation script name in the component installation package matches the Driver List, whether the Win32APP Component and Component Version_Path are correctly entered in the Driver List, and whether the StoreAPP Component APPID information is correctly entered in the Driver List. Furthermore, the driver component must contain at least one set of HWID (Hardware ID) information.

[0083] Figure 5 A schematic diagram of the component package compilation process is shown.

[0084] Combine Figure 5 , compiling the component package according to the driver list to obtain the configuration component package process can be achieved by executing the following sub-steps S11 to S13:

[0085] Step S11: In response to the component selection operation, extract information from the driver list to obtain component package extraction information, and automatically load information based on the component package extraction information.

[0086] According to the driver list, extract the information of each component package, such as component name, version, manufacturer, HWID, date, APPID, Extension ID (extension unique identifier), etc.

[0087] Furthermore, Figure 6 A schematic flow chart of the driver list information extraction steps is shown.

[0088] Combine Figure 6 In response to the component selection operation, the process of extracting information from the driver list and obtaining component package extraction information can be implemented by executing the following sub-steps S11-1 to S11-3:

[0089] Step S11 - 1 : In response to a component selection operation, extract required component information according to a header of a driver list.

[0090] Different component package types can be defined by stage number. Each component package type is assigned a stage number. Stage numbers are used to define the order in which components are installed, typically starting with stage 60 and incrementing by 1 for each subsequent stage number.

[0091] The graphical interface can provide a component selection button (for selecting the stage number). After the user selects the component through the selection operation, the interface will automatically fill in the extraction information at the corresponding position based on the header of the driver list.

[0092] Step S11 - 2 : Identify and classify the extracted component information according to the component package type to obtain component package extraction information.

[0093] Different types of component packages use slightly different identification information for classification. Application-class component packages are identified based on whether they have an APPID, while custom-class component packages are identified based on whether they have a Version_Path. If neither APPID nor Version_Path is present, the component is classified as a driver-class component.

[0094] Step S11-3: Storing the component package extracted information in a designated location according to a preset file format, so that when automatically loading information, information is called in the designated location according to the component package type to obtain the component package information.

[0095] Step S12: Capture the currently loaded component package information, and compare and verify the component package information with the component package extraction information.

[0096] Before writing component package information to the inst.ini configuration file, the interface captures the currently loaded component package information and compares it with the component package extraction information. If there are no anomalies, the component package extraction information is written to the inst.ini configuration file. If there are anomalies, an error message is displayed and the failed items are reported to the driver list manager for correction.

[0097] Figure 7 A schematic diagram of the process flow of component package information comparison and verification steps is shown.

[0098] Combine Figure 7 The process of comparing and verifying the component package information with the component package extraction information can be implemented by executing the following sub-steps S12-1 to S12-2:

[0099] Step S12-1: Filter target extraction information of the same component package type as the component package information from the component package extraction information.

[0100] Step S12-2: Based on the component package type, perform information comparison and verification on the component package information and the target extraction information.

[0101] Among them, when performing information comparison and verification:

[0102] For the Driver Component class package, the information compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information;

[0103] For StoreAPP Component packages, the information compared and verified includes the application version and manufacturer, installation script name, APPID information, HWID information, and Extension ID information;

[0104] For Win32APP Component class or Component class component package, the comparison and verification information includes application version and manufacturer, installation script name, and Version_Path.

[0105] For example, the verification information of various component packages is shown in Tables 1 to 3 below:

[0106]

[0107] Table 1: Driver Component class verification information

[0108]

[0109] Table 2: Verification information of the StoreAPP Component class

[0110]

[0111] Table 3: Win32APP Component class or Component class verification information

[0112] If a required item is missing in the component package, the interface will prompt that a required item is missing when the component package is compiled. If a prohibited item is filled in, the interface will prompt that the item does not need to be filled in.

[0113] It should be pointed out that the Win32APP Component class and the Component class component package are made in the same way, but the placement of the component package is different.

[0114] Step S13: If the information comparison and verification is successful, the component package extraction information is written into the configuration file as component package configuration information, and the configuration file is compressed to obtain a configuration component package.

[0115] If the information comparison and verification fails, the component package compilation will be stopped and an error message will be prompted.

[0116] Component packages are compiled according to the four types described above until all provided components are compiled. The component information contained in the inst.ini configuration file is imported one by one through the above steps. This process enables automatic verification and processing of component packages of different types, thereby improving the efficiency and accuracy of component package compilation.

[0117] For example, Figure 8 A schematic diagram of a UI design interface compiled by a component package provided by an embodiment of the present invention is shown.

[0118] In the graphical interface, select the stage number corresponding to the component package to determine the component category. Compile the component according to the provided driver list information. If there are no errors during the compilation process, the component package has been compiled successfully. Continue until all provided components are compiled.

[0119] Figure 8 The related information of the components involved is as follows:

[0120] Stage_Num: The corresponding information of each installation package, each package corresponds to a number.

[0121] FilePath: installation package path.

[0122] DriverExtensionID: Driver or storeAPP Extension ID, which can be obtained from the installation file inf file.

[0123] Version_Path: The path to obtain the stage file version information.

[0124] APPID: The full name of the APP.

[0125] Version: Version information.

[0126] AsCmd: The corresponding installation script name in the installation package.

[0127] Vendor: The manufacturer information of the installation package.

[0128] HW_ID_Quantity: How many HWID information needs to be checked when installing the driver.

[0129] HWID_X: Driver HWID information.

[0130] SupportWinRE: Whether the driver supports WinRE.

[0131] RBTAFINST: Whether the stage needs to be restarted after installation is complete.

[0132] Step 104: automatically decompress the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required for configuring a new project;

[0133] Step 105: automatically create a component configuration path based on the configuration file, and place the component package configuration information into the component configuration path;

[0134] Identify the inst.ini information generated by compiling component packages. Specifically, it identifies the name of each component and its placement path, automatically decompresses the component package, creates a path, and places the corresponding component files. Based on the contents of the inst.ini configuration file, it automatically creates all component paths and places the resources required for the new project in the corresponding paths.

[0135] Step 106: Uninstall the WIM file and perform hash value calculation on all files in the newly configured Driver CD to complete Driver CD production.

[0136] After unmounting the previously mounted WIM file, the hash value of the files contained in the newly configured entire Driver CD is automatically calculated to complete the production of the Driver CD.

[0137] In an embodiment of the present invention, an efficient method for producing a Driver CD is provided. On the one hand, customized content modification of the Driver CD file and component package compilation can be automatically and efficiently completed, enabling automated installation methods for bare-board image USB disk deployment and PXE server deployment. This not only improves testing efficiency but also reduces errors caused by human operation, allowing non-professionals to complete Driver CD production, thereby providing a batch installation solution for testing and significantly saving time and development costs. On the other hand, by matching the driver list (Driver List) with each component package, component package information errors can be avoided in advance, ensuring that the correct first version of the Driver CD is provided to customers, thereby improving customer satisfaction.

[0138] For better explanation, refer to Figure 9 , which shows a schematic diagram of the overall process of an efficient Driver CD production method provided by an embodiment of the present invention. It should be noted that this embodiment only briefly describes the general process of efficient Driver CD production. The specific implementation process of each step can be understood by referring to the relevant content in the previous embodiment. A detailed description is omitted here. It is understood that the present invention is not limited to this.

[0139] Step 901: Obtain the WIM file of the old version Driver CD and mount the WIM file.

[0140] Step 902: Identify the modified project information input by the user, and modify the original project information in the WIM file according to the modified project information.

[0141] Step 903: Delete the original WIM file in the Software folder and replace it with the modified WIM file required by the new project.

[0142] Step 904: Obtain a driver list, compile a component package according to the driver list, and obtain a configuration component package.

[0143] Step 905: Automatically decompress the configuration component package to obtain a configuration file, which includes component package configuration information required when configuring a new project.

[0144] Step 906: Automatically create a component configuration path based on the configuration file, and place the component package configuration information into the component configuration path.

[0145] Step 907: Unmount the previously mounted WIM file and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production.

[0146] Reference Figure 10 , shows a structural block diagram of an efficient Driver CD production device provided by an embodiment of the present invention, which may specifically include:

[0147] The file mounting module 1001 is used to obtain the WIM file of the old version of the Driver CD and mount the WIM file;

[0148] The project information modification module 1002 is used to identify the modified project information input by the user and modify the original project information in the WIM file according to the modified project information;

[0149] The component package compiling module 1003 is used to obtain a driver list, compile the component package according to the driver list, and obtain a configuration component package;

[0150] The component package decompression module 1004 is used to automatically decompress the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required when configuring a new project;

[0151] A component configuration path creation module 1005 is configured to automatically create a component configuration path based on the configuration file and place the component package configuration information into the component configuration path;

[0152] The file uninstallation module 1006 is used to uninstall the WIM file and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production.

[0153] In an optional embodiment, the component package compilation module 1003 includes:

[0154] an information extraction module, configured to extract information from the driver list in response to a component selection operation, obtain component package extraction information, and automatically load information based on the component package extraction information;

[0155] An information comparison and verification module is used to capture the currently loaded component package information and compare and verify the component package information with the component package extraction information;

[0156] The configuration file writing module is used to write the component package extraction information as component package configuration information into the configuration file when the information comparison and verification is successful, compress the configuration file, and obtain the configuration component package.

[0157] In an optional embodiment, the information extraction module includes:

[0158] a component information extraction module, configured to extract required component information according to a header of the driver list in response to a component selection operation;

[0159] A component information classification module is used to identify and classify the extracted component information according to the component package type to obtain component package extraction information;

[0160] The component package extraction information storage module is used to store the component package extraction information in a specified location according to a preset file format, so as to obtain component package information by performing information call at the specified location according to the component package type when automatically loading information.

[0161] In an optional embodiment, the component package types include Driver Component class, StoreAPPComponent class, Win32APP Component class, and Component class, and the information comparison and verification module includes:

[0162] a target extraction information screening module, configured to screen target extraction information having the same component package type as the component package information from the component package extraction information;

[0163] The information comparison and verification submodule is used to compare and verify the component package information with the target extraction information in combination with the component package type; wherein, when performing the information comparison and verification:

[0164] For the Driver Component class package, the information compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information;

[0165] For StoreAPP Component packages, the information compared and verified includes the application version and manufacturer, installation script name, APPID information, HWID information, and Extension ID information;

[0166] For Win32APP Component class or Component class component package, the comparison and verification information includes application version and manufacturer, installation script name, and Version_Path.

[0167] In an optional embodiment, the device further includes:

[0168] The component package compilation stop module is used to stop the component package compilation and prompt an error message when the information comparison verification fails.

[0169] In an optional embodiment, the project information includes the Driver CD name, project name, platform information, Driver CD version, installation type, and operating system version.

[0170] In an optional embodiment, the device further includes:

[0171] The WIM file replacement module is used to delete the original WIM file in the Software folder and replace it with the modified WIM file required by the new project.

[0172] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the aforementioned method embodiment.

[0173] An embodiment of the present invention further provides an electronic device, the device including a processor and a memory:

[0174] The memory is used to store program codes and transmit the program codes to the processor;

[0175] The processor is configured to execute the efficient Driver CD production method of any embodiment of the present invention according to the instructions in the program code.

[0176] An embodiment of the present invention further provides a computer-readable storage medium, which is used to store program code. The program code is used to execute the efficient Driver CD production method of any embodiment of the present invention.

[0177] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0178] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0179] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0180] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0181] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0182] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that the technical solutions described in the above embodiments can still be modified, or some of the technical features thereof can be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for efficiently producing a Driver CD, characterized in that: include: Obtain the WIM file of the old version of the Driver CD and mount the WIM file; Identifying the modified project information input by the user, and modifying the original project information in the WIM file according to the modified project information; Obtaining a driver list, compiling a component package according to the driver list, and obtaining a configuration component package; Automatically decompressing the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required when configuring a new project; Automatically create a component configuration path according to the configuration file, and place the component package configuration information into the component configuration path; Uninstall the WIM file and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production; The step of compiling a component package according to the driver list to obtain a configuration component package includes: In response to a component selection operation, extracting information from the driver list to obtain component package extraction information, and automatically loading information based on the component package extraction information; Capture the currently loaded component package information, and compare and verify the component package information with the component package extraction information; If the information comparison and verification is successful, the component package extraction information is written into the configuration file as component package configuration information, and the configuration file is compressed to obtain a configuration component package.

2. The efficient Driver CD production method according to claim 1, characterized in that: In response to the component selection operation, extracting information from the driver list to obtain component package extraction information includes: In response to a component selection operation, extracting required component information according to a header of the driver list; Identify and classify the extracted component information according to the component package type to obtain component package extraction information; The component package extraction information is stored in a designated location according to a preset file format, so that when the information is automatically loaded, information is called in the designated location according to the component package type to obtain the component package information.

3. The efficient Driver CD production method according to claim 2, characterized in that: The component package types include Driver Component class, StoreAPP Component class, Win32APP Component class, and Component class. The information comparison and verification of the component package information with the component package extraction information includes: Filtering target extraction information having the same component package type as the component package information from the component package extraction information; In combination with the component package type, the component package information is compared and verified with the target extraction information; wherein, when performing the information comparison and verification: For the Driver Component class package, the information compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information; For StoreAPP Component packages, the information compared and verified includes the application version and manufacturer, installation script name, APPID information, HWID information, and Extension ID information; For Win32APP Component class or Component class component package, the comparison and verification information includes application version and manufacturer, installation script name, and Version_Path.

4. The efficient Driver CD production method according to claim 1, characterized in that: Also includes: If the information comparison and verification fails, the component package compilation will be stopped and an error message will be prompted.

5. The efficient method for producing a Driver CD according to any one of claims 1 to 4, characterized in that: The project information includes the Driver CD name, project name, platform information, Driver CD version, installation type, and operating system version.

6. The efficient Driver CD production method according to claim 5, characterized in that: After modifying the original project information in the WIM file according to the modified project information, the method further includes: Delete the original WIM file in the Software folder and replace it with the modified WIM file required for the new project.

7. A device for efficiently producing Driver CD, characterized in that: include: A file mounting module, used to obtain the WIM file of the old version of the Driver CD and mount the WIM file; A project information modification module, configured to identify modified project information input by a user and modify the original project information in the WIM file according to the modified project information; A component package compilation module is used to obtain a driver list, compile the component package according to the driver list, and obtain a configuration component package; A component package decompression module, configured to automatically decompress the configuration component package to obtain a configuration file, wherein the configuration file includes component package configuration information required when configuring a new project; A component configuration path creation module, configured to automatically create a component configuration path based on the configuration file, and place the component package configuration information into the component configuration path; A file uninstallation module is used to uninstall the WIM file and calculate hash values ​​for all files in the newly configured Driver CD to complete Driver CD production; The component package compilation module includes: an information extraction module, configured to extract information from the driver list in response to a component selection operation, obtain component package extraction information, and automatically load information based on the component package extraction information; An information comparison and verification module is used to capture the currently loaded component package information and compare and verify the component package information with the component package extraction information; The configuration file writing module is used to write the component package extraction information as component package configuration information into the configuration file when the information comparison and verification is successful, compress the configuration file, and obtain the configuration component package.

8. An electronic device, characterized in that: The device includes a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the efficient DriverCD production method according to any one of claims 1 to 6 according to the instructions in the program code.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium is used to store program code, and the program code is used to execute the efficient Driver CD production method according to any one of claims 1 to 6.

Images