← Back to Patent Explorer
US6128731A Expired / Lapsed US ⏱️ 0.0 years remaining

Advanced boot sequence for an +86 computer system that maintains expansion card device compatibility

Assignee: Morgan Stanley and Co LLC
•
Filing: 1998-10-21
•
Granted: 2000-10-03
•
Expires: 2018-10-21
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract An ×86 based computer system that implements a firmware based boot process without an ×86 BIOS that supports expansion devices coupled to the computer system, wherein the expansion devices include their own respective BIOS extensions. The computer system includes an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus. The non-volatile memory includes firmware which when executed by the processor cause the computer system to implement the boot process. The firmware initializes device drivers for the computer system and initializes an application programming interface for the device drivers. The firmware then initializes a compatibility component for interfacing with the device drivers, wherein the compatibility component is operable for translating accesses by a first software application to an ×86 BIOS into corresponding accesses to the device drivers. This enables the first software application to execute on the computer system by using the compatibility component while a second software application is able to execute on the computer system by accessing the application programming interface directly. The firmware then runs an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory. The memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is made available to the first application and the second application.

Inventors

  • 👤 Saeed S. Zarrin
  • 👤 John Sully
  • 👤 Daniel Brown
  • 👤 Edward E. Wilcox

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-09 14:57
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/44; G06F9/4401

Claims Analysis

Total Claims: 30
Claim 1
Independent Claim 230 words
An ×86 based computer system that implements a firmware based boot process without an ×86 BIOS that supports expansion devices coupled to the computer system, wherein the expansion devices include their own respective BIOS extensions, comprising: a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, the non-volatile memory including firmware which when executed by the processor cause the computer system to implement the steps of: a) initializing device drivers for the computer system using the firmware; b) initializing an application programming interface for the device drivers by using the firmware; c) initializing a compatibility component for interfacing with the device drivers, wherein the compatibility component is operable for translating accesses by a first software application to an ×86 BIOS into corresponding accesses to the device drivers, such the first software application is able to execute on the computer system by using the compatibility component while a second software application is able to execute on the computer system by accessing the application programming interface directly; and d) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 2
Dependent Claim 230 words
An ×86 based computer system that implements a firmware based boot process without an ×86 BIOS that supports expansion devices coupled to the computer system, wherein the expansion devices include their own respective BIOS extensions, comprising: a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, the non-volatile memory including firmware which when executed by the processor cause the computer system to implement the steps of: a) initializing device drivers for the computer system using the firmware; b) initializing an application programming interface for the device drivers by using the firmware; c) initializing a compatibility component for interfacing with the device drivers, wherein the compatibility component is operable for translating accesses by a first software application to an ×86 BIOS into corresponding accesses to the device drivers, such the first software application is able to execute on the computer system by using the compatibility component while a second software application is able to execute on the computer system by accessing the application programming interface directly; and d) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 3
Dependent Claim 43 words
The system of claim 1, wherein the first software application is a legacy application adapted to execute on an ×86 BIOS based computer system and the expansion device is a legacy expansion device adapted to couple to an ×86 BIOS based computer system.
Claim 4
Dependent Claim 45 words
The system of claim 1, further including the step of performing a bus discovery process to initialize the expansion device, wherein the expansion device is coupled to the computer system via a bus, wherein the firmware determines whether the expansion device includes the BIOS extension.
Claim 5
Dependent Claim 52 words
The system of claim 1, wherein the firmware causes the computer system to further implement the step of running a portion of an ×86 BIOS to initialize the area in volatile memory, wherein the area is configured by the portion to interface with the first software application to enable it to execute.
Claim 6
Dependent Claim 34 words
The system of claim 4, wherein the area in volatile memory corresponds to a 640K memory configuration created in an ×86 BIOS based computer system when the ×86 BIOS based computer system is booted.
Claim 7
Dependent Claim 34 words
The system of claim 1, wherein the firmware causes the computer system to further implement the step of initializing an exception handler to generate exceptions when the first software program accesses the ×86 BIOS.
Claim 8
Dependent Claim 33 words
The system of claim 6, wherein the firmware causes the computer system to further implement the step of initializing the exception handler to generate exceptions when the BIOS extension accesses the ×86 BIOS.
Claim 9
Dependent Claim 25 words
The system of claim 1, wherein the majority of the software code comprising the first software application executes natively on the computer system without translation.
Claim 10
Dependent Claim 24 words
The system of claim 1, wherein the majority of the software code comprising the BIOS extension executes natively on the computer system without translation.
Claim 11
Dependent Claim 253 words
A unified memory architecture ×86 based computer system that implements a firmware based boot process without an ×86 BIOS, comprising: a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, the non-volatile memory including firmware which when executed by the processor cause the computer system to implement the steps of: a) initializing software drivers for hardware of the computer system; b) initializing an application programming interface for the hardware of the computer system; c) running a portion of an ×86 BIOS to initialize a memory area in volatile memory, wherein the area is configured by the portion to interface with a first software application to enable the first software application to execute; d) initializing a compatibility component for interfacing with the hardware, wherein the compatibility component is operable for translating accesses by the first software application to an ×86 BIOS into corresponding accesses to the hardware, such the first software application is able to execute on the computer system by using the compatibility component and the memory area while a second software application is able to execute on the computer system by accessing the application programming interface directly; and e) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 12
Dependent Claim 253 words
A unified memory architecture ×86 based computer system that implements a firmware based boot process without an ×86 BIOS, comprising: a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, the non-volatile memory including firmware which when executed by the processor cause the computer system to implement the steps of: a) initializing software drivers for hardware of the computer system; b) initializing an application programming interface for the hardware of the computer system; c) running a portion of an ×86 BIOS to initialize a memory area in volatile memory, wherein the area is configured by the portion to interface with a first software application to enable the first software application to execute; d) initializing a compatibility component for interfacing with the hardware, wherein the compatibility component is operable for translating accesses by the first software application to an ×86 BIOS into corresponding accesses to the hardware, such the first software application is able to execute on the computer system by using the compatibility component and the memory area while a second software application is able to execute on the computer system by accessing the application programming interface directly; and e) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 13
Dependent Claim 43 words
The system of claim 10, wherein the first software application is a legacy application adapted to execute on an ×86 BIOS based computer system and the expansion device is a legacy expansion device adapted to couple to an ×86 BIOS based computer system.
Claim 14
Dependent Claim 45 words
The system of claim 10, further including the step of performing a bus discovery process to initialize the expansion device, wherein the expansion device is coupled to the computer system via a bus, wherein the firmware determines whether the expansion device includes the BIOS extension.
Claim 15
Dependent Claim 52 words
The system of claim 10, wherein the firmware causes the computer system to further implement the step of running a portion of an ×86 BIOS to initialize the area in volatile memory, wherein the area is configured by the portion to interface with the first software application to enable it to execute.
Claim 16
Dependent Claim 34 words
The system of claim 13, wherein the area in volatile memory corresponds to a 640K memory configuration created in an ×86 BIOS based computer system when the ×86 BIOS based computer system is booted.
Claim 17
Dependent Claim 34 words
The system of claim 10, wherein the firmware causes the computer system to further implement the step of initializing an exception handler to generate exceptions when the first software program accesses the ×86 BIOS.
Claim 18
Dependent Claim 33 words
The system of claim 15, wherein the firmware causes the computer system to further implement the step of initializing the exception handler to generate exceptions when the BIOS extension accesses the ×86 BIOS.
Claim 19
Dependent Claim 25 words
The system of claim 10, wherein the majority of the software code comprising the first software application executes natively on the computer system without translation.
Claim 20
Dependent Claim 24 words
The system of claim 10, wherein the majority of the software code comprising the BIOS extension executes natively on the computer system without translation.
Claim 21
Dependent Claim 224 words
In a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, a firmware based boot process without an ×86 BIOS that supports expansion devices coupled to the computer system, wherein the expansion devices include their own respective BIOS extensions, the non-volatile memory storing the firmware which when executed by the processor cause the computer system to perform the steps of: a) initializing device drivers for the computer system using the firmware; b) initializing an application programming interface for the device drivers by using the firmware; c) initializing a compatibility component for interfacing with the device drivers, wherein the compatibility component is operable for translating accesses by a first software application to an ×86 BIOS into corresponding accesses to the device drivers, such the first software application is able to execute on the computer system by using the compatibility component while a second software application is able to execute on the computer system by accessing the application programming interface directly; and d) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 22
Dependent Claim 224 words
In a computer system including an ×86 processor coupled to a volatile memory and a non-volatile memory via a bus, a firmware based boot process without an ×86 BIOS that supports expansion devices coupled to the computer system, wherein the expansion devices include their own respective BIOS extensions, the non-volatile memory storing the firmware which when executed by the processor cause the computer system to perform the steps of: a) initializing device drivers for the computer system using the firmware; b) initializing an application programming interface for the device drivers by using the firmware; c) initializing a compatibility component for interfacing with the device drivers, wherein the compatibility component is operable for translating accesses by a first software application to an ×86 BIOS into corresponding accesses to the device drivers, such the first software application is able to execute on the computer system by using the compatibility component while a second software application is able to execute on the computer system by accessing the application programming interface directly; and d) running an expansion device BIOS extension from an expansion device coupled to the computer system to initialize a memory area in volatile memory, wherein the memory area is configured by the BIOS extension to interface with the expansion device, such that the expansion device is available to the first application and the second application.
Claim 23
Dependent Claim 43 words
The process of claim 19, wherein the first software application is a legacy application adapted to execute on an ×86 BIOS based computer system and the expansion device is a legacy expansion device adapted to couple to an ×86 BIOS based computer system.
Claim 24
Dependent Claim 45 words
The process of claim 19, further including the step of performing a bus discovery process to initialize the expansion device, wherein the expansion device is coupled to the computer system via a bus, wherein the firmware determines whether the expansion device includes the BIOS extension.
Claim 25
Dependent Claim 52 words
The process of claim 19, wherein the firmware causes the computer system to further implement the step of running a portion of an ×86 BIOS to initialize the area in volatile memory, wherein the area is configured by the portion to interface with the first software application to enable it to execute.
Claim 26
Dependent Claim 34 words
The process of claim 22, wherein the area in volatile memory corresponds to a 640K memory configuration created in an ×86 BIOS based computer system when the ×86 BIOS based computer system is booted.
Claim 27
Dependent Claim 34 words
The process of claim 19, wherein the firmware causes the computer system to further implement the step of initializing an exception handler to generate exceptions when the first software program accesses the ×86 BIOS.
Claim 28
Dependent Claim 33 words
The process of claim 24, wherein the firmware causes the computer system to further implement the step of initializing the exception handler to generate exceptions when the BIOS extension accesses the ×86 BIOS.
Claim 29
Dependent Claim 25 words
The process of claim 19, wherein the majority of the software code comprising the first software application executes natively on the computer system without translation.
Claim 30
Dependent Claim 24 words
The process of claim 19, wherein the majority of the software code comprising the BIOS extension executes natively on the computer system without translation.

References Cited (Backward Citations)

US5689726A Cited
US5854913A Cited
US5758081A Cited
US5694582A Cited
US6032247A Cited
US5905888A Cited
US5915106A Cited
US5887164A Cited
US5913058A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2003-10-03 2004-04-03 2004-10-03 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2007-10-03 2008-04-03 2008-10-03 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2011-10-03 2012-04-03 2012-10-03 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag