Method and device for efficiently manufacturing Driver CD

Abstract

The invention discloses a Driver CD efficient manufacturing method and device which are used for solving the problems that in the existing bare board testing stage, due to the fact that a driver needs to be manually installed to manufacture a testing environment, the testing efficiency is low, and errors are prone to occurring. Comprising the following steps: acquiring a WIM file of an old version Driver CD, and mounting the WIM file; identifying the modified item information, and modifying the original item information in the WIM file according to the modified item information; obtaining a driving program list, and compiling the component package according to the driving program list to obtain a configuration component package; the configuration component package is automatically decompressed, a configuration file is obtained, and the configuration file comprises component package configuration information needed when the new project is configured; automatically creating a component configuration path according to the configuration file, and placing the component package configuration information to the component configuration path; and unloading the WIM file, and carrying out hash value calculation on all files in the newly configured Driver CD to complete 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 making a Driver CD, a device for efficiently making 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 usually contains drivers for specific hardware devices. Users can complete the driver installation by installing the software on the CD.

[0003] However, during the bare board testing phase, customers usually do not provide a Driver CD 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. In addition, this method can only produce Driver CDs one-to-one, which is prone to problems such as some drivers not being installed properly due to human errors. At the same time, when providing drivers to customers, there are occasional errors in the production of Driver CDs, and the correct version of the driver needs to be re-provided, affecting the project progress and score. In addition, if the Driver CD is manually modified, there will be too many change points, and there is no manual modification history in previous projects, so the testing efficiency is low. Summary of the invention

[0004] The invention provides a method for efficiently making a Driver CD, a device for efficiently making 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 test stage, a test environment needs to be manually installed to make a driver, resulting in low test efficiency and easy errors.

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

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

[0007] 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;

[0008] Obtain a driver list, compile a component package according to the driver list, and obtain a configuration component package;

[0009] 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;

[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 perform hash value calculation on 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, the information is called at the designated location according to the component package type to obtain the component package information.

[0020] Optionally, the component package types include Driver Component class, StoreAPP Component class, Win32APP Component class and 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 the information comparison and verification is performed:

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

[0024] For the StoreAPP Component package, the information to be 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 information to be compared and verified includes the application version and manufacturer, installation script name, and Version_Path.

[0026] Optionally, the method further comprises:

[0027] If the information comparison 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 category 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, 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;

[0034] A component package compiling 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, 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;

[0036] A component configuration path creation module, used to automatically create a component configuration path according to 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 perform hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

[0038] The present invention also provides an electronic device, the 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 used to execute the Driver CD efficient production method as described in any one of the above items according to the 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 codes, and the program codes are used to execute the Driver CD efficient production method as described in any one of the above items.

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

[0043] The invention provides an efficient method for making a Driver CD. The WIM file of the old version of the Driver CD is obtained, and the WIM file is mounted; the modified project information is identified, and the original project information in the WIM file is modified according to the modified project information; the driver list is obtained, and the component package is compiled according to the driver list to obtain the configuration component package; then the configuration component package is automatically decompressed to obtain the configuration file, and the configuration file includes the component package configuration information required when configuring a new project; according to the configuration file, the component configuration path is automatically created, and the component package configuration information is placed in the component configuration path; the WIM file is uninstalled, and the hash value calculation is performed on all files in the newly configured Driver CD, so that the Driver CD production is automatically and quickly completed, which can not only improve the test efficiency, but also reduce the 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 drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. 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 creative work.

[0045] Figure 1It is a flowchart of the steps of a method for efficiently making a Driver CD;

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

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

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

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

[0050] Figure 6 A schematic diagram of a process flow of extracting driver list information;

[0051] Figure 7 A schematic diagram of a flow chart of information comparison and verification steps of component package information;

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

[0053] Fig. 9 It is a schematic diagram of the overall process of an efficient method for making a Driver CD;

[0054] Fig.10 The structure block diagram of a device for efficiently producing Driver CD 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 creative work are within the scope of protection of the present invention.

[0057] As an example, during the bare board testing phase, customers usually do not 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. In addition, this method can only produce Driver CDs one-to-one, which is prone to problems such as some drivers not being installed properly due to human errors. At the same time, when providing drivers to customers, there are occasional errors in the production of Driver CDs, and the correct version of the driver needs to be re-provided, affecting the project progress and score. In addition, if the Driver CD is manually modified, there will be too many change points, and there is no history of manual modification in previous projects, resulting in low testing efficiency.

[0058] Therefore, one of the core inventive points of an embodiment of the present invention is to provide an efficient method for producing a Driver CD in order to realize the production of 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 and modify the project information, and modify the original project information in the WIM file according to the modified project information; obtain a driver list, compile the component package according to the driver list, and obtain a configuration component package; then automatically decompress the configuration component package to obtain a configuration file, which includes the component package configuration information required when configuring a new project; according to the configuration file, automatically create a component configuration path, and place the component package configuration information to 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.

[0059] By adopting the technical solution provided by the present invention, on the one hand, the customized content modification of the Driver CD file and the compilation of the component package can be automatically and efficiently completed, and the automated installation method of bare board stage image U disk deployment and PXE (Preboot Execution Environment) server deployment can be realized, which can not only improve the test efficiency, but also reduce the errors caused by human operation, so that non-professionals can also complete the Driver CD production, thereby providing a batch installation solution for testing, significantly saving time and development costs. On the other hand, by matching the driver list (Driver List) and each component package, the component package information error problem 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 making 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 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 often used in scenarios such as operating system deployment, system backup, and recovery.

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

[0064] Customization (or Customisation) refers to the process of customizing products or services according to the specific needs and preferences of customers. Customization usually 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 for the Driver CD production process can be first constructed through UI design. The graphical interface can provide multiple selectable old versions of Driver CDs. The user can select one of the old versions of Driver CDs through a selection operation. Based on the user's selection operation for the old version of Driver CD, 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 Driver CD directory file path that needs to be modified. Users can enter or select the project information that needs to be modified (that is, write the Driver CD customization information required for the new project) through the graphical interface so that the system can 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, 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) is deleted and replaced 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, obtaining a driver list, compiling a component package according to the driver list, and obtaining a configuration component package;

[0080] Next is the component package compilation process. The component package compilation mainly includes three steps: driver list information processing, loading component package information and comparing and verifying the driver list extracted information, and component package information entry.

[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 mainly compiles the above four types of component package information into inst.ini files (configuration files). Component package compilation mainly checks whether the inf file version and date information in the driver are consistent with the driver list (Driver List). At the same time, check whether the installation script name of the component installation package is consistent with the driver list, whether the Win32APP Component and Component component Version_Path are correctly filled in the driver list, and whether the StoreAPP Component component APPID information is correctly filled in the driver list. In addition, the driver component must contain at least one set of HWID (Hardware ID, hardware identifier) ​​information.

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

[0084] Combination Figure 5 , compiling the component package according to the driver list to obtain the process of configuring the component package 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] Further, Figure 6 A schematic flow chart of the driver list information extraction steps is shown.

[0088] Combination 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 the component selection operation, extract the required component information according to the header of the driver list.

[0090] Different component package types can be defined by stage number. Each component package type is assigned a stage number. The stage number is mainly used to define the installation order of components, usually starting from stage60, and each subsequent component stage number is incremented by 1.

[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] Among them, for different types of component packages, the identification information used for classification is slightly different. Application component packages are identified based on whether they have APPID, and customized component packages are identified based on whether they have Version_Path. If neither APPID nor Version_Path is present, it is classified as a driver component.

[0094] Step S11-3: Storing the component package extraction information in a designated location according to a preset file format, so as to call the component package information in the designated location according to the component package type when automatically loading the 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 the component package information into the inst.ini configuration file, the interface will capture the currently loaded component package information and compare it with the component package extraction information. If there is no abnormality, the component package extraction information will be written into the inst.ini configuration file. If there is an abnormality, an error reminder will be reported, and the failed items will be fed back to the person in charge of the driver list for correction.

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

[0098] Combination 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, compare and verify the component package information with the target extraction information.

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

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

[0103] For the StoreAPP Component package, the information to be 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 information to be compared and verified includes the application version and manufacturer, installation script name, and Version_Path.

[0105] Exemplarily, 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 the required items of the component package are missing, the interface will prompt that the required items are not filled in when the component package is compiled. If the prohibited items are filled in, the interface will prompt that the items do 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 the component package configuration information, and the configuration file is compressed to obtain the configuration component package.

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

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

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

[0118] Select the stage number corresponding to the component package in the graphical interface to determine which type of component the component belongs to. Compile the component according to the provided driver list information. If there is no error during the compilation process, it means that the component package has been compiled successfully, until all the provided components are compiled.

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

[0120] Stage_Num: 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.

[0132] Step 104, 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;

[0133] Step 105, automatically creating a component configuration path according to the configuration file, and placing the component package configuration information into the component configuration path;

[0134] Identify the inst.ini information generated by the component package compilation. Specifically, identify the name of each component and the path where the component is placed, automatically decompress the component package to create a path and place the corresponding component files. Thus, according to the content of the inst.ini configuration file, all component paths are automatically created, and the resources required for the new project are placed in the corresponding path.

[0135] Step 106, uninstall the WIM file, and calculate the hash values ​​of all files in the newly configured Driver CD to complete the Driver CD production.

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

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

[0138] For better explanation, refer to Fig. 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 pointed out that this embodiment only briefly describes the general process of efficient Driver CD production, and the specific implementation process of each step can be understood by referring to the relevant content in the aforementioned embodiment, which will not be described here. It can be understood that the present invention is not limited to this.

[0139] Step 901: Obtain the WIM file of the old version of the 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 according to 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 perform hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

[0146] Reference Fig.10 , shows a structural block diagram of a Driver CD efficient 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, used to automatically create a component configuration path according to 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 perform hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

[0153] In an optional embodiment, the component package compiling 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 into the configuration file as component package configuration information 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 type includes a Driver Component class, a StoreAPPComponent class, a Win32APP Component class, and a Component class, and the information comparison and verification module includes:

[0162] A target extraction information screening module, used for screening 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 to be compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information;

[0165] For the StoreAPP Component package, the information to be 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 information to be compared and verified includes the 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 a Driver CD name, a project name, platform information, a Driver CD version, an installation type, and an 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 comprising a processor and a memory:

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

[0175] The processor is used to execute the Driver CD efficient 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 codes, and the program codes are used to execute the efficient Driver CD production method of any embodiment of the present invention.

[0177] Those skilled in the art can 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

[0180] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0181] If the integrated unit is implemented in the form of 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, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc., various media that can store program codes.

[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 aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may 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: Get the WIM file of the old version of Driver CD and mount the WIM file; 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; Obtain a driver list, compile a component package according to the driver list, and obtain a configuration component package; 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; 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 perform hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

2. The efficient Driver CD production method according to claim 1, characterized in that: The step of compiling the component package according to the driver list to obtain the 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.

3. The efficient Driver CD production method according to claim 2, 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, the information is called at the designated location according to the component package type to obtain the component package information.

4. The efficient Driver CD production method according to claim 3, characterized in that: The component package types include Driver Component class, StoreAPP Component class, Win32APP Component class and Component class, and 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 the information comparison and verification is performed: For the Driver Component class package, the information to be compared and verified includes the driver version and manufacturer, installation script name, HWID information, and Extension ID information; For the StoreAPP Component package, the information to be 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 information to be compared and verified includes the application version and manufacturer, installation script name, and Version_Path.

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

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

7. The efficient Driver CD production method according to claim 6, 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.

8. 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, 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; A component package compiling 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, 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; A component configuration path creation module, used to automatically create a component configuration path according to the configuration file, and place the component package configuration information into the component configuration path; The file uninstallation module is used to uninstall the WIM file and perform hash value calculation on all files in the newly configured Driver CD to complete the Driver CD production.

9. An electronic device, characterized in that: The device comprises a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the DriverCD efficient production method described in any one of claims 1-7 according to the instructions in the program code.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program codes, and the program codes are used to execute the efficient Driver CD production method according to any one of claims 1 to 7.

Images