CN111831363A - Control method and device for registry data operation - Google Patents
Control method and device for registry data operation Download PDFInfo
- Publication number
- CN111831363A CN111831363A CN202010970553.5A CN202010970553A CN111831363A CN 111831363 A CN111831363 A CN 111831363A CN 202010970553 A CN202010970553 A CN 202010970553A CN 111831363 A CN111831363 A CN 111831363A
- Authority
- CN
- China
- Prior art keywords
- registry
- data information
- application layer
- lowest
- value
- 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.)
- Granted
Links
Images
Classifications
-
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
-
- 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/4406—Loading of operating system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Virology (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a control method of registry data operation, which is used for shielding malicious monitoring and forced interception of third-party software and comprises the following steps: receiving data information from an application layer, wherein the data information at least comprises registry keys and key value information, driving and allocating a designated memory to receive the data information from the application layer, registering a registry callback function with a lowest altitude value when a trigger condition is met, and adding the data information of the application layer into a task queue to enable the data information of the application layer to be processed when the registry callback function with the lowest altitude value is called by a system; and driving to create a resource recovery thread and recover the specified memory. The method is simple to operate, convenient to use, capable of effectively shielding malicious monitoring and interception of other software, and high in commercial value.
Description
Technical Field
The invention belongs to the field of computer technology application, and particularly relates to a control method and device for registry data operation.
Background
Windows uses a set of dedicated load order groups for file system filter drivers and micro-filter drivers that are loaded at system startup. The old file system filter driver can only be attached to the top of the existing file system driver stack and cannot be attached in the middle of the stack. Thus, the type of launch of the driver and load order group is important for legacy filesystem filter drivers because the previous filter driver can be attached to the filesystem driver stack after it is loaded. The driver is first loaded based on its boot type, which represents the stage of booting the system. For details on the boot type, please refer to "driver boot type" in the context of determining driver load time. All file system filter drivers and pico filter drivers that specify the start type "service _ start" are loaded before the driver for start _ system _ start or service _ auto _ start. The launch type is specified by the StartType entry in the ServiceInstally section of the INF file for installing the micro-filter driver.
In each "start" type category, a "load order" group determines when the file system filter driver and the micro-filter driver are loaded. The micro-filter driver may be loaded at any time. For interoperability with legacy filesystem filter drivers, the filter driver still needs to load the concept of order groups. Each pico-filter driver must have a name ofAltitude (H) levelIs identified by the unique identifier of (1). When the micro-filter driver is loaded, the height of the micro-filter driver defines its position relative to other micro-filter drivers in the i/o stack. Altitude is an infinite precision string of characters that is interpreted as a decimal number. If the number height of the micro-screener driver is low, a micro-screener driver with a large value is loaded into the i/o stack below it. Each load order group has a set of defined heights. The height allocated to the micro-screener driver is governed by Microsoft. The micro-filter driver must specify an altitude range value representing the load order group. The elevation value of the micro-filter driver is specified in the instance definition of the string portion in the INF file used to install the micro-filter driver. The instance definition may also be specified by calling the instancesetupcall routine in the FLT _ registry structure. Multiple instances and heights may be defined for the micro-filter driver. These example definitions apply to all volumes.
The following rules regarding launch type and load order groups determine when the micro-filter driver will be loaded: designating a micro-screener driver of a specific start type and load order group to be loaded simultaneously with other file system screener drivers and micro-screener drivers in the start type and load order group; in each load order group, the file system filter driver and the pico filter driver are typically loaded in a random order. This typically results in loading drivers based on their installation order; if the file system filter driver or micro-filter driver does not specify a load order group, it is loaded behind all other drivers of the same boot type that specify the load order group.
In order to avoid thread reentry, an operating system provides a high concept in registry callback, registry operation initiated in high-altitude registry callback is intercepted by low-altitude registry callback, but registry operation initiated in low-altitude registry callback is not intercepted by high-altitude registry callback, at present, the system is often forcibly monitored and maliciously intercepted by third-party software when performing relevant registry operation, and at present, a control method which can shield the third-party software and directly perform registry writing operation does not exist, namely, a control method and a device for registry data operation do not exist.
Disclosure of Invention
Aiming at the technical defects in the prior art, the invention aims to provide a control method and a control device for registry data operation, according to one aspect of the invention, the control method for registry data operation is provided, which is used for shielding malicious monitoring and forced interception of third-party software, and comprises the following steps:
a: receiving data information from an application layer, wherein the data information at least comprises registry keys and key value information;
b: and adding the data information of the application layer into a task queue so that the data information of the application layer is processed when the registry callback function of the lowest altitude value is called by a system.
Preferably, before the step b, the method further comprises the step i: and registering the registry callback function of the lowest altitude value when the triggering condition is met.
Preferably, the trigger condition is: when the user authorization instruction is acquired.
Preferably, the step i comprises the steps of:
i 1: determining altitude values recalled by the registries of the one or more third-party software in the current working state, and taking the lowest value of the altitude values recalled by the registries of the one or more third-party software as a first altitude value;
i 2: a registry callback function that adjusts and/or registers a lowest altitude value, the lowest altitude value being lower than the first altitude value.
Preferably, the step i comprises the steps of:
i 3: register a registry callback function of the lowest altitude value that the system can accept as the lowest value.
Preferably, the step b includes:
b 1: associating the data information of the application layer with a registry callback function of a lowest altitude value;
b 2: and adding the data information of the application layer into a task queue, and processing the data information of the application layer when the registry callback function of the lowest altitude value is passively called by a system so as to shield the monitoring of third-party software.
Preferably, after the step a, the method further comprises: the driver allocates the designated memory to receive the data information from the application layer.
Preferably, after the step b, the method further comprises:
c: and driving to create a resource recovery thread and recover the specified memory.
According to another aspect of the present invention, there is provided a control apparatus for registry data operation, which adopts the control method, including:
the first receiving means: for receiving data information from an application layer;
a first processing device: the method comprises the step of adding data information of the application layer into a task queue so that the data information of the application layer is processed when a registry callback function with the lowest altitude value is called by a system.
Preferably, the first processing means includes:
a second processing device: for associating data information of the application layer with a registry callback function of a lowest elevation value;
a third processing device: the method is used for adding the data information of the application layer into a task queue, and processing the data information of the application layer when the registry callback function of the lowest altitude value is passively called by a system so as to shield the monitoring of third-party software.
The data information from the application layer is received, the data information at least comprises registry keys and key value information, and the data information of the application layer is added into a task queue, so that the data information of the application layer is processed when a registry callback function with the lowest altitude value is called by a system. The invention can realize the penetration of the registry, shield other third-party software and the like to realize callback monitoring, and carry out operations such as writing, deleting and the like. In order to avoid reentry, the operating system provides a high concept in the registry callback, and registry operation initiated in the high-altitude registry callback is intercepted by the low-altitude registry callback, but registry operation initiated in the low-altitude registry callback is not intercepted by the high-altitude registry callback, so that in order to avoid thread reentry, only registry operation initiated in the lowest-altitude registry callback function does not enter other registry functions, and one registry callback is registered, and monitoring and interception of other registry callbacks can be shielded by the initiated registry operation. The method is simple to operate, convenient to use, capable of effectively shielding malicious monitoring and interception of other software, and high in commercial value.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:
FIG. 1 is a flowchart illustrating a control method for data operations of a registry according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a specific flowchart of a registry callback function for registering a lowest altitude value when a trigger condition is satisfied according to a first embodiment of the present invention;
FIG. 3 is a diagram illustrating a specific flowchart of adding the data information of the application layer to a task queue so that the data information of the application layer is processed when the registry callback function of the lowest altitude value is called by the system according to the second embodiment of the present invention; and
fig. 4 is a block diagram of a control device for controlling registry data operation according to another embodiment of the present invention.
Detailed Description
In order to better and clearly show the technical scheme of the invention, the invention is further described with reference to the attached drawings.
Fig. 1 shows a detailed flowchart of a control method for registry data operation according to an embodiment of the present invention, and the present invention discloses a control method for registry data operation for shielding malicious monitoring and forced interception of third-party software, which includes the following steps:
firstly, step S101 is entered, and data information is received from an application layer, where the data information at least includes registry keys and key value information, and the application layer is the seventh layer of the seven-layer OSI model. The application layer interfaces directly with applications and provides common web application services. The application layer also issues requests to the presentation layer. The application layer is the highest layer of the open system and directly provides services for application processes. The service elements are divided into two types, namely a common application service element CASE and a specific application service element SASE, and a registry key and key value information are Windows system registry entries, and related functions and performances of the Windows operating system can be changed or optimized by editing and modifying.
A registry is an important database in Microsoft Windows for storing system and application settings, where all data is organized in keys and sub-keys by a tree-like structure, much like a directory structure. Each key contains a specific set of information and the key name of each key is related to the information it contains. If this key contains a sub-key, there will be a "+" sign to the left of the folder representing this key in the registry editor window to indicate that there is more content in this folder. If the folder is opened and expanded by the user, the "+" will change to "-", and the keys of the registry contain data in various formats. The data types can include general data types, various operating system specific data types of Windows NT kernel, and component/application specific special data types, which can only be edited as binary numbers by a user.
Finally, step S102 is entered, and the data information of the application layer is added into the task queue so that the data information of the application layer is processed when the registry callback function of the lowest altitude value is called by the system, and those skilled in the art understand that, in order to avoid thread reentry, the operating system provides a concept of height in the registry callback, i.e. the altitude value lower than the registry callback altitude values of other third-party software in the system, when the triggering condition is satisfied, the registry callback function of the lowest altitude value is registered, which will be further described in the following detailed description, and after the registry callback function of the lowest altitude value is registered, the data information of the application layer is added into the task queue, and since the system operates very frequently, the system will passively call and process the data information of the application layer, because the altitude value of the registered registry callback is lower than that of any other third-party software, the registry operation initiated in the high-altitude-value registry callback is intercepted by the low-altitude-value registry callback, but the registry operation initiated in the low-altitude-value registry callback is not intercepted by the high-altitude-value registry callback, and the processed data information of the application layer is not intercepted by the third-party software.
In a preferred embodiment, after the step S102, the method further includes a step S103 of driving to create a resource recycling thread and recycle the specified memory, and in such an embodiment, after the step S101, the method further includes driving to allocate the specified memory to receive data information from an application layer, and further driving to create a resource recycling thread and recycle the specified memory after adding the data information of the application layer to a task queue so that the data information of the application layer is processed when a registry callback function of a lowest altitude value is called by a system.
Fig. 2 is a schematic diagram illustrating a specific flow of the registry callback function for registering the lowest altitude value when the triggering condition is satisfied according to the first embodiment of the present invention, and those skilled in the art understand that before the step S102, the method further includes the steps of: when a trigger condition is met, registering a registry callback function of a lowest altitude value, that is, when registering the registry callback function of the lowest altitude value, a certain trigger condition needs to be met, in a preferred embodiment, the trigger condition is that when obtaining a user authorization instruction, the driver performs default execution at initialization, and registers the registry callback function of the lowest altitude when the driver initializes, and in other embodiments, the registry callback function of the lowest altitude value can also be registered when receiving data information from an application layer, in such an embodiment, when and only when a write operation needs to be performed on the registry, the system sends the data information of the application layer which needs to be written to the driver, and the driver further registers the registry callback function of the lowest altitude value. In other embodiments, the registry callback function with the lowest altitude value may be registered when the data information is monitored and intercepted by the third-party software, that is, when the registry callback driving registration of the random altitude value is intercepted by other third-party software, the operations are rolled back, recorded, deleted and restarted, and when the registry start operation is performed again, the registry callback function with the lowest altitude value is registered.
Those skilled in the art will appreciate that the above steps further include the steps of:
firstly, step S201 is entered, and the altitude value of the registry callback of one or more third-party software is determined, and the lowest value of the altitude values of the registry callbacks of one or more third-party software is taken as the first altitude value, in such an embodiment, a plurality of third-party software will exist in the system, and each of the third-party software has the altitude value of its own registry callback function, for example, the altitude value of the first third-party software is 300, the altitude value of the second third-party software is 265, the altitude value of the third-party software is 330, and then the first altitude value is the altitude value of the second third-party software.
In such an embodiment, after step S201 is performed, step S202 is performed, namely, a registry callback function for adjusting and/or registering a lowest altitude value, which is lower than the first altitude value, and further, a registry callback function for adjusting and/or registering a lowest altitude value, which may be set to 264, 260, 200, etc.
Those skilled in the art will appreciate that, in addition to the determination of the lowest altitude value used to implement the callback of the registry function in the above steps S201 to S202, the lowest altitude value may be determined by the registry callback function registering the lowest altitude value that can be recognized by the system, i.e., the lowest value that can be recognized by the registered system is driven regardless of the altitude value of other third-party software, and the lowest altitude value may be set to 1, 10, 50, and so on.
Fig. 3 is a schematic diagram illustrating a specific process of adding the data information of the application layer into a task queue so as to process the data information of the application layer when the registry callback function of the lowest altitude value is called by the system, according to a second embodiment of the present invention, where the step S102 includes:
firstly, step S1021 is entered, and the data information of the application layer is associated with the registry callback function of the lowest altitude value, in such an embodiment, the application layer sends the registry key and key value information to be modified to the driver, the driver registers the registry callback function of the lowest altitude, and after receiving the data of the application layer, the driver adds the data into the task queue for processing.
Then, step S1022 is performed, the data information of the application layer is added to the task queue, and when the registry callback function of the lowest altitude value is passively called by the system, the data information of the application layer is processed to shield monitoring of third-party software, where step S1022 may refer to step S102, and details are not repeated here.
Fig. 4 shows a schematic block connection diagram of a control apparatus for registry data operation according to another embodiment of the present invention, and the present invention discloses not only a control method for registry data operation, but also a control apparatus for implementing registry data operation, including a first receiving apparatus 1: for receiving data information from the application layer, the operation principle of the first receiving apparatus 1 may refer to the foregoing step S101, which is not described herein again.
Further, the control device for the registry data operation further comprises the first processing device 2: for adding the data information of the application layer into the task queue so as to process the data information of the application layer when the registry callback function of the lowest altitude value is called by the system, the working principle of the first processing device 2 may refer to the foregoing step S102, which is not described herein again.
Further, the first processing device 2 comprises a second processing device 21: for associating the data information of the application layer with the registry callback function of the lowest altitude value, the working principle of the second processing device 21 may refer to the foregoing step S1021, which is not repeated herein.
Further, the first processing device 2 comprises a third processing device 22: the third processing device 22 may refer to the foregoing step S1022, and details of the working principle of the third processing device are omitted here.
It should be noted that the specific implementation of each of the above device embodiments is the same as the specific implementation of the corresponding method embodiment, and is not described herein again.
The sail displays provided herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose devices may be used with the teachings herein. The required structure for constructing such a device will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some embodiments, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Furthermore, those of skill in the art will understand that although some embodiments described herein include some features included in other embodiments, not others, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The foregoing description of specific embodiments of the present invention has been presented. It is to be understood that the present invention is not limited to the specific embodiments described above, and that various changes and modifications may be made by one skilled in the art within the scope of the appended claims without departing from the spirit of the invention.
Claims (10)
1. A control method of registry data operation is used for shielding malicious monitoring and forced interception of third-party software, and is characterized by comprising the following steps:
a: receiving data information from an application layer, wherein the data information at least comprises registry keys and key value information;
b: and adding the data information of the application layer into a task queue so that the data information of the application layer is processed when the registry callback function of the lowest altitude value is called by a system.
2. The control method according to claim 1, characterized by further comprising, before the step b, a step i of: and registering the registry callback function of the lowest altitude value when the triggering condition is met.
3. The control method according to claim 2, characterized in that the trigger condition is: when the user authorization instruction is acquired.
4. The control method according to claim 2, wherein the step i includes the steps of:
i 1: determining altitude values recalled by the registries of the one or more third-party software in the current working state, and taking the lowest value of the altitude values recalled by the registries of the one or more third-party software as a first altitude value;
i 2: a registry callback function that adjusts and/or registers a lowest altitude value, the lowest altitude value being lower than the first altitude value.
5. The control method according to claim 2, wherein the step i includes the steps of:
i 3: register a registry callback function of the lowest altitude value that the system can accept as the lowest value.
6. The control method according to claim 1, wherein the step b includes:
b 1: associating the data information of the application layer with a registry callback function of a lowest altitude value;
b 2: and adding the data information of the application layer into a task queue, and processing the data information of the application layer when the registry callback function of the lowest altitude value is passively called by a system so as to shield the monitoring of third-party software.
7. The control method according to claim 1, characterized by further comprising, after the step a: the driver allocates the designated memory to receive the data information from the application layer.
8. The control method according to claim 7, characterized by further comprising, after the step b:
c: and driving to create a resource recovery thread and recover the specified memory.
9. A control apparatus of registry data operation, which employs the control method according to any one of claims 1 to 8, characterized by comprising:
first receiving device (1): for receiving data information from an application layer;
first treatment device (2): the method comprises the step of adding data information of the application layer into a task queue so that the data information of the application layer is processed when a registry callback function with the lowest altitude value is called by a system.
10. The control device according to claim 9, characterized in that the first processing means (2) comprise:
second processing device (21): for associating data information of the application layer with a registry callback function of a lowest elevation value;
third processing device (22): the method is used for adding the data information of the application layer into a task queue, and processing the data information of the application layer when the registry callback function of the lowest altitude value is passively called by a system so as to shield the monitoring of third-party software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010970553.5A CN111831363B (en) | 2020-09-16 | 2020-09-16 | Control method and device for registry data operation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010970553.5A CN111831363B (en) | 2020-09-16 | 2020-09-16 | Control method and device for registry data operation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111831363A true CN111831363A (en) | 2020-10-27 |
| CN111831363B CN111831363B (en) | 2021-02-23 |
Family
ID=72919053
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010970553.5A Active CN111831363B (en) | 2020-09-16 | 2020-09-16 | Control method and device for registry data operation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831363B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567670A (en) * | 2011-12-28 | 2012-07-11 | 南京邮电大学 | Filter drive encryption implementing method for file system |
-
2020
- 2020-09-16 CN CN202010970553.5A patent/CN111831363B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567670A (en) * | 2011-12-28 | 2012-07-11 | 南京邮电大学 | Filter drive encryption implementing method for file system |
Non-Patent Citations (2)
| Title |
|---|
| MASIMARO: "Minfilter过滤框架", 《HTTPS://CLOUD.TENCENT.COM/DEVELOPER/ARTICLE/1395241》 * |
| MICROSOFT: "支持分层注册表筛选驱动程序", 《HTTPS://DOCS.MICROSOFT.COM/ZH-CN/WINDOWS-HARDWARE/DRIVERS/KERNEL/SUPPORTING-LAYERED-REGISTRY-FILTERING-DRIVERS》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111831363B (en) | 2021-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6323865B1 (en) | Automatic font management within an operating system environment | |
| US6430663B1 (en) | Methods for selecting a boot partition and hiding a non-selected partition | |
| US7024549B1 (en) | Disk drive having a protected partition configured to load an operating system for performing a user-selected function | |
| US7275150B2 (en) | Method and system for adding frequently selected applications to a computer startup sequence | |
| US5974517A (en) | Method and system for mounting a system partition as a logical drive while an operating system is operational by modifying a partition table | |
| US20090216781A1 (en) | Technique for Dynamic Creation of a User Catalog for a Storage System | |
| EP3260993A1 (en) | File operation method and device | |
| CN111443912B (en) | Component-based page rendering method, device, computer equipment and storage medium | |
| US6229537B1 (en) | Hosting windowed objects in a non-windowing environment | |
| US5903896A (en) | Method for installing a file on demand using a preview | |
| US7424719B2 (en) | Application with multiple embedded drivers | |
| EP1763751B1 (en) | Multi-source, multi-destination data transfers | |
| US5887169A (en) | Method and apparatus for providing dynamic entry points into a software layer | |
| JP2003005973A (en) | Method and device and program for multi-machine network install using writeable media | |
| KR101551206B1 (en) | A vehicle data control system and a control method | |
| WO2008112385A1 (en) | Isolating, managing and communicating with user interface elements | |
| US8327111B2 (en) | Method, system and computer program product for batched virtual memory remapping for efficient garbage collection of large object areas | |
| CN111831363B (en) | Control method and device for registry data operation | |
| US20050060378A1 (en) | Method and apparatus for providing language modularization | |
| JP2000163291A (en) | Computer system and method for preparing computer- readable medium | |
| US20040003221A1 (en) | Method and apparatus for tuning multiple instances of kernel modules | |
| US7007273B2 (en) | Object oriented model of preloading software | |
| US6915401B2 (en) | System and method for managing off-screen buffers for electronic images | |
| JP2000163255A (en) | Computer system for accessing computer-readable medium and method therefor | |
| US6490678B1 (en) | Combination editable and fixed entry input menu field used in a menu for a computer system prior to execution of an operating system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |