CN109375928B - Method and device for integrating and managing third-party driving software based on NSIS script - Google Patents
Method and device for integrating and managing third-party driving software based on NSIS script Download PDFInfo
- Publication number
- CN109375928B CN109375928B CN201811283030.2A CN201811283030A CN109375928B CN 109375928 B CN109375928 B CN 109375928B CN 201811283030 A CN201811283030 A CN 201811283030A CN 109375928 B CN109375928 B CN 109375928B
- Authority
- CN
- China
- Prior art keywords
- installation
- version
- information
- camera
- current system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for integrating and managing third-party driving software based on NSIS script, wherein the method comprises the following steps: judging whether the system version of the current system supports installation of an installation package made by NSIS; if the installation is supported, judging whether the current system has an installation file of the camera driver; if so, judging whether the version of the current camera drive is consistent with the version of the camera drive of the installation package; if not, the camera driven version of the installation package is quiesced. The method and the device provided by the application can strictly check and control the compatibility of the camera drive of the current system and the vision system, can avoid the manual operation of a user through silent installation, and save time.
Description
Technical Field
The application relates to the technical field of software management, in particular to a method and a device for integrating and managing third-party driving software based on an NSIS script.
Background
The camera processing components vision and VisionBOX are industrial grade split type machine vision systems, the image processing, communication and storage functions are completed by a controller, and the controller can be one or more cameras connected. When the camera processing component visionissambly or VisionBOX is released, the camera processing component visionissambly or VisionBOX needs to be made into an installation program and released in the form of an exe file, and a client needs to install the camera processing component on an industrial personal computer or a computer of the client by executing the exe file.
However, VISIONAssembly and VisionBOX require a user to first install a driver of a corresponding camera to be able to control the camera and then process a captured image. That is, both of the above-described vision processing systems require camera-driven support. However, a great amount of waiting time is required for a user to download a corresponding camera driver, and a problem of abnormal use due to incompatibility of a vision system and a current camera driver is likely to occur.
Disclosure of Invention
The application provides a method and a device for integrating and managing third-party driving software based on an NSIS script, which are used for solving the problems that the existing camera driving program downloading time is long and the compatibility with a visual system is poor.
In a first aspect, the present application provides a method for integrating and managing third-party driver software based on NSIS scripts, where the method includes:
judging whether the system version of the current system supports installation of an installation package made by NSIS;
if the installation is supported, judging whether the current system has an installation file of the camera driver;
if so, judging whether the version of the current camera drive is consistent with the version of the camera drive of the installation package;
if not, the camera driven version of the installation package is quiesced.
With reference to the first aspect, in a first implementable manner of the first aspect, the step of, if installation is supported, determining whether the current system has an installation file of a camera driver includes:
acquiring registry information of the current system;
traversing and reading the registry information;
determining installation information of the current system according to the registry information, wherein the installation information comprises: installed and uninstalled.
With reference to the first aspect, in a second implementable manner of the first aspect, if the installation is supported, the specific step of determining whether the current system has an installation file of the camera driver further includes:
judging current installation information;
if the registry is not installed, judging whether all the registry information is read;
if all the registry information is read, determining that the installation information is not installed; and if not, continuously reading the registry information, and determining the installation information of the current system according to the registry information.
With reference to the first aspect, in a third implementable manner of the first aspect, if the current camera driver version is consistent with the camera driver version of the installation package, the specific step of determining whether the current camera driver version is consistent with the camera driver version of the installation package includes:
acquiring the version information of the camera drive of the current system according to the registry information;
acquiring version information in a configuration file corresponding to the camera driver of the installation package;
and comparing the version information of the camera drive of the current system with the version information of the camera drive of the installation package, and judging whether the version information is the same.
With reference to the first aspect, in a fourth implementable manner of the first aspect, if the inconsistency, silent installation of the camera-driven version of the installation package further includes, before:
and if the current system is inconsistent with the current system, sending prompt information and/or uninstalling the camera drive of the current system.
With reference to the first aspect, in a fifth implementable manner of the first aspect, the step of unloading the camera driver of the current system further includes:
determining an uninstalling character string of the camera according to the registry information of the current system;
calling a corresponding NSIS unloading statement according to the packaging software corresponding to the camera driver of the current system and the unloading character string;
and executing an unloading task according to the NSIS unloading statement.
With reference to the first aspect, in a sixth implementable manner of the first aspect, the method further includes:
judging whether the camera drive of the installation package is installed or not;
and if the installation is finished, storing all files related to the camera driver of the installation package into a folder of the installation path.
A second aspect of the present application provides an apparatus for integrating and managing third-party driver software based on NSIS scripts, the apparatus comprising:
the system version judging unit is used for judging whether the system version of the current system supports installation of the installation package made by NSIS;
an installation file judging unit, configured to judge whether an installation file of a camera driver exists in the current system if installation is supported;
a drive version judging unit, configured to judge whether a version of a current camera drive is consistent with a version of a camera drive of the installation package if the current camera drive exists;
an installation unit for silently installing the camera driving version of the installation package if the two are not consistent.
As can be seen from the above technologies, the present application provides a method and an apparatus for integrating and managing third-party driver software based on NSIS scripts, wherein the method includes: judging whether the system version of the current system supports installation of an installation package made by NSIS; if the installation is supported, judging whether the current system has an installation file of the camera driver; if so, judging whether the version of the current camera drive is consistent with the version of the camera drive of the installation package; if not, the camera driven version of the installation package is quiesced. When the system is used, the system version of the current system is checked, whether the installation operation of the installation package made by NSIS is supported or not is determined, and if the installation operation of the installation package made by NSIS is not supported, the system version needs to be replaced or a matched installation package needs to be replaced; if the camera driver version is not installed, or the camera driver version installed by the current system is inconsistent with the camera driver version of the installation package, the camera driver version of the installation package is selected to be installed in a silent mode. The method and the device provided by the application can strictly check and control the compatibility of the camera drive of the current system and the vision system, can avoid the manual operation of a user through silent installation, and save time.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without any creative effort.
Fig. 1 is a flowchart of a method for integrating and managing third-party software based on NSIS scripts according to an embodiment of the present application;
fig. 2 is a flowchart of a method for determining whether a camera driver is installed in a current system according to an embodiment of the present disclosure;
fig. 3 is a flowchart of a method for determining whether registry information is read completely according to an embodiment of the present disclosure;
fig. 4 is a flowchart of a method for comparing camera driving versions according to an embodiment of the present disclosure;
fig. 5 is a flowchart of a method for handling inconsistency of camera driver versions according to an embodiment of the present application;
fig. 6 is a flowchart of a method for uninstalling a camera driver of a current system according to an embodiment of the present disclosure;
fig. 7 is a flowchart of a method for saving a camera driver related file according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an apparatus for integrating and managing third-party driver software based on NSIS scripts according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, a flowchart of a method for integrating and managing third-party software based on NSIS scripts according to an embodiment of the present application is shown, where the method includes:
step 101, judging whether the system version of the current system supports installation of an installation package made by NSIS;
step 102, if the installation is supported, judging whether the current system has an installation file of a camera driver;
103, if yes, judging whether the version of the current camera driver is consistent with the version of the camera driver of the installation package;
and 104, if the installation package is inconsistent, the camera driving version of the installation package is installed in a silent mode.
When the system version is used, the system version of the current system is checked, generally the system version refers to windows version, and whether the system version supports the installation operation of the installation package made by NSIS is determined. The installation package made by NSIS can run under windows, a plurality of windows functions are packaged by the installation package, calling is convenient, and guided scripts are produced, so that the installation package is very convenient.
If not, the system version needs to be replaced or the installation package matched with the current system version needs to be replaced; if the camera driver version is not installed, or the camera driver version installed by the current system is inconsistent with the camera driver version of the installation package, the camera driver version of the installation package is selected to be installed in a silent mode. In the installation process provided by the embodiment of the application, the silent installation mode is automatically selected, so that a user does not need to download the camera driver at all and does not need to execute the step and selection for installing the camera driver step by step.
The method and the device provided by the application can strictly check and control the compatibility of the camera drive of the current system and the vision system, can avoid the manual operation of a user through silent installation, and save time.
Please refer to fig. 2, which is a flowchart illustrating a method for determining whether a camera driver is installed in a current system according to an embodiment of the present disclosure. The specific step of judging whether the current system has the installation file of the camera driver if the installation is supported comprises the following steps:
step 201, obtaining registry information of the current system;
step 202, traversing and reading the registry information;
step 203, determining installation information of the current system according to the registry information, wherein the installation information comprises: installed and uninstalled.
The registry of the windows operating system can be accessed very conveniently by using the NSIS script, so that the registry information of the current system is obtained, and the registry information usually records the installation, updating and other records of each software. The NSIS script judges whether the installation record of the camera driver exists in the registry information by reading all registry information, and further judges whether a camera driver of a certain camera is installed. If the installation record exists, determining that the installation information is installed; if the installation record does not exist, the installation information is determined to be uninstalled.
Please refer to fig. 3, which is a flowchart illustrating a method for determining whether the registry information is read completely according to an embodiment of the present disclosure. If the installation is supported, the specific step of judging whether the current system has the installation file of the camera driver further comprises the following steps:
step 301, judging current installation information;
step 302, if the registry is not installed, judging whether all the registry information is read;
step 303, if all the registry information is read, determining that the installation information is not installed; and if not, continuously reading the registry information, and determining the installation information of the current system according to the registry information.
An inspection period for inspecting the current reading progress can be set, when the preset inspection period is reached, the current reading progress is inspected, that is, the current installation information is judged, and if the registry information read before does not contain the installation record of the camera drive, the current installation information is not installed. If the previously read registry information contains an installation record of the camera drive, the reading is stopped even if the preset check period is not reached, and the installation information is determined to be installed.
If the current installation information is not installed, judging whether all registry information is read currently or not, and if all registry information is read, directly determining that the installation information is not installed; and if the unread registry information exists, continuing reading until the installation record is read or all the registry information is read, and determining the final installation information.
Please refer to fig. 4, which is a flowchart illustrating a method for comparing camera driver versions according to an embodiment of the present disclosure. The specific step of judging whether the version of the current camera driver is consistent with the version of the camera driver of the installation package if the current camera driver exists comprises the following steps:
step 401, acquiring version information of the camera driver of the current system according to the registry information;
402, acquiring version information in a configuration file corresponding to the camera driver of the installation package;
and 403, comparing the version information of the camera driver of the current system with the version information of the camera driver of the installation package, and judging whether the version information is the same.
By using the NSIS script, the registry of the windows operating system can be accessed very conveniently, the version information of the camera driver of the current system is obtained from the registry information, and the configuration file of the installation package also contains the version information of the camera driver. By comparing whether the version information of the camera driver and the version information of the camera driver are consistent or not, whether the camera driver of the current system is consistent with the camera driver of the installation package or not can be accurately judged, and whether the camera driver needs to be installed again or not is further judged.
Please refer to fig. 5, which is a flowchart illustrating a method for handling inconsistency between camera driver versions according to an embodiment of the present application. The if not, quiescing installation of the camera driven version of the installation package further comprises:
and 501, if the current system is inconsistent with the current system, sending prompt information and/or uninstalling the camera drive of the current system.
If the version of the camera driver of the current system is found to be inconsistent with the version of the camera driver provided by the installation package, it is proved that the camera driver of the current system has the problems of incompatibility, outdated, abnormal use and the like, so that a prompt needs to be given to a user, and at this time, prompt information can be sent, for example: the current version is not available and prompt information for re-installation or omission options is required. Typically the user will choose to reinstall the available versions and therefore may choose to install the version of the camera driver provided by the installation package either after prompting or directly. In order to avoid the problems of conflict, interference and the like caused by a camera drive program existing in the current system to the versions of the reinstalled camera drives, the camera drives of the current system are uninstalled before the installation package is used for providing the camera drives, and therefore the system fluency after the camera drives are reinstalled is guaranteed.
Please refer to fig. 6, which is a flowchart illustrating a method for offloading a camera driver of a current system according to an embodiment of the present disclosure. The specific step of unloading the camera drive of the current system further comprises:
601, determining an uninstalling character string of the camera according to the registry information of the current system;
step 602, calling a corresponding NSIS uninstall statement according to the packaging software corresponding to the camera driver of the current system and the uninstall character string;
and 603, executing an unloading task according to the NSIS unloading statement.
The NSIS script may access the windows operating system, and then access the registry information, and extract the uninstall string related to the camera driver from the registry information. According to the packaging software corresponding to the camera driver of the current system, all files of the current camera driver are packaged through the packaging software, the NSIS unloading statement is called according to the unloading character string, and all the packaged files of the current camera driver are unloaded, so that the efficiency is high, and the unloading is thorough.
Please refer to fig. 7, which is a flowchart illustrating a method for saving a file related to a camera driver according to an embodiment of the present disclosure. The method further comprises the following steps:
step 701, judging whether the camera driver of the installation package is installed completely;
and step 702, if the installation is finished, storing all files related to the camera driver of the installation package into a folder of the installation path.
After the installation package is completely installed, the camera driver at the moment can completely support the control and operation of visionissably and VisionBOX, and at the moment, all files related to the camera driver of the installation package are saved into a certain folder of the installation path, so that the backup or the search of a user can be facilitated. It should be noted that it is necessary to detect that the camera driver of the current installation package has been installed, and that the storage form with partially installed camera driver is not supported, so as to prevent the problem of incomplete storage or repeated storage.
Please refer to fig. 8, which is a schematic structural diagram of an apparatus for integrating and managing third-party driver software based on NSIS scripts according to an embodiment of the present application. The device comprises:
the system version judging unit 1 is used for judging whether the system version of the current system supports installation of an installation package made by NSIS;
an installation file judging unit 2, configured to judge whether an installation file of a camera driver exists in the current system if installation is supported;
a drive version judging unit 3, configured to judge whether a version of a current camera drive is consistent with a version of a camera drive of the installation package if the current camera drive exists;
an installation unit 4 for silent installation of the camera driven version of the installation package if not identical.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: the information acquisition unit is used for acquiring registry information of the current system; the reading unit is used for reading the registry information in a traversing manner; an installation information determining unit, configured to determine installation information of the current system according to the registry information, where the installation information includes: installed and uninstalled.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: an installation information judgment unit for judging the current installation information; a registry information reading progress judging unit, configured to judge whether all the registry information is read if the registry information is not installed; a final installation information determination unit configured to determine that the installation information is not installed if all the registry information has been read; and if not, continuously reading the registry information, and determining the installation information of the current system according to the registry information.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: a current camera drive version obtaining unit, configured to obtain, according to the registry information, version information of a camera drive of the current system; the installation package camera drive version acquisition unit is used for acquiring version information in a configuration file corresponding to the camera drive of the installation package; and the comparison unit is used for comparing the version information of the camera drive of the current system with the version information of the camera drive of the installation package and judging whether the version information is the same.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: and the instruction sending unit is used for sending prompt information and/or unloading the camera drive of the current system if the camera drive is inconsistent with the current camera drive.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: the uninstalling character string determining unit is used for determining the uninstalling character string of the camera according to the registry information of the current system; the statement calling unit is used for calling a corresponding NSIS unloading statement according to the packaging software corresponding to the camera drive of the current system and the unloading character string; and the unloading unit is used for executing an unloading task according to the NSIS unloading statement.
In another embodiment of the apparatus for integrating and managing third-party driver software based on NSIS script provided by the present application, the apparatus further includes: the installation progress judging unit is used for judging whether the camera drive of the installation package is installed or not; and the saving unit is used for saving all files related to the camera drive of the installation package into a folder of the installation path if the installation is finished.
As can be seen from the foregoing technical solutions, an embodiment of the present application provides a method and an apparatus for integrating and managing third-party driver software based on an NSIS script, where the method includes: judging whether the system version of the current system supports installation of an installation package made by NSIS; if the installation is supported, judging whether the current system has an installation file of the camera driver; if so, judging whether the version of the current camera drive is consistent with the version of the camera drive of the installation package; if not, the camera driven version of the installation package is quiesced. When the system is used, the system version of the current system is checked, whether the installation operation of the installation package made by NSIS is supported or not is determined, and if the installation operation of the installation package made by NSIS is not supported, the system version needs to be replaced or a matched installation package needs to be replaced; if the camera driver version is not installed, or the camera driver version installed by the current system is inconsistent with the camera driver version of the installation package, the camera driver version of the installation package is selected to be installed in a silent mode. The method and the device provided by the application can strictly check and control the compatibility of the camera drive of the current system and the vision system, can avoid the manual operation of a user through silent installation, and save time.
It should be noted that, in specific implementations, the present invention also provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps in each embodiment of the user identity service providing method or the user registration method provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (5)
1. The method for integrating and managing third-party driving software based on the NSIS script is characterized by comprising the following steps:
judging whether the windows system version of the current system supports installation of an installation package made by NSIS;
if the installation is supported, judging whether the current system has an installation file of the camera driver;
if so, judging whether the version of the current camera drive is consistent with the version of the camera drive of the installation package;
if the current system is inconsistent with the current system, sending prompt information and/or uninstalling the camera driver of the current system, and installing the camera driver version of the installation package in a silent mode after the uninstallation is finished; the specific step of unloading the camera drive of the current system further comprises: determining an uninstalling character string of the camera according to the registry information of the current system; calling a corresponding NSIS unloading statement according to the packaging software corresponding to the camera driver of the current system and the unloading character string; executing an unloading task according to the NSIS unloading statement;
wherein, if the installation is supported, the specific step of judging whether the current system has the installation file of the camera driver comprises the following steps:
acquiring registry information of the current system;
traversing and reading the registry information;
determining installation information of the current system according to the registry information, wherein the installation information comprises: installed and uninstalled.
2. The method according to claim 1, wherein the specific step of determining whether the current system has an installation file of the camera driver if installation is supported further comprises:
judging current installation information;
if the registry is not installed, judging whether all the registry information is read;
if all the registry information is read, determining that the installation information is not installed; and if not, continuously reading the registry information, and determining the installation information of the current system according to the registry information.
3. The method according to claim 2, wherein the specific step of determining whether the current camera driver version is consistent with the camera driver version of the installation package, if any, comprises:
acquiring the version information of the camera drive of the current system according to the registry information;
acquiring version information in a configuration file corresponding to the camera driver of the installation package;
and comparing the version information of the camera drive of the current system with the version information of the camera drive of the installation package, and judging whether the version information is the same.
4. The method of claim 1, further comprising:
judging whether the camera drive of the installation package is installed or not;
and if the installation is finished, storing all files related to the camera driver of the installation package into a folder of the installation path.
5. An apparatus for integrating and managing third-party driver software based on NSIS script, the apparatus comprising:
the system version judging unit is used for judging whether the windows system version of the current system supports installation of the installation package made by NSIS;
an installation file judging unit, configured to judge whether an installation file of a camera driver exists in the current system if installation is supported;
a drive version judging unit, configured to judge whether a version of a current camera drive is consistent with a version of a camera drive of the installation package if the current camera drive exists;
an installation unit for silently installing the camera drive version of the installation package if the installation package is inconsistent;
the instruction sending unit is used for sending prompt information and/or unloading the camera drive of the current system if the instruction sending unit is inconsistent;
the uninstalling character string determining unit is used for determining the uninstalling character string of the camera according to the registry information of the current system; the statement calling unit is used for calling a corresponding NSIS unloading statement according to the packaging software corresponding to the camera drive of the current system and the unloading character string; the unloading unit is used for executing an unloading task according to the NSIS unloading statement;
the device further comprises: the information acquisition unit is used for acquiring registry information of the current system; the reading unit is used for reading the registry information in a traversing manner; an installation information determining unit, configured to determine installation information of the current system according to the registry information, where the installation information includes: installed and uninstalled.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811283030.2A CN109375928B (en) | 2018-10-31 | 2018-10-31 | Method and device for integrating and managing third-party driving software based on NSIS script |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811283030.2A CN109375928B (en) | 2018-10-31 | 2018-10-31 | Method and device for integrating and managing third-party driving software based on NSIS script |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109375928A CN109375928A (en) | 2019-02-22 |
| CN109375928B true CN109375928B (en) | 2022-02-25 |
Family
ID=65391275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811283030.2A Active CN109375928B (en) | 2018-10-31 | 2018-10-31 | Method and device for integrating and managing third-party driving software based on NSIS script |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109375928B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH113220A (en) * | 1997-06-11 | 1999-01-06 | Hitachi Ltd | Control software supply system |
| CN102609285A (en) * | 2012-02-06 | 2012-07-25 | 中兴通讯股份有限公司 | Method for intelligent drive matched loading |
| CN106294133A (en) * | 2016-07-29 | 2017-01-04 | 腾讯科技（深圳）有限公司 | Detection method, relevant apparatus and the system of a kind of application program installation kit |
-
2018
- 2018-10-31 CN CN201811283030.2A patent/CN109375928B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH113220A (en) * | 1997-06-11 | 1999-01-06 | Hitachi Ltd | Control software supply system |
| CN102609285A (en) * | 2012-02-06 | 2012-07-25 | 中兴通讯股份有限公司 | Method for intelligent drive matched loading |
| CN106294133A (en) * | 2016-07-29 | 2017-01-04 | 腾讯科技（深圳）有限公司 | Detection method, relevant apparatus and the system of a kind of application program installation kit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109375928A (en) | 2019-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117169B (en) | Method and device for repairing kernel vulnerability | |
| CN108399132B (en) | Scheduling test method, device and storage medium | |
| US7185335B2 (en) | Programmatic application installation diagnosis and cleaning | |
| CN106897095B (en) | Method and device for hot repairing application program, readable storage medium and computing equipment | |
| CN105760200A (en) | Terminal device and system updating method thereof | |
| CN112732310B (en) | Firmware upgrading method, system, equipment and medium based on embedded guide partition | |
| CN111309387B (en) | Method and device for loading drive, electronic equipment and storage medium | |
| CN103970564A (en) | Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions | |
| US5987625A (en) | Method and apparatus for testing network bootable devices | |
| CN105302687A (en) | Linux-based hard disk sequence detection method | |
| CN111552491A (en) | Method, device and storage medium for upgrading firmware of transfer equipment of mobile carrier | |
| WO2016082450A1 (en) | Method for upgrading user terminal, and user terminal | |
| CN112015587B (en) | Method and device for enhancing reliability of operating system | |
| CN111638916A (en) | General android mobile terminal driving system and method for data forensics | |
| US8949588B1 (en) | Mobile telephone as bootstrap device | |
| CN111090546A (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| CN110990253A (en) | Method and device for realizing application debugging, computer storage medium and terminal | |
| CN109375928B (en) | Method and device for integrating and managing third-party driving software based on NSIS script | |
| CN112564956A (en) | Remote upgrading method, equipment and device for client and storage medium | |
| CN112269707A (en) | USB enumeration detection method, USB host device and storage medium | |
| CN116775061A (en) | Deployment method, device, equipment and storage medium of micro-service application | |
| CN110196730B (en) | Hot patch management method, device and storage medium of application program | |
| CN110045971B (en) | System upgrade recovery method and device | |
| CN105278993A (en) | Linux system based drive module upgrading method and apparatus | |
| CN115757138A (en) | Method and device for determining script abnormal reason, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100094 Beijing city Haidian District Cui Hunan loop 13 Hospital No. 7 Building 7 room 701 Applicant after: Lingyunguang Technology Co., Ltd Address before: 100094 Beijing city Haidian District Cui Hunan loop 13 Hospital No. 7 Building 7 room 701 Applicant before: LUSTER LIGHTTECH GROUP Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |