BIOS
<!-- /firstHeading --><!-- bodyContent --><!-- tagline -->From Wikipedia, the free encyclopedia
<!-- /tagline --><!-- subtitle -->
<!-- /subtitle --><!-- jumpto -->Jump to:
navigation,
search
<!-- /jumpto --><!-- bodycontent -->This article is about the personal computer term. For other uses, see
Bios.
In
IBM PC compatible computers, the
basic input/output system (BIOS), also known as the
System BIOS or
ROM BIOS (
/
ˈ
b
aɪ
.
oʊ
s
/), is a
de facto standard defining a
firmware interface.<SUP id=cite_ref-pcguidedefinition_0-0 class=reference>
[1]</SUP> The name originated in earlier computers running CP/M and other operating systems, where the BIOS was loaded from disc rather than stored as firmware (
EPROMs were not yet available); and from around 2010 the BIOS firmware of PCs started to be replaced by a
Unified Extensible Firmware Interface (UEFI).<SUP style='WHITE-SPACE: nowrap' class=Template-Fact>[
citation needed]</SUP>
Phoenix AwardBIOS
CMOS (non-volatile memory) Setup utility on a standard PC
The BIOS software is built into the
PC, and is the first code run by a PC when powered on ('boot firmware'). When the PC starts up, the first job for the BIOS is the
power-on self-test, which initializes and identifies system devices such as the
video display card,
keyboard and
mouse,
hard disk drive,
optical disc drive and other
hardware. The BIOS then locates
boot loader software held on a
peripheral device (designated as a 'boot device'), such as a
hard disk or a
CD/
DVD, and loads and executes that software, giving it control of the PC.<SUP id=cite_ref-1 class=reference>
[2]</SUP> This process is known as
booting, or booting up, which is short for
bootstrapping.
BIOS software is stored on a
non-volatile
ROM chip on the
motherboard. It is specifically designed to work with each particular model of computer, interfacing with various devices that make up the complementary chipset of the system. In modern computer systems the
BIOS chip's contents can be rewritten without removing it from the motherboard, allowing BIOS software to be upgraded in place.
A BIOS has a
user interface (UI), typically a menu system accessed by pressing a certain key on the keyboard when the PC starts. In the BIOS UI, a user can:
- configure hardware
- set the system clock
- enable or disable system components
- select which devices are eligible to be a potential boot device
- set various password prompts, such as a password for securing access to the BIOS UI functions itself and preventing malicious users from booting the system from unauthorized peripheral devices.
The BIOS provides a small
library of basic input/output functions used to operate and control the peripherals such as the keyboard, text display functions and so forth, and these software library functions are callable by external software. In the IBM PC and AT, certain peripheral cards such as hard-drive controllers and video display adapters carried their own BIOS extension
Option ROM, which provided additional functionality.
Operating systems and executive software, designed to supersede this basic firmware functionality, will provide replacement software interfaces to applications.
The
role of the BIOS has changed over time. As of 2011, the BIOS is being replaced by the more complex
Extensible Firmware Interface (EFI) in many new machines, but BIOS remains in widespread use, and EFI booting has only been supported in
Microsoft's
operating system products supporting
GPT<SUP id=cite_ref-2 class=reference>
[3]</SUP> and
Linux kernels 2.6.1 and greater builds (and in
Mac OS X on
Intel-based Macs).<SUP id=cite_ref-3 class=reference>
[4]</SUP> However, the distinction between BIOS and EFI is rarely made in terminology by the average computer user, making BIOS a catch-all term for both systems.
[edit] Terminology
The term BIOS (Basic Input/Output System) was invented by
Gary Kildall and first appeared in the
CP/M operating system in 1975, describing the machine-specific part of CP/M loaded during boot time that interfaced directly with the
hardware (CP/M machines usually had only a simple
boot loader in their
ROM). Later versions of CP/M, as well as
Concurrent CP/M,
Concurrent DOS,
DOS Plus,
Multiuser DOS,
System Manager and
REAL/32 came with an
XIOS (Extended Input/Output System) instead of the BIOS. Most versions of
DOS have a file called "
IO.SYS", "
IBMBIO.COM", "IBMBIO.SYS" or "DRBIOS.SYS", called the DOS BIOS, that is analogous to the CP/M BIOS.
Among other classes of computers, the generic terms
boot monitor,
boot loader or
boot ROM were commonly used. Some Sun and PowerPC-based computers use
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] IBM PC-compatible BIOS chips
In principle, the BIOS in ROM was customized to the particular manufacturer's hardware, allowing low-level services (such as reading a keystroke or writing a sector of data to diskette) to be provided in a standardized way to the operating system. For example, an IBM PC might have had either a monochrome or a color display adapter, using different display memory addresses and hardware, but a single, standard, BIOS system call would be invoked to display a character at a specified position on the screen in
text mode.
Boot Block |
DMI Block |
Main Block |
PhoenixBIOS D686. This BIOS chip is housed in a
PLCC package, which is, in turn, plugged into a PLCC socket.
Prior 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. EPROM chips may be erased by prolonged exposure to ultraviolet light, which accessed the chip via the window. Chip manufacturers use EPROM programmers (blasters) to program EPROM chips. Electrically erasable (EEPROM) chips allow BIOS reprogramming using higher-than-normal voltage.<SUP id=cite_ref-4 class=reference>
[5]</SUP> BIOS versions are upgraded to take advantage of newer versions of hardware and to correct bugs in previous revisions of BIOSes.<SUP id=cite_ref-5 class=reference>
[6]</SUP>
Beginning with the IBM AT, PCs supported a hardware clock settable through BIOS. It had a century bit which allowed for manually changing the century when the year 2000 happened. Most BIOS revisions created in 1995 and nearly all BIOS revisions in 1997 supported
the year 2000 by setting the century bit automatically when the clock rolled past midnight, December 31, 1999.<SUP id=cite_ref-6 class=reference>
[7]</SUP>
The first flash chips were 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). 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 16 megabytes. Some modern motherboards are including even bigger NAND
flash memory ICs on board which are capable of storing whole compact operating system distribution like some
Linux distributions. For example, some recent ASUS motherboards included
SplashTop Linux embedded into their NAND flash memory ICs.
[edit] Flashing the BIOS
In modern PCs the BIOS is stored in
rewritable memory, allowing the contents to be replaced or 'rewritten'. This rewriting of the contents is sometimes termed
flashing. This can be done by a special program, usually provided by the system's manufacturer, or at
POST, with a BIOS image in a hard drive or
USB flash drive. A file containing such contents is sometimes termed 'a BIOS image'. A BIOS might be reflashed in order to upgrade to a newer version to fix bugs or provide improved performance or to support newer hardware, or a reflashing operation might be needed to fix a damaged BIOS. A BIOS may also be "flashed" by putting the file on the root of a USB drive and booting.
[edit] BIOS chip vulnerabilities
An
American Megatrends BIOS showing a “
Intel CPU uCode Loading Error” after a failed attempt to upload microcode patches into the CPU.
EEPROM 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.
[edit] Overclocking
Some BIOS chips allow
overclocking, an action in which the
CPU is adjusted to a higher
clock rate than its factory preset. Overclocking may, however, seriously compromise system reliability in insufficiently cooled computers and generally shorten component lifespan. Overclocking, incorrectly performed, may also cause component temperatures to rise so quickly that they destroy themselves.
[edit] Virus attacks
There are at least four known BIOS attack viruses, two of which were for demonstration purposes. The first one found in the wild was Mebromi, targeting Chinese users.
[edit] CIH
Main article:
CIH (computer virus)
The first was a virus which was able to erase Flash ROM BIOS content, rendering computer systems unstable.
CIH, also known as "
Chernobyl Virus", appeared for the first time in mid-1998 and became active in April 1999. It affected systems' BIOSs 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 removed from the motherboard to be reprogrammed elsewhere. Damage from CIH was possible since the virus was specifically targeted at the then widespread Intel i430TX motherboard chipset, and the most common operating systems of the time were based on the
Windows 9x family allowing direct hardware access to all programs.
Detached BIOS Chip
Modern systems are not vulnerable to CIH because of a variety of chipsets being used which are incompatible with the Intel i430TX chipset, 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 such as
Linux,
Mac OS X,
Windows NT-based Windows OS like
Windows 2000,
Windows XP and newer, do not allow user-mode programs to have direct hardware access. As a result, as of 2008, CIH has become essentially harmless, at worst causing annoyance by infecting executable files and triggering alerts from antivirus software. Other BIOS viruses remain possible, however;<SUP id=cite_ref-7 class=reference>
[8]</SUP> since most Windows home users without Windows Vista/7's UAC run all applications with administrative privileges, a modern CIH-like virus could in principle still gain access to hardware.
[edit] Black Hat 2006
The second one was a technique presented by John Heasman, principal security consultant for UK-based Next-Generation Security Software at the Black Hat Security Conference (2006), where he showed how to elevate privileges and read physical memory, using malicious procedures that replaced normal
ACPI functions stored in flash memory.
[edit] Persistent BIOS infection
The third one, known as "Persistent BIOS infection", was a method presented in CanSecWest Security Conference (Vancouver, 2009) and SyScan Security Conference (Singapore, 2009) where researchers Anibal Sacco<SUP id=cite_ref-8 class=reference>
[9]</SUP> and Alfredo Ortega, from Core Security Technologies, demonstrated insertion of malicious code into the decompression routines in the BIOS, allowing for nearly full control of the PC at every start-up, even before the operating system is booted.
The proof-of-concept does not exploit a flaw in the BIOS implementation, but only involves the normal BIOS flashing procedures. Thus, it requires physical access to the machine or for the user on the operating system to be root. Despite this, however, researchers underline the profound implications of their discovery: “We can patch a driver to drop a fully working
rootkit. We even have a little code that can remove or disable antivirus.”<SUP id=cite_ref-9 class=reference>
[10]</SUP>
[edit] Mebromi
Mebromi is a
trojan primarily targeting Chinese users using the
AwardBIOS and
Microsoft Windows. Upon execution it will first search to see if the system uses the AwardBIOS. If the system does use the AwardBIOS it infects the BIOS. Then it installs a rootkit infecting the
Master boot record. Mebromi selectively seeks out if a computer is protected by
antivirus software made by two Chinese companies:
Rising Antivirus and Jiangmin KV Antivirus.<SUP id=cite_ref-10 class=reference>
[11]</SUP> <SUP id=cite_ref-11 class=reference>
[12]</SUP> <SUP id=cite_ref-12 class=reference>
[13]</SUP>
[edit] Firmware on adapter cards
A computer system can contain several BIOS firmware chips. The motherboard BIOS typically contains code to access hardware components absolutely necessary for bootstrapping the system, such as the keyboard (either
PS/2 or on a
USB human interface device), and storage (
floppy drives, if available, and PATA or SATA hard disk controllers). In addition, plug-in adapter cards such as
SCSI,
RAID,
network interface cards, and video boards often include their own BIOS (e.g.
Video BIOS), complementing or replacing the system BIOS code for the given component. (This code is generally referred to as an
option ROM). Even devices built into the motherboard can behave in this way; their option ROMs can be stored as separate code on the main BIOS flash chip, and upgraded either in tandem with, or separately from, the main BIOS.
An add-in card usually only requires an option ROM if it:
- Needs to be used before the operating system can be loaded (usually this means it is required in the bootstrapping process), and
- Is too sophisticated or specific a device to be handled by the main BIOS
Older
PC
operating systems, such as
MS-DOS (including all DOS-based versions of Microsoft Windows), and early-stage bootloaders, may continue to use the BIOS for input and output. However, the restrictions of the BIOS environment means that modern OSes will almost always use their own
device drivers to directly control the hardware. Generally, these device drivers only use BIOS and option ROM calls for very specific (non-performance-critical) tasks, such as preliminary device initialization.
In order to discover memory-mapped
ISA option ROMs during the boot process, PC BIOS implementations scan real memory from <CODE>0xC0000</CODE> to <CODE>0xF0000</CODE> on 2
KiB boundaries, looking for a ROM
signature: <CODE>0xAA55</CODE> (0x55 followed by 0xAA, since the
x86 architecture is
little-endian). In a valid expansion ROM, this signature is immediately followed by a single byte indicating the number of 512-byte blocks it occupies in real memory. The next byte contains an offset describing the option ROM's
entry point, to which the BIOS immediately transfers control. At this point, the expansion ROM code takes over, using BIOS services to register
interrupt vectors for use by post-boot applications, provide a user configuration interface, or display diagnostic information.
There are many methods and utilities for examining the contents of various motherboard BIOS and expansion ROMs, such as Microsoft
DEBUG or the Unix
dd.
[edit] BIOS boot specification
If 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 BIOS's 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.<SUP style='WHITE-SPACE: nowrap' class=Template-Fact>[
citation needed]</SUP>
The specification can be downloaded from the ACPICA website. The official title is BIOS Boot Specification (Version 1.01, 11 January 1996) and is available here: <SUP id=cite_ref-13 class=reference>
[14]</SUP>
[edit] Changing role of the BIOS
Some
operating systems, for example
MS-DOS, rely on the BIOS to carry out most input/output tasks within the PC.<SUP id=cite_ref-14 class=reference>
[15]</SUP> A variety of technical reasons makes it inefficient for some recent operating systems written for CPUs with a word length of
32-bits or more 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
real mode runtime interface.
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, thermal management. To quote
Linus Torvalds, the task of BIOS is "just load the
OS and get the hell out of there". 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 supports EFI via the
elilo and
GNU GRUB boot loaders. 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 Technology have followed suit with the MSI K9ND MS-9282 and MSI K9SD MS-9185 resp. the M57SLI-S4 models.
[edit] SLIC
Some BIOSes contain a "SLIC" (software licensing description table), a digital signature placed inside the BIOS by the manufacturer, for example
Dell. This SLIC is inserted in the ACPI table and contains no active code. Computer manufacturers that distribute OEM versions of Microsoft Windows and Microsoft application software can use the SLIC to authenticate licensing to the OEM Windows Installation disk and/or system
recovery disc containing Windows software. Systems having a SLIC can be preactivated with an OEM product key, and they verify an XML formatted OEM certificate against the SLIC in the BIOS as a means of self-activating (see
System Locked Preinstallation). If a user performs a fresh install of Windows, they will need to have possession of both the OEM key and the digital certificate for their SLIC in order to bypass activation; in practice this is extremely unlikely and hence the only real way this can be achieved is if the user performs a restore using a pre-customised image provided by the OEM.
[edit] Reprogrammable microcode
Recent
Intel processors (P6 and P7) have reprogrammable
microcode. The BIOS may contain patches to the processor code to allow errors in the initial processor code to be fixed, updating the processor microcode each time the system is powered up. Otherwise, an expensive processor swap would be required.<SUP id=cite_ref-15 class=reference>
[16]</SUP> For example, the
Pentium FDIV bug became an expensive fiasco for Intel that required a
product recall because the original Pentium did not have patchable microcode.
[edit] The BIOS business
The 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. Former vendors include
Award Software and
Microid Research which were acquired by
Phoenix Technologies in 1998; Phoenix later phased out the Award Brand name.
General Software, which was also acquired by Phoenix in 2007, sold BIOS for Intel processor based embedded systems.
[edit] Comparison
|
AwardBIOS |
AMIBIOS |
Insyde |
SeaBIOS |
License |
Proprietary |
Proprietary |
Proprietary |
LGPL v3 |
32-bit PCI BIOS calls |
? |
? |
? |
Yes |
<ABBR title="Advanced Host Controller Interface">AHCI</ABBR> |
Yes |
Yes |
? |
Yes |
<ABBR title="Advanced Power Management">APM</ABBR> |
Yes |
Yes |
Yes <SMALL>(1.2)</SMALL> |
Yes <SMALL>(1.2)</SMALL> |
<ABBR title="BIOS Boot Specification">BBS</ABBR> |
Yes |
Yes |
Yes |
Yes |
Boot menu |
Yes |
Yes |
Yes |
Yes |
Compression |
Yes <SMALL>(LHA)</SMALL> |
Yes <SMALL>(LHA)</SMALL> |
Yes <SMALL>(RLE)</SMALL> |
Yes <SMALL>(LZMA)</SMALL> |
CMOS |
Yes |
Yes |
Yes |
Yes |
<ABBR title="Enhanced Disk Drive">EDD</ABBR> |
Yes |
Yes |
Yes |
Yes <SMALL>(3.0)</SMALL> |
<ABBR title="Extended System Configuration Data">ESCD</ABBR> |
Yes |
Yes |
? |
No |
GUID Partition Table (GPT) |
? |
No |
? |
No |
Language |
Assembly |
Assembly |
Assembly |
C |
<ABBR title="Logical Block Addressing">LBA</ABBR> |
Yes <SMALL>(48)</SMALL> |
Yes <SMALL>(48)</SMALL> |
Yes |
Yes <SMALL>(48)</SMALL> |
MultiProcessor Specification |
Yes |
Yes |
Yes |
Yes |
Option ROM |
Yes |
Yes |
Yes |
Yes |
Password |
Yes |
Yes |
Yes |
No |
<ABBR title="Post Memory Manager">PMM</ABBR> |
? |
Yes |
? |
Yes |
Setup screen |
Yes |
Yes |
Yes |
No |
SMBIOS |
Yes |
Yes |
Yes |
Yes <SMALL>(2.4)</SMALL> |
Splash screen |
Yes |
Yes <SMALL>(PCX)</SMALL> |
Yes |
Yes <SMALL>(BMP, JPG)</SMALL> |
USB booting |
Yes |
Yes |
Yes |
Yes |
USB hub |
? |
? |
? |
Yes |
USB keyboard |
Yes |
Yes |
Yes |
Yes |
USB mouse |
Yes |
Yes |
Yes |
Yes |
[edit] See also
[edit] References
- ^ The PC Guide - System BIOS
- ^ HowStuffWorks: What BIOS Does.
- ^ Windows and GPT FAQ
- ^ Extensible Firmware Interface (EFI) and Unified EFI (UEFI)
- ^ "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.
- ^ New BIOS Virus Withstands HDD Wipes, March 27, 2009 by Marcus Yam - Tom's Hardware US
- ^ Sacco, Anibal; Alfredo Ortéga. "Persistent BIOS Infection". Exploiting Stuff. http://exploiting.wordpress.com/2009/03/23/cansecwest-was-great-here-the-presentation-slides/. Retrieved 2010-02-06.
- ^ Fisher, Dennis. "Researchers unveil persistent BIOS attack methods". Threat Post. http://threatpost.com/en_us/blogs/researchers-unveil-persistent-bios-attack-methods-031909. Retrieved 2010-02-06.
- ^ Giuliani, Marco. "Mebromi: the first BIOS rootkit in the wild". blog. http://blog.webroot.com/2011/09/13/mebromi-the-first-bios-rootkit-in-the-wild/. Retrieved 2011-09-19.
- ^ "360发布“BMW病毒”技术分析报告". blog. http://bbs.360.cn/4005462/251096134.html. Retrieved 2011-09-19.
- ^ Yuan, Liang. "Trojan.Mebromi". Threat Response. http://www.symantec.com/security_response/writeup.jsp?docid=2011-090609-4557-99. Retrieved 2011-09-19.
- ^ http://www.acpica.org/documentation/related_documents.php BIOS Boot Specification (Version 1.01, 11 January 1996)
- ^ Smart Computing Article - What Is The BIOS? - Computing Basics July 1994 • Vol.5 Issue 7
- ^ Scott Mueller, Upgrading and repairing PCs 15th edition, Que Publishing, 2003 ISBN 0789729741, pages 109-110
[edit] Further reading
- IBM Personal Computer Technical Reference manual (First Edition, ed.). IBM Corporation. Revised March 1983.
- How BIOS Works - howStuffWorks
[edit] External links
[edit] Specifications
<!-- NewPP limit reportPreprocessor node count: 7317/1000000Post-expand include size: 50294/2048000 bytesTemplate argument size: 14071/2048000 bytesExpensive parser function count: 3/500--><!-- Saved in parser cache with key enwiki

cache:idhash:4473-0!*!0!!en!4!* and timestamp 20120214174933 generated by srv242 -->