An apparatus and method to force the computer system to boot from the boot block. During a computer system power-up and initialization, the computer system determines if the escape key is pressed. If so, the computer system will boot from the code in the boot block, proceeding as if the flash ROM is corrupted. This forces the computer system to boot from the boot block even though the system determines that the flash ROM is not corrupt, allowing the user to flash a ROM at the user's discretion.
|
1. A method to force a computer system into a boot block recovery to flash an image into a non-volatile memory, the method comprising the steps of:
providing a non-volatile memory with a boot block and a system block, wherein the boot block is generally read only and the system block is generally writable; and executing a system start-up routine in the boot block, the start-up routine comprising the steps of: checking for a predetermined user input on system start-up; and if the predetermined user input is detected, forcing execution of boot block recovery code in the boot block, else booting from the system block. 9. A system to force a computer system into a boot block recovery to flash an image for use with a processor, the system comprising:
a non-volatile memory; a system block residing in the non-volatile memory, the system block being generally writable; a boot block residing in the non-volatile memory the boot block generally read only; and boot block code stored in the boot block, the boot block code, when executed, causing the processor to perform the step of: executing a system start-up routine in the boot block, the start-up routine comprising the steps: checking for a predetermined user input on system start-up; and if the predetermined user input is detected, forcing execution of boot block recovery code in the boot block, else booting from the system block. 30. A method to rewrite the boot code of a computing system, the method comprising the steps of:
providing a non-volatile memory with a read-only boot block containing a set of hardware initialization procedures directed to a flash of a non-volatile memory and containing a writable system block containing boot-up procedures; checking for a predetermined user input that is of a predetermined duration during a computer power-up; and if the predetermined user input of the predetermined duration is detected, executing a flash procedure, comprising the steps of: executing the hardware initialization procedures in the boot block to flash the system block of the non-volatile memory; and executing the boot-up procedures, which may or may not have been modified by the flash procedure, in the system block. 18. A computer system that enters into a boot block recovery to flash an image, the computer system comprising:
a processor; a non-volatile memory coupled to the processor; a user input device coupled to the processor for receiving an input; a system block residing in the non-volatile memory, the system block being generally writable; a boot block residing in the non-volatile memory the boot block being generally read only; and boot block code stored in the boot block, the boot block code, when executed, causing the processor to perform the step of: executing a system start-up routine in the boot block, the start-up routine comprising the steps of: checking for a predetermined user input on system start-up; and if the predetermined user input is detected, forcing execution of boot block recovery code in the boot block, else booting from the system block. 4. The method of
after the step of checking for a predetermined user input on system start-up, if no predetermined user input has been entered, performing the steps of: determining if the non-volatile memory has become corrupt; and responsive to determining the non-volatile memory has become corrupt, forcing execution of boot block recovery code in the boot block. 5. The method of
7. The method of
8. The method of
loading a minimal system via a boot using boot block code; and reprogramming the non-volatile memory using the minimal system.
13. The system of
after the step of checking for a predetermined user input on system start-up, if no predetermined user input has been entered, performing the steps of: determining if the non-volatile memory has become corrupt; and responsive to determining the non-volatile memory has become corrupt, forcing execution of boot block recovery code in the boot block. 14. The system of
16. The system of
17. The system of
loading a minimal system in a boot using boot block code; and reprogramming the non-volatile memory using the minimal system.
19. The computer system of
22. The computer system of
after the step of checking for a predetermined user input on system start-up, if no predetermined user input has been entered, performing the steps of: determining if the non-volatile memory has become corrupt; and responsive to determining the non-volatile memory has become corrupt, forcing execution of boot block recovery code in the boot block. 23. The computer system of
25. The computer system of
26. The computer system of
loading a minimal system in a boot using boot block code; and reprogramming the non-volatile memory using the minimal system.
32. The method of
if the predetermined user input of the predetermined duration is not detected, executing the boot-up procedures in the system block.
33. The method of
|
1. Field of the Invention
The present invention relates to flashing an image in a non-volatile memory, and more specifically to forcing the system into a boot block recovery mode even when the non-volatile memory is not corrupt.
2. Description of the Related Art
The pursuit of low maintenance computers has been a defining issue among personal computer manufacturers for many years. The satisfaction of a personal computer (PC) user is related to the reliability of the PC and to the ease of the troubleshooting/correction procedures. PC's that require a low level of maintenance or eliminate troubleshooting and repair by outside technicians have advantages over maintenance intensive PC's. An error which often exceeds the average user's skill level is when the PC's system programmable Read Only Memory (ROM) becomes corrupt.
Historically ROM, which is non-volatile, was not in-system updatable. ROM memories store code and data required to initialize and operate a system. However, as system enhancement and upgrades became common, the desirability of an updatable ROM increased. A need for an updatable ROM was met by the creation of the Electrically-Erasable-Programmable-Read-Only-Memory (EEPROM). The EEPROM is in-system writable and non-volatile. The EEPROM, by means of an electric pulse, can be programmed and erased. A more recent innovation in the memory technology field is flash ROM. Flash ROM is inherently non-volatile and allows for in-system updateability. Flash ROM can be updated by "flashing" a new ROM image on to the chip, while the system is operational, from a variety of possible sources, including removable media devices, modem links, or parallel or serial connectors.
Flash ROMs are frequently used to store embedded code in the PC. A PC system ROM traditionally contains the resident code that runs the system. A Basic Input/Output System (BIOS) is a typical embedded code storage application of the PC. The BIOS is low level code interfacing the operating system to the specific hardware implementation. Typical BIOS functions include the initialization of disk drives, including floppy, hard, and compact, and initialization of the video and graphical interfaces. The BIOS is specifically configured for each PC based on the presence of specific hardware and the current version or manufacturer of the hardware. If the PC hardware is updated or modified, the BIOS may need to be upgraded to properly initialize the new hardware. An updated BIOS can be flashed, by the user, to the flash ROM, after the user has replaced or upgraded a component to the PC.
A potential problem exists when an updated BIOS is flashed. An incorrect BIOS could inadvertently be flashed or the flash could be interrupted resulting in a corrupted ROM. If this occurs, the system would not initialize. To prevent this, the flash ROM memory array is divided into two distinct sections, the boot block and the main block. The previously discussed applications have all resided in the main block of the flash ROM. The boot block of the flash ROM is protected from an ordinary flash, and that data will remain even after a corrupted flash ROM image is flashed.
The boot block can thus be used to store kernel code necessary to initialize the basic components of the system if a corrupted ROM image is present. This may be no more than code sufficient to allow the corrupted ROM to be re-flashed. Typically, the boot block code cannot be altered by standard ROM power levels, such as 3-5 volts, the levels necessary to perform an in-system ROM flash. Instead, the boot block code is usually programmed by using higher voltage levels, such as 12 volts. Therefore even if the ROM is incorrectly flashed because of the code present in the boot block, the system will still initialize enough to allow the user to flash the correct ROM image to the flash ROM, using the techniques discussed above. The boot block traditionally contains the initialization routines for a floppy disk and a keyboard, but no video interface.
Typically, to determine if a flash ROM is corrupt, the computer system verifies the validity of the flash ROM by using a checksum. A checksum is typically calculated by adding all the bytes in the flash ROM; this value should equal a predetermined amount, the checksum amount. If the value does not equal the checksum amount, then the computer system determines that the flash ROM is corrupt and proceeds to execute the boot block code. If the value equals the checksum amount, the computer system determines the flash ROM is not corrupt, and executes the system block code.
A potential problem exists if a corrupt flash ROM's checksum value does equal the checksum amount by chance, if a virus infected image has previously been loaded into the flash ROM, or if it is otherwise desired or necessary to re-flash the ROM without a normal system boot. In these cases, the computer proceeds with a regular boot even though the flash ROM is corrupt. Techniques that enhance the flexibility of re-flashing a ROM would be desirable.
With the increase in distributed networks and the abilities of PCs to link to each other and to link to various networks, improvements in PC security is desirable. Historically, a PC could be "secured" by physical isolation. Today's networked environment, however, makes such total isolation impractical. Therefore, techniques that enhance security of PCs would also be desirable.
A method, apparatus, and computer system according to the invention that forces the computer system into boot block recovery even if there is no internal indication that a re-flash is necessary. The apparatus or computer system determines, during power-up, if an input device has been initialized. If the input device has been initialized, the computer system monitors the input device to see if an input is entered. If an input is entered within a predetermined period, the computer system compares the input to a predetermined recovery input. If the input matches the predetermined recovery input, then the computer system executes the code contained in the boot block rather than the other portion of the flash.
A better understanding of the present invention can be obtained when the following detailed description of the preferred embodiment is considered in conjunction with the following drawings, in which:
The following disclosures are hereby incorporated by reference:
U.S. application Ser. No. 09/070,936, entitled "A COMPUTER METHOD AND APPARATUS TO PROMPT FOR ADMINISTRATIVE PASSWORD TO FLASH A CORRUPTED NON-VOLATILE MEMORY," by Don R. James, Jr., Randall L. Hess, and Jeffrey D. Kane, filed concurrently herewith;
U.S. application Ser. No. 09/070,821, entitled "BOOT BLOCK SUPPORT FOR ATAPI REMOVABLE MEDIA DEVICES," by Paul J. Broyles and Don R. James, Jr., filed concurrently herewith;
U.S. application Ser. No. 09/070,457, entitled "SECURITY METHODOLOGY FOR DEVICES HAVING PLUG AND PLAY CAPABILITIES," by Christopher E. Simonich and Robin T. Tran, filed concurrently herewith;
U.S. application Ser. No. 09/070,942, entitled "METHOD AND APPARATUS FOR REMOTE ROM FLASHING AND SECURITY MANAGEMENT FOR A COMPUTER SYSTEM," by Manual Novia Wayne P. Sharum; Paul H. McGahn and Paul B. Hokanson; Adrien Chrisan filed concurrently herewith;
U.S. application Ser. No. 09/070,866, entitled "A METHOD FOR FLASHING ESCD AND VARIABLES INTO A ROM," by Mark A. Piwonka, Louis S. Hobson, Geffrey D. Kane and Randall L. Hess, filed concurrently herewith;
U.S. application Ser. No. 08/684,413, entitled "FLASH ROM PROGRAMMING," by Patrick R. Cooper, David J. Delisle, and Hung Q. Le filed Jul. 19, 1996; and
U.S. application Ser. No. 09/071,128, entitled "A UNIFIED PASSWORD PROMPT OF A COMPUTER SYSTEM," by Michael D. Garrett, Randall L. Hess; Chi W. So, and Mohammed Anwarmariz, filed concurrently herewith; all of which are assigned to the assignee of this invention.
Turning to
The host bridge 14 is preferably coupled to the processor socket 16, which is preferably designed to receive a Pentium II processor module 30, which in turn includes a microprocessor core 32 and a level two (L2) cache 34. The processor socket 16 could be replaced with different processors other than the Pentium II without detracting from the spirit of the invention.
The host bridge 14, when the Intel 440LX Host Bridge is employed, supports extended data out (EDO) dynamic random access memory (DRAM) and synchronous DRAM (SDRAM), a 64/72-bit data path memory, a maximum memory capacity of one gigabyte, dual inline memory module (DIMM) presence detect, eight row address strobe (RAS) lines, error correcting code (ECC) with single and multiple bit error detection, read-around-write with host for PCI reads, and 3.3 volt DRAMs. The host bridge 14 support up to 66 megahertz DRAMs, whereas the processor socket 16 can support various integral and nonintegral multiples of that speed.
The ISA bridge 24 also includes enhanced power management. It supports a PCI bus at 30 or 33 megahertz and an ISA bus 12 at ¼ of the PCI bus frequency. PCI revision 2.1 is supported with both positive and subtractive decode. The standard personal computer input/output (I/O) functions are supported, including a direct memory access (DMA) controller, two 82C59 interrupt controllers, an 8254 timer, a real time clock (RTC) with a 256 byte complementary metal oxide semiconductor (CMOS) static RAM (SRAM), and chip selects for system Read Only Memory (ROM), RTC, keyboard controller, an external microcontroller, and two general purpose devices. The enhanced power management within the ISA bridge 24 includes full clock control, device management, suspend and resume logic, advanced configuration and power interface (ACPI), and system management bus (SMBus) control, which implement the inter-integrated circuit (I2C) protocol.
The PCI bus 10 couples a variety of devices that generally take advantage of a high speed data path. This includes a small computer system interface (SCSI) controller 26, with both an internal port 38 and an external port 40. In the disclosed embodiment, the SCSI controller 26 is a AIC-7860 SCSI controller. Also coupled to the PCI bus 10 is a network interface controller (NIC) 42, which preferably supports the ThunderLan™ power management specification by Texas Instruments. The NIC 42 is coupled through a physical layer 44 and a filter 46 to an RJ-45 jack 48, and through a filter 50 to a AUI jack 52.
Between the PCI Bus 10 and the ISA Bus 12, an ISA/PCI backplane 54 is provided which include a number of PCI and ISA slots. This allows ISA cards or PCI cards to be installed into the system for added functionality.
Further coupled to the ISA Bus 12 is an enhanced sound system chip (ESS) 56, which provides sound management through an audio in port 58 and an audio out port 60. The ISA bus 12 also couples the ISA bridge 24 to a Super I/O chip 62, which in the disclosed embodiment is a National Semiconductor Corporation PC87307VUL device. The Super I/O 62 contains several logical devices, one of which is a Real Time Clock (RTC). Resident in the RTC of the Super I/O chip 62 is non-volatile Random Access Memory (NV RAM) 63. This Super I/O chip 62 provides a variety of input/output functionality, including a parallel port 64, an infrared port 66, a keyboard controller for a keyboard 68, a mouse port for a mouse 70, additional series ports 72, and a floppy disk drive controller for a floppy disk drive 74. These devices are coupled through connectors to the Super I/O 62. Resident on the keyboard 68 are light emitting diodes (LEDs) 69. The floppy disk drive 74 includes disk drives for a 3½" and 5¼" floppy disks, and includes Advanced Technology Attachment Packet Interface (ATAPI) drives.
The ISA bus 12 is also coupled through bus transceivers 76 to a flash ROM 78, which can include both basic input/output system (BIOS) code for execution by the processor 32, as well as an additional code for execution by microcontrollers in a ROM-sharing arrangement.
The ISA bus 12 further couples the ISA bridge 24 to a security, power, ACPI, and miscellaneous application specific integrated circuit (ASIC) 80, which provides a variety of miscellaneous functions for the system. The ASIC 80 includes security features, system power control, light emitting diode (LED) control, a PCI arbiter, remote wake up logic, system fan control, hood lock control, ACPI registers and support, system temperature control, and various glue logic.
Finally, a video display 82 can be coupled to the AGP connector 18 for display of data by the computer system S.
Again, a wide variety of systems could be used instead of the disclosed system S without detracting from the spirit of the invention.
Turning now to
A boot block sector 202 consists of a first boot block sector 204 of 16 kilobytes and a second boot block sector 206 of 8 kilobytes. The remaining 232 kilobytes form a system block 208 divided into 5 sectors 210-218. In the disclosed embodiment, the first sector 210 has 8 kilobytes, the second sector 212 has 32 kilobytes, and the remaining three sectors 214, 216, and 218 have 64 kilobytes equally. The code stored in the system block 208 preferably contains the Basic Input/Output System (BIOS) code. The BIOS is code interfacing between the operating system and the specific hardware configuration, allowing the same operating system to be used with different hardware configurations. The boot block 202 contains the code necessary to initialize the systems when an anomaly during power-up is detected or when designated by the user. During a boot block 202 initialization, preferably a reduced set of hardware is initialized, thus reducing the size of the code in the boot block 202. The boot block 202 code typically contains an initialization procedure for only the hardware necessary to perform limited functions. Typically a limited function necessary to be performed during boot block 202 initialization is the flash of the ROM 78. The boot block 202 contains code initializing the hardware components necessary to flash the ROM 78 and to prompt the user for an administrative password. The boot block 202 code is contained within the boot block 202, which is protected from spurious initialization. The system block 208 is electronically protected, but the system S is at least physically capable of disabling that protection and overwriting the system block 208. During a flash, the system block 208 sectors is rewritten with a new flash ROM image.
Turning now to
The function keys 302 include 12 keys, designated F1-F12, located along the top of keyboard 68. The numeric keypad 304 is located on the right side of the keyboard. The numeric keypad is configured to resemble a standard adding machine format. The scroll keys 306 are located between the numeric keypad 304 and the QWERTY keys 308. The scroll keys allow the user to move a cursor, displayed on the video display 82 of
The QWERTY keys 308 occupy the left and center of the keyboard 68. The QWERTY keys resemble the standard layout of a typewriter. The QWERTY keys include the letters of the alphabet, digits 0-9, and standard documentation characters. The escape key 310 is located in the top left corner of the keyboard 68. The escape key 310 and function keys 302 can be used to communicate a variety of information to the computer system S, depending on the program currently being executed by the computer system S.
During initial power-up (not a warm boot) the computer system S according to the invention can be forced into booting from the boot block 202 code by pressing and holding down the escape key 310 prior to power-up and during the initialization period. If the escape key 310 is detected, the processor 32 will execute the boot block 202 code and proceed as if a corrupted ROM is detected. The boot block 202 procedure is discussed in copending application "A COMPUTER METHOD AND APPARATUS TO PROMPT FOR ADMINISTRATIVE PASSWORD TO FLASH A CORRUPTED NON-VOLATILE MEMORY," incorporated by reference above. While pressing the escape key 310 is illustrative of the disclosed embodiment, the techniques according to the invention could be implemented by a wide variety of inputs, including but not limited to other keys or a mouse 70.
Turning to
The processor 32 causes error beeps at step 540 and then flashes the keyboard 68 LEDs 69 at step 545 via an 8042 keyboard controller in the Super I/O 62. Then the processor 32 initializes the 8259s interrupt controllers in step 550. The processor 32 then powers up a real time clock (RTC) in step 555 and sets up a memory map and programs the ISA bridge 12 in step 560. The processor 32 then clears the Extended BIOS Data Area (EBDA) and base memory at step 565 before initializing the real time clock (RTC) and direct memory access (DMA) controller at step 570. The processor 32 then unmasks supported interrupt requests (IRQs) at step 575. Proceeding to
The processor 32 then unlocks the flash ROM 78 protection at step 630 and determines if a diskette is present in the floppy drive 74 at step 635. If no diskette is present, the processor 32 then turns on the keyboard 68 LEDs 69, in accordance with the exemplary predefined prompt set, in step 637 before ending the procedure in step 665. The system must be reset to retry ROM flash. If a diskette is present, the processor locks the CMOS and Super I/O access at step 640. The processor 32 then issues audio beeps at step 645 and then performs a boot of the system at step 650. The boot is performed by issuing an INT 19 software interrupt. The boot is performed by the initialized floppy drive, ATAPI drive, or over the parallel or serial ports. If the boot fails, then the processor 32 turns on the keyboard 68 LEDs 69, in accordance with the exemplary predefined prompt set, at step 660 to alert the user. If the boot does not fail, the processor 32 turns on the keyboard 68 LEDs 69, in accordance with the exemplary predefined prompt set, at step 662 and continues to step 665, where the routine is complete. The flow chart diagram ends 665.
Turning now to
The foregoing disclosure and description of the invention are illustrative and explanatory thereof, and various changes in the size, shape, materials, components, circuit elements, wiring connections and contacts, as well as in the details of the illustrated circuitry and construction and method of operation may be made without departing from the spirit of the invention.
James, Jr., Don R., Hess, Randall L., Kane, Jeffrey D.
Patent | Priority | Assignee | Title |
10198388, | Sep 20 2013 | Seagate Technology LLC | Data storage system with pre-boot interface |
6687854, | Oct 27 2000 | TSAI, AN-TE | Method of visually signaling computer hardware faults on keyboard |
6718401, | Jun 27 2001 | BEIJING XIAOMI MOBILE SOFTWARE CO , LTD | System and method for device support |
6785846, | Dec 22 2000 | Intel Corporation | Inexpensive method for diagnosing manufacturing defects in an embedded system |
6832320, | Jul 28 1998 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Ownership tag on power-up screen |
6910157, | Jul 16 1999 | SAMSUNG ELECTRONICS CO , LTD , A CORP OF THE REPUBLIC OF KOREA | Portable computer system for indicating power-on self-test state on LED indicator |
6941452, | Jan 07 2002 | Inventec Corporation | Display system and method for BIOS updating |
7047444, | Dec 26 2001 | Kabushiki Kaisha Toshiba | Address selection for testing of a microprocessor |
7069472, | Sep 29 2000 | Hewlett-Packard Development Company, L.P. | Method for restoring CMOS in a jumperless system |
7254701, | Sep 12 2001 | Winbond Electronics Corp. | Method and device for safeguarding a digital process device |
7350067, | Jun 22 2005 | Hewlett-Packard Development Company, L.P.; HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Bios security management |
7370138, | May 06 2004 | Samsung Electronics Co., Ltd. | Mobile communication terminal including NAND flash memory and method for booting the same |
7599889, | Aug 04 2004 | Hewlett-Packard Development Company, L.P. | Ownership tag on power up screen |
8464038, | Oct 13 2009 | GOOGLE LLC | Computing device with developer mode |
8813244, | Feb 28 2011 | GOOGLE LLC | Developer switch |
9015459, | Aug 10 2011 | Samsung Electronics Co., Ltd. | Method of initializing operation of a memory system |
Patent | Priority | Assignee | Title |
3890601, | |||
4942606, | Feb 07 1989 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Computer with improved keyboard password functions |
4959860, | Feb 07 1989 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Power-on password functions for computer system |
5150407, | Dec 16 1991 | Secured data storage devices | |
5325532, | Sep 25 1992 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Automatic development of operating system boot image |
5327531, | Sep 21 1992 | LENOVO SINGAPORE PTE LTD | Data processing system including corrupt flash ROM recovery |
5375243, | Oct 07 1991 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Hard disk password security system |
5377343, | Jul 19 1990 | Kabushiki Kaisha Toshiba | Security circuit for protecting data stored in an internal memory of a microcomputer |
5388267, | May 29 1991 | Dell USA L P | Method and apparatus for updating and restoring system BIOS functions while maintaining BIOS integrity |
5544356, | Dec 31 1990 | Intel Corporation | Block-erasable non-volatile semiconductor memory which tracks and stores the total number of write/erase cycles for each block |
5557783, | Nov 04 1994 | Canon Kabushiki Kaisha | Arbitration device for arbitrating access requests from first and second processors having different first and second clocks |
5603055, | Jan 27 1994 | NXP B V | Single shared ROM for storing keyboard microcontroller code portion and CPU code portion and disabling access to a portion while accessing to the other |
5870520, | Jun 06 1995 | HTC Corporation | Flash disaster recovery ROM and utility to reprogram multiple ROMS |
5889987, | Sep 30 1996 | Intel Corporation | Flexible non-volatile memory controller with boot block emulation |
5937434, | Feb 14 1997 | Intel Corporation | Method of managing a symmetrically blocked nonvolatile memory having a bifurcated storage architecture |
5944820, | Oct 15 1997 | Dell U.S.A., L.P. | Modifiable partition boot record for a computer memory device |
5951685, | Dec 20 1996 | SAMSUNG ELECTRONICS CO , LTD | Computer system with system ROM including serial-access PROM coupled to an auto-configuring memory controller and method of shadowing BIOS code from PROM |
5951686, | Mar 31 1997 | TREND MICRO INCORPORATED | Method and system for reboot recovery |
5960445, | Apr 24 1996 | Sony Corporation | Information processor, method of updating a program and information processing system |
5964873, | Mar 10 1997 | Samsung Electronics Co., Ltd. | Method for updating a ROM BIOS |
5974528, | Apr 17 1998 | Winbond Electronics Corp. | Microcomputer with embedded flash memory having on-chip programming capability and method of programming data into the embedded flash memory |
5987605, | Feb 28 1998 | Keysight Technologies, Inc | Methods and apparatus for dual-boot memory selection, update, and recovery in a programmable device |
5991875, | Sep 17 1997 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | System configuration card |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Feb 05 1998 | JAMES, DON R | Compaq Computer Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009145 | /0791 | |
Feb 05 1998 | HESS, RANDALL L | Compaq Computer Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009145 | /0791 | |
Feb 05 1998 | KANE, JEFFREY D | Compaq Computer Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009145 | /0791 | |
Apr 30 1998 | Compaq Computer Corporation | (assignment on the face of the patent) | / | |||
Jun 20 2001 | Compaq Computer Corporation | COMPAQ INFORMATION TECHNOLOGIES GROUP, L P | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 012379 | /0653 | |
Oct 01 2002 | Compaq Information Technologies Group, LP | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 015000 | /0305 |
Date | Maintenance Fee Events |
Sep 26 2005 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Oct 06 2005 | ASPN: Payor Number Assigned. |
Sep 28 2009 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Aug 26 2013 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Mar 26 2005 | 4 years fee payment window open |
Sep 26 2005 | 6 months grace period start (w surcharge) |
Mar 26 2006 | patent expiry (for year 4) |
Mar 26 2008 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 26 2009 | 8 years fee payment window open |
Sep 26 2009 | 6 months grace period start (w surcharge) |
Mar 26 2010 | patent expiry (for year 8) |
Mar 26 2012 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 26 2013 | 12 years fee payment window open |
Sep 26 2013 | 6 months grace period start (w surcharge) |
Mar 26 2014 | patent expiry (for year 12) |
Mar 26 2016 | 2 years to revive unintentionally abandoned end. (for year 12) |