<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; bios</title> <atom:link href="http://www.ghacks.net/tag/bios/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Fri, 10 Feb 2012 13:29:21 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>Windows 8, Boot Security And Third Party Operating Systems</title><link>http://www.ghacks.net/2011/09/23/windows-8-boot-security-and-third-party-operating-systems/</link> <comments>http://www.ghacks.net/2011/09/23/windows-8-boot-security-and-third-party-operating-systems/#comments</comments> <pubDate>Fri, 23 Sep 2011 08:34:29 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Windows]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[microsoft]]></category> <category><![CDATA[secure boot]]></category> <category><![CDATA[uefi]]></category> <category><![CDATA[windows 8]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=50748</guid> <description><![CDATA[Things got heated up quite a bit in the past two days as Microsoft started to reveal information about boot security in Windows 8. The main concern raised by Matthew Garrett and others was that secure boot could prevent the installation and use of third party operating systems like Linux on an OEM system running [...]]]></description> <content:encoded><![CDATA[<p>Things got heated up quite a bit in the past two days as Microsoft started to <a
href="http://blogs.msdn.com/b/b8/archive/2011/09/20/reengineering-the-windows-boot-experience.aspx">reveal</a> information about boot security in Windows 8. The main concern raised by <a
href="http://mjg59.dreamwidth.org/5552.html">Matthew Garrett</a> and others was that secure boot could prevent the installation and use of third party operating systems like Linux on an OEM system running Windows 8.</p><p><em>Please note that this is only a issue for UEFI systems, if you plan to upgrade an existing system with BIOS you won&#8217;t be affected by it.</em></p><blockquote><p>The UEFI secure boot protocol is the foundation of an architecturally neutral approach to platform and firmware security. Based on the Public Key Infrastructure (PKI) process to validate firmware images before they are allowed to execute, secure boot helps reduce the risk of boot loader attacks. Microsoft relies on this protocol in Windows 8 to improve platform security for our customers.</p></blockquote><p>Microsoft today responded to those claims in another article <a
href="http://blogs.msdn.com/b/b8/archive/2011/09/22/protecting-the-pre-os-environment-with-uefi.aspx">on the</a> Building Windows 8 blog. OEM systems shipping with Windows 8 will have secure boot enabled by default to only load verified operating system loaders during boot time. This prevents malware from switching the boot loader, but also other operating systems that are not signed from being loaded.</p><p>While Secure Boot is enabled by default, it is up to the OEM to add controls to UEFI to allow the user to disable the feature. The Samsung tablet that Microsoft gave away on the BUILD conference for instance came with an option to disable Secure Boot on the device.</p><p><img
src="http://www.ghacks.net/wp-content/uploads/2011/09/secure-boot.jpg" alt="secure boot" title="secure boot" width="480" height="329" class="alignnone size-full wp-image-50749" /></p><p>Microsoft employee Tony Mangefeste notes that &#8220;OEMs are free to choose how to enable this support&#8221;, which means that OEM could make the decision to not implement the override in the UEFI configuration. This would then mean that customers would not be able to boot third party operating systems from the OEM machine.</p><p>The only option that consumers have at this point is to find out about this in advance before making a purchase. I for one would never buy a system that prevents me from loading a third party OS.</p><p>Your options to install Windows 8 are:</p><ul><li>Install Windows 8 on a PC with BIOS.</li><li>Build your own new PC, or have it build for you.</li><li>Verify that the OEM PC with Windows 8 is offering an option to disable Secure Boot before purchasing it.</li><li>Hope that someone will come up with a hacked firmware to disable Secure Boot</li></ul><p>What&#8217;s your take on Secure Boot? I personally think that it improves security, and do not think that it is an issue as long as all OEMs add the means to disable the feature. Let me know in the comments.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2011/09/23/windows-8-boot-security-and-third-party-operating-systems/feed/</wfw:commentRss> <slash:comments>7</slash:comments> </item> <item><title>Program Your Computer to Sleep and Wake Itself Each Night Using BIOS and Software Features</title><link>http://www.ghacks.net/2011/06/14/program-your-computer-to-sleep-and-wake-itself-each-night-using-bios-and-software-features/</link> <comments>http://www.ghacks.net/2011/06/14/program-your-computer-to-sleep-and-wake-itself-each-night-using-bios-and-software-features/#comments</comments> <pubDate>Tue, 14 Jun 2011 21:01:27 +0000</pubDate> <dc:creator>Melanie Gross</dc:creator> <category><![CDATA[Software]]></category> <category><![CDATA[Windows]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[shutdown]]></category> <category><![CDATA[sleep]]></category> <category><![CDATA[windows software]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=46482</guid> <description><![CDATA[Our computers get worked over pretty hard. We run them nonstop all day, pulling up a dozen different windows with ten different operations going on in each. When we go to sleep many of us leave our machines running, partially because we think we may return to it later and half because we are just [...]]]></description> <content:encoded><![CDATA[<p>Our computers get worked over pretty hard.  We run them nonstop all day, pulling up a dozen different windows with ten different operations going on in each.  When we go to sleep many of us leave our machines running, partially because we think we may return to it later and half because we are just too lazy to turn it off.  They do what they are supposed to, most of the time, and don’t give us any trouble, yet we still make them work without end.</p><p>Who cares, right?  They are computers, after all, and it’s our right to leave them running.  While true, it is good for a computer to get a break once in a while.  While most computers can stay on for weeks on end without significant damage, it is best to turn most computers off completely each and every day when not in use for an extended period.<br
/> While it may not hurt much to shut computers down at the end of the day, many people are annoyed to have to boot them back up in the morning.  The two minutes it takes for a Windows machine is just too long, and some users leave their computers on all night to avoid the “lengthy” process of booting.</p><p>But what if your computer could shut itself off after it knows you have gone to bed and then wake itself back up again?  Such a situation would be downright ideal – you wouldn’t have to remember to shut it down before leaving it for the day, and you wouldn’t have to wait for it to start back up in the morning.  What’s not to love?</p><p>This how-to will remind users how to program their computers to shut themselves down after day’s end and will introduce, to users with a modern enough BIOS, a way to have it start up on its own.<br
/> GHacks.net actually shared with you an automatic shutdown program called <a
href="http://www.ghacks.net/2008/09/05/automatic-shutdown/">Smart Shutdown</a> a few years back.  While a solid option, some people have had problems getting it to work on Windows 7 machines.  Luckily, another option called Switch Off provides the same features with support for Windows 7.  The program can be downloaded <a
href="http://www.airytec.com/en/switch-off/">here</a>.</p><p>Follow the steps of the automatic installer, and when finished a new icon should be sitting on your taskbar.  Clicking on it brings up a handy interface that allows you to choose how often you would like your machine to take itself down.  Make your selections before clicking Enable Task.</p><p><img
src="http://www.ghacks.net/wp-content/uploads/2011/06/smart-shutdown.png" alt="smart shutdown" title="smart shutdown" width="306" height="379" class="alignnone size-full wp-image-46483" /></p><p>Getting your machine to boot back up on its own is a little more hit and miss, but most recent machines should have you covered.  Unfortunately software cannot be used to bring your computer up from a shutdown – that would defeat the purpose of a shutdown.  But if you enter your BIOS options as your computer is just beginning to boot, you may find a series of options under Power Management Options or something to that effect.</p><p>Take a look there for an alarm feature which will automatically turn your computer back on.  It may be labeled as Resume by RTC or RTC Alarm.  Program it to come up an hour or so before you use it each day, and like magic, your login screen will await with your computer feeling rejuvenated after a long night’s sleep.</p><p>That may be going too far, but giving your computer a rest really is good for its components.  You aren’t using it anyway, so why not let it go down for the night?</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2011/06/14/program-your-computer-to-sleep-and-wake-itself-each-night-using-bios-and-software-features/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Bios Beep Codes Viewer</title><link>http://www.ghacks.net/2010/06/23/bios-beep-codes-viewer/</link> <comments>http://www.ghacks.net/2010/06/23/bios-beep-codes-viewer/#comments</comments> <pubDate>Wed, 23 Jun 2010 13:20:14 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Software]]></category> <category><![CDATA[Windows]]></category> <category><![CDATA[beep codes]]></category> <category><![CDATA[beep codes viewer]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[bios beep codes]]></category> <category><![CDATA[portable software]]></category> <category><![CDATA[windows software]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=26989</guid> <description><![CDATA[Part of a computer&#8217;s boot process is the Power On Self Test (POST) that tests the hardware of the computer. POST communicates successful or failed tests with beep codes. These BIOS beep codes provide the user with information about the system&#8217;s state and aid in the troubleshooting process in case one of the boot tests [...]]]></description> <content:encoded><![CDATA[<p>Part of a computer&#8217;s boot process is the Power On Self Test (POST) that tests the hardware of the computer. POST communicates successful or failed tests with beep codes. These BIOS beep codes provide the user with information about the system&#8217;s state and aid in the troubleshooting process in case one of the boot tests failed.</p><p>Some hardcore technicians might know all the beep codes and their meaning, everyone else might benefit from a software like Rizone&#8217;s Beep Code Viewer which provides details about every beep code and possible causes.</p><p><span
id="more-26989"></span><div
id="attachment_26990" class="wp-caption alignnone" style="width: 510px"><img
src="http://www.ghacks.net/wp-content/uploads/2010/06/bios-beep-codes-500x435.png" alt="bios beep codes" title="bios beep codes" width="500" height="435" class="size-medium wp-image-26990" /><p
class="wp-caption-text">bios beep codes</p></div></p><p>The software displays information about AMI, AWARD, IBM and Phoenix bios beep codes. Each beep sequence is listed with its linked error name and troubleshooting tips on how to resolve the issue.</p><p>It is important to select the right BIOS manufacturer as all are making use of their own beep code system. 1 long and 3 short beeps for instance indicates a memory failure on AMI systems but video display circuitry problems on IBM systems.</p><p>Most troubleshooting tips are general in nature. The tips to resolve the previously mentioned memory failure for instance asks the user to remove newly installed memory from the system, move or swap the memory and to test the memory in another computer if the other tips do not resolve the hardware issue.</p><p>The software does not offer an option to print out the beep codes. It is however possible to copy and paste the text into a text editor to print it from there.</p><p><a
href="http://www.rizone3.com/">Rizone Beep Codes Viewer</a> is a portable software for Microsoft Windows operating systems. It is compatible with both 32-bit and 64-bit editions.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2010/06/23/bios-beep-codes-viewer/feed/</wfw:commentRss> <slash:comments>8</slash:comments> </item> <item><title>Things To Do When Your Motherboard OnBoard Lan Dies</title><link>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/</link> <comments>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/#comments</comments> <pubDate>Sat, 18 Apr 2009 14:42:16 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[gigabyte]]></category> <category><![CDATA[gigabyte lan]]></category> <category><![CDATA[hardware tips]]></category> <category><![CDATA[lan]]></category> <category><![CDATA[motherboard]]></category> <category><![CDATA[onboard lan]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/</guid> <description><![CDATA[The onboard LAN of my Gigabyte ep35-ds4 motherboard died just a few hours ago. Was surfing the Internet and suddenly connection errors showed up. That&#8217;s bad as the onboard LAN is located on the motherboard of the computer system. It could be that not only the LAN died but also other components. Now what can [...]]]></description> <content:encoded><![CDATA[<p><img
src="http://www.ghacks.net/wp-content/uploads/2009/04/motherboard_lan.jpg" alt="motherboard lan" title="motherboard lan" width="128" height="119" class="alignleft size-full wp-image-12134" />The onboard LAN of my Gigabyte ep35-ds4 motherboard died just a few hours ago. Was surfing the Internet and suddenly connection errors showed up. That&#8217;s bad as the onboard LAN is located on the motherboard of the computer system. It could be that not only the LAN died but also other components. Now what can you do if your motherboard&#8217;s onboard LAN dies?</p><p><span
id="more-12135"></span>First thing was to check the installed hardware in the Windows Control Panel. If you operate a different operating system you need to find and access the equivalent there. The LAN was not listed there anymore. That was bad. It could have been a driver problem so the next step was to check for hardware that was not installed yet. The LAN was not found there either.</p><p>Next step was to reboot the computer and check in the Bios. While doing that I verified that the LAN led was still on. The BIOS showed zero LAN configuration options. I knew that there were some before which gave me the confirmation that something was seriously wrong. Next step CMOS reset. This is done by setting a jumper on the motherboard. The LAN options did not show up then either. I could have tried installing a new BIOS but this sounded awfully risky with dead components on the motherboard.</p><p>You got two options basically at this point. The fast option is to add a new PCI LAN card and install it on the computer system. Good LAN cards should provide better performance than onboard LAN. That&#8217;s what I did. The other option is to contact the manufacturer of the motherboard and wait for an answer. Can take some days, usual result is a replacement or repair which can take weeks or even months. Not a good option if you need to be online most of the day.</p><p>To put everything in a list:</p><ul><li>Check if the operating system lists the onboard component.</li><li>Check if it can be found by scanning for hardware.</li><li>Check if the lights are on (if it has lights)</li><li>Shutdown the computer and see if everything is connected properly</li><li>Check the Bios for the onboard component</li><li>Reset the Bios</li><li>Replace the Nic or replace the motherboard or contact support.</li></ul><p>Do you have any additional tips on how to cope with a dead onboard LAN?</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2009/04/18/things-to-do-when-your-motherboard-onboard-lan-dies/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>Bios Update Made Easy</title><link>http://www.ghacks.net/2008/08/17/bios-update-made-easy/</link> <comments>http://www.ghacks.net/2008/08/17/bios-update-made-easy/#comments</comments> <pubDate>Sun, 17 Aug 2008 09:52:55 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[Knowledge]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[bios update]]></category> <category><![CDATA[computer bios]]></category> <category><![CDATA[motherboard]]></category> <category><![CDATA[update bios]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=6229</guid> <description><![CDATA[Many users shy away from updating the computer bios of their motherboard probably because of the fear of damaging the motherboard irreparably. Methods have evolved in the last years and it is easier and safer to update the bios than it was five years ago. The following article explains an easy and straightforward way of [...]]]></description> <content:encoded><![CDATA[<p>Many users shy away from updating the computer bios of their motherboard probably because of the fear of damaging the motherboard irreparably. Methods have evolved in the last years and it is easier and safer to update the bios than it was five years ago.</p><p>The following article explains an easy and straightforward way of updating the computer bios. The main question that everyone should ask himself before updating the BIOS is if it is beneficiary to update the Bios. The article takes a look at finding that out as well. The phrase &#8220;never change a running system&#8221; has some truth to it but it is still a good idea to check for new Bios versions every now and then.</p><p>It does make sense to check for Bios updates before upgrading computer components. New Bios versions can add support for faster processors, computer memory, lower temperaturs and even add new features.</p><p><span
id="more-6229"></span><strong>Step 1: Identifying the Bios</strong></p><p>Probably the most important step in the Bios updating process is to identify the current motherboard and Bios version properly. The easiest way would be to check a receipt or motherboard manual if one was provided with the computer. If that&#8217;s long gone you can try software like <a
href="http://www.cpuid.com/softwares/cpu-z.html">cpu-z</a> to find out about your motherboard and Bios.</p><p><img
src="http://www.ghacks.net/wp-content/uploads/2008/08/bios_update.jpg" alt="bios update" title="bios update" width="390" height="440" class="alignnone size-medium wp-image-6230" /></p><p>The Mainboard tab contains the information about the motherboard and Bios. Important are the motherboard manufacturer, the motherboard model and the Bios version.</p><p>Cpu-Z supports many motherboards but not all. If your motherboard cannot be identified you need to check the post screen during boot. That&#8217;s the first screen that is being displayed. Hit the pause key after the computer memory is shown and you should find information about the computer Bios as well.</p><p><strong>Step 2: Checking for Bios Updates</strong></p><p>With the information gathered in step 1 it is now possible to visit the manufacturer&#8217;s website and see if new Bios versions are available. The computer manufacturer above is Gigabyte and the motherboard is the EP35-ds4. A good start would be to enter the name of the manufacturer followed by the motherboard model into a search engine.</p><p>That usually leads straight to the page dedicated to the motherboard model.  The Bios version shown in the screenshot above was F2, a check on the Gigabyte EP35-DS4 website shows that the latest Bios version is F5. Most manufacturers display information about changes and additions that have been introduced with each new Bios version. In this case support for the Update CPU ID Intel Yorkfield QX9770 CPU has been added as well as a fix for an ICH9R RAID issue.</p><p>After identifying the Bios updates it would now be time to make a decision if the update would be useful. In the case of the above Bios it would be useful if the ICH9R Raid was used in the current configuration or if the user had plans to build in the  Intel Yorkfield QX9770 CPU.</p><p><strong>Step 3: Updating the Bios</strong></p><p>Step 3 is the actual update process. Every motherboard manufacturer has his own way and software to update the Bios. Methods range from booting to DOS, to updates directly in Windows to updates in the Bios itself.</p><p>In the case of the Gigabyte Bios the Bios was provided with a Dos executable and a batch file. A boot disk would have to be created and the files placed on it. Other manufacturers are offering applications that update the Bios from within Windows which is more comfortable obviously.</p><p>The best way is to search the manufacturer&#8217;s website for information on how to apply the Bios update. It&#8217;s always a good idea to backup the old Bios before applying the new one. That option is usually offered in the software that updates the Bios.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2008/08/17/bios-update-made-easy/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Reveal or Reset the Bios Passwords</title><link>http://www.ghacks.net/2008/06/07/reveal-or-reset-the-bios-passwords/</link> <comments>http://www.ghacks.net/2008/06/07/reveal-or-reset-the-bios-passwords/#comments</comments> <pubDate>Sat, 07 Jun 2008 14:33:47 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Linux]]></category> <category><![CDATA[Software]]></category> <category><![CDATA[Windows]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[bios password]]></category> <category><![CDATA[cmos]]></category> <category><![CDATA[cmos password]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=4897</guid> <description><![CDATA[Password protecting the Bios is considered a weak protection, something that professionals can find out or reset in no time. Besides the obvious possibilities to set a jumper or remove the bios battery to reset the bios password it is also possible to reveal or reset the bios password by using a software like CmosPwd [...]]]></description> <content:encoded><![CDATA[<p>Password protecting the Bios is considered a weak protection, something that professionals can find out or reset in no time. Besides the obvious possibilities to set a jumper or remove the bios battery to reset the bios password it is also possible to reveal or reset the bios password by using a software like <a
href="http://www.cgsecurity.org/wiki/CmosPwd">CmosPwd</a> which is available for Windows, DOS and Linux.</p><p>Most users will probably run the application in Windows. To do that they need to access the command line and install a driver that gives &#8220;direct port I/O access for specified ports to user-mode process (ring 3) using Ke386SetIoAccessMap and Ke386IoSetAccessProcess kernel functions.&#8221; The driver is located in the Windows directory of the software package after unzipping it to the computer.</p><p>The command <strong>ioperm.exe -i</strong> is used to install the driver which can be uninstalled with <strong>ioperm.exe -u</strong> after the bios password has been revealed. Once the driver is installed the bios password can be revealed with the command <strong>Cmospwd_win.exe</strong> which displays a list similar to the one below.</p><p><span
id="more-4897"></span><img
src="http://www.ghacks.net/wp-content/uploads/2008/06/cmos_password-500x194.jpg" alt="cmos password" title="cmos password" width="500" height="194" class="alignnone size-medium wp-image-4898" /></p><p>The application requests the password for all known bioses. Only one hit will be found obviously which in the case of my bios was test in the Award 6.0 line. Reseting the bios can be initiated in DOS with the command <strong>cmospwd /k</strong>. Please note that the cmospwd.exe file is located in the DOS directory of the application. It can also be reset with the <strong>cmospwd_win /k</strong> in Windows.</p><p>Most notebooks store the bios password in an eeprom which can only be retrieved with an eeprom reader.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2008/06/07/reveal-or-reset-the-bios-passwords/feed/</wfw:commentRss> <slash:comments>10</slash:comments> </item> <item><title>Goodbye BIOS Here Comes UEFI</title><link>http://www.ghacks.net/2008/02/06/goodbye-bios-here-comes-uefi/</link> <comments>http://www.ghacks.net/2008/02/06/goodbye-bios-here-comes-uefi/#comments</comments> <pubDate>Wed, 06 Feb 2008 10:06:51 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[Operating Systems]]></category> <category><![CDATA[Windows]]></category> <category><![CDATA[amd]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[intel]]></category> <category><![CDATA[microsoft]]></category> <category><![CDATA[uefi]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2008/02/06/goodbye-bios-here-comes-uefi/</guid> <description><![CDATA[UEFI which is an acronym for Unified Extensible Firmware Interface which will eventually replace the 20+ year old Bios. The new standard is backed by everyone so to speak including Intel, AMD, Microsoft, IBM, American Megatrends, Phoenix Technologies and Apple.]]></description> <content:encoded><![CDATA[<p>UEFI which is an acronym for Unified Extensible Firmware Interface which will eventually replace the 20+ year old Bios. The new standard is backed by everyone so to speak including Intel, AMD, Microsoft, IBM, American Megatrends, Phoenix Technologies and Apple.</p><p>Support will be added to Windows Vista with Service Pack 1 and is already available for Microsoft Windows Server 2008 and first motherboards supporting UEFI are already available on the market (MSI P35 Neo3). One of the main differences between BIOS and UEFI is the way applications are coded. Assembler was used if functions or applications had to be coded for the BIOS while a higher level language code will be used to program the UEFI.</p><p>The memory footprint is about 10 times smaller as well. The main benefits for customers are a better presentation and (probably) motherboards that are more stable. When will the transition be complete ? Insiders suggest that it might take between two or three years.</p><p><span
id="more-3129"></span><br
/><blockquote>The UEFI specification defines a new model for the interface between personal-computer operating systems and platform firmware. The interface consists of data tables that contain platform-related information, plus boot and runtime service calls that are available to the operating system and its loader. Together, these provide a standard environment for booting an operating system and running pre-boot applications.</p></blockquote> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2008/02/06/goodbye-bios-here-comes-uefi/feed/</wfw:commentRss> <slash:comments>6</slash:comments> </item> <item><title>Find out the which BIOS is installed in your PC</title><link>http://www.ghacks.net/2007/10/10/find-out-the-which-bios-is-installed-in-your-pc/</link> <comments>http://www.ghacks.net/2007/10/10/find-out-the-which-bios-is-installed-in-your-pc/#comments</comments> <pubDate>Wed, 10 Oct 2007 09:25:57 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Operating Systems]]></category> <category><![CDATA[Windows]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[computer]]></category> <category><![CDATA[msinfo32]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2007/10/10/find-out-the-which-bios-is-installed-in-your-pc/</guid> <description><![CDATA[A friend of mine was recently asking me if I knew how to find out which BIOS was installed in his computer. He wanted to know for two reasons. The first was that he could not remember and was not able to figure out on his own. He did want to buy a better CPU and had to know which were supported by his motherboard and BIOS.]]></description> <content:encoded><![CDATA[<p>A friend of mine was recently asking me if I knew how to find out which BIOS was installed in his computer. He wanted to know for two reasons. The first was that he could not remember and was not able to figure out on his own. He did want to buy a better CPU and had to know which were supported by his motherboard and BIOS.</p><p>The second reason was related. He wanted to check if a BIOS upgrade was available to see if an update to a newer version would add support for faster CPUs.</p><p>Finding out which BIOS is installed in a computer is not complicated at all. You could pay attention to the boot sequence but a far better and easier way is to use a software that ships with Windows anyway.</p><p><span
id="more-2108"></span><img
src="http://www.ghacks.net/files/screens/2007/10/system-bios.jpg" alt="system bios" /></p><p>To find out you simply have to type &#8216;msinfo32&#8242; in a command prompt. Once you know which BIOS is installed you can search for updates on the Internet. If you can remember the motherboard manufacturer and version it would be even easier of course, but if you can&#8217;t remember this is your best choice.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2007/10/10/find-out-the-which-bios-is-installed-in-your-pc/feed/</wfw:commentRss> <slash:comments>6</slash:comments> </item> <item><title>Find out your bios password</title><link>http://www.ghacks.net/2007/01/03/find-out-your-bios-password/</link> <comments>http://www.ghacks.net/2007/01/03/find-out-your-bios-password/#comments</comments> <pubDate>Wed, 03 Jan 2007 16:01:05 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Hacking]]></category> <category><![CDATA[Hardware]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[cmos]]></category> <category><![CDATA[cmospwd]]></category> <category><![CDATA[discover]]></category> <category><![CDATA[dos]]></category> <category><![CDATA[hack]]></category> <category><![CDATA[motherboard]]></category> <category><![CDATA[password]]></category> <category><![CDATA[pwd]]></category> <category><![CDATA[reveal]]></category> <category><![CDATA[Windows]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2007/01/03/find-out-your-bios-password/</guid> <description><![CDATA[The bios can be protected with a password to prevent others from accessing its settings. You have to enter the password to be able to access it, if you can't provide the correct one the access gets denied. The following method describes a way to recover the password if you forgot it or bought a used computer with a bios password.]]></description> <content:encoded><![CDATA[<p>The bios can be protected with a password to prevent others from accessing its settings. You have to enter the password to be able to access it, if you can&#8217;t provide the correct one the access gets denied. The following method describes a way to recover the password if you forgot it or bought a used computer with a bios password.</p><p><a
href="http://www.cgsecurity.org/wiki/CmosPwd" target="_blank">CmosPwd</a> is a free program that is able to display information about the bios once it is executed.  You do need to create a bootable disk to be able to execute the program in dos mode. To create a bootable disk in windows right-click the disk drive and select format from the list of options. It is important that you enable the option Create an MS-DOS startup disk.</p><p><span
id="more-1061"></span></p><p>Once the disk is created copy the contents from the dos folder of cmospwd to the disk and restart the computer. You will have to remove all hard drives from the system if you do not automatically boot from disk drive. Type cmospwd.exe in the command line and the password should appear. Ignore the information about the other bios manufacturers and take a look at the one your computer is using.</p><p>Another possible method would be to start the computer in safe mode with command prompt which could work as well. You still need to access the files somewhere so make sure that the hard drive is accessible.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2007/01/03/find-out-your-bios-password/feed/</wfw:commentRss> <slash:comments>14</slash:comments> </item> <item><title>How to bypass your bios password</title><link>http://www.ghacks.net/2006/02/27/how-to-bypass-your-bios-password/</link> <comments>http://www.ghacks.net/2006/02/27/how-to-bypass-your-bios-password/#comments</comments> <pubDate>Mon, 27 Feb 2006 14:02:16 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Knowledge]]></category> <category><![CDATA[bios]]></category> <category><![CDATA[bios password]]></category> <category><![CDATA[bios tips]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=336</guid> <description><![CDATA[A bios password prevents access to the bios for unauthorised users. Sometimes this password gets forgotten and you face the difficulty to find a way to enter your bios again. The article "<a
href="http://www.info-directory.info/Article301.html" target="_blank">how to bypass your bios password</a>" explains in detail various methods that bypass the bios password. So, if you are in need, take a look and try the available methods.]]></description> <content:encoded><![CDATA[<p>A bios password prevents access to the bios for unauthorised users. Sometimes this password gets forgotten and you face the difficulty to find a way to enter your bios again. The article &#8220;<a
href="http://www.info-directory.info/Article301.html" target="_blank">how to bypass your bios password</a>&#8221; explains in detail various methods that bypass the bios password. So, if you are in need, take a look and try the available methods.</p><p><span
id="more-336"></span></p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2006/02/27/how-to-bypass-your-bios-password/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
