| Related sites for http://en.wikipedia.org/wiki/BIOS |
| MATTsoft_Boot_Manager__MBTMGR Boots multiple OSs, including several on one FAT partition. Download, installation documents. | | Multiboot_Specification Specifies interface between boot loader and OS, so any complying boot loader should be able to load any complying OS. [PDF] | | Multi-booting_Solaris_and_Other_Operating_Systems Describes installing Solaris on a PC with other OSs, and joint use of Solaris boot manager and other boot loaders. | | Netboot Includes boot manager functionality and boots Linux, DOS and FreeBSD via a TCP/IP network using BOOTP and TFTP. | | OSL2000 A universal boot manager allowing selection from a number of operating systems. Includes support for booting from USB, CDROM and other devices. | | SOLO__Shag/Os_LOader Boot loader for Shag/OS which also supports, Linux and other PC operating systems. Includes source. | | SyMon Boot manager with support of up to 36 primary partitions, | | SysLinux Home of SysLinux (floppy), PXELinux (network), ISOLinux (CD-ROM), ExtLinux (ext2/3) utilities to boot Linux kernel; MemDisk, tool to boot legacy OSs (e.g., DOS) from nontraditional media. | | zBoot_Manager An effective boot manager, which allows the easy install and use of multiple operating systems on a single hard drive. Directly install other OSs to extended partitions and logic drivers. | | OS-List Loosely categorized, unalphabetized list of 100 OSs. | | Oberon_Central Directory of Oberon systems and compilers, source code and applications. Offers bibliography, on-line papers and research documentation, FAQ, links and newsgroup archive. | | Dennis_Brylow\'s_Xinu_Lab_Infrastructure_Page Keeps the Xinu Millenium Edition: first port to a modern RISC architecture: PowerPC G3 and G4. Marquette University Department of Mathematics, Statistics and Computer Science. | | Douglas_Comer Xinu creator, Distinguished Professor of Computer Science, Purdue University; information, essays, affiliations. | | PDP-11_Xinu Directory with Xinu OS for LSI-11 PDP-11 series of 16-bit computers; distribution has SunCHIP (a.k.a. CHIP) C compiler and assembler, both written in C. Unix archive. The Unix Heritage Society, Unix A | | Xinu Growing article, with links to many related topics. Wikipedia. | | Xinu_Version_7_0_on_the_Sun Large page, many details of using Xinu on Sun 2 and 3 with 68k CPUs. | | Application_Note_µC/OS-II_and_Turbo_C++_1_01 Describes port of µC/OS-II to x86 CPU, via Borland compiler. Quantum Leaps, LLC. [PDF] | | Micrium,_Inc_ Makes µC/OS, µC/OS-II (MicroC/OS, MicroC/OS-II), full source code, no royalty, free non-commercial use; other software for embedded use: Embedded Systems Building Blocks, µC/GUI for most 8- to 64-b | | Micrium_µC/OS-II__The_Real-Time_Kernel Description, information, downloads, support. DeviceTools. | | MicroC/OS-II Growing article, with links to many related topics. Wikipedia. | | Simulation_of_uC/OS-II_on_Win32_Platform Environment for uC/OS-II RTOS on Windows 32-bit platform; has 2 main modules, run as normal programs: module 1 (WCOS) runs RTOS with embedded program, module 2 (WSim) has functions to run and control | | MicroC/OS-II__The_Real_Time_Kernel By Jean J. Labrosse; Elsevier Newnes, 2002, ISBN 9781578201037. Describes design, implementation of RTOS; reference to kernel, and detailed and readable design study for embedded system students. | | Gasmann\'s_ReactOS_Fansite Screenshots and registry files. | | Gge\'s_ReactOS_page ReactOS overview, news, regression tests, ToDo list. | | ReactoOS_Network_Infrastructure NDIS, AFD, TDI, TCPIP, WSHTCPIP protocols and other network matters of ReactOS. | | ReactOS_0_2_0 GUI overview. | | reactOS_-_Free_clone_of_Windows_NT ReactOS at FSF/UNESCO Free Software Directory. | | ReactOS_Fansite Software compatibility information, articles and screenshots. | | ReactOS_Package_Manager View of the ReactOS Package Tree online. Information about ReactOS Package Manager. | | ReactOS_Reviewed__The_Next_Windows? Detailed review of ReactOS. | | ReactOS_Screenshots Screenshots of ReactOS at OSDir.com. | | ROS_Explorer_FAQ ReactOS Explorer frequently asked questions. | | Some_ideas_for_ReactOS Ideas description about what should be developed and some downloads for ReactOS. | | SourceForge_net__ReactOS ReactOS project page. | | Steven_Edwards_Interview Interview with wine and ReactOS developer. | | Canary_Islands_THEOS Centro de Cálculo de Tenerife, S.L. THEOS VAR since OASIS time: system software, freeware utilities. | | Entry-Master_Systems,_Inc_ Makes access control, revenue control, and security management software. THEOS-based, integrated with Windows 3.x/95/98-NT/XP, has Web interface. | | Freeware_sources Links to several requested THEOS programs. | | Halliburton_Systems_Inc Custom THEOS Programming | | THEOS Growing article, with links to many related topics. Wikipedia. |
|
BIOS - Wikipedia, the free encyclopedia /**/ /**/ if (wgNotice != '') document.writeln(wgNotice); BIOS From Wikipedia, the free encyclopedia Jump to: navigation, search  This article or section has multiple issues. Please help improve the article or discuss these issues on the talk page.It may be confusing or unclear for some readers. Tagged since October 2008.It may require general cleanup to meet Wikipedia's quality standards. Tagged since October 2008.For other uses, see Bios.BIOS: Phoenix AwardBIOS CMOS (non-volatile memory) Setup utility on a standard PCStored onPROMEPROMFlash memoryCommon manufacturersAmerican MegatrendsInsyde SoftwarePhoenix TechnologiesByosoftOthersIn computing, BIOS is an acronym that stands for Basic Input/Output System, or in some cases, Built In Operating System.[1] The latter term dates from the late 1970s and early 1980s when the PCs of the day normally contained a comprehensive operating system in their ROMs. The latter acronym is still much used in conjunction with gadgetry containing dedicated computers, such as modern digital cameras, home appliances with automatic functionality, computer printers and other peripherals.BIOS refers, in part, to the firmware code (a type of boot loader) run by a PC when first powered on. The primary function of the BIOS is to identify and initialize system component hardware such as the video display card, hard disk, and floppy disk and some other hardware devices. This is to prepare the machine into a known low capability state, so other software programs stored on various media can be loaded, executed, and given control of the PC.[2] This process is known as booting, or booting up, which is short for bootstrapping.The BIOSes of IBM PC class machines are coded programs embedded on a chip that recognize and control various devices that make up x86 personal computers, and provide a small library of basic Input/Output functions that can be called to operate and control the peripherals such as the keyboard, text display functions and so forth.Computers designed to run Windows ME or Windows 2000, or later, supersede this basic monitor functionality by taking over direct control of the interrupt table and replacing the monitor routines with faster and more robust low-level modules that, unlike the BIOS function set, are re-entrant. Various BIOS functions in ROM were left in control in earlier Windows versions, and the BIOS only comes into play today in the alternate shell Cmd.exe, or if the machine is booted into a legacy DOS version.[citation needed]Contents1 Terminology2 The BIOS Chip history3 BIOS chip vulnerabilities3.1 Virus attacks4 Firmware on adapter cards5 The BIOS boot specification6 Changing role of the BIOS7 The BIOS business8 See also9 References10 Footnotes11 External links11.1 Specifications//[edit] TerminologyThe term first appeared in the CP/M operating system, describing the part of CP/M loaded during boot time that interfaced directly with the hardware (CP/M machines usually had a simple boot loader in ROM, and nothing else). Most versions of DOS have a file called "IBMBIO.COM" or "IO.SYS" that is analogous to the CP/M disk BIOS. The term was also known as Binary Input/Output System and Basic Integrated Operating System.Among other classes of computers, the generic terms boot monitor, boot loader or boot ROM were commonly used. Some Sun and Macintosh PowerPC computers used Open Firmware for this purpose. There are a few alternatives for Legacy BIOS in the x86 world: Extensible Firmware Interface, Open Firmware (used on the OLPC XO-1) and coreboot.[edit] The BIOS Chip historyBoot BlockDMI BlockMain Block  ROM with BIOSPrior to the early 1990s, BIOSes were stored in ROM or PROM chips, which could not be altered by users. As its complexity and need for updates grew, and re-programmable parts became more available, BIOS firmware was most commonly stored on EEPROM or flash memory devices. According to Robert Braver, the president of the BIOS manufacturer Micro Firmware, Flash BIOS chips became common around 1995 because the electrically erasable PROM (EEPROM) chips are cheaper and easier to program than standard erasable PROM (EPROM) chips. PROM chips may be erased by prolonged exposure to ultraviolet light, which accessed the chip via the window. Chip manufacturers use PROM blasters to reprogram EPROM chips. EEPROM chips come with the additional feature of allowing a BIOS reprogramming via higher-than-normal amounts of voltage.[3] BIOS versions are upgraded to take advantage of newer versions of hardware and to correct bugs in previous revisions of BIOSes.[4]The first flash chips attached to the ISA bus. Starting in 1997, the BIOS flash moved to the LPC bus, a functional replacement for ISA, following a new standard implementation known as "firmware hub" (FWH). Most BIOS revisions created in 1995 and nearly all BIOS revisions in 1997 supported the year 2000.[5] In 2006, the first systems supporting a Serial Peripheral Interface (SPI) appeared, and the BIOS flash moved again.The size of the BIOS, and the capacities of the ROM, EEPROM and other media it may be stored on, has increased over time as new features have been added to the code; BIOS versions now exist with sizes up to 8 megabytes. Some modern motherboards are including even bigger NAND Flash ROM ICs on board which are capable of storing whole compact operating system distribution like some Linux distributions. For example, some recent ASUS motherboards including SplashTop Linux embedded into their NAND Flash ROM ICs.[edit] BIOS chip vulnerabilitiesEEPROM chips are advantageous because they can be easily updated by the user; hardware manufacturers frequently issue BIOS updates to upgrade their products, improve compatibility and remove bugs. However, this advantage had the risk that an improperly executed or aborted BIOS update could render the computer or device unusable. To avoid these situations, more recent BIOSes use a "boot block"; a portion of the BIOS which runs first and must be updated separately. This code verifies if the rest of the BIOS is intact (using hash checksums or other methods) before transferring control to it. If the boot block detects any corruption in the main BIOS, it will typically warn the user that a recovery process must be initiated by booting from removable media (floppy, CD or USB memory) so the user can try flashing the BIOS again. Some motherboards have a backup BIOS (sometimes referred to as DualBIOS boards) to recover from BIOS corruptions. In 2007, Gigabyte began offering motherboards with a QuadBIOS recovery feature.[6][edit] Virus attacksThere was at least one virus which was able to erase Flash ROM BIOS content, rendering computer systems unusable.CIH, also known as "Chernobyl Virus", affected systems BIOS and often they could not be fixed on their own since they were no longer able to boot at all. To repair this, Flash ROM IC had to be ejected from the motherboard to be reprogrammed somewhere else. Damage from the CIH virus was possible since most motherboards at the time of CIH propagation used the same chip set, Intel TX, and most common operating systems such as Windows 95 allowed direct hardware access to all programs.Modern systems are not vulnerable to CIH because of a variety of chip sets being used which are incompatible with the Intel TX chip set, and also other Flash ROM IC types. There is also extra protection from accidental BIOS rewrites in the form of boot blocks which are protected from accidental overwrite or dual and quad BIOS equipped systems which may, in the event of a crash, use a backup BIOS. Also, all modern operating systems like Windows XP, Windows Vista, Linux just do not allow direct hardware access to user mode programs. So, as of year 2008, CIH has become almost harmless and at most just bothers users by infecting executable files without being able to cause any real harm, only triggering numerous virus alerts from antivirus software.[edit] Firmware on adapter cardsA computer system can contain several BIOS firmware chips. The motherboard BIOS typically contains code to access fundamental hardware components such as the keyboard, floppy drives, ATA (IDE) hard disk controllers, USB human interface devices, and storage devices. In addition, plug-in adapter cards such as SCSI, RAID, Network interface cards, and video boards often include their own BIOS, complementing or replacing the system BIOS code for the given component.In some devices that can be used by add-in adapters and actually directly integrated on the motherboard, the add-in ROM may also be stored as separate code on the main BIOS flash chip. It may then be possible to upgrade this "add-in" BIOS (sometimes called an option ROM) separately from the main BIOS code.Add-in cards usually only require such an add-in BIOS if they:Need to be used prior to the time that the operating system loads (e.g. they may be used as part of the process which loads (bootstraps) the operating system), and:Are not sufficiently simple, or generic in operation to be handled by the main BIOS directlyPC operating systems such as DOS, including all DOS-based versions of MS Windows, as well as bootloaders, may continue to make use of the BIOS to handle input and output. However, other modern operating systems will interact with hardware devices directly by using their own device drivers to directly access the hardware. Occasionally these add-in BIOSs are still called by these operating systems, in order to carry out specific tasks such as preliminary device initialization.To find these memory mapped expansion ROMs during the boot process, PC BIOS implementations scan real memory from 0xC0000 to 0xF0000 on 2 kibibyte boundaries looking for the ROM signature bytes of 55h followed by AAh (0xAA55). For a valid expansion ROM, its signature is immediately followed by a single byte indicating the number of 512-byte blocks it occupies in real memory. The BIOS then jumps to the offset located immediately after this size byte; at which point the expansion ROM code takes over, using the BIOS services to register interrupt vectors for use by post-boot applications and provide a user configuration interface, or display diagnostic information.There are many methods and utilities for dumping the contents of various motherboard BIOS and expansion ROMs. Under a Microsoft OS, DEBUG can be used to examine 64 KiB segments of memory and save the contents to a file. For UNIX systems the dd command can be used by a user with root privileges: "dd if=/dev/mem bs=1k skip=768 count=256 2>/dev/null | strings -n 8".[edit] The BIOS boot specificationIf the expansion ROM wishes to change the way the system boots (such as from a network device or a SCSI adapter for which the BIOS has no driver code), it can use the BIOS Boot Specification (BBS) API to register its ability to do so. Once the expansion ROMs have registered using the BBS APIs, the user can select among the available boot options from within the BIOSes user interface. This is why most BBS compliant PC BIOS implementations will not allow the user to enter the BIOS's user interface until the expansion ROMs have finished executing and registering themselves with the BBS API.[citation needed][edit] Changing role of the BIOSSome operating systems, for example MS-DOS, rely on the BIOS to carry out most input/output tasks within the PC.[7] A variety of technical reasons makes it inefficient for some recent operating systems written for 32-bit CPUs such as Linux and Microsoft Windows to invoke the BIOS directly. Larger, more powerful, servers and workstations using PowerPC or SPARC CPUs by several manufacturers developed a platform-independent Open Firmware (IEEE-1275), based on the Forth programming language. It is included with Sun's SPARC computers, IBM's RS/6000 line, and other PowerPC CHRP motherboards. Later x86-based personal computer operating systems, like Windows NT, use their own, native drivers which also makes it much easier to extend support to new hardware, while the BIOS still relies on a legacy 16-bit runtime interface. As such, the BIOS was relegated to bootstrapping, at which point the operating system's own drivers can take control of the hardware.There was a similar transition for the Apple Macintosh, where the system software originally relied heavily on the ToolBox—a set of drivers and other useful routines stored in ROM based on Motorola's 680x0 CPUs. These Apple ROMs were replaced by Open Firmware in the PowerPC Macintosh, then EFI in Intel Macintosh computers.Later BIOS took on more complex functions, by way of interfaces such as ACPI; these functions include power management, hot swapping and thermal management. However BIOS limitations (16-bit processor mode, only 1 MiB addressable space, PC AT hardware dependencies, etc.) were seen as clearly unacceptable for the newer computer platforms. Extensible Firmware Interface (EFI) is a specification which replaces the runtime interface of the legacy BIOS. Initially written for the Itanium architecture, EFI is now available for x86 and x86-64 platforms; the specification development is driven by The Unified EFI Forum, an industry Special Interest Group.Linux has supported EFI via the elilo boot loader. The Open Source community increased their effort to develop a replacement for proprietary BIOSes and their future incarnations with an open sourced counterpart through the coreboot and OpenBIOS/Open Firmware projects. AMD provided product specifications for some chipsets, and Google is sponsoring the project. Motherboard manufacturer Tyan offers coreboot next to the standard BIOS with their Opteron line of motherboards. MSI and Gigabyte have followed suit with the MSI K9ND MS-9282 and MSI K9SD MS-9185 resp. the M57SLI-S4 models.[edit] The BIOS businessThe vast majority of PC motherboard suppliers license a BIOS "core" and toolkit from a commercial third-party, known as an "independent BIOS vendor" or IBV. The motherboard manufacturer then customizes this BIOS to suit its own hardware. For this reason, updated BIOSes are normally obtained directly from the motherboard manufacturer.Major BIOS vendors include American Megatrends (AMI), Insyde Software, Phoenix Technologies and Byosoft.[edit] See alsoAdvanced Configuration and Power Interface (ACPI)ARCSBIOS boot devicesBIOS interrupt callscoreboot, a project whose aim is to create a free replacement for the BIOtensible Firmware Interface (EFI)FirmwareInput/Output Base AddressNonvolatile BIOS memoryOpen FirmwarePower-On Self Test (POST)[edit] ReferencesIBM Personal Computer Technical Reference manual (First Edition, ed.). IBM Corporation. Revised March 1983. How BIOS Works - HowStuffWorks[edit] Footnotes^ "The Free Dictionary". Retrieved on 2008-11-04.^ HowStuffWorks: What BIOS Does.^ "Decoding RAM & ROM ." Smart Computing. June 1997. Volume 8, Issue 6.^ "Upgrading Your Flash BIOS For Plug And Play." Smart Computing. March 1996. Volume 7, Issue 3.^ "Time To Check BIOS." Smart Computing. April 1999. Volume 7, Issue 4.^ "Quad BIOS is a unique GIGABYTE feature that includes DualBIOS and Xpress BIOS Rescue Technology. This combination delivers a safety assurance mechanism that sports a total of 4 copies of BIOS distributed between the Flash ROM, hard-disk and driver CD." Gigabyte Corporate News, January 15, 2007.^ http://www.smartcomputing.com/editorial/article.asp?article=articles%2F1994%2Fjuly94%2Fpcn0713%2Fpcn0713.asp[edit] External linksChanging PC BIOS Settings at HowStuffWorksFlashing the BIOS at HowStuffWorksBIOS Recovery, Chip replacement, Update instructionsWim's BIOS PageTweakBIOS - BIOS information and tweakingBIOS options explainedAward BIOS identification pageBoot-CDs and Boot-DiskettesInformation about the BIOS, POST, BIOS recovery and chip replacementBIOS from A to ZBIOS for BeginnersBIOS Password resetSome universal and/or firmware flash tools are: UniFlash and flashrom - a Linux tool.[edit] SpecificationsPreventing BIOS Failures Using Intel® Boot Block Flash Memory (December 1998)BIOS Boot Specification 1.01 (January 1996)Implementing a Plug and Play BIOS Using Intel's Boot Block Flash Memory (February 1995)Retrieved from "http://en.wikipedia.org/wiki/BIOS" Categories: BIOS | Boot loadersHidden categories: Wikipedia articles needing clarification | Cleanup from October 2008 | All pages needing cleanup | All articles with unsourced statements | Articles with unsourced statements since July 2008 | Articles with unsourced statements since October 2008 Views Article Discussion Edit this page History Personal tools Log in / create account if (window.isMSIE55) fixalpha(); Navigation Main page Contents Featured content Current events Random article Search Interaction About Wikipedia Community portal Recent changes Contact Wikipedia Donate to Wikipedia Help Toolbox What links here Related changesUpload fileSpecial pages Printable version Permanent linkCite this page Languages العربية Azərbaycan Bosanski Brezhoneg Български Català Česky Dansk Deutsch Español Euskara فارسی Français Galego 한국어 Hrvatski Bahasa Indonesia Italiano עברית Kurdî / كوردی Latviešu Lëtzebuergesch Lietuvių Magyar മലയാളം Bahasa Melayu Nederlands 日本語 Norsk (bokmål) Polski Português Română Русский Shqip Simple English Slovenčina Slovenščina Српски / Srpski Suomi Svenska Tagalog ไทย Tiếng Việt Türkçe Українська 中文   This page was last modified on 7 January 2009, at 07:42. All text is available under the terms of the GNU Free Documentation License. (See Copyrights for details.) Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a U.S. registered 501(c)(3) tax-deductible nonprofit charity. Privacy policy About Wikipedia Disclaimers if (window.runOnloadHook) runOnloadHook(); |
|
