CN100437490C - Method for mounting driving program and computer system thereof - Google Patents
Method for mounting driving program and computer system thereof Download PDFInfo
- Publication number
- CN100437490C CN100437490C CNB2006100738980A CN200610073898A CN100437490C CN 100437490 C CN100437490 C CN 100437490C CN B2006100738980 A CNB2006100738980 A CN B2006100738980A CN 200610073898 A CN200610073898 A CN 200610073898A CN 100437490 C CN100437490 C CN 100437490C
- Authority
- CN
- China
- Prior art keywords
- driver
- storage element
- stored
- address information
- system kernel
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention provides a method for installing a driving program and a computer system. Firstly, a system kernel, the driving program and address information are stored into a first storage unit, wherein the address information is used for defining scheduled storage space in a second storage unit for scheduled storing the driving program; subsequently, the system kernel in the first storage unit is stored into system kernel storage space in the second storage unit, and the driving program in the first storage unit is stored into the scheduled storage space; then the system kernel is operated, and based on the address information, the driving program is read from the preset space to install the driving program.
Description
Technical field
The invention relates to a kind of method and system that computer software is installed, particularly do not need dynamically to dispose relevant for a kind of that the storage area gives driver so that the method for Fast Installation driver and computer system thereof.
Background technology
Generally speaking, computer system can be carried out boot program earlier after start, then just executive operating system (operating system, OS), and computer system normally executive system kernel (kernel) control above-mentioned boot program.Known as industry, system kernel can be installed a plurality of essential substantially drivers, for example integrated drive electronics (integrated drive electronics, IDE) driver.
Known target computer execution system kernel is divided into two parts with a plurality of driver ways of installation, first utilizes the exploitation that operating system and developing instrument software (for example windows visualstudio 6.0) are installed to come development system kernel and driver with computing machine earlier, afterwards, exploitation with computing machine with a system kernel and driver driver integrating document of composition and be placed in the object computer; Second portion then is that object computer utilizes the driver integrating document to come install driver.
See also Fig. 1, Fig. 1 is the functional block diagram of known target computing machine 10.Object computer 10 has storage element 12,14 and central processing unit (CPU) 16, the driver integrating document I F that wherein has system kernel SK and driver Da, Db then is developed with computing machine DC and deposits to storage element 12, required program code and operational data when storage element 14 then is used for temporary object computer 10 runnings.
At first, central processing unit 16 first executive system kernel SK, and behind central processing unit 16 discoveries and initialization storage element 14, central processing unit 16 just will be deposited in system kernel SK in the storage element 12 and copy to storage area S_SK in the storage element 14, afterwards, and central processing unit 16 is just carried out from storage area S_SK reading system kernel SK.Then, when executory system kernel SK needed install driver Da, then system kernel SK can go earlier storage element 12 to find driver Da, and the file header of analysis-driven program Da (file header) FHa learns related parameter values.Then, be convenient to dynamically to dispose storage area Sa in the storage element 14, suppose that the start address of storage area Sa is SAa, then executory system kernel SK is just according to start address SAa, driver Da is write in the storage area Sa, and revise the relevant position of the driver Da among the storage area Sa according to parameter value relevant in start address SAa and the file header FHa, basis for example, reloc Section revises related data.Next, central processing unit 16 can be carried out the initialization running of driver Da to the execution starting point EPa of slave driver Da, central processing unit 16 returns executive system kernel SK more afterwards, this moment, the installation of driver Da was finished, similarly, when executory system kernel SK needed install driver Db, after then system kernel SK can go earlier storage element 12 to find driver Db, the file header FHb of analysis-driven program Db was to learn related parameter values.Then, executory system kernel SK is after the file size of learning driver Db, it is convenient to dynamically dispose in the storage element 14 storage area Sb, the start address of supposing storage area Sb is SAb, then executory system kernel SK is according to start address SAb, driver Db is write in the storage area Sb, and revise the relevant position of the driver Db among the storage area Sb according to parameter value relevant in start address SAb and the file header FHb.Next, the initialization that central processing unit 16 can be carried out driver Db to the execution starting point EPb of driver Db operates, central processing unit 16 returns executive system kernel SK more afterwards, and this moment, the installation of driver Db was finished.At last, object computer 10 is finished the installation procedure of driver Da, Db.
If will continue to load and other a plurality of drivers of installation, can finish installation procedure as long as repeat above-mentioned steps.As mentioned above, need go earlier storage element 12 to read and check the relevant information of driver Da when system kernel SK dynamic loading and install driver Da, system kernel SK dynamically drives the suitable storage area Sa of storage element 14 configurations again and gives driver Da use afterwards, thus, initialization procedure not only complexity is high and can expend the plenty of time, that is causes the usefulness of known target computing machine 10 not good.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of is that driver is given so that the method for this driver of Fast Installation and computer system in pre-configured storage area before system kernel operation, to address the above problem.
According to above-mentioned purpose, the invention provides a kind of method of install driver, comprise the following steps: stocking system kernel, driver and address information in first storage element, wherein address information is the predetermined predetermined storage space that is stored in second storage element of definition driver; And the system kernel in first storage element is stored in a system kernel storage area in second storage element, the driver in first storage element is stored in predetermined storage space; And operation is stored in system kernel in this system kernel storage area in second storage element and reads driver with the foundation address information from predetermined storage space and come install driver.
According to above-mentioned purpose, the present invention also provides a kind of method that produces system software, be applicable to object computer with storage element, comprise the following steps: that (a) is stored in predetermined storage space in the storage element with the decision address information with driver is predetermined, address information is with so that the object computer install driver; And (b) produce system software according to system kernel, driver and the address information of object computer.
According to above-mentioned purpose, the present invention provides a kind of computer system again, comprising: first storage element, and it includes system kernel, driver and address information; Second storage element; And controller, be coupled to first, second storage element, be used for the system kernel in first storage element is stored in system kernel storage area in second storage element, and the driver in first storage element is stored in predetermined storage space in second storage element; And operation is stored in system kernel in this system kernel storage area in second storage element and reads driver with the foundation address information from predetermined storage space and come install driver; Wherein address information is used to define the predetermined predetermined storage space that is stored in second storage element of driver.
According to above-mentioned purpose, the present invention more provides a kind of computer system that is used to produce system software, comprise: first logical block, it decides address information according to a predetermined storage space in the predetermined storage element that is stored in object computer of driver, and address information is used for auxiliary mark computing machine install driver; And second logical block, it produces system software according to system kernel, driver and address information; And storage element, be coupled to this first logical block and this second logical block, be used for storing this system software.
Description of drawings
Fig. 1 is the functional block diagram of known target computing machine.
Fig. 2 is the functional block diagram of an embodiment of the present invention's one object computer.
Fig. 3 is the synoptic diagram of first embodiment of storage element shown in Figure 2 pairing storage area configuration.
Fig. 4 is the functional block diagram of the present invention's one exploitation with an embodiment of computing machine.
Fig. 5 is exploitation shown in Figure 4 produces the driver integrating document with computing machine a process flow diagram.
Fig. 6 has the process flow diagram that the driver integrating document of description list is carried out the extensible firmware interface and a plurality of drivers are installed for object computer utilization shown in Figure 2.
Fig. 7 is the synoptic diagram of second embodiment of storage element shown in Figure 2 pairing storage area configuration.
[main element label declaration]
10,20,30 computer systems, 12,14,22,24,48 storage elements
16,26,46 microprocessors, 41,42 logical blocks
Embodiment
In one embodiment of the invention, object computer 30 desires are carried out extensible firmware interface (extensiblefirmware interface) EFI and a plurality of driver D1, D2 are installed.The brief description the present invention of elder generation, the present invention was divided into for two megastages, at first, prior to the phase one utilization operating system (operationsystem is installed, OS) exploitation with developing instrument software (for example windows visual studio 6.0) produces the system software that includes description list with computing machine 20, in present embodiment, system software is driver integrating document IPF, and include extensible firmware interface EFI and driver D1, D2, and the address information that is write down in the description list is definition driver D1, the predetermined address information that is stored in the storage area in the object computer 30 of D2; Then, exploitation is deposited in driver integrating document IPF in the object computer 30 with computing machine 20.Afterwards, in subordinate phase, object computer 30 utilizes the driver integrating document IPF with above-mentioned address information to carry out extensible firmware interface EFI and install driver D1, D2, at this moment, object computer 30 need not dynamically to check the size of driver D1, D2 before install driver D1, D2.As is known in the industry, object computer 30 can be installed a plurality of basic and essential driver D1, D2, for instance then after carrying out extensible firmware interface EFI, driver D1 is integrated drive electronics (integrated drive electronics, an IDE) driver.Next will introduce exploitation earlier respectively, above-mentioned first, second stage steps flow chart separately will be described in detail in detail respectively afterwards again with the structure of computing machine 20 with object computer 30.
See also Fig. 2, Fig. 2 is the functional block diagram of an embodiment of object computer 30 of the present invention.As shown in the figure, object computer 30 includes a plurality of storage elements 22,24 (for example storer) and a microprocessor 26 (for example central processing unit (CPU)).In present embodiment, storage element 22 is a nonvolatile memory, for instance, it is a ROM (read-only memory), the driver integrating document IPF that stores in it says as above-mentioned institute, be stored to again in the storage element 22 after producing with computing machine 20 by exploitation earlier, will be as for the flow process that produces driver integrating document IPF in hereinafter describing in detail.Driver integrating document IPF includes system kernel (kernel), a plurality of driver D1, a D2 and a description list DT, driver D1, D2 has file header (file header) PEH1 separately, PEH2, file header PEH1, PEH2 records driver D1 separately, the execution starting point of D2 (entry point) EP1, the information of EP2, and about retouch reach table DT narration will in after length provide, please note, do not influencing under the technology of the present invention exposure, Fig. 2 only shows two driver D1, D2, yet, the present invention does not limit to the quantity of the driver of installation, in addition, in present embodiment, this system kernel is aforesaid extensible firmware interface EFI, yet this system kernel is not confined to extensible firmware interface EFI, in fact it can be the program code of the installation procedure of any controlling and driving program, for instance, the pre-loaded driver of the present invention to the mechanism of storage element also can be applicable to the required driver of operating system installation, also belongs to category of the present invention.In the present embodiment, storage element 24 is a volatile memory, and for instance, storage element 24 is a dynamic RAM, please cooperate and consult Fig. 3, and Fig. 3 is the synoptic diagram of first embodiment of storage element 24 pairing storage area configurations.In first embodiment, storage area S1 is in close proximity to after the storage area S_EFI, and storage area S2 is in close proximity to after the storage area S1, and storage area S_EFI, S1, S2 are predetermined be used for temporary respectively extensible firmware interface EFI and driver D1, D2 in boot program, after will being specified in about this part.Microprocessor 26 is to be coupled to storage element 22,24, is used for the running of controlled target computing machine 30.
See also Fig. 4, Fig. 4 develops the functional block diagram of an embodiment who uses computing machine 20 for the present invention.Exploitation includes microprocessor 46 and storage element 48 with computing machine 20.Microprocessor 46 includes a plurality of logical blocks 41,42, each logical block the 41, the 42nd, (logic gate) constituted by a plurality of logic gates, be used for the actuating logic computing implementing the function of microprocessor 46, and the performed logical operation of logical block 41,42 will in after the length detailed description.Storage element 48 is coupled to microprocessor 46, in order to storage data, for example can will integrate extensible firmware interface EFI and driver D1, the D2 that becomes driver integrating document IPF in order to store.
Next introduce the detailed process of above-mentioned phase one.Please consult Fig. 2, Fig. 3, Fig. 4 and Fig. 5 simultaneously, Fig. 5 is exploitation shown in Figure 4 produces driver integrating document IPF with computing machine 20 a process flow diagram.Exploitation includes the following step with the operation that computing machine 20 produces driver integrating document IPF:
Step 200: beginning;
Step 202: logical block 41 is recorded in the address related data AD1 of driver D1 in the description list DT;
Step 204: logical block 41 is recorded in the address related data AD2 of driver D2 in the description list DT;
Step 206: logical block 42 is integrated extensible firmware interface EFI and driver D1, D2 and description list DT to produce driver integrating document IPF;
Step 208: exploitation is with after the computing machine 20 driver integrating document IPF being deposited in the storage element 22 of object computer 30; And
Step 210: finish.
Below be described in detail the present invention and develop the flow process that produces driver integrating document IPF with computing machine 20.In present embodiment, begin back (step 200) in flow process, the logical block 41 of microprocessor 46 is learnt the storage area S1 in the predetermined in the future storage element 24 that is stored in object computer 30 of driver D1 (now be stored in storage element 48 in), the relevant position that logical block 41 is revised driver D1 according to parameter value relevant in the start address SA1 of storage area S1 and the file header of driver D1 (file header) PEH1 (is for example adjusted and is needed the parameter value revised among the file header PEH1, for instance, similarly be execution starting point (entry point) EP1... that adjusts driver D1 or the like), because aforesaid operations is known by industry, so do not give unnecessary details in addition.Then, logical block 41 is recorded in the address related data AD1 of driver D1 in the description list DT, address related data AD1 includes filename, start address SA1 or displacement (offset) OFFSET_1 of driver D1, and carries out starting point EP1 or the like (step 202).Next logical block 41 is learnt the storage area S2 in the predetermined in the future storage element 24 that is stored in object computer 30 of driver D2 (now be stored in storage element 48 in), the relevant position that logical block 41 is revised driver D2 according to parameter value relevant in the file header PEH2 of the start address SA2 of storage area S2 and driver D2 (is for example adjusted and is needed the parameter value revised among the file header PEH2, for instance, similarly be the execution starting point EP2 that adjusts driver D2); Then, logical block 41 is recorded in the address related data AD2 of driver D2 in the description list DT, and address related data AD2 includes filename, start address SA2 or the displacement OFFSET_2 of driver D2, and carries out starting point EP2 (step 204).Aforementioned displacements OFFSET_1, OFFSET_2 can be specified voluntarily by the programmer, and the address that the start address SA_EFI of storage area S_EFI shown in Figure 3 adds top offset OFFSET_1 is that address that the predetermined start address SA1 that is used for depositing the storage area S1 of driver D1, start address SA_EFI add top offset OFFSET_2 then is the predetermined start address SA2 that is used for depositing the storage area S2 of driver D2.In addition, in present embodiment, description list DT is predetermined is stored in the storage area S_EFI, and be arranged in (for example being recorded in the file header of extensible firmware interface EFI) before the extensible firmware interface EFI, therefore, description list DT is in the predetermined storage address of storage element 24, be the predetermined storage address of extensible firmware interface EFI, just the start address SA_EFI of storage area S_EFI in storage element 24.Yet in other embodiment, description list DT also can be stored in microprocessor 26 and can access arrive Anywhere.
Then, logical block 42 is integrated extensible firmware interface EFI, driver D1, D2 and description list DT to produce driver integrating document IPF, and driver integrating document 1PF can be deposited in (step 206) in the storage element 48, last earlier, exploitation is deposited in driver integrating document 1PF in the storage element 22 of object computer 30 with computing machine 20 again, finishes whole flow process (step 208,210).In the present embodiment, above-mentioned driver D1, D2 file header PEH1, PEH2 separately is all PE file header (portable executable file header) that is all meets Portable that Microsoft (MicroSoft) proposed and can carry out common object file format specification (Microsoft PortableExecutable and Common Object File Format Specification); In addition, in other embodiments of the invention, the address related data AD1 of driver D1 can not write down and carry out starting point EP1, carry out starting point EP1 because also record in the file header PEH1 of driver D1, that is to say, for the related data AD1 of address, carry out the information that starting point EP1 is selectivity (optional) record.In like manner, for the related data AD2 of address, carry out starting point EP2 for the information that also writes down for selectivity.
Next introduce the detailed process of above-mentioned subordinate phase.Please cooperate Fig. 3 and consult Fig. 6 simultaneously, Fig. 6 carries out the process flow diagram of extensible firmware interface EFI and install driver D1, D2 for object computer shown in Figure 2 30 utilizes the driver integrating document IPF with description list DT, and Fig. 6 includes the following step:
Step 300: beginning;
Step 302: microprocessor 26 begins to carry out extensible firmware interface EFI;
Step 304: microprocessor 26 copies to driver integrating document IPF in the storage element 24 from storage element 22;
Step 306: microprocessor 26 reads driver D1 from storage area S1 and comes install driver D1 according to the address related data AD1 that is write down among the description list DT;
Step 308: microprocessor 26 reads driver D2 from storage area S2 and comes install driver D2 according to the address related data AD2 that is write down among the description list DT; And
Step 310: finish.
From the above, the amount of capacity of storage area S1 of the present invention, S2 is not as going earlier storage element 22 to check the actual file size of driver D1, D2 and determined by microprocessor 26 as the known technology, that is to say, before subordinate phase is implemented, start address SA_EFI, SA1, SA2 all are the numerical value that is predetermined, but not dynamically decide when subordinate phase is implemented again.In addition, emphasis of the present invention is that promptly extensible firmware interface EFI and driver D1, D2 are reserved in the position of storage element 24 the insides of object computer 30 in advance in advance, therefore, extensible firmware interface EFI and driver D1, D2 are integrated into a driver integrating document IPF only are one embodiment of the present invention, and the present invention is not as limit.Please refer to Fig. 7, Fig. 7 is the synoptic diagram of second embodiment of storage element shown in Figure 2 24 pairing storage areas configurations.As shown in Figure 7, storage area S_EFI, S1, S2 are separated from each other, representing that just extensible firmware interface EFI, driver D1, D2 are separately stored in non-conterminous storage area S_EFI, S1, the S2, is that a driver integrating document IPF is deposited in the storage element 24 again but not be integrated into earlier.
For above-mentioned this second embodiment, when carrying out the phase one, after execution of step 200～204, exploitation is deposited in extensible firmware interface EFI, driver D1, D2 and description list DT in the storage element 22 of object computer 30 with computing machine 20 with computing machine 20 in exploitation.Afterwards, after object computer 30 execution of step 300～302 of subordinate phase, object computer 30 copies to driver integrating document IPF and description list DT, driver D1, D2 respectively in non-conterminous storage area S_EFI in the storage element 24, S1, the S2, continues the execution that execution in step 306～310 has been finished subordinate phase then.In addition, exploitation also can be same computing machine with computing machine 20 and object computer 30, and computing machine executes the phase one (being regarded as exploitation computing machine 20 this moment) earlier, carries out subordinate phase (being regarded as object computer 30 this moment) after the shutdown again.
In first embodiment shown in Figure 3,26 of microprocessors need to carry out driver integrating document IPF, can carry out extensible firmware interface EFI in regular turn and carry out driver D1, the installation of D2, because in first embodiment, extensible firmware interface EFI and driver D1, D2 is closely placed becomes driver integrating document IPF, but not similarly be among second embodiment (as shown in Figure 7), extensible firmware interface EFI and driver D1, D2 is distributed in the storage element 24 dispersedly, therefore execution extensible firmware interface EFI and install driver D1 are being installed, during D2, first embodiment saves than second embodiment and reads the driver D1 that is stored in the storage element 24, the time of D2, and more can not allow the residue free space of storage element 24 be partitioned into the several piece storage area, that is the effective utilization of the storage element 24 of first embodiment is preferable.
Compared to known technology, the installation method of driver of the present invention and computer system can be before system kernel (for example operating system or extensible firmware interface) operations, the preferential driver of installing of needs is stored in the storage area pre-configured in the storage element of computer system into, afterwards, computer system can read and carry out the driver that has been stored in the storage element apace with directly and carry out the installation of driver apace, does not read in the storage element and install driver and do not need just to go dynamically (dynamically) that driver is stored to after the system kernel operation.So, the present invention just is loaded into way in another storage element (for example dynamic RAM) to the driver in the storage element (for example ROM (read-only memory)) before system kernel operation, can simplify the initialization procedure of computer system, effectively reduce the complexity of installation process and reduce the known storage area that dynamically disposes and give the required plenty of time of expending of driver.
The above only is preferred embodiment of the present invention, and all equalizations of being done according to claim scope of the present invention change and modify, and all should belong to covering scope of the present invention.
Claims (14)
1. the method for an install driver comprises the following steps:
(a) stocking system kernel, driver and address information are in first storage element, and wherein this address information is used to define the predetermined predetermined storage space that is stored in second storage element of this driver;
(b) this system kernel in this first storage element is stored in a system kernel storage area in this second storage element, and this driver in this first storage element is stored in this predetermined storage space; And
(c) this system kernel that moves in this system kernel storage area that is stored in this second storage element is installed this driver to read this driver according to this address information from this predetermined storage space.
2. method according to claim 1, wherein this predetermined storage space is in close proximity to this system kernel storage area.
3. method according to claim 1, wherein step (b) also includes this address information that this first storage element is stored and writes this second storage element, and step (c) is according to this stored in this second storage element address information this driver to be installed.
4. method according to claim 1, wherein this address information is stored in the start address of this predetermined storage space for this driver.
5. method according to claim 1, wherein this system kernel is the extensible firmware interface.
6. method according to claim 1, wherein this first storage element is a ROM (read-only memory), and this second storage element is a dynamic RAM.
7. computer system comprises:
First storage element, stocking system kernel, driver and address information;
Second storage element; And
Controller, be coupled to this first, this second storage element, be used for this system kernel in this first storage element is stored in the interior system kernel storage area of this second storage element, and this driver in this first storage element is stored in the interior predetermined storage space of this second storage element; And this system kernel that operation is stored in this interior system kernel storage area of this second storage element is installed this driver to read this driver according to this address information from this predetermined storage space;
Wherein this address information is used to define predetermined this predetermined storage space that is stored in this second storage element of this driver.
8. computer system according to claim 7, wherein this predetermined storage space is in close proximity between this system kernel is stored to.
9. computer system according to claim 7, wherein this controller this address information that this first storage element is stored writes this second storage element; And this controller is installed this driver according to this stored in this second storage element address information.
10. computer system according to claim 7, wherein this address information includes the start address that this driver is stored in this predetermined storage space.
11. computer system according to claim 7, wherein this system kernel is the extensible firmware interface.
12. computer system according to claim 7, wherein this first storage element is a ROM (read-only memory), and this second storage element is a dynamic RAM.
13. a computer system that is used to produce system software comprises:
First logical block, it decides address information according to the predetermined storage space in the predetermined storage element that is stored in object computer of driver, and this address information is used for auxiliary this object computer this driver is installed;
Second logical block, it produces this system software according to system kernel, this driver and this address information; And
Storage element is coupled to this first logical block and this second logical block, is used for storing this system kernel, this driver and this address information and this system software.
14. computer system according to claim 13, wherein this second logical block is integrated this system kernel, this driver and this address information and is used as this system software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100738980A CN100437490C (en) | 2006-04-05 | 2006-04-05 | Method for mounting driving program and computer system thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100738980A CN100437490C (en) | 2006-04-05 | 2006-04-05 | Method for mounting driving program and computer system thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1825284A CN1825284A (en) | 2006-08-30 |
| CN100437490C true CN100437490C (en) | 2008-11-26 |
Family
ID=36935970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100738980A Active CN100437490C (en) | 2006-04-05 | 2006-04-05 | Method for mounting driving program and computer system thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100437490C (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5598563A (en) * | 1992-11-16 | 1997-01-28 | Microsoft Corporation | Method of loading device drivers from ROM without requirement of system to have any harddisks or floppy drives and without using config.sys file |
| US5675795A (en) * | 1993-04-26 | 1997-10-07 | International Business Machines Corporation | Boot architecture for microkernel-based systems |
| CN1380603A (en) * | 2001-04-10 | 2002-11-20 | 英业达股份有限公司 | Peripheral equipment with internal driving program and its mounting method |
| CN1536484A (en) * | 2003-04-02 | 2004-10-13 | 2000 | Movable operation system and method for loading said system |
| CN1577252A (en) * | 2003-07-29 | 2005-02-09 | 刘丁阳 | Method and equipment for automatic assembling equipment and driving program |
-
2006
- 2006-04-05 CN CNB2006100738980A patent/CN100437490C/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5598563A (en) * | 1992-11-16 | 1997-01-28 | Microsoft Corporation | Method of loading device drivers from ROM without requirement of system to have any harddisks or floppy drives and without using config.sys file |
| US5675795A (en) * | 1993-04-26 | 1997-10-07 | International Business Machines Corporation | Boot architecture for microkernel-based systems |
| CN1380603A (en) * | 2001-04-10 | 2002-11-20 | 英业达股份有限公司 | Peripheral equipment with internal driving program and its mounting method |
| CN1536484A (en) * | 2003-04-02 | 2004-10-13 | 2000 | Movable operation system and method for loading said system |
| CN1577252A (en) * | 2003-07-29 | 2005-02-09 | 刘丁阳 | Method and equipment for automatic assembling equipment and driving program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1825284A (en) | 2006-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100547551C (en) | Use the method and system of general WindowsPE in the dissimilar operating systems | |
| US20050144608A1 (en) | Operating system allowing running of real-time application programs, control method therefor, and method of loading dynamic link libraries | |
| US6000023A (en) | Method for partitioning storage regions on hard disk and computer system adapted to the same | |
| US8589913B2 (en) | Tracking block-level writes | |
| KR101121641B1 (en) | Apparatus and method for controlling operation of system | |
| US6523101B1 (en) | Installed-software development assistance system | |
| US20010032038A1 (en) | Method for applying control data for an electronic motor vehicle control unit | |
| CN101814038A (en) | Method for increasing booting speed of computer | |
| CN1645345A (en) | Information processing apparatus and method | |
| JP2009151826A (en) | Modifiable partition boot record for computer memory device | |
| CN105830023A (en) | Executable code for constrained computing environments | |
| US8397055B2 (en) | Method and system for post-build modification of firmware binaries to support different hardware configurations | |
| CN101166229A (en) | A TV software update method | |
| CN114691178B (en) | Firmware upgrading method and device based on EtherCAT communication driver | |
| CN101484878B (en) | A method to use global variables for pre-EFI initialization modules in EFI-based firmware | |
| CN1242322C (en) | Universal software developing supporting system | |
| CN100437490C (en) | Method for mounting driving program and computer system thereof | |
| US20080028384A1 (en) | Interconnection interface for flexible online/offline deployment of an n-layered software application | |
| US20060248327A1 (en) | Computer rapid boot system and method | |
| CN101604253A (en) | Computer system and startup method | |
| JP2006202233A (en) | Controller and program for same | |
| US20190065176A1 (en) | Method for Changing Over to a Firmware Version in an Electrical Control Unit for a Drive System, Electrical Control Unit and Drive System | |
| CN1371051A (en) | BIOS updating method of computer system | |
| TWI309380B (en) | Method and computer system capable of expediting installation of a driver during a computer boot sequence | |
| CN100336036C (en) | Multiple operating system boot loading method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |