CN105094865B - Method and device for loading user-defined IE (Internet Explorer) kernel - Google Patents

Method and device for loading user-defined IE (Internet Explorer) kernel Download PDF

Info

Publication number
CN105094865B
CN105094865B CN201410193735.0A CN201410193735A CN105094865B CN 105094865 B CN105094865 B CN 105094865B CN 201410193735 A CN201410193735 A CN 201410193735A CN 105094865 B CN105094865 B CN 105094865B
Authority
CN
China
Prior art keywords
kernel
path
registry
module
loading
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
Application number
CN201410193735.0A
Other languages
Chinese (zh)
Other versions
CN105094865A (en
Inventor
赵歆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Yayue Technology Co ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201410193735.0A priority Critical patent/CN105094865B/en
Publication of CN105094865A publication Critical patent/CN105094865A/en
Application granted granted Critical
Publication of CN105094865B publication Critical patent/CN105094865B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The invention discloses a method for loading a custom IE kernel, which comprises the following steps: reading a self-defined IE kernel path in a redirection registry; the IE kernel path in the redirection registry is a storage path corresponding to the user-defined IE kernel; and loading a self-defined IE kernel according to the IE kernel path in the redirection registry, and creating an IE object. The invention also discloses a device for loading the user-defined IE kernel. The invention obtains the storage path corresponding to the self-defined IE kernel from the redirection registry, and further when loading the IE kernel, the loaded IE kernel is the self-defined IE kernel, and the object returned to the application program is the IE object created according to the self-defined IE kernel, thereby being beneficial to improving the performance of the application program and enriching the functions of the application program.

Description

Method and device for loading user-defined IE (Internet Explorer) kernel
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for loading a custom IE kernel.
Background
The IE (browser) kernel is a browser kernel component provided by the Windows operating system, is highly integrated with the Windows operating system, and refers to a rendering engine adopted by the browser, which is used for parsing the syntax of a web page, rendering and displaying the web page, and determining how the browser displays the content of the web page and the format information of the web page.
The browser developed based on the IE kernel can generally only use the IE kernel integrated in the operating system to render a web page, and when the IE kernel installed in the operating system is older, advanced features cannot be provided, and the browser is slow and has many vulnerabilities, so that the application of the browser is greatly limited. Although a user can select to upgrade the IE kernel of the system, the IE kernel is highly integrated with the operating system, which is related to various aspects of the operating system, and once the IE kernel is upgraded, the IE kernel may have a great influence on the entire operating system and all software related to the IE kernel, and may also have serious consequences such as incompatibility of the software, incapability of starting the system, and the like.
Disclosure of Invention
The embodiment of the invention provides a method and a device for loading a user-defined IE kernel, which enable a browser to load IE kernels of other versions different from an operating system IE kernel without influencing the operating system or other software.
The embodiment of the invention provides a method for loading a custom IE kernel, which comprises the following steps:
reading a self-defined IE kernel path in a redirection registry; the IE kernel path in the redirection registry is a storage path corresponding to the user-defined IE kernel;
and loading a self-defined IE kernel according to the IE kernel path in the redirection registry, and creating an IE object.
The embodiment of the present invention further provides a device for loading a custom IE kernel, including:
the path acquisition module is used for reading a custom IE kernel path in the redirection registry; the IE kernel path in the redirection registry is a storage path corresponding to the user-defined IE kernel;
and the loading module is used for loading the self-defined IE kernel according to the IE kernel path in the redirection registry and creating the IE object.
The embodiment of the invention acquires the IE kernel path from the redirection registry instead of the registry of the operating system, the acquired IE kernel path is a storage path corresponding to the user-defined IE kernel, and further when the IE kernel is loaded, the user-defined IE kernel is loaded, and the object returned to the application program is an IE object created according to the user-defined IE kernel, thereby being beneficial to improving the performance of the application program and enriching the functions of the application program.
Drawings
FIG. 1 is a flowchart of a first embodiment of a method for loading a custom IE kernel in accordance with the present invention;
FIG. 2 is a flowchart of a second embodiment of a method for loading a custom IE kernel in accordance with the present invention;
FIG. 3 is a flowchart of a third embodiment of a method for loading a custom IE kernel in accordance with the present invention;
FIG. 4 is a schematic structural diagram of an apparatus for loading a custom IE kernel according to a first embodiment of the present invention;
FIG. 5 is a diagram illustrating a second embodiment of an apparatus for loading a custom IE kernel in accordance with the present invention;
FIG. 6 is a schematic structural diagram of an apparatus for loading a custom IE kernel according to a third embodiment of the present invention;
fig. 7 is a bus diagram of a terminal where a device for loading a custom IE kernel is located in the embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, fig. 1 is a flowchart of a method for loading a custom IE kernel according to a first embodiment of the present invention. The method for loading the custom IE kernel provided by the embodiment comprises the following steps:
step S10, reading the self-defined IE kernel path in the redirection registry;
when an application needs to use an IE kernel, such as a browser for web page rendering, an object creation function CoCreateInstance function is usually called to create an IE object. The storage path of the IE kernel is first found. Different from the traditional way of searching the IE kernel path from the registry of the operating system, the embodiment needs to load the self-defined IE kernel, the self-defined IE kernel is different from the IE kernel of the operating system, and the version of the self-defined IE kernel is possibly higher than that of the IE kernel of the operating system, so that the self-defined IE kernel has better characteristics and can realize more and richer functions. Therefore, the application program of this embodiment calls the CoCreateInstance function to acquire the storage path of the custom IE kernel, the storage path of the custom IE kernel is not stored in the registry of the operating system but stored in the redirected registry, and the CoCreateInstance function acquires the IE kernel path from the redirected registry by controlling the position of the CoCreateInstance function to query the IE kernel path, where the acquired IE kernel path is the storage path of the custom IE kernel.
And step S20, loading the self-defined IE kernel according to the IE kernel path in the redirection registry, and creating the IE object.
After the storage path of the user-defined IE kernel is obtained, a CoCreateInstance function is called to load the user-defined IE kernel for creating an IE object, and the created IE object is returned to an application program so as to realize webpage rendering and display.
In this embodiment, when an IE kernel path needs to be obtained, the IE kernel path is obtained from the redirection registry instead of the registry of the operating system, so that the obtained IE kernel path is a storage path corresponding to the custom IE kernel, and further, when the IE kernel is loaded, the custom IE kernel is loaded, and the object returned to the application program is an IE object created according to the custom IE kernel, which is beneficial to improving the performance of the application program and enriching the functions of the application program.
As shown in fig. 2, fig. 2 is a flowchart of a second embodiment of the method for loading a custom IE kernel according to the present invention. Step S10 and step S20 in the present embodiment are the same as those in the embodiment shown in fig. 1, except that step S10 is preceded by:
step S30, reading the identification code of the parameter to be acquired in the registry of the operating system;
step S40, judging whether the parameter to be acquired in the operating system registry is an IE kernel path according to the identification code; if so, go to step S10; if not, go to step S50;
in step S50, the parameters determined to be non-IE kernel paths in the operating system registry are obtained.
In this embodiment, the CoCreateInstance function is called to obtain not only the IE kernel path but also some other parameters from the registry of the operating system, and for the other parameters, the parameters are directly obtained from the registry of the operating system, and only when the parameters obtained from the registry are the IE kernel path, the parameters are transferred to the redirection registry to be obtained. The parameters stored in the registry usually correspond to an identification code CLSID, which can be identified by a key value query function NtQueryValueKey function associated with the coccreateinstance function. When the identification code is identified to be the specific value for identifying the IE kernel path, the parameter corresponding to the identification code is the IE kernel path, and the CoCreateInstance function does not acquire the parameter in the registry of the operating system, but turns to redirect the registry for acquisition. If the identification code is not identified to be a specific value for identifying the IE kernel path, the parameter in the registry of the operating system is directly acquired without going to other registries. In the embodiment, the identification code of the parameter in the registry is identified, whether the parameter to be acquired is the IE kernel path is judged, and when the identification code is identified to be the specific value for identifying the IE kernel path, the redirection registry is switched to acquire the user-defined IE kernel path, so that the loaded IE kernel is the user-defined IE kernel, the performance of the application program is improved, the function of the application program is enriched, and meanwhile, the influence on the operating system or other software is avoided.
As shown in fig. 3, fig. 3 is a flowchart of a third embodiment of the method for loading a custom IE kernel according to the present invention. Step S10 and step S20 in the present embodiment are the same as those in the embodiment shown in fig. 1, except that step S10 is preceded by:
step S60, judging whether the module of the IE kernel to be loaded is a dynamic link library imported statically or not; if so, go to step S70; if not, go to step S10;
step S70, obtaining the path of the appointed folder from the path modifying function of the dynamic link library;
and step S80, loading the self-defined IE kernel stored in the specified folder, and creating the IE object.
The embodiment considers that, although the operating system defaults to reading the IE kernel path from the registry for most modules, the custom IE kernel can be loaded in a manner of going to the redirection registry to obtain the custom IE kernel path, for the statically imported dynamic link library DLL, the operating system defaults to not reading the IE kernel path from the registry but using the default folder system32 path of the operating system, and for the default folder, the way of going to the redirection registry cannot be adopted. Aiming at the situation, all files related to the user-defined IE kernel can be stored in a designated folder in advance, the path of the designated folder is written into a path modification function SetDllDirectory function of a dynamic link library, when the CoCreateInstance function loads the IE kernel, the path stored in the SetDllDirectory function can be called to find the designated folder, and the user-defined IE kernel is obtained from the designated folder for loading, so that the user-defined IE kernel is loaded by the statically imported DLL, the application program performance is improved, the application program function is enriched, and meanwhile, the operating system or other software cannot be influenced.
As shown in fig. 4, fig. 4 is a schematic structural diagram of a device for loading a custom IE kernel according to a first embodiment of the present invention. The apparatus for loading a custom IE kernel mentioned in this embodiment includes:
a path obtaining module 110, configured to read a custom IE kernel path in the redirection registry;
and the loading module 120 is configured to load the self-defined IE kernel according to the IE kernel path in the redirection registry, and create an IE object.
When an application needs to use an IE kernel, such as a browser for web page rendering, an object creation function CoCreateInstance function is usually called to create an IE object. The storage path of the IE kernel is first found. Different from the traditional way of searching the IE kernel path from the registry of the operating system, the embodiment needs to load the self-defined IE kernel, the self-defined IE kernel is different from the IE kernel of the operating system, and the version of the self-defined IE kernel is possibly higher than that of the IE kernel of the operating system, so that the self-defined IE kernel has better characteristics and can realize more and richer functions. Therefore, the application program of this embodiment calls the CoCreateInstance function to acquire the storage path of the custom IE kernel, the storage path of the custom IE kernel is not stored in the registry of the operating system but stored in the redirected registry, and the CoCreateInstance function acquires the IE kernel path from the redirected registry by controlling the position of the CoCreateInstance function to query the IE kernel path, where the acquired IE kernel path is the storage path of the custom IE kernel.
After the storage path of the user-defined IE kernel is obtained, a CoCreateInstance function is called to load the user-defined IE kernel for creating an IE object, and the created IE object is returned to an application program so as to realize webpage rendering and display.
In this embodiment, when an IE kernel path needs to be obtained, the IE kernel path is obtained from the redirection registry instead of the registry of the operating system, so that the obtained IE kernel path is a storage path corresponding to the custom IE kernel, and further, when the IE kernel is loaded, the custom IE kernel is loaded, and the object returned to the application program is an IE object created according to the custom IE kernel, which is beneficial to improving the performance of the application program and enriching the functions of the application program.
As shown in fig. 5, fig. 5 is a schematic structural diagram of a device for loading a custom IE kernel according to a second embodiment of the present invention. The path obtaining module 110 and the loading module 120 in this embodiment are the same as those in the embodiment shown in fig. 4, except that the following modules are added:
an identification code obtaining module 130, configured to read an identification code of a parameter to be obtained in an operating system registry;
the identification code judging module 140 is used for judging whether the parameter to be acquired is an IE kernel path according to the identification code;
the parameter acquiring module 150 is used for acquiring the parameter when the identification code judging module judges that the parameter to be acquired is not the IE kernel path;
the path obtaining module 110 is further configured to, when the identifier determining module determines that the parameter to be obtained is an IE kernel path, read a custom IE kernel path in the redirection registry.
In this embodiment, the CoCreateInstance function is called to obtain not only the IE kernel path but also some other parameters from the registry of the operating system, and for the other parameters, the parameters are directly obtained from the registry of the operating system, and only when the parameters obtained from the registry are the IE kernel path, the parameters are transferred to the redirection registry to be obtained. The parameters stored in the registry usually correspond to an identification code CLSID, which can be identified by a key value query function NtQueryValueKey function associated with the coccreateinstance function. When the identification code is identified to be the specific value for identifying the IE kernel path, the parameter corresponding to the identification code is the IE kernel path, and the CoCreateInstance function does not acquire the parameter in the registry of the operating system, but turns to redirect the registry for acquisition. If the identification code is not identified to be a specific value for identifying the IE kernel path, the parameter in the registry of the operating system is directly acquired without going to other registries. In the embodiment, the identification code of the parameter in the registry is identified, whether the parameter to be acquired is the IE kernel path is judged, and when the identification code is identified to be the specific value for identifying the IE kernel path, the redirection registry is switched to acquire the user-defined IE kernel path, so that the loaded IE kernel is the user-defined IE kernel, the performance of the application program is improved, the function of the application program is enriched, and meanwhile, the influence on the operating system or other software is avoided.
As shown in fig. 6, fig. 6 is a schematic structural diagram of a device for loading a custom IE kernel according to a third embodiment of the present invention. The embodiment includes all modules in the embodiment shown in fig. 4, and the difference is that a dynamic link library determining module 160 is further added, and is used for determining whether a module to be loaded with an IE kernel is a statically imported dynamic link library;
the path obtaining module 110 is further configured to, when the dynamic link library determining module 160 determines that the module to be loaded with the IE kernel is the statically imported dynamic link library, obtain a path of the specified folder from a path modification function of the dynamic link library;
the loading module 120 is further configured to load a custom IE kernel stored in the designated folder, and create an IE object;
the path obtaining module 110 is further configured to, when the dynamic link library determining module 160 determines that the module to be loaded with the IE kernel is not the statically imported dynamic link library, read the self-defined IE kernel path in the redirection registry.
The embodiment considers that, although the operating system defaults to reading the IE kernel path from the registry for most modules, the custom IE kernel can be loaded in a manner of going to the redirection registry to obtain the custom IE kernel path, for the statically imported dynamic link library DLL, the operating system defaults to not reading the IE kernel path from the registry but using the default folder system32 path of the operating system, and for the default folder, the way of going to the redirection registry cannot be adopted. Aiming at the situation, all files related to the user-defined IE kernel can be stored in a designated folder in advance, the path of the designated folder is written into a path modification function SetDllDirectory function of a dynamic link library, when the CoCreateInstance function loads the IE kernel, the path stored in the SetDllDirectory function can be called to find the designated folder, and the user-defined IE kernel is obtained from the designated folder for loading, so that the user-defined IE kernel is loaded by the statically imported DLL, the application program performance is improved, the application program function is enriched, and meanwhile, the operating system or other software cannot be influenced.
As shown in fig. 7, fig. 7 is a bus diagram of a terminal where a device loading a custom IE kernel is located in the embodiment of the present invention. The terminal may include: at least one processor 301, e.g., a CPU, at least one network interface 304, a user interface 303, a memory 305, at least one communication bus 302. Wherein a communication bus 302 is used to enable the connection communication between these components. The user interface 303 may include a Display (Display), a Keyboard (Keyboard), a standard wired interface, and a standard wireless interface. The network interface 304 may include a standard wired interface, a wireless interface (e.g., a WIFI interface). Memory 305 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The memory 305 may also be at least one storage device located remotely from the processor 301. Memory 305, which is a type of computer storage medium, may include an operating system, a network communications module, a user interface module, and a loaded custom IE kernel.
In the terminal where the device for loading the custom IE kernel shown in fig. 7 is located, the network interface 304 is mainly used for connecting a server and performing data communication with the server; the user interface 303 is mainly used for receiving a user instruction and interacting with a user; and processor 301 may be configured to call the load custom IE kernel stored in memory 305 and perform the following operations:
reading a self-defined IE kernel path in a redirection registry;
and loading a self-defined IE kernel according to the IE kernel path in the redirection registry, and creating an IE object.
In one embodiment, the processor 301 invoking the load custom IE kernel stored in memory 305 may also perform the following operations:
reading an identification code of a parameter to be acquired in an operating system registry;
judging whether the parameters to be acquired in the operating system registry are IE kernel paths or not according to the identification codes;
when the identification code judging module judges that the parameter to be acquired is not the IE kernel path, acquiring the parameter which is judged to be the non-IE kernel path in the operating system registry;
and when the identification code judging module judges that the parameter to be acquired is the IE kernel path, reading the self-defined IE kernel path in the redirection registry.
In one embodiment, the processor 301 invoking the load custom IE kernel stored in memory 305 may also perform the following operations:
judging whether a module of an IE kernel to be loaded is a statically imported dynamic link library or not;
when the module of the IE kernel to be loaded is a statically imported dynamic link library, acquiring the path of the specified folder from a path modification function of the dynamic link library; loading a self-defined IE kernel stored in the appointed folder, and creating an IE object;
and when the module to be loaded with the IE kernel is not a statically imported dynamic link library, reading a self-defined IE kernel path in the redirection registry.
In this embodiment, the terminal where the apparatus for loading the custom IE kernel described in fig. 7 is located is obtained from the redirection registry instead of the registry of the operating system when the IE kernel path needs to be obtained, so that the obtained IE kernel path is the storage path corresponding to the custom IE kernel, and further when the IE kernel is loaded, the custom IE kernel is loaded, and the object returned to the application program is to create an IE object according to the custom IE kernel, which is beneficial to improving the performance of the application program and enriching the functions of the application program.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (9)

1. A method for loading a custom IE kernel, comprising the steps of:
judging whether a module of an IE kernel to be loaded is a statically imported dynamic link library or not;
when the module of the IE kernel to be loaded is the statically imported dynamic link library, acquiring a path of a specified folder from a path modification function of the dynamic link library, loading a self-defined IE kernel stored in the specified folder, and creating an IE object;
when the module of the IE kernel to be loaded is not the statically imported dynamic link library, reading a self-defined IE kernel path in a redirection registry; the IE kernel path in the redirection registry is a storage path corresponding to the user-defined IE kernel;
and loading a self-defined IE kernel according to the IE kernel path in the redirection registry, and creating an IE object.
2. The method for loading the custom IE kernel according to claim 1, wherein the reading the custom IE kernel path in the redirection registry when the module of the IE kernel to be loaded is not the statically imported dynamic link library comprises:
reading an identification code of a parameter to be acquired in an operating system registry;
judging whether the parameters to be acquired in the operating system registry are IE kernel paths or not according to the identification codes;
when the module of the IE kernel to be loaded is not the statically imported dynamic link library and the parameter to be acquired in the operating system registry is the IE kernel path, executing the step of reading the self-defined IE kernel path in the redirection registry;
and when the module of the IE kernel to be loaded is not the statically imported dynamic link library and the parameter to be acquired in the operating system registry is not the IE kernel path, acquiring the parameter which is judged to be a non-IE kernel path in the operating system registry.
3. The method of loading a custom IE kernel as in claim 1 wherein said step of reading a custom IE kernel path in a redirection registry calls a coccreateinstance function to execute.
4. The method for loading a custom IE kernel according to claim 2, wherein the step of determining whether the parameter to be obtained is an IE kernel path according to the identification code calls an NtQueryValueKey function to execute.
5. The method of loading a custom IE kernel as in claim 1 wherein the path modification function of the dynamically linked library is a setdllldirectory function.
6. An apparatus for loading a custom IE kernel, comprising:
the dynamic link library judging module is used for judging whether the module to be loaded with the IE kernel is a statically imported dynamic link library or not;
the loading module is also used for loading the self-defined IE kernel stored in the appointed folder and creating an IE object;
a path obtaining module, configured to obtain, when the module of the IE kernel to be loaded is the statically imported dynamic link library, a path of the specified folder from a path modification function of the dynamic link library; when the module of the IE kernel to be loaded is not the statically imported dynamic link library, reading a self-defined IE kernel path in a redirection registry; the IE kernel path in the redirection registry is a storage path corresponding to the user-defined IE kernel;
and the loading module is used for loading the self-defined IE kernel according to the IE kernel path in the redirection registry and creating the IE object.
7. The apparatus for loading a custom IE kernel as defined in claim 6, further comprising:
the identification code acquisition module is used for reading the identification code of the parameter to be acquired in the registry of the operating system;
the identification code judging module is used for judging whether the parameters to be acquired in the operating system registry are IE kernel paths or not according to the identification codes;
the parameter acquisition module is used for acquiring the parameter which is judged to be a non-IE kernel path in the operating system registry when the module of the IE kernel to be loaded is not the statically imported dynamic link library and the identification code judgment module judges that the parameter to be acquired is not the IE kernel path;
the path obtaining module is further configured to, when the module to be loaded with the IE kernel is not the statically imported dynamic link library and the identification code determining module determines that the parameter to be obtained is the IE kernel path, read a custom IE kernel path in a redirection registry.
8. The apparatus for loading a custom IE kernel according to claim 7, wherein the path obtaining module calls a coccreateinstance function to read a custom IE kernel path in a redirection registry;
the identification code judging module calls an NtQueryValueKey function to judge whether the parameter to be acquired is an IE kernel path or not according to the identification code;
the path modification function of the dynamic link library called by the path acquisition module is a SetDllDirectory function.
9. A storage medium having stored thereon computer instructions, wherein said computer instructions, when executed, implement a method of loading a custom IE kernel as claimed in any of claims 1-5.
CN201410193735.0A 2014-05-08 2014-05-08 Method and device for loading user-defined IE (Internet Explorer) kernel Active CN105094865B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410193735.0A CN105094865B (en) 2014-05-08 2014-05-08 Method and device for loading user-defined IE (Internet Explorer) kernel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410193735.0A CN105094865B (en) 2014-05-08 2014-05-08 Method and device for loading user-defined IE (Internet Explorer) kernel

Publications (2)

Publication Number Publication Date
CN105094865A CN105094865A (en) 2015-11-25
CN105094865B true CN105094865B (en) 2020-02-18

Family

ID=54575389

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410193735.0A Active CN105094865B (en) 2014-05-08 2014-05-08 Method and device for loading user-defined IE (Internet Explorer) kernel

Country Status (1)

Country Link
CN (1) CN105094865B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113986889B (en) * 2021-12-28 2022-04-05 天津南大通用数据技术股份有限公司 Method and system for realizing intelligent expansion of database function

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7725737B2 (en) * 2005-10-14 2010-05-25 Check Point Software Technologies, Inc. System and methodology providing secure workspace environment
CN102508710A (en) * 2011-09-28 2012-06-20 奇智软件(北京)有限公司 Method and system for switching between IE6 kernel and novel IE kernel
CN102981874A (en) * 2012-11-15 2013-03-20 北京奇虎科技有限公司 Computer processing system and registry redirection method
CN103617079A (en) * 2011-09-28 2014-03-05 北京奇虎科技有限公司 Method and system for switching between IE6 kernel and novel IE kernel

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7725737B2 (en) * 2005-10-14 2010-05-25 Check Point Software Technologies, Inc. System and methodology providing secure workspace environment
CN102508710A (en) * 2011-09-28 2012-06-20 奇智软件(北京)有限公司 Method and system for switching between IE6 kernel and novel IE kernel
CN103617079A (en) * 2011-09-28 2014-03-05 北京奇虎科技有限公司 Method and system for switching between IE6 kernel and novel IE kernel
CN102981874A (en) * 2012-11-15 2013-03-20 北京奇虎科技有限公司 Computer processing system and registry redirection method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
手把手教你修复主页;匿名;《电脑爱好者》;20091231;第63页 *

Also Published As

Publication number Publication date
CN105094865A (en) 2015-11-25

Similar Documents

Publication Publication Date Title
US9602347B2 (en) Method, system and program for browser to switch IE kernel
CN108027741B (en) File processing method, device, terminal and storage medium based on patch upgrade
CN104049986B (en) plug-in loading method and device
US8972976B2 (en) Device and method for automatic driver installation
US9244702B1 (en) Installer-free applications using native code modules and persistent local storage
CN106716351B (en) Method and electronic equipment for displaying webpage
EP3032418A1 (en) Permission control method and device
US20140298318A1 (en) Computer-executable application packaging method, computer-executable device and storage media performing the same
WO2016177341A1 (en) Interface calling method and device, and terminal
CN106648685B (en) Intelligent terminal system application processing method and device and intelligent terminal
US10338867B2 (en) Non-transitory computer-readable recording medium storing computer-readable instructions for causing information processing device to execute image process, and information processing device
CN103778373A (en) Virus detection method and device
CN109522500B (en) Webpage display method, device, terminal and storage medium
US20140317537A1 (en) Browser based application program extension method and device
KR20140061002A (en) Method and system of installing shortcut through mobile application
CN105446739A (en) UI interface setting method and apparatus
CN106775876B (en) Method for quickly starting application by android system
CN110941779B (en) Page loading method and device, storage medium and electronic equipment
US20140298316A1 (en) Managing method for application program installation and electronic device
US20110231837A1 (en) Virtual application package reconstitution
CN109558187B (en) User interface rendering method and device
CN105094865B (en) Method and device for loading user-defined IE (Internet Explorer) kernel
CN104601798A (en) Customized application startup control method and device
CN106293790B (en) application program upgrading method and device based on Firefox operating system
EP2768206B1 (en) Download management method and device based on android browser

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20221122

Address after: 1402, Floor 14, Block A, Haina Baichuan Headquarters Building, No. 6, Baoxing Road, Haibin Community, Xin'an Street, Bao'an District, Shenzhen, Guangdong 518133

Patentee after: Shenzhen Yayue Technology Co.,Ltd.

Address before: 2, 518044, East 403 room, SEG science and Technology Park, Zhenxing Road, Shenzhen, Guangdong, Futian District

Patentee before: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd.