JP2012525647A - Method and system for providing data module lock to device hardware, system and method for verifying that a circuit card is compatible with a computer - Google Patents

Abstract

  A system and method for verifying that a circuit card is compatible with a computer to which the circuit card is installed accesses a list of compatible circuit cards stored in the computer's non-volatile memory; and Determining whether it is included in the list and storing operating software on the circuit card only if the circuit card is included in the list of compatible circuit cards. The list of compatible circuit cards can be a plug and play identification information (PnP ID) list stored in the BIOS data of the computer. If the circuit card is not included in the list of compatible circuit cards, power can be removed from the circuit card.

Description

  The present invention relates generally to computer systems, and more particularly to a method for ensuring that a component circuit card operates only on authorized computing devices.

  Modern personal computers, including notebook computers, employ several plug-in modules or cards to provide networking and communication functions. For example, notebook computers are typically assembled and sold to consumers with a built-in wireless (eg, WiFi transceiver) communication card. In the future, notebook computers may be manufactured including cellular network communication cards. Such communication cards include embedded memory that is used to program the functions of the communication card itself. Thus, in addition to providing a communication function, such a communication card is also an embedded data card.

  The US Federal Communications Commission (FCC) regulates the telecommunications industry, including specific rules for intentional and unintentional radiating equipment. Specifically, the FCC issues regulations to control cellular and PCS communication systems, including requirements for devices such as cellular or PCS external or embedded data cards used with notebook computers. FCC regulations protect consumer health and minimize interference with other electronic devices or licensed wireless services. Before the transmitter can be sold in the United States, the transmitter manufacturer must obtain permission from the FCC by demonstrating compliance with the relevant part of Part 47 of the Federal Regulations Code. I must.

  Beyond requiring authentication of the transmitter component, the FCC also requires that the computer and component verify that the component being installed is authenticated to the computer. Such a suitability determination ensures that the wireless transmission function is enabled only for components that have been tested and shown to be compatible with a particular model of computer. This regulation prevents consumers from inadvertently attaching circuit cards or other components to untested computers, thereby leading to violations of FCC product certification requirements. Therefore, WWAN module vendors are required to configure their computer products to perform a suitability determination for each installed component.

  Traditionally, computer manufacturers routinely verify that any component circuit card, such as an embedded data card or communications card in the computer, is certified for use with the computer before it is enabled. Is included in the BIOS (basic input / output system). FIG. 1 illustrates an exemplary method used by a computer manufacturer to verify that a component circuit card connected to a computer is authorized for use with the computer before it is enabled. Indicates. In overview, the BIOS routine may supply power to the card at step 1 and obtain its identification (ID) number at step 3. The plug and play identification (“PnP ID”) number of this card is generally assigned by the card manufacturer to a particular model of card and stored in a non-volatile memory register on the card. In general, a card ID includes a number that identifies the manufacturer, known as a vendor ID (VID), and a number that identifies a specific model or product, known as a product ID (PID). Together, a vendor ID and product ID, referred to herein as a PNP ID, is a number that is globally unique to a particular FCC certified product.

  The BIOS routine then compares in step 5 the PNP ID number received from the card to a list of numbers that are authorized for use with the computer. This PNP ID list is typically stored in the computer's non-volatile memory (eg, electronically programmable read-only memory-EPROM) along with the BIOS software. In test 7, if the card's PNP ID number is on the computer's PNP ID list, in step 11, power is applied to the card, allowing the card to begin operation. However, if the card's PNP ID number is not on the computer's PNP ID list (ie, test 7 = “No”), in step 9, the BIOS disables the card or removes power to the card. To do. FCC regulations require that this process be performed prior to enabling the card's transmitter for each cold power up. In this way, if a communication card is attached to a computer where it is not authorized, the computer does not enable the card, thereby ensuring that the card does not emit intentional emissions.

  The FCC further requires that component circuit cards with wireless transmitters themselves perform conformance tests to ensure that they are used only on certified computers. Therefore, component manufacturers must now include conformance tests as part of the functionality of the component circuit card. By requiring that each component circuit card be connected to a computer for which it is certified, the FCC regulations further include the BIOS routines described above by the computer manufacturer. Protect consumers if they fail. FIG. 2 illustrates an exemplary method used by circuit card manufacturers to comply with this FCC requirement. In step 13, when power is applied to the circuit card, in step 15, the circuit card accesses the computer's PNP ID list from the computer's BIOS EPROM. Then, in step 17, the circuit card checks the received PNP ID list to see if the entry matches the card's PNP ID. In test 19, if the circuit card is included in the PNP ID list, in step 23, the circuit card continues to operate. However, if the circuit card is not included in the computer's PNP ID list (ie, test 19 = “No”), in step 21, the circuit card stops.

  The method for compliance with the FCC regulations described above and illustrated in FIG. 2 requires non-volatile memory and software stored on a circuit card dedicated to complying with this conformance test requirement. This undesirably increases the complexity and cost of the circuit card.

  Various implementation systems and methods for verifying that a circuit card is authenticated to that computer as part of a software download application for the circuit card stored on the hard drive of a particular computer and executed by the processor of the computer Is disclosed. By offloading card and computer compatibility tests to the computer processor and software maintained on the computer hard drive, various embodiments allow for less complex, more affordable FCC-compliant circuit cards To.

  The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the above general description and the following detailed description, illustrate the features of the invention. Help explain.

FIG. 2 is a process flow diagram of a conventional method for a computer to ensure that a circuit card is authorized for use in the computer. FIG. 2 is a process flow diagram of a conventional method for a circuit card to ensure that the circuit card is authorized for use at a host computer. 1 is a system block diagram of an exemplary computer suitable for use with an embodiment. FIG. 3 is a process flow diagram of one embodiment. FIG. 6 is a process flow diagram of an alternative embodiment. FIG. 6 is a process flow diagram of an alternative embodiment.

  Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.

  As used herein, the term “computer” refers to any form of computing device, particularly including notebook computers and portable computing devices. As used herein, the terms “card”, “circuit card”, and “embedded data card” may be included in a computer system to provide a specific transmitter function and require separate FCC certification. A circuit component. The card can be in the form of a single integrated circuit, chipset, or several integrated circuits and circuit elements that can be mounted in a computer system. In a preferred embodiment, the card is a communication card such as a wireless transceiver or a cellular network transceiver that, when attached, allows the computer to communicate with an external wireless network. However, various embodiments apply to any circuit element where the card certificate must be verified and the operating software must be downloaded to the circuit element for the operating software to function.

  Recent FCC regulations that require circuit cards to verify their own certifications for use in a host computer, if the consumer purchases the module and can be installed after the notebook is purchased, It affects the design of circuit cards and can affect their cost and complexity. In order to perform authentication verification in the circuit card, as described above with respect to FIG. 2, the circuit card needs to include a non-volatile memory that stores operating software for performing this test. In most applications, this test is not necessary because the circuit card is installed by the original equipment manufacturer (OEM) of the computer. OEMs are unlikely to install inappropriate circuit cards during assembly, and the FCC does not require the card manufacturer to prove the certification process if only the OEM can install the card. Also, most consumers do not change their computers after purchase by installing new or replacement circuit cards. Thus, in most cases, verification testing is not required, and including compatibility test functions within the circuit card is a non-volatile memory and operating software complexity (and therefore additional) that is almost useless in most situations. Cost).

  In order to comply with FCC requirements while minimizing circuit card complexity, the various embodiments described herein are part of an initialization process that loads operating software onto a circuit card from a computer hard disk. Shift the conformance test to software running on a computer processor. In this way, the circuit card does not need to include non-volatile memory or store software instructions for performing the compatibility test.

  Many circuit cards used in modern computer systems include their own on-board processors that must consist of software instructions for the circuit card to function. Examples of such processor-mounted circuit cards include wireless telecommunication cards (eg, WiFi and cellular network transceiver cards) and GPS receiver cards. Such circuit cards typically include a processor comprised of operating software and random access memory for storing software instructions as well as data. Such circuit cards cannot function without being programmed with their own operating software. Some circuit cards include non-volatile memory that stores operating software instructions used to program its on-board processor. However, some circuit cards require that operating instructions be loaded into non-volatile memory on the circuit card in order to program its on-board processor. Circuit cards that use volatile memory and that are programmed by software stored on a computer hard drive can be inexpensive, by delivering new operating software to consumers (e.g., via the Internet). Can be easily upgraded (by providing software updates). Therefore, before such a circuit card can function, an initialization software routine that runs on the host computer (referred to herein as a “circuit card initialization software routine”) Circuit card operating software must be downloaded to volatile memory. Such circuit card initialization software is either well-known in the computer arts, part of the host computer boot routine, one of the software applications executed during start-up, or component driver software Can be part of

  Various embodiments may be implemented on a variety of computer systems and computer architectures. FIG. 3 is a component diagram of the basic elements of a computer system 50 in which various embodiments may be implemented. As shown in FIG. 3, a typical computer 50 will include a processor 51 such as a microprocessor or microcomputer, a non-volatile memory 52 such as an EPROM, a hard disk memory 54, and a circuit card 56.

  The circuit card 56 can be any of a variety of circuit cards, integrated circuit chips, circuit boards or component devices subject to FCC compliance test requirements. The circuit card 56 may include volatile memory 57 and a card processor 58 that is programmed by operating software instructions stored in the volatile memory 57. Card processor 58 must be programmed with operating parameters and / or using at least some operating software stored in computer hard disk memory 54. The circuit card 56 may be included in the computer 50 as an integral component card or may be an external component such as an external modem, as indicated by the dashed line.

  During initial startup (ie, cold startup), the computer processor 51 may initially be configured with BIOS software and configuration data stored in the non-volatile memory 52. As part of the startup sequence, the computer processor 51 will consist of software instructions downloaded from the hard disk memory 54 of the computer. In various embodiments, the software instructions downloaded to the computer processor 51 include circuit card initialization software routines stored on the hard disk 54. The circuit card initialization software routine causes the processor 51 to perform various method steps as well as the operational data and / or software instructions required by the card processor 58 to perform its functions. Load into memory 57. In particular, as will be described in more detail below, the computer processor 51 adds to the computer's PNP ID list stored in the computer's non-volatile memory 52 to determine whether the circuit card 56 is compatible with the computer 50. For access, it may consist of software instructions stored in the hard disk memory 54. In addition, the computer processor 51 may also access other information related to the circuit card 56, such as a manufacturing string, system ID, etc., useful for determining the compatibility between the circuit card and the notebook system. If the conformance test described in more detail below with reference to FIGS. 4-6 is successful, the processor 51 may download circuit card operating software from the hard disk 54 to the non-volatile memory 57 in the circuit card 56. it can. When so programmed, the circuit card processor 58 can perform the functions of the circuit card 56.

  In various embodiments, a circuit card initialization software routine running on the processor 51 of the computer causes the processor 51 to perform a circuit card compatibility test before downloading the circuit card operating software. The circuit card initialization software routine will generally be stored in the computer hard drive memory 54 when the corresponding circuit card is installed. For example, if the circuit card 56 is installed in the computer 50 by the OEM, the OEM will ensure that the appropriate circuit card initialization software routine is stored in the hard disk memory 54 provided in the computer 50. Become. If circuit card 56 is sold as an aftermarket product that can be purchased and installed by the consumer, the product package is inserted by the consumer into a corresponding recorder (e.g., a compact disc drive (not shown)). It may include a tangible storage medium, such as a compact disc, that can upload the circuit card initialization software routine to the computer hard drive memory 54. Alternatively, the consumer can be prompted to download a circuit card initialization software routine from the Internet. For some applications, the circuit card initialization software routine may replace non-volatile memory instead of hard drive memory 54, such as in mobile devices that employ electronic memory rather than magnetic disk memory (e.g., cellular phones, PDAs, etc.) 52 (such as flash memory).

  In one embodiment, there is a specific circuit card initialization software routine included in the computer's hard disk memory 54 for each circuit card 56 attached to the computer 50. In another embodiment, the computer 50 can perform the circuit card compatibility test of the embodiments described below using the PNP ID number stored in the hard disk memory 54 for each circuit card to be tested. A generic circuit card software installation routine may be executed. In this way, compliance testing can be performed without having to first energize the circuit card 56 or include non-volatile memory or circuitry on the circuit card 56 that can provide its ID to the computer processor 51. Can be completed.

  FIG. 4 shows an exemplary process flow diagram of one embodiment. During a computer initialization routine, sometimes referred to as a “boot” routine, in step 30, the circuit card initialization software routine is activated. This routine can be called as part of the computer's BIOS process. Before starting to download software to the circuit card 56, in step 32, the circuit card initialization software routine causes the computer's processor 51 to query the computer's PNP ID list. This can be accomplished by the processor 51 accessing the PNP ID list from the computer's BIOS EPROM memory 52. For example, the PNP ID list can be accessed using standard Microsoft calls to BIOS information.

  Upon receipt of the PNP ID list, in step 34, the circuit card initialization software routine causes the processor 51 to check the PNP ID list for the PNP ID of the circuit card 56. To do this, the circuit card initialization software routine may recall the circuit card ID from the data field stored in the computer's hard disk memory 54. Alternatively, the circuit card ID can be programmed into the code of the conformance test software routine. In test 36, if the circuit card is on the computer's PNP ID list, in step 38, the circuit card initialization software routine subsequently downloads operating software to the circuit card. Once the circuit card is programmed, at step 40, the circuit card can begin normal operation. However, if the circuit card initialization software routine determines that the circuit card is not listed in the computer's PNP ID list (ie, test 36 = “No”), then in step 42, the circuit card operating software download is terminated. obtain. This will cause unauthenticated cards (i.e., cards that are not authenticated or possibly not listed in the PNP ID list) to stay in the software download stage before they can be used or activated. . In one embodiment, in step 44, the circuit card initialization software routine may also cause the processor to remove power to the circuit card if the circuit card ID is not listed in the computer's PNP ID list.

  This embodiment inevitably complies with FCC requirements for circuit card certification at cold power-up because the circuit card operating software is removed from the circuit card volatile memory whenever power to the circuit card 56 is interrupted. To comply. Even if the compatibility test is not performed, the circuit card 56 will not operate without its operating software, so the circuit card 56 will not operate.

  The timing of conformance testing within the computer's initialization routine can vary depending on the manufacturer's preference. For example, the circuit card initialization software routine may operate whenever computer 50 itself is started (ie, from a cold power up). In this way, the circuit card 56 is checked and activated as part of the overall startup sequence of the computer. Alternatively, the circuit card initialization software routine may be run when the circuit card 56 is activated, such as when the user chooses to activate a particular function. For example, if the computer 50 is configured so that the wireless communication card is not activated (eg, a setting suitable for using the computer on a commercial aircraft), then a conformance test need not be performed. However, if the user later chooses to activate the wireless communication function of the computer, the circuit card initialization software routine will be activated and a compatibility test will be performed at this point.

  An alternative embodiment that may be implemented in a computer system that includes a “hibernate” or “standby” partial operating mode is shown in FIG. In the sleep or standby mode, the computer 50 is brought into a state where a quick restart is possible. In some embodiments, some memory modules may continue to be powered to maintain software and / or data in the memory. Since the FCC only requires that a suitability test be performed each time the computer 50 performs a cold power up, there is no regulatory need to perform the process steps described above with respect to FIG. Referring to FIG. 5, when the computer returns to normal operation from standby or hibernation, a circuit card initialization software routine may be activated at step 30. In this embodiment, the circuit card initialization software routine may first cause the computer's processor 51 to determine in a test 46 whether the instant startup process is a return from either a hibernation or standby state. This can be accomplished by testing a flag in memory that indicates the type of startup that is in progress. If the startup is part of a cold power-up (ie, test 46 = “No”), in steps 32-44, the process may continue in the manner described above with respect to FIG. However, if the circuit card initialization software routine has been activated as part of a hibernation or return from standby state (i.e., test 46 = “Yes”), in step 38, the software routine causes the computer processor 51 to The circuit card 56 may be jumped to the step of downloading operating software.

  The embodiment shown in FIG. 5 may allow a quicker restart from hibernation or standby by eliminating the need to perform a conformance test. This embodiment is compliant with FCC requirements, as conformance testing need only be performed when a cold power up is performed. Some additional steps may also be included to ensure that the non-conforming circuit card is not energized after restart from hibernation or standby.

  In a further embodiment shown in FIG. 6, the circuit card initialization software routine is a computer memory (e.g., maintained during hibernation or standby) that indicates whether the previous implementation of the circuit card conformance test was successful. 52 or 54) may also include a flag variable test 48 stored. If the computer processor 51 determines that the ID of the circuit card is listed in the PNP ID list (ie, test 36 = “Yes”), in step 37, this compatibility flag may be set. This can be accomplished by the processor 51 storing a flag (eg, “1”) in a particular address in the computer's memory to indicate that the circuit card 56 has been determined to be compatible. . Then, in a subsequent return from hibernation or standby, the circuit card initialization software routine determines in test 46 that the circuit card 56 has been initialized after hibernation or standby, and then in test 48. The processor can be checked for flags. If the match flag is set (eg, equal to “1”), processor 51 may jump to software download step 38. However, if the conformance flag is not set (i.e., test 48 = "No"), indicating that the previous conformance test has failed, processor 51 then proceeds as described above with respect to FIG. The suitability test may be performed again by performing steps 32-36. Alternatively, the processor 51 may subsequently end the software download at step 42 and remove power from the circuit card 56 at step 44 as indicated by the dashed line in FIG.

  The embodiment shown in FIG. 6 ensures that a non-compliant circuit card is not activated even when the computer 50 is returning from hibernation or standby. This embodiment may also bypass performing a compatibility test if the previous test has already shown that the circuit card 56 is not compatible.

  This embodiment has several advantages. By performing compatibility tests using computer processor 51 and software stored in computer hard disk memory 54, circuit card 56 can be less complex and therefore less expensive. There is no need for non-volatile memory on the circuit card 56 (otherwise it would be required to store software instructions to perform conformance tests), thereby reducing the cost from circuit card design. Such components can potentially be eliminated. Even if the non-volatile memory is part of the circuit card 56 for other functional purposes, it is not necessary to fill the non-volatile memory with conformance test software instructions, so it can be used for other card functions More memory will remain. This embodiment also eliminates the complexity associated with providing software in the circuit card 56 that can access memory in the BIOS of the computer. Since circuit cards can be manufactured for a variety of computers, including computers that have not yet been designed and built, this advantage can be achieved with circuit card software that can access specific memories in a wide variety of computer architectures. Eliminate the challenge of designing. In summary, the present embodiment has allowed the circuit card 56 to be a simpler and less expensive design than would normally be required to comply with FCC requirements.

  Note that storing the circuit card compatibility test software on the computer hard drive is more vulnerable to modification by the user than if the software was embedded in the non-volatile memory of the circuit card. However, this is a problem because the FCC requirement prevents consumers from inadvertently installing non-compliant circuit cards in a computer system and does not prevent coordinated efforts to modify or destroy the computer system. I don't get it. This does not protect against hackers, but protects the general consumer. Nonetheless, the circuit card initialization software routine is encrypted or protected by a digital signature so that the computer processor can detect if the software routine has been modified and prevent operation if it has been modified. obtain. Circuit card initialization software routines are also stored in hidden files or hidden memory locations on the hard drive to make it more difficult for users to locate and modify software files. obtain.

  The hardware used to implement the above embodiments can be processing elements and memory elements configured to execute a set of instructions, the set of instructions corresponding to the method steps described above. Is for executing. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

  Those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. Let's be done. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in a variety of ways for each particular application, but such implementation decisions should not be construed as departing from the scope of the present invention.

  The order of several steps may be varied from the order described herein without departing from the spirit and scope of the invention and the claims, and thus the order of the steps of the method described above and shown in the figures. Is for illustration only. The method or algorithm steps described in connection with the embodiments disclosed herein may be implemented directly in hardware, implemented in software modules executed by a processor, or a combination of the two. The software module is either RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art Can reside in processor readable memory, which can be An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC may reside in a user terminal or mobile device. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal or mobile device. Further, in some aspects, the method or algorithm steps and / or actions may be incorporated into a computer program product, one or any combination of code and / or instructions on a machine-readable medium and / or computer-readable medium. , Or as a set of them.

  The above description of various embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. obtain. Accordingly, the present invention is not limited to the embodiments shown herein, but instead, the claims have the broadest scope consistent with the principles and novel features disclosed herein. Should be given.

50 computer system
51 processor
52 Nonvolatile memory
54 Hard disk memory
56 circuit card
57 Volatile memory
58 Card processor

Claims (20)

A computer-implemented method for verifying that a circuit card is compatible with a computer,
Accessing a list of compatible circuit cards stored in a non-volatile memory of the computer;
Determining whether the circuit card is included in the list of compatible circuit cards;
Storing the operating software instructions on the circuit card only if the circuit card is included in the list of compatible circuit cards.   2. The computer-implemented method according to claim 1, wherein the list of compatible circuit cards is a plug and play identification information (PnP ID) list stored in BIOS data of the computer.   The computer-implemented method of claim 1, further comprising removing power from the circuit card if the circuit card is not included in the list of compatible circuit cards. Determining whether the computer is recovering from standby or hibernation;
Without the step of accessing the list of compatible circuit cards and the step of determining whether the circuit card is included in the list of compatible circuit cards, the computer may enter standby or hibernation mode. The computer-implemented method of claim 1, further comprising storing operating software on the circuit card if it is recovered. Determining whether the computer has previously determined that the circuit card is included in the list of compatible circuit cards;
Accessing the list of compatible circuit cards if the computer has previously determined that the circuit card is included in the list of compatible circuit cards; and wherein the circuit card is in the list of compatible circuit cards 5. The computer-implemented method of claim 4, further comprising: storing operating software on the circuit card without repeating the step of determining whether or not it is included in the circuit card. A processor;
A hard disk memory coupled to the processor;
A non-volatile memory coupled to the processor, the non-volatile memory storing BIOS data and software instructions;
A circuit card coupled to the processor, the circuit card including a random access memory,
The hard disk memory is
Accessing a list of compatible circuit cards stored in the non-volatile memory;
Determining whether the circuit card is included in the list of compatible circuit cards;
A processor executable configured to cause the processor to perform steps including storing operating software instructions on the circuit card only if the circuit card is included in the list of compatible circuit cards. Memorized software instructions,
Computer system.   7. The computer system according to claim 6, wherein the list of compatible circuit cards is stored in BIOS data of the computer as a plug and play identification information (PnP ID) list.   The hard disk memory is a processor implementation configured to further cause the processor to perform steps including removing power from the circuit card if the circuit card is not included in the list of compatible circuit cards. 7. A computer system as claimed in claim 6, storing possible software instructions. The hard disk memory is
Determining whether the computer is recovering from standby or hibernation;
Without the step of accessing the list of compatible circuit cards and the step of determining whether the circuit card is included in the list of compatible circuit cards, the computer may enter standby or hibernation mode. 7. The computer of claim 6, storing processor-executable software instructions configured to cause the processor to further perform steps including storing operating software on the circuit card if recovering. system. The hard disk memory is
Determining whether the computer has previously determined that the circuit card is included in the list of compatible circuit cards;
Accessing the list of compatible circuit cards if the computer has previously determined that the circuit card is included in the list of compatible circuit cards; and wherein the circuit card is in the list of compatible circuit cards Storing the operating software on the circuit card without repeating the step of determining whether the processor is included in processor executable software configured to further cause the processor to perform 10. The computer system according to claim 9, wherein instructions are stored. Means for accessing a list of compatible circuit cards stored in a non-volatile memory of the computer;
Means for determining whether the circuit card is included in the list of compatible circuit cards;
Means for storing operating software instructions on the circuit card only if the circuit card is included in the list of compatible circuit cards.   12. The computer according to claim 11, wherein the list of compatible circuit cards is a plug and play identification information (PnP ID) list stored in BIOS data of the computer.   12. The computer of claim 11, further comprising means for removing power from the circuit card if the circuit card is not included in the list of compatible circuit cards. Means for determining whether the computer is recovering from standby or hibernation;
Without the step of accessing the list of compatible circuit cards and the step of determining whether the circuit card is included in the list of compatible circuit cards, the computer may enter standby or hibernation mode. 12. The computer of claim 11, further comprising means for storing operating software on the circuit card if being recovered. Means for determining whether the computer has previously determined that the circuit card is included in the list of compatible circuit cards;
Accessing the list of compatible circuit cards if the computer has previously determined that the circuit card is included in the list of compatible circuit cards; and wherein the circuit card is in the list of compatible circuit cards 15. The computer of claim 14, further comprising means for storing operating software on the circuit card without repeating the step of determining whether it is included. Accessing a list of compatible circuit cards stored in the non-volatile memory;
Determining whether the circuit card is included in the list of compatible circuit cards;
Processor-executable software configured to cause a processor to perform a step including storing operating software instructions on the circuit card only if the circuit card is included in the list of compatible circuit cards A tangible processor readable storage medium storing instructions.   17. The tangible processor readable storage medium of claim 16, wherein the list of compatible circuit cards is stored in the BIOS data of the computer as a plug and play identification information (PnP ID) list.   The stored processor executable software instructions cause the processor to further perform steps including removing power from the circuit card if the circuit card is not included in the list of compatible circuit cards. The tangible processor-readable storage medium of claim 16, configured in The stored processor executable software instructions are:
Determining whether the computer is recovering from standby or hibernation;
Without the step of accessing the list of compatible circuit cards and the step of determining whether the circuit card is included in the list of compatible circuit cards, the computer may enter standby or hibernation mode. The tangible processor readable storage medium of claim 16, configured to further cause the processor to perform steps including: storing operating software on the circuit card if recovered. The stored processor executable software instructions are:
Determining whether the computer has previously determined that the circuit card is included in the list of compatible circuit cards;
Accessing the list of compatible circuit cards if the computer has previously determined that the circuit card is included in the list of compatible circuit cards; and wherein the circuit card is in the list of compatible circuit cards And storing the operating software on the circuit card without repeating the step of determining whether the processor is included in the processor. A tangible processor-readable storage medium according to claim 1.