The 30-year-long Reign of BIOS is Over: Why UEFI Will Rock Your IT

by Administrator ‎19-07-2011 07:36 AM - edited ‎22-08-2011 05:09 AM

The BIOS has been around for more than three decades. What made sense then is a weak link in your computing infrastructure now. It may be time to move on.

As you deal with legacy technology and all its limitations, your IT staff will encounter more and more issues going forward: hardware compatibility problems, cost-intensive troubleshooting, slow boot and resume times, and limited pre-boot tools – just to name a few. Compared to newer UEFI systems, computers running the classic BIOS require a higher maintenance effort and are limited in their capabilities. We’ll get to the problems and benefits later.

There is no doubt: UEFI will replace BIOS eventually. However, many managers, IT personnel, and even enterprise architects are uncertain of UEFI’s origins or what it actually brings to the table. By the end of this article, you’ll have a clear understanding of this emerging standard and if it is worth your company’s investment.

What is UEFI?

From a bird’s eye view, UEFI has the same purpose as your typical BIOS. It’s responsible for initializing the hardware of your PCs and laptops, and then handing full hardware control over to the operating system. However, in terms of pure pre-boot functionality and extensibility UEFI is light-years ahead (see “IT Benefits” below), and it also addresses some basic problems with our aging architecture.


BIOS has been tweaked over the course of 30 years to fit modern hardware, such as multi-threaded and multicore processors, but make no mistake: Its core is still designed for PCs with one simple CPU, the long-dead ISA bus, and memory without a memory controller. BIOS was designed for ancient technology and we are starting to feel the implications of building on top of it.


The industry has tried again and again to standardize a successor to the almost decaying BIOS. All of those standards failed. Then, back in 1998, Intel initiated the “Intel Boot Initiative” (IBI) for the enterprise-class Intel IA-32 and -64 processors and later rebranded the initiative to EFI, Extensible Firmware Interface. There was a need to address the growing pains of BIOS, such as its limited storage and pre-boot manageability.
Intel pushed its efforts by eventually handing over the entire EFI initiative and all its specifications to the newly founded UEFI forum, which to this date consists of some of the leaders of our industry: AMD, American Megatrends Inc, Apple, Dell, HP, IBM, Insyde, Intel, Lenovo, Microsoft, and Phoenix Technologies.

The Unified Extensible Firmware Interface was born. UEFI forum members are responsible for keeping the UEFI specifications up to date to and adapt them to the ever-changing hardware and software requirements. “170 members and growing! […] UEFI platforms crossed 50% of IA worldwide units,” Intel announced at the 2011 meeting.

What’s Wrong with Now?

To understand UEFI’s benefits, you need to be aware of some of BIOS’ major flaws.

First of all, servicing a fleet of company desktop PCs or laptops that are in a non-bootable state (i.e. the OS is “broken”) is tough. Managing a PC over the network without Windows or Linux to boot from is time- and cost-consuming. The IT support staff needs a pre-boot environment that permits basic remote troubleshooting and maintenance tools. If anything goes wrong, you want to push a button and restore the PC to a functional state – from the comfort of your desk.

Second, the BIOS was developed in 1979 and is far beyond out-of-date. Its limited execution space (1024 Kbytes!) and its limited number of addressable devices causes more and more problems in today’s architecture. Your IT systems need to handle an increasing amount of devices. BIOS will fail you at some point – it will simply deny handling the device or may even cause problems in an OS environment.

Speaking of devices: Thanks to today’s vast number of USB ports, PCI devices, or built-in controllers (none of which existed 20-30 years ago), BIOS struggles with initializing them one-by-one. This struggle results in delays of up to 30 seconds before the actual operating system start its first boot sequence!    

Furthermore, the BIOS is physically unable to boot from hard disks with more than 2.1 TB. Back in the 80s, that kind of capacity seemed like a fairy tale, but we are being ushered into an era of hard disks with multiple terabytes of disk space. (See Solid State Drives for Desktop PCs and Laptops: Ready for Prime Time?)

Want to invest in 3 TB hard disks? Then there’s no (feasible) way around UEFI; only the new GUID table supports booting from anything bigger than 2.1 TB.

The problem lies within the old MBR (Master Boot Record) system used by most BIOSes. The partition table is limited to 2.1 TB, so your clients can’t boot from these devices – at least not without time-consuming workarounds or specialized tools.

“As we move beyond BIOS, we will need a 64-bit pre-OS environment that takes advantage of the UEFI environment while offering shell scripting ability, hardware access, simplicity and familiarity,” wrote Dong Wei, vice president of the Unified Forum and HP Distinguished Technologist in the official UEFI book, Harnessing the UEFI Shell.

UEFI Benefits and Innovation

UEFI addresses all of the abovementioned issues. However, keep in mind that UEFI is not a single “product” that looks exactly the same on every type of PC or laptop. UEFI is a basic firmware with a huge framework. To make full use of UEFI, the hardware needs to specifically support and come with UEFI applications. It’s a flexible design.

However, many UEFI implementations are highly developed and share common benefits:

  • Enterprise management: Thanks to support for third party drivers and applications, your IT staff can remotely manage systems equipped with UEFI without booting into Windows or any other OS! This enables you to have a common infrastructure for managing computers across your entire network. Obviously, this is a money saver: Imagine fixing computers by remotely turning them on and running UEFI troubleshooting tools or restoring the image from a backup server. It essentially eliminates the need for the classic “system DVD.”
  • Pre-OS and network security: UEFI’s enhanced networking API allows for a rich network authentication (log-on) in a pre-boot environment. Also, it offers support for TPM and and authenticode signatures. It’s simply an additional layer of security.
  • UEFI is “OS-like:” By default, you have full access to the entire hardware of your computer – Ethernet adapter, Wi-Fi, Bluetooth, graphics card, USB, even the audio chip, as well as full blown x86 and x64 support. This enables not only high-resolution UIs, but highly functional pre-boot environments. HP put its System Diagnostics tool (written specifically for UEFI) on laptops and desktops starting in mid-2008.
    MSI puts ClickBios on its board, a UEFI environment with some basic maintenance, diagnostics and Instant-On environments (for gaming, multimedia etc.). Unfortunately, that MSI mainboard – based on the P45 chipset – has been discontinued.
    Note, these interfaces aren’t mandatory. Some manufacturers may build beautiful UIs in their UEFI environment; some may just skip the UI aspect entirely.
  • Faster boot and resume times: UEFI handles devices initialization within seconds. This increases IT staff productivity (and user impatience), especially if your business requires rebooting or going in and out of hibernation a lot.
  • Support for HDDs with more than 2.1 TBytes: UEFI solves this problem by introducing the newer partition table called GUID (global unique identifier), which is finally capable to address more than 2 terabytes of storage. Bottom line: If your business revolves around having huge amounts of data on your PC client, investing in UEFI-capable hardware is a no-brainer.
  • Specialized UEFI applications: Without the need to boot into an OS, your IT workers could have fast access to their important data – providing that either your IT department or the OEM implements the add-in (see below). Possible scenario: Your staff can quickly glance at their Outlook e-mails or calendars without booting up the notebook. UEFI and its applications are on-screen within seconds.

Why the Slow Adoption?

It’s a simple matter of resource investment on the OEM side: UEFI is still a framework. Thus, to create unique pre-boot environments, add-ins, diagnostic tools, and specific hardware support, OEMs need to invest heavily into software development and tools.

Several companies are rolling out UEFI on a large scale, including Apple, IBM, and HP. This slide shows what HP has been doing in this business over the past two years:


It’s a major undertaking and many companies have held back until now.

You cannot upgrade your current PC fleet to UEFI. There is no feasible way to upgrade the BIOS chip on motherboards. From a technical point of view, it’s a completely different piece of software. Think of UEFI as an important aspect for future IT equipment decisions. Furthermore, only the 64-Bit versions of Windows 7, Windows Vista (SP1), and its bigger server editions (Windows Server 2008, Server 2008 R2) support the UEFI platform natively. 32-bit-platforms are only supported by UEFI mainboards with a special BIOS compatibility layer (CSM); this is something to look for if your infrastructure requires 32-bit operating systems.

If you think your IT infrastructure might benefit from UEFI, then your next step is to take it for a test drive. If your OEM doesn’t offer the UEFI tools you require, invest in your own pre-boot tools. For further information, I recommend reading UEFI forums whitepaper on evaluating the platform. A basic element of experimenting with UEFI is tianacore.

Predictions and Evaluations

The new “BIOS” is on the rise. The UEFI forum expects OEMs to finally adopt their new firmware on a large scale: In 2011, they predict, you will see more desktop clients equipped with UEFI than its predecessor. So what does this mean for you?
If the benefits we outlined in this article are important to you, then it’s time to evaluate UEFI sooner rather than later. You need to find a suitable hardware platform or partner that incorporates the UEFI software you need and start a small-scale test drive.
If you decide to hold off for now, then make no mistake: The transition is inevitable. UEFI will probably come with the next fleet of desktop PCs and notebooks you purchase.

by fauxscot(anon) on ‎19-07-2011 12:34 PM

Wow.  Having been in the electronics industry for 30+ years, I am amazed at what legacy problems still stick with us like burrs in our socks.  I'd never have thought the liberal limits of some of this stuff would be reached.  Fascinating.

OTOH, I note that my wife's Macbook has none of these issues.   Kind of different.   

by John Elliott(anon) on ‎20-07-2011 01:33 AM

The BIOS has been around since the era of 1 MByte RAM

1 MByte address space -- the first PCs had as little as 16K RAM.

by Jörg(anon) on ‎20-07-2011 02:28 AM


thanks for sharing your insights!

> UEFI is “OS-like:” By default, you have full access to the entire hardware of your computer –
> Ethernet adapter, Wi-Fi, Bluetooth, graphics card, USB ...

Hmm, apart from all the benefits this enables also a whole new breed of boot virus, rootkits ...  :-(


by Administrator on ‎20-07-2011 02:45 AM

Fauxscott - indeed, very different, your wife's MacBook runs on a mixture of EFI (1.0) and UEFI.

John, you're absolutely right. I'll correct that asap.

Jörg, yes, there's potential for viruses since UEFI allows running custom code. However, as the UEFI implementations vary from manufacturer to manufacter, I don't think that's a huge threat right now.Besides, the latest specifications show that UEFI is capable of defending itself quite well - that includes driver signing, hash-based authentification etc. (see

by Stephen Hoffman(anon) on ‎26-07-2011 09:11 AM

EFI is certainly an improvement over BIOS, for many of the reasons cited above, and for some other and additional reasons.

But the added flexibility and the new capabilities of EFI do have a cost. With BIOS, you're usually very limited to what you can do, how much documentation or knowledge you might need to use it, and around what sorts of trouble you can get into.  BIOS is usually menu-based, after all.

EFI does have a boot menu, but you can need to use the EFI command shell for various tasks.  And unfortunately, classic EFI presents one of the more arcane user command shells I've encountered.  (I'd hope that more current versions have addressed some of the usability issues here, and that future versions will continue to see shell improvements.)  

As for an example of shell-level confusion, have a look at the EFI device identification strings displayed in the shell.  Figuring out what device you're looking at isn't at all obvious in the default EFI environment.  Here are two examples of these device names, extracted from some of the HP documentation that references EFI:

Acpi(000222F0,200)/Pci(1|0) 50060B00001CF2DC 1.36 (3.02.170) 

Acpi(000222F0,200)/Pci(1|1) 50060B00001CF2DE 1.36 (3.02.170)

These two ACPI strings happen to be Fibre Channel Host Bus Adapters. 

As for the inconsistent interfaces and vendor-specific extensions, the implementation of EFI on some of the HP servers can have three and potentially more command interfaces that the user is presented with; the EFI interface, the Baseboard Management Controller (BMC) interface, and the particular variation of management processor installed in the server.  These interfaces and environments are quite different, too.  (I'd expect that HP is addressing some of these issues, too.)

As for another source of both confusion and inconsistency, the EFI-level device names (which don't match any operating system device names) will change as disks are added or removed (such as loading a DVD ROM into an optical drive, or creating partitions), so tasks including block-mode disk imaging isn't quite going to produce quite all of what you'd expect.  The EFI-level fs0: device will be a different device, depending on whether there's a DVD loaded in the drive or not.  If there's no DVD, then fs0: is the first Microsoft FAT partition on your configured disks.   If there's a (bootable) DVD loaded, then fs0: is the DVD.

As for FAT, the boot partition volume format expected by EFI is Microsoft FAT, so yes, you'll have to watch for malware infestations.  This isn't at all unique to EFI, however.  Malware adapts, and EFI may (will?) have to start hardening itself against the EFI versions of bootblock infestations.

Some details on an area referenced the article: BIOS can boot from disks larger than 2.1 using the GPT partitioning scheme, and the GPT scheme is the same extension to the older MBR structures that is referenced in the article; GPT disks do contain an MBR for compatibility.  (Google "Hah!IdontneedEFI" for details of the  "time-consuming workarounds or specialized tools" mentioned above - and these tools are something I suspect at least some of the platform vendors will be interested in deploying.)

While discussing tools, I would not necessarily expect that the integrated nor add-on tools can necessarily perform even basic system-level functions, such as managing and updating device firmware.   And some of these tools packages don't live where you'd expect, they're resident on the target hard disk.  If that boot disk is corrupted, you'll need to access the tools on a different disk. 

EFI is surprisingly ignorant of the Fibre Channel environment for such a comparatively recent innovation, and equally ignorant of the LAN environment, for that matter.  The automatic determination of the network devices and services might be present isn't provided.  (This could certainly be addressed with vendor-specific add-ons, but the baseline EFI doesn't necessarily provide FC nor LAN configuration detection.) 

While discussing networking, EFI can offer some particularly useful features not mentioned in the article above, such as an ftp client and a dhcp client, meaning that it is possible to download files directly into the EFI environment from remote servers.  EFI also has support for remote (diskless) bootstraps.  

And though not part of EFI, the the HP management processors are exceedingly useful adjuncts to EFI, and can provide remote access into EFI and the BMC environments.

EFI is very different, very powerful, and unfortunately also quite frustrating for many new users.

(As for Apple and EFI?  Apple placed its own and far simpler interface atop EFI.  You will need to load tools to even access the EFI-level environment on Apple hardware.)

Yes, EFI is definitely better than BIOS.  Yes, it can directly partition far larger disks.  Do I appreciate what EFI can bring?  Yes.  But definitely wallk into this brave new post-BIOS world with your eyes wide open.  And (if you're running servers) seriously consider acquiring the remote management processor option; the HP management processor options are quite powerful, and well worth the extra investment.

And as the author suggests, definitely test-drive EFI.  It's often worth it to IT, but can definitely require some practice and testing and site-local documentation before an IT-led deployment.

by Jokwe(anon) on ‎28-07-2011 12:57 PM

Same as above

by spuffler(anon) on ‎14-08-2011 09:21 PM

Wondering if any of this is going to be open standards oriented. Yet another 'must purchase secret copy-restricted documents' situation isn't beneficial to most of the consumers outsideof the developer pools. Having critical elements of the boot process be exclusively hidden from scrutiny can lead to entrapping an error.

by tc(anon) on ‎20-08-2011 05:09 AM

>> Support for HDDs with more than 2.1 GBytes: UEFI solves this problem by introducing the newer partition table called GUID (global unique identifier), which is finally capable to address more than 2 terabytes of storage

I've seen really nasty problem with the new disk labels in our development department (not getting correctly recognized by our software) - I really hope that the new GUIDs won't affect the UEFI rollout. IPv6 is a disastrous one already.

Thanks for the great article.

Also I think you made a typo there 2.1 GBytes -> 2.1 TBytes.

by Administrator on ‎22-08-2011 06:00 AM

Hey tc, thanks for sharing your experience! Has your DEV department solved the issues yet? Is there a workaround? That might be helpful to our readers.

(typo corrected)

Best, Sandro

by Name(anon) on ‎18-02-2012 07:53 AM

I have to admit,it is a very racist article.

Remember UEFI is a big step forward, baby step forward. Allowing UEFI "kernel" to be more complicated than it suppose to be, its a bad idea. Under your OS there will be running UEFI "kernel", with access to the internet and your hardware and OS. So under your OS will be sitting agent that can do much more than just POST and allow to boot from 2TB hdd's it can talk with your OS, monitor it and more.

Calling BIOS out-of-date? You can call it unsupported, unmaintained, but still it is not true. UEFI will probably takeover many hardware motherboards. I do not want to have mysterious, non free code running under my OS. BIOS was more secure because of space and lack of internet. You could not directly attack BIOS, but by BIOS you could attack OS. Right now UEFI can be attacked directly and compromise your OS.

And yes it will rock IT hard, after many overtaken Hosts by attacking UEFI directly.

That was my cent.

by SteveS(anon) on ‎21-02-2012 05:44 AM

With fttp and netboot (e.g. iPXE) why don't OEMs provide a UEFI BIOS to reinstall your original OS across the internet?

1. Connect Enet cable (or use WiFi)

2. Invoke UEFI BIOS and download via fttp/iPXE(?) WinPE OS into Ramdrive

3. Partition and format HDD (prompt user)

4. Download from net and install Windows (8) to HDD

This is possible now and could easily be done by OEMs or even MS - they just need to host the files on a server  - see at for how to boot over the internet now. As the System Model number is known by the BIOS (DMI) and the OS original SKU (e.g. Win 8 Pro) could also be set in the BIOS (in the case of Win 8 even the Product Key will already be in the BIOS!) - reinstalling the original OS could be done at any time and no large Recovery DVDs needed!


by carlos santana (anon) on ‎17-03-2012 03:05 PM

You sir, are an idiot.

You could use your mouse to navigate in the bios GUI on some 386/486 bios, which was slow and stupid and it's only coming back again after 20 fucking years, also the ability of turning on and off your computer remotely without booting to an OS is complete shit from a security standpoint and also you might have forgotten to mention the advantages of the bios, because just in case you didn't understanded yet, you can't do something and have only advantages to it.

You made me lose my time reading a heavily biased comparison between EFI and BIOS when i wanted an objective one.

by InsertGUIDHere(anon) on ‎24-04-2012 06:19 PM

Pretty much the same.

by Dan Casey(anon) on ‎20-06-2012 04:03 PM

great story.  how do i update my "efi" through hp support?

by mspl(anon) on ‎26-06-2012 12:16 AM

It is not true that there're problems with >2.1TB drives. What BIOS does is load the first sector of the disk, the rest depends on the code there. Doesn't matter if the drive has 100 MB or 100 TB. Also, bioses have been supporting int13 extensions (read: full LBA support) for good 15 years as well - which was required to go past old 8.4 GB barrier. So "can't support >2.1TB" is pure bullshit.

As for booting from gpt layout on bios-only boards, take for example syslinux and its "gpt handover protocol":

Simple, efficient, elegant.

SandroVillinger wrote:

Furthermore, the BIOS is physically unable to boot from hard disks with more than 2.1 TB. Back in the 80s, that kind of capacity seemed like a fairy tale, but we are being ushered into an era of hard disks with multiple terabytes of disk space. (See Solid State Drives for Desktop PCs and Laptops: Ready for Prime Time?)

The problem lies within the old MBR (Master Boot Record) system used by most BIOSes. The partition table is limited to 2.1 TB, so your clients can’t boot from these devices – at least not without time-consuming workarounds or specialized tools.


It's at best half-true. If M$ side of the world intendently decides to ignore absolutely banal solutions, doesn't make things impossible. And it's really trivial here, simply coming down to "don't ignore gpt layout" on non-uefi systems. As soon as bootmgr is loaded (or even ntldr on xp64 systems), there should be no problems. But why bother, right ? Hell - even syslinux can pull and load window's bootmgr directly with no problems (if microsoft programmers are that lazy ...).

FWIW, linux side of the world have 0 problems or issues with that. And requires 0 "time-consuming workarounds or specialized tools." BSD side of the world /probably/ similar, but I haven't looked into that area.

by kn9sli(anon) on ‎28-11-2012 02:28 PM

I see more problems than solutions. I will just not boot from a 2.1 tb hard drive .

by msackett04(anon) on ‎01-01-2013 04:27 PM

UEFI restricts the user to only loading operating systems with digitally signed certificates, and the kicker is that Microsoft is in charge of who is digitally signed.  If a distro wants it's users to be able to run their software, they need Microsofts approval.  This is severely restrictive, and treats Linux as an inferior OS.  If anything, UEFI should be changed from "secure boot" to "restricted boot."  Users deserve a choice on which OS they install on their hardware, along with what software they want.  I do not recall bios ever restricting my choice of what OS I want to run.  Microsoft is trying to squeeze the competition out, and demoralize them by forcing them to request Microsofts permission to run on a device.  UEFI is not a bad idea, but should be in the hands of OEM'S, not an evil corporation that just got off Monopoly probation.  Then OEM's can freely sign all OS's to the bootloader, without paying dues to Microsoft.  If Microsoft makes their own hardware, then fine, regulate it, but to claim all PC's should pay for a Microsoft license in order to run on pc's is ludicrous.

by CRove(anon) on ‎13-01-2013 03:46 PM
Old PC's maybe will get more valuable in time. When people realize that UEFI is Big Brother in your Computer. Another dreams of him which seem to become true. It is an OS you cannot interfere. It will have backdoors, but you cannot install a firewall or AV. Remote control is what it says. PC turned off doesn't matter, the HDD can be accessed, like the RAM and everything else and all this even over WIFI. The signed certificates is another story ... one about about identity and access control, which also is completely in Big Brothers hand. Don't throw away good old PC's ....
by John Phoenix(anon) on ‎26-01-2013 09:26 AM

msackett04 you are wrong. Microsoft does not control giving out secure boot keys for UEFI. They Only control giving out secure boot keys to allow dual booting with Windows 8 retail as comes preloaded on a new system by the OEM. Microsoft requires the OEM to use UEFI and secure boot with Windows 8 retail or they do not allow the OEM to build and sell a system with Windows 8 preinstalled.

If you don't have Windows 8 retail preinstalled by the OEM, you have no problem and do not require obtaining such a key from Microsoft.

While it may be true this does hurt Windows 8 retail users who want to boot other OS's along with Windows 8, there are ways around this. 1) You can switch manually from UEFI and legacy bios to install and run your linix system - on many systems there is a legacy bios compatibility layer. Not all systems have this, some new systems are UEFI only.  2) The distro of choice can have a bootloader that allows you to boot from UEFI as in the cace of Ubuntu, Mint, fedora and a few others. Not all Linux distros of other non linux systems have such boot loaders in place yet but most are working on it. 3) for Linux for instance, The Linix Foundation is working on obtaining a secure boot key from Microsoft to allow the proper dual booting with Windows 8 retail withouth the need for a hacked bootloader. This is in the works and other non linux operating systems I'm sure will follow.

Again, if you dont have a new machine that has Windows 8 preinstalled you don't have to worry about a secure boot key. You will still if UEFI is enabled, have to use a proper bootloader for your OS to work with UEFI, just as every OS had to be set up to work with Bios. There is nothing new here. You cannot take an existing system of any kind made for one type of input output system and expect it to work with another type of input output system. You can't install Mac OSX on PC for instance without some hacking to the way in which it cooperates with your hardware.

by Brian Harvey(anon) on ‎02-02-2013 07:06 PM

The real concern with UEIF is secure boot and it's potential to lock out open source and/or other "undesirable" OSs.

by JustThisOnceAndNoMore(anon) on ‎03-02-2013 02:21 PM

I have noticed that these "new" changes in other areas seem to leave out the user. I saw this with browsers and the Internet. I even put my "two cents" worth in to keep in some fashion much of the "role your own HTML", but with some distain I was rebuffed.

I hope that these techs create tools and tutorials for the least of us.



by Name1(anon) on ‎18-02-2013 12:08 PM

UEFI IS FULL OF BUGS! AND SECURITY RISKS! Replace the USER control of Hardware with Mass Control for IT.

Any time you take away control from the Hardware from the USER and give it to the IT Guy For MASS management you Create MASSIVE Security FLAWS on a MASSIVE Scale.  Whats Better USER control Or MASS CONTROL  clearly this is a big brother issue at the SOFTWARE LEVEL no Improvements just TAKEOVERS & BUGS!

Oh FATASTIC LETS USE UEFI to check email! And use an Unencrypted Clear Password Transfer Protocol Service like FTP to transfer files hardware level control to it!   Whats the point of an OS if you can just tap into and REPLACE THE Firmware of a computer over the internet through some bug! HUGE Security Flaw!

Not To mention upsetting THE entire LINUX community with secure boot GOOD JOB Micro/HardPenalty/Intruder!

I Will NOT Be buying HARDWARE with UEFI! I will Standup for my rights as a computer user and do what I want with my hardware without having to ask permission! I will control my own computer I will NOT ALLOW Blatant disregard for security sacrificed for mass control to rule my life!

Watch this an konw what i'm talking about!

by name2(anon) on ‎18-02-2013 12:09 PM

Fast Forward to 18:33 for the BUGS and Security Risks~!

by Todd(anon) on ‎08-03-2013 09:23 PM

Slapped together a new system using

ASRock Intel X79 Extreme4 motherboard

Kingston HyperBeast 2400MHz DDR3 19200 RAM

Intel i7 3820 processor

Nvidia GTX660 Graphics Card

212 EVO CPU Cooler

This was my first intro into the world of UEFI, ACPI, HPET Tables, DeepSX, BRCM's and ME Subsystems..

It would be nice to have a short explanation of the acronym and it's intended purpose while trying to figure out if you want to use it or not.. instead of playing catch-up after the fact.

by Feikert D(anon) on ‎11-03-2013 10:02 PM


by NH(anon) on ‎29-04-2013 11:36 PM

Well, I can say after reading the above comments..... I am confused on what to do....... 

I am an old fart from days long past when you had memory of 1mb and you were king (laugh).

I am not an IT Tech and just a home user and builder for the past 40 years i guess. After building my new system this week using the ASUS P9X79Pro (UEFI capable) mB.... I do not know what to do anymore based on the above comments. I am currently running GPT with Windows 7 Pro; 16GB DDR3 / 2133 (XMS) memory and other nonsense. I have my bios currently set to use IDE vs. the UEFI option.

My computer right now runs great but still confused on whether or not to change the setting in the BIOS over to UEFI setting.  I generally understand the Security key issue, but being a home builder I do not know if it applys, and I am running Windows anyway for my op system so all should work - no dual boot, no linux.

I even recall using a Bios Translation program back in the days for old bios's to see the larger hard drive sizes / partitions.  Back then, w/out the translation program it would not recog the full size of the hd.  Move forward, and here we are.....  I want to be able to use some of the new 3TB and 4TB drives for back of files and things 

So again,  here I sit with my new system wondering if I shouild flip the switch to UEFI.

Comments welcome.  You can reach me at:





by Revansiddappa India(anon) on ‎22-06-2013 04:36 AM

Good! Interesting!. It has great advantages in coming days. I am of the openian that along with UEFI; lagecy BIOS should also be provided as one of the setting. So that user can (for time being) switch over which is suiatable for the application. I think this is possible and comapred to UEFI; legacy BIOS requires very very less resource. Hope UEFI forum will consider the same.

Post a Comment
Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.

The HP Input Output site is sponsored by HP and features articles and content from HP and third-party contributors. Third-party articles and content, while paid for by HP, do not necessarily represent the views and opinions of HP. HP does not endorse this content and is not responsible for its accuracy, availability and quality.

Follow Us
"It's Not My Job" - Handling the Vendor Finger-Pointing Trap Is Teamwork Dead? A Post-Agile Prognosis Improving Your Personal Brand with Social Networking 5 Types of Meetings Every Business Must Explore
┼ Based on energy, paper and toner savings from regular printer usage. Results may vary.