U.S. patent application number 10/128150 was filed with the patent office on 2004-02-05 for system and method for automated display driver management.
Invention is credited to Han, Taisheng, Rochford, Keith Garrett II.
Application Number | 20040025156 10/128150 |
Document ID | / |
Family ID | 29248439 |
Filed Date | 2004-02-05 |
United States Patent
Application |
20040025156 |
Kind Code |
A1 |
Rochford, Keith Garrett II ;
et al. |
February 5, 2004 |
System and method for automated display driver management
Abstract
A method and system of an automated computer video display
driver management system in setting up a video driver for a
corresponding video display controller adapter is disclosed. The
process including the steps of verifying motherboard chipset,
removing pre-existing driver files, and installing appropriate
driver files for the video display controller adapter installed in
the computer system.
Inventors: |
Rochford, Keith Garrett II;
(Yorba Linda, CA) ; Han, Taisheng; (Placentia,
CA) |
Correspondence
Address: |
OPPENHEIMER WOLFF & DONNELLY
P. O. BOX 10356
PALO ALTO
CA
94303
US
|
Family ID: |
29248439 |
Appl. No.: |
10/128150 |
Filed: |
April 22, 2002 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10128150 |
Apr 22, 2002 |
|
|
|
09747783 |
Dec 22, 2000 |
|
|
|
60285396 |
Apr 16, 2001 |
|
|
|
Current U.S.
Class: |
717/174 ;
715/719 |
Current CPC
Class: |
G06F 9/4411
20130101 |
Class at
Publication: |
717/174 ;
345/719 |
International
Class: |
G06F 009/445 |
Claims
What is claimed is:
1. A process for installing a video display software driver in a
computer system for a corresponding video display controller
adapter, comprising: identifying motherboard chipset in the
computer system; removing all display driver files in the computer
system; and installing display driver files into the computer
system.
2. A process for installing a video display software driver in a
computer system as recited in claim 1, wherein the identifying
motherboard chipset further comprising: determining motherboard
chipset by reading chipset information in the registry of the
computer system; and determining whether or not GART driver needs
to be updated.
3. A process for installing a video display software driver in a
computer system as recited in claim 1, wherein the process of
removing all display driver files including establishing a list of
enumerated display adapters and deleting all enumerated display
adapter files.
4. A process for installing a video display software driver in a
computer system as recited in claim 1, including installing the
driver files in names different from their ultimate names and
renaming the names to their ultimate names during a subsequent
rebooting process.
5. A system for installing a video display software driver in a
computer system for a corresponding video display controller
adapter, comprising: means for identifying motherboard chipset in
the computer system; means for removing all display driver files in
the computer system; and means for installing display driver files
into the computer system.
6. A system for installing a video display software driver in a
computer system as recited in claim 5, wherein the means for
identifying motherboard chipset further comprising: means for
determining motherboard chipset by reading chipset information in
the registry of the computer system; and means for determining
whether or not GART driver needs to be updated.
7. A process for installing a video display software driver in a
computer system as recited in claim 5, wherein the means for of
removing all display driver files including means for establishing
a list of enumerated display adapters and deleting all enumerated
display adapter files.
8. A process for installing a video display software driver in a
computer system as recited in claim 5, including means for
installing the driver files in names different from their ultimate
names and renaming the names to their ultimate names during a
subsequent rebooting process.
9. A computer program product embodying a program of instructions
executable by a machine to perform method steps for installing a
video display software driver in a computer system for a
corresponding video display controller adapter, said product being
operative to execute a method comprising: identifying motherboard
chipset in the computer system; removing all display driver files
in the computer system; and installing display driver files into
the computer system.
10. A computer program product as recited in claim 9, wherein the
identifying motherboard chipset further comprising: determining
motherboard chipset by reading chipset information in the registry
of the computer system; and determining whether or not GART driver
needs to be updated.
11. A computer program product as recited in claim 9, wherein the
process of removing all display driver files including establishing
a list of enumerated display adapters and deleting all enumerated
display adapter files.
12. A computer program product as recited in claim 9, including
installing the driver files in names different from their ultimate
names and renaming the names to their ultimate names during a
subsequent rebooting process.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] Reference is made to and priority claimed from U.S.
Provisional Application Serial No. 60/285,396, filed Apr. 20, 2001,
entitled "System and Method for Automated Driver Management;" this
is further a continuation-in-part application to U.S. application
Ser. No. 09/747,783, filed Dec. 22, 2000, entitled "Method and
Apparatus for Automated Driver Management."
COPYRIGHT RIGHT NOTICE
[0002] A portion of the disclosure of this patent document contains
material, which is subject to copyright protection. The copyright
owner has no objection to the facsimile reproduction by anyone of
the patent document or the patent disclosure, as it appears in the
Patent and Trademark Office patent file or records, but otherwise
reserves all copyright rights whatsoever.
BACKGROUND OF THE INVENTION
[0003] 1. Field of the Invention:
[0004] The present invention relates generally to the filed of
setting up a computer video driver, and more particularly to the
system and apparatus of an automated computer video driver
management system in setting up a video driver in accordance with
the video controller utilized in the computer system.
[0005] 2. Description of the Prior Art:
[0006] FIG. 1 is a flow diagram illustrating the process of
installing a new video interface controller in a computer system.
As shown in FIG. 1, conventionally, replacing a video interface
controller card in a computer system involves the following
process:
[0007] A) power off the computer system to avoid causing damages to
components or hazardous to the person who is going to install the
new video controller card (step 10);
[0008] B) remove the computer case cover to gain access to the bus
for installing the new video controller card or remove the
pre-existing video controller card in the system (step 12);
[0009] C) remove the old video controller adapter for installing
the new video controller adapter (step 14);
[0010] D) install the new video controller adapter in the bus of
the computer system (step 16);
[0011] E) replace the case cover (step 18);
[0012] F) power on the computer system (step 20); and
[0013] G) follow video controller adapter manufacturer's directions
for installing the video display driver for the new adapter (step
22).
[0014] The problem with this process is that in some cases the
preexisting display drivers are not correctly removed from the
system and the new display adapter tries to use those old drivers.
This will result in a botched installation and will limit function
to a standard VESA SVGA screen display of 640.times.480.times.4 bit
color.
[0015] The above-identified problem occurs as a result of the
Windows System Registry contains no entry for a Standard VGA PCI
graphics adapter device. As a result, the system is forced to
identify all new video graphics adapters with the drivers it
already has installed in the system. However, the driver installed
previously is invariably incorrect for the new video controller
adapter.
[0016] When installing an upgraded P&P (Plug and Play) graphics
adapter in a computer system running Microsoft Windows 95, Windows
98, Windows ME, and Windows 2000 operating systems, several
problems can occur. The first is that the computer system can
become confused and attempt to use wrong video drivers for the
graphics card, resulting in a configuration that is limited to the
bare minimum video functions--if it functions at all. The second is
that on many modem motherboards, the video controller chipsets are
manufactured by a third party vendor other than Intel. Because of
Intel's claim on AGP (Accelerated Graphics Port, which is a
platform bus specification that provides high performance graphics
capabilities on personal computers) technology, AGP controllers
made by other vendors may need special drivers in order to allow
AGP graphics cards to work correctly. Many home and business users
do not know that this is an essential step before the newly
installed graphic card will properly function, and as a result may
cause tremendous trouble properly configuring their graphics
adapters.
SUMMARY OF THE INVENTION
[0017] Automated Driver Management (ADM) addresses this problem by
interacting with the user's computer system before a new graphics
adapter is installed. When run, ADM actively causes the computer
system to install the Standard PCI Graphics Adapter driver that is
inherent to all Microsoft Windows operating systems. This driver
provides a wide degree of compatibility and is suitable for the
purposes of graphic adapter upgrades. This guarantees that the
older video graphics driver has been removed and will not interfere
with the installation of a new graphics adapter.
[0018] Briefly, a presently preferred embodiment of the present
invention includes a process for installing a video display
software driver in a computer system for a corresponding video
display controller adapter. The process includes the steps of
identifying motherboard chipset in the computer system; removing
all display driver files in the computer system; and installing
display driver files into the computer system.
[0019] An alternative embodiment of the present invention includes
a system for installing a video display software driver in a
computer system for a corresponding video display controller
adapter. The system includes means for identifying motherboard
chipset in the computer system; means for removing all display
driver files in the computer system; and means for installing
display driver files into the computer system.
[0020] In yet another embodiment of the present invention includes
a computer program product embodying a program of instructions
executable by a machine to perform method steps for installing a
video display software driver in a computer system for a
corresponding video display controller adapter. The product being
operative to execute a method including the steps of identifying
motherboard chipset in the computer system; removing all display
driver files in the computer system; and installing display driver
files into the computer system.
[0021] The foregoing and other objects, features, and advantages of
the present invention will be apparent from the following detailed
description of the preferred embodiment which makes reference to
the several figures of the drawing.
IN THE DRAWING
[0022] FIG. 1 is a flow diagram illustrating the conventional
process of installing a new video interface controller in a
computer system;
[0023] FIG. 2 is a flow diagram illustrating an exemplary process
of installing a new video interface controller in a computer system
of the preferred embodiment of the present invention;
[0024] FIG. 3 is a flow diagram illustrating an exemplary
embodiment of the ADM process of the present invention;
[0025] FIG. 4 is a flow diagram illustrating an exemplary process
in the message.exe program of the present invention.
[0026] FIG. 5 is a flow diagram illustrating an exemplary overview
process of installing video drivers in accordance with the present
invention;
[0027] FIG. 6 is a flow diagram depicting an exemplary process of
checking graphics chipset installed in a computer system;
[0028] FIG. 7 is a flow diagram showing an exemplary process of
removing video driver files in a computer system according to the
present invention; and
[0029] FIG. 8 is a flow diagram illustrating an exemplary process
of installing new video drivers for a new video card installed in a
computer system according to the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0030] The present invention provides a method for an automated
video display driver management system. The automated video display
driver management system of the present invention uses a very
simple and straightforward methodology to accomplish the task of
installing a driver for a video display controller adapter. The
invention can be executed via Win32 API through the following
process:
[0031] 1) identify the operating system (OS) version of the target
system and direct the code execution to the proper subroutines
based on the OS version;
[0032] 2) open the display control panel;
[0033] 3) feed the installation sequence to the display control
panel utilizing the KeyBd_Event API.
[0034] As illustrated in FIG. 2, the present invention discloses a
method that simplifies the process of installing a corresponding
software driver when a new video controller board is installed in a
computer system. The process includes the following operation:
[0035] A) execute a proprietary automated driver management (ADM)
application program (step 24); (please see FIG. 3 for details of
ADM operation).
[0036] B) power off the computer system to avoid causing damages to
components or hazardous to the person who is going to install the
new video controller card (step 26);
[0037] C) remove case cover to gain access to adapter cards (step
28);
[0038] D) remove the pre-existing video display controller adapter
from the system bus to free up space for the new video display
controller adapter (step 30);
[0039] E) install the new video display controller adapter in the
system bus (step 32);
[0040] F) replace the case cover to protect adapter cards (step
34);
[0041] G) power on the computer to get it working again (step
36);
[0042] H) follow manufacturer's directions for installing the
drivers for the new adapter (step 38).
[0043] This method, with ADM being run first, eliminates the
problems of a new display adapter trying to use drivers for the old
display adapter. Note how it fits seamlessly into the standard
installation process.
[0044] FIG. 3 is a flow diagram illustrating an exemplary
embodiment of installing the software driver for the newly
installed video display controller adapter in the ADM process of
the present invention. The process of automatically installing a
corresponding software driver for a new video display controller
board comprises the following operation:
[0045] A) User selects the "Run ADM" option from the main
installation screen of the installer CD to execute the ADM
application program (step 40);
[0046] B) The execution of ADM application program operation is not
being displayed in the program form (step 42). In one embodiment, a
form containing a proprietary graphics in the form of a thermometer
style progress bar or an hour-glass is being displayed in stead.
This is done to allow the user to monitor the progress of the
operation without actually seeing all of the system operations in
action.
[0047] C) A secondary program file called Message.exe is copied
over to user system from the installation disk (step 44). This
program will be used in subsequent process of the ADM driver
installation operation. This file is copied over at this point
because the full operation of the ADM program requires the computer
system to be rebooted after the installation operation is complete.
In one embodiment of the invention, the installation disk is in the
form of a compact disk.
[0048] When the computer system reboots, it looses all information
that has not been saved to the hard drive. With the message file
copied over, and with the registry setting that is implemented in
subsequent step H to be described, the ADM program will be able to
pick up where it left off when the computer starts back up after a
necessary reboot.
[0049] D) ADM identifies the version of the operating system under
which the system is in running (step 46). This is done by examining
the major and minor product release version information stored in
the System Registry and interpreting the operating system type
based on those version numbers. This is done because different
version of the Windows operating systems use different menu systems
to interact with the Windows Display Control Panel. It is essential
that the operating system release version be identified for the ADM
operation to be successfully performed. By detecting the operating
system, the program will be able to choose the correct sequence of
keystrokes that are needed to navigate the Display Control Panel.
E1/E2) These are the two different subroutines that are used to
contain the instructions to be used based on the operating system
type. One subroutine exists for each operating system that the
program supports (Windows 95 and Windows 98). Both of these
subroutines use the method described in step G (sending keyboard
commands to the Display Control Panel), but they each use a
different sequence of keystrokes depending on the operating system
version.
[0050] F) Next is to open the Display Control Panel under the
Windows operating system (step 48). This process begins the main
execution operation for ADM. At this point, the Windows Display
Control Panel is opened so that the ADM program will have fall
access to it. This is conducted by making a standard system call
and running the desk.cpl file (which is the Display Control Panel
in Windows 95 and Windows 98).
[0051] G) Next is to invoke command keystrokes via KeyBd_Event
application program (step 50). This is the most important portion
of the program's operation. At this point, keyboard commands are
automatically sent to the Windows Display Control Panel that was
opened just prior to this process step.
[0052] The commands are sent using the Win32 API Keybd_Event, a
standard Windows system call. There is a delay of between 1500 and
3000 milliseconds between the issuance of each command to provide
the computer with sufficient time to process each command before
the next is issued. While a delay of 500 milliseconds was found to
be appropriate, these longer delay in timing is provided ensure
that certain computers not equipped with the latest technology that
may be slower than the most up-to-date computer technology would
also have sufficient time to process each step. This delay can be
eliminated (as is planned in the next revision of the software) by
examining the state of the Windows Display Control Panel and only
allowing the ADM program to continue to the next command when the
Display Control Panel has finished processing the last command.
This will result in a very big boost in program execution time
(thereby lowering the time needed to execute the program).
[0053] The sequence of keystrokes being most important to ADM, are
provided below:
[0054] In a Windows 98 environment, the keystroke sequence is:
[0055] ALT-D--Presses advanced button
[0056] CTL-TAB--Moves to settings tab
[0057] ALT-C--Presses change button
[0058] ENTER--Presses next button
[0059] DOWN--Presses down arrow (to display a list of all
drivers)
[0060] ENTER--Presses next button
[0061] ALT-A--Chooses show all hardware
[0062] ALT-M--Moves focus to manufactures section
[0063] HOME--Chooses first item in manufacturers section
[0064] ALT-D--Moves focus to device section
[0065] DOWN--Presses down arrow
[0066] DOWN--Presses down arrow (standard pci vga adapter is now
selected)
[0067] ENTER--Presses next button
[0068] ENTER--Presses next button
[0069] ENTER--Presses next button
[0070] ALT-A--Presses apply button
[0071] ENTER--Presses close button
[0072] In a Windows 95 environment, the keystroke sequence is:
[0073] ALT-A--Presses advanced button
[0074] ALT-C--Presses change button
[0075] ALT-A--Chooses show all hardware
[0076] ALT-M--Moves focus to manufacturers section
[0077] HOME--Chooses first item in manufacturers section
[0078] ALT-D--Moves focus to device section
[0079] DOWN--Presses down arrow
[0080] DOWN--Presses down arrow (standard PCI VGA adapter is now
selected)
[0081] ENTER--Presses next button
[0082] ALT-A--Presses apply button
[0083] TAB--Moves focus to next button/object
[0084] TAB--Moves focus to next button/object
[0085] ENTER--Presses OK button
[0086] TAB--Moves focus to next button/object
[0087] TAB--Moves focus to next button/object
[0088] TAB--Moves focus to next button/object
[0089] ENTER--Presses close button
[0090] After executing one of these subroutines, they both pass
control of the program to a finishing routine in step 52 as shown
in FIG. 3. In this routine there is one final keystroke that is
issued and is the same for both Windows 95 and Windows 98. This is
ENTER--it presses or selects the "OK" button for the confirmation
dialog box that is asking if it is "OK" to reboot the computer
system at this time. The "OK" must be selected or pressed so that
the system reboots and the changes that have been made for the
newly installed video display controller adapter can take effect.
As each keystroke is issued, the thermometer bar or hour-glass as
described in step 42 above increments itself in order to give an
ongoing display of progress to the user.
[0091] H) Next step is to finalize the Reboot Registry settings
(step 52). In this step the final entries are made to the system
registry. The most important of which is the RunOnce entry to the
KLM/Software/Microsoft/Win- dows/CurrentVersion/RunOnce registry
key that makes the computer call the Message.exe program
immediately when the system is rebooted. The other step is the
final issuance of a keystroke (the ENTER key) that allows the
computer to reboot--as mentioned at the end of step 50 described
above.
[0092] I) Next step is to reboot the computer system (step 54). The
computer reboots and Message.exe is being executed before the
operating system can fully load, due to the registry entry that was
made for it in step 52. This is a very simple program that
instructs the user to perform subsequent steps in the installation
process (such as physically removing the pre-existing video display
controller adapter and installing the new one) and then shuts off
the power to the computer. Please see FIG. 4 for more detailed
description regarding the process in the Message.exe program.
[0093] J) The user substitutes the pre-existing video display
controller adapter with the new adapter, and proceeds to power on
the computer system (step 56).
[0094] K) During the process of rebooting the computer system,
Windows recognizes a new video display adapter has been installed,
and will not attempt to use drivers from the previous adapter. It
will set the active display driver to the Standard VGA Adapter
driver that is common to all versions of Windows and it will then
cause the computer to be rebooted (step 58).
[0095] L) Once the operating system detects the new video display
controller adapter, it reboots the computer system automatically
with the standard VGA drive (step 60). This is the rebooting that
Windows will do on its own as described in step 58. This step is
needed to allow Windows an opportunity to reload all of the updated
settings in effect.
[0096] M) After the computer boots up this time, a command left in
the HKLM/Software/Microsoft/Windows/CurrentVersion/RunOnce registry
key (entered by the Message.exe program that executed in step 54
described above) will tell it to execute a program on the main
installation CD that brings up a proprietary installation screen,
so that the user can choose the install driver option in order to
finalize the installation of their graphics adapter (step 62).
[0097] FIG. 4 is a flow diagram illustrating an exemplary process
in the message.exe program of the present invention. Message.exe is
a simple program that is meant to be a helper program for ADM of
the present invention. It is used primarily to provide feedback and
information to the user so that they retain a sense of control over
the installation operation of the present invention. While all of
the ADM and Message.exe operations could be done without any
feedback to the user at all, most users would develop a very
disconcerted feeling if they saw their computer engaging in so many
processes with no feedback whatsoever. The operation of the program
message.exe includes the following processes:
[0098] A) A standard program form is created that contains text
information advising the user that the computer system will now be
shut down and that they are to remove their old graphics adapter
and install a new one (step 64). It further refers the user to his
or her owner's manual. This is a user interface feature and is not
extremely important to the overall operational process. There is
also a button created on this form that following steps (steps
66-70) will be executed if the button is when clicked.
[0099] B) Message.exe now looks for the original source CD by
scanning through the drive letters from lowest to highest looking
for the CD (step 66). When it finds the CD it notes its location
and exits the process step. It is essential to conduct this step 66
because a proprietary setup program must be executed automatically
for the user when the last reboot for ADM occurs (in step 62
illustrated in FIG. 3). With this information, the location of the
CD in the system can be recorded and then refer to it in future
operations when necessary.
[0100] C) The location of the CD is entered into the
HKLM/Software/Microsoft/Windows/CurrentVersion/RunOnce registry key
for use in the next full reboot in order to automatically launch
our setup CD (step 68).
[0101] D) The computer is powered off (step 70) so that the user
can remove pre-existing video display controller card and install a
new one.
[0102] Following is the source code for the Automated Driver
Management operation:
[0103] unit adm;
[0104] interface
[0105] uses
[0106] Windows, Messages, SysUtils, Classes, Graphics, Controls,
Forms, Dialogs,
[0107] StdCtrls,ShellApi, ComCtrls, ExtCtrls, Registry;
[0108]
[0109] An alternative to the above-described process address the
problem by interacting with the operating system used in the
computer system. As is illustrated in FIG. 5, the process involves
steps in conducting chipset check (step 72), driver removal (step
74), and driver installation (step 76). The chipset check process
(step 72) determines the chipset on the motherboard of the computer
system, and whether or not appropriate corresponding video drivers
have been installed for the motherboard to use the AGP graphics
adapter In the driver removal process (step 74), searches for
display driver files in the computer system are being conducted.
Once the files are identified, they are removed. Further, all
references to display adapters from the computer system are being
removed in order to force a complete re-detection of display
hardware. The driver removal process (step 76) eliminates the risk
of utilizing a wrong display driver for the computer system. The
final process is install drivers for the appropriate display
adapter in the computer system. The process includes coping all
essential driver files for the display adapter to that Windows
initiates a re-detection operation for the appropriate
corresponding display driver.
[0110] As is described above, ADM (Automatic Driver Management)
operates in three stages, with the last two working in direct
conjunction with one other. The first stage is to check the chipset
(step 72) on the motherboard of the computer system. In this stage,
the first step is to determine the operating system in the computer
system, as different approaches must be used by the software
depending on the operating system. Here, the check verifies whether
or not Windows NT is being used as the operating system (step 78).
The process terminates if the computer system is using Windows NT
operating system. Otherwise, the computer system's registry is
being examined to determine the hardware identification codes that
it detected as being installed (step 80). Next, reference those
identification codes against an internal database to find matches
for the motherboard chipset--from this operation the type of
chipset that is used on the computer can be identified (step 82).
The next step is to determine whether or not the operating system
running in the system is Windows 2000 (step 84). If the operating
system is Windows 2000, then providing the user of the system with
an opportunity to either update the Graphic Aperture Remapping
Table (GART) or to install new drivers in the system (step 86) and
terminates the process after it is done. A GART is a table used to
map pages of graphics information into memory. If the operating
system is not Windows 2000, then based on the type of chipset
identified, examine the registry to determine whether appropriate
GART drivers are installed in the system (step 88). If GART drivers
are installed, then proceed to install display drivers (step 90)
and terminates the process after display drivers are installed.
Otherwise, install GART drivers before display drivers are
installed and go back to the beginning of this process to verify
appropriate drivers are being installed in the computer system.
[0111] After the chipset on the motherboard has been identified and
appropriate GART driver has been installed, the next major
operation is to remove the pre-existing files in the system related
to video display. The driver removal process is illustrated in FIG.
7. The process starts with searching all the .inf driver files in
the hard drive of the computer system (step 94). Next, identified
.inf flies must be determined whether or not they are display
driver files (step 96) and delete any that are display driver files
(step 98). The process of deleting display driver files continues
until all .inf files have been identified (step 100). Next is to
examine the computer's registry and build a list of all graphics
adapters detected (step 102) and examine the computer's registry
and build a list of all display drivers installed (step 104). The
process continues with removing all graphics adapters from the
registry (step 106) and remove all installed display drivers from
the registry (step 108).
[0112] The last stage of the automated driver management operation
is to install new drivers, which is illustrated in FIG. 8, for the
video display hardware in the computer system. The process starts
with using a tailored .inf file, coping all needed driver flies to
the computer using the Windows "setup.dll" program (step 110). This
process allows newer version of the files to be copied onto the
system even though such files are in existence in the system. The
tailored .inf file will copy flies with a name different from their
ultimate name eventually used in the computer system and have these
names renamed in subsequent booting process before the operating
systems attempt to load them and putting them back in use. Next
step is to reboot the Windows operating system (step 112), and
renaming all files to their correct name prior to loading them
(step 114). This is done so as to allow older files of the same
name to be updated with newer versions, even though they might be
currently in use by the computer system, which does not allow any
overwriting to the files. Next is to identify new video hardware
and its corresponding video drivers (step 116). This process occurs
automatically because after removing the pre-existing driver files,
the Windows is responding to the situation as a new video hardware
has been installed in the system and would trigger the Windows'
internal operation to installation and driver search processes.
Next, the Windows operation will reboot the computer system and
allow Windows to detect the card and use the newly installed
drivers (step 118).
[0113] Following is code for carrying out the operation described
above.
[0114] Although the present invention has been particularly shown
and described above with reference to a specific embodiment, it is
anticipated that alterations and modifications thereof will no
doubt become apparent to those skilled in the art. It is therefore
intended that the following claims be interpreted as covering all
such alterations and modifications as fall within the true spirit
and scope of the invention.
* * * * *