<?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>Mumyls Blog &#187; Hardware</title>
	<atom:link href="http://www.mumyls.com/category/tips/computers/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mumyls.com</link>
	<description>Better Than Yesterday</description>
	<lastBuildDate>Wed, 29 Sep 2010 01:28:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>BIOS Update Procedure</title>
		<link>http://www.mumyls.com/2009/03/bios-update-procedure/</link>
		<comments>http://www.mumyls.com/2009/03/bios-update-procedure/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 00:36:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Operating System]]></category>
		<category><![CDATA[bios]]></category>
		<category><![CDATA[procedure]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.mumyls.web.id/2009/03/bios-update-procedure/</guid>
		<description><![CDATA[All latest Motherboards today, 486/ Pentium / Pentium Pro etc.,ensure that upgrades are easily obtained by incorporating the system BIOS in a FLASH Memory component. With FLASH BIOS, there is no need to replace an EPROM component. Once downloaded, the upgrade utility fits on a floppy disc allowing the user to save, verify and update [...]]]></description>
			<content:encoded><![CDATA[<p>All latest Motherboards today, 486/ Pentium / Pentium Pro etc.,ensure that upgrades are easily obtained by incorporating the system BIOS in a FLASH Memory component. With FLASH BIOS, there is no need to replace an EPROM component. Once downloaded, the upgrade utility fits on a floppy disc allowing the user to save, verify and update the system BIOS. A hard drive or a network drive can also be used to run the newer upgrade utilities. However, memory managers can not be installed while upgrading. </p>
<p> <span id="more-79"></span>
</p>
<p>Most pre-Pentium motherboards do not have a Flash BIOS. The following instructions therefore do not apply to these boards. If your motherboard does not have a Flash BIOS (EEPROM) you will need to use an EPROM programmer to re-program the BIOS chip. See your dealer for more information about this. </p>
<p>Please read the following instructions in full before starting a Flash BIOS upgrade:   <br />A. Create a Bootable Floppy (in DOS) </p>
<p>â€¢With a non-formatted disk, type the following: </p>
<p>format a:/s </p>
<p>â€¢If using a formatted disk, type: </p>
<p>sys a: </p>
<p>This procedure will ensure a clean boot when you are flashing the new BIOS. </p>
<p>B. Download the BIOS file </p>
<p>â€¢Download the correct BIOS file by clicking on the file name of the BIOS file you wish to download. </p>
<p>â€¢Save the BIOS file and the Flash Utility file in the boot disk you have created. Unzip the BIOS file and the flash utility file. If you don&#8217;t have an &quot;unzip&quot; utility, download the WinZip for Windows 95 shareware/ evaluation copy for that one time use from _www.winzip.com or _www.pkware.com. Most CD ROMs found in computer magazines, have a shareware version of WinZip on them. </p>
<p>â€¢You should have extracted two files: </p>
<p>Flash BIOS utility eg: flash7265.exe (for example) </p>
<p>BIOS eg: 6152J900.bin (example) </p>
<p>Use the latest flash utility available unless otherwise specified (either on the BIOS update page or in the archive file). This information is usually provided. </p>
<p>C. Upgrade the System BIOS </p>
<p>During boot up, write down the old BIOS version because you will need to use it for the BIOS backup file name. </p>
<p>Place the bootable floppy disk containing the BIOS file and the Flash Utility in drive a, and reboot the system in MS-DOS, preferably Version 6.22 </p>
<p>â€¢At the A:&gt; prompt, type the corresponding Flash BIOS utility and the BIOS file with its extension. </p>
<p>For example: </p>
<p>flash625 615j900.bin </p>
<p>â€¢From the Flash Memory Writer menu, select &quot;Y&quot; to &quot;Do you want to save BIOS?&quot; if you want to save (back up) your current BIOS (strongly recommended), then type the name of your current BIOS and its extension after FILE NAME TO SAVE: eg: a:\613J900.bin </p>
<p>Alternatively select &quot;N&quot; if you don&#8217;t want to save your current BIOS. Beware, though, that you won&#8217;t be able to recover from a possible failure. </p>
<p>â€¢Select &quot;Y&quot; to &quot;Are you sure to program?&quot; </p>
<p>â€¢Wait until it displays &quot;Message: Power Off or Reset the system&quot; </p>
<p>Once the BIOS has been successfully loaded, remove the floppy disk and reboot the system. If you write to BIOS but cannot complete the procedure, do not switch off, because the computer will not be able to boo, and you will not be given another chance to flash. In this case leave your system on until you resolve the problem (flashing BIOS with old file is a possible solution, provided you&#8217;ve made a backup before) </p>
<p>Make sure the new BIOS version has been loaded properly by taking note of the BIOS identifier as the system is rebooting. </p>
<p>For AMI BIOS   <br />Once the BIOS has been successfully loaded, remove the floppy disk and reboot the system holding the &quot;END&quot; key prior to power on until you enter CMOS setup. If you do not do this the first time booting up after upgrading the BIOS, the system will hang. </p>
<p>BIOS Update Tips   <br />note:    <br />1.Make sure never to turn off or reset your computer during the flash process. This will corrupt the BIOS data. We also recommend that you make a copy of your current BIOS on the bootable floppy so you can reflash it if you need to. (This option is not available when flashing an AMI BIOS). </p>
<p>2. If you have problems installing your new BIOS please check the following: </p>
<p>Have you done a clean boot?   <br />In other words, did you follow the above procedure for making a bootable floppy? This ensures that when booting from &quot;A&quot; there are no device drivers on the diskette. Failing to do a clean boot is the most common cause for getting a &quot;Memory Insufficient&quot; error message when attempting to flash a BIOS. </p>
<p>If you have not used a bootable floppy, insure a clean boot either by </p>
<p>a) pressing F5 during bootup </p>
<p>b) by removing all device drivers on the CONFIG.SYS including the HIMEM.SYS. Do this by using the EDIT command. </p>
<p>Have you booted up under DOS?   <br />Booting in Windows is another common cause for getting a &quot;Memory Insufficient&quot; error message when attempting to flash a BIOS. Make sure to boot up to DOS with a minimum set of drivers. Important: Booting in DOS does not mean selecting &quot;Restart computer in MS-DOS Mode&quot; from Windows98/95 shutdown menu or going to Prompt mode in WindowsNT, but rather following the above procedure (format a: /s and rebooting from a:\). </p>
<p>Have you entered the full file name of the flash utility and the BIOS plus its extension?   <br />Do not forget that often you will need to add a drive letter (a:\) before flashing the BIOS. Example: when asked for file name of new BIOS file which is on your floppy disk, in case you&#8217;re working from c:\ your will need to type a:\615j900.bin, rather than 615j900.bin only.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mumyls.com/2009/03/bios-update-procedure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beep Code Manual</title>
		<link>http://www.mumyls.com/2009/03/beep-code-manual/</link>
		<comments>http://www.mumyls.com/2009/03/beep-code-manual/#comments</comments>
		<pubDate>Wed, 18 Mar 2009 10:53:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[beep]]></category>
		<category><![CDATA[bios]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[Hard Ware]]></category>

		<guid isPermaLink="false">http://www.mumyls.web.id/?p=72</guid>
		<description><![CDATA[BIOS Beep Codes When a computer is first turned on, or rebooted, its BIOS performs a power-on self test (POST) to test the system&#8217;s hardware, checking to make sure that all of the system&#8217;s hardware components are working properly. Under normal circumstances, the POST will display an error message; however, if the BIOS detects an [...]]]></description>
			<content:encoded><![CDATA[<p>BIOS Beep Codes</p>
<p>When a computer is first turned on, or rebooted, its BIOS performs a power-on self test (POST) to test the system&#8217;s hardware, checking to make sure that all of the system&#8217;s hardware components are working properly. Under normal circumstances, the POST will display an error message; however, if the BIOS detects an error before it can access the video card, or if there is a problem with the video card, it will produce a series of beeps, and the pattern of the beeps indicates what kind of problem the BIOS has detected.<span id="more-72"></span><br />
Because there are many brands of BIOS, there are no standard beep codes for every BIOS.</p>
<p>The two most-used brands are AMI (American Megatrends International) and Phoenix.</p>
<p>Below are listed the beep codes for AMI systems, and here are the beep codes for Phoenix systems.</p>
<p>AMI Beep Codes</p>
<p>Beep Code Meaning<br />
1 beep DRAM refresh failure. There is a problem in the system memory or the motherboard.<br />
2 beeps Memory parity error. The parity circuit is not working properly.<br />
3 beeps Base 64K RAM failure. There is a problem with the first 64K of system memory.<br />
4 beeps System timer not operational. There is problem with the timer(s) that control functions on the motherboard.<br />
5 beeps Processor failure. The system CPU has failed.<br />
6 beeps Gate A20/keyboard controller failure. The keyboard IC controller has failed, preventing gate A20 from switching the processor to protect mode.<br />
7 beeps Virtual mode exception error.<br />
8 beeps Video memory error. The BIOS cannot write to the frame buffer memory on the video card.<br />
9 beeps ROM checksum error. The BIOS ROM chip on the motherboard is likely faulty.<br />
10 beeps CMOS checksum error. Something on the motherboard is causing an error when trying to interact with the CMOS.<br />
11 beeps Bad cache memory. An error in the level 2 cache memory.<br />
1 long beep, 2 short Failure in the video system.<br />
1 long beep, 3 short A failure has been detected in memory above 64K.<br />
1 long beep, 8 short Display test failure.<br />
Continuous beeping A problem with the memory or video.<br />
BIOS Beep Codes</p>
<p>Phoenix Beep Codes</p>
<p>Phoenix uses sequences of beeps to indicate problems. The &#8220;-&#8221; between each number below indicates a pause between each beep sequence. For example, 1-2-3 indicates one beep, followed by a pause and two beeps, followed by a pause and three beeps. Phoenix version before 4.x use 3-beep codes, while Phoenix versions starting with 4.x use 4-beep codes. Click here for AMI BIOS beep codes.<br />
4-Beep Codes<br />
Beep Code Meaning<br />
1-1-1-3 Faulty CPU/motherboard. Verify real mode.<br />
1-1-2-1 Faulty CPU/motherboard.<br />
1-1-2-3 Faulty motherboard or one of its components.<br />
1-1-3-1 Faulty motherboard or one of its components. Initialize chipset registers with initial POST values.<br />
1-1-3-2 Faulty motherboard or one of its components.<br />
1-1-3-3 Faulty motherboard or one of its components. Initialize CPU registers.<br />
1-1-3-2<br />
1-1-3-3<br />
1-1-3-4 Failure in the first 64K of memory.<br />
1-1-4-1 Level 2 cache error.<br />
1-1-4-3 I/O port error.<br />
1-2-1-1 Power management error.<br />
1-2-1-2<br />
1-2-1-3 Faulty motherboard or one of its components.<br />
1-2-2-1 Keyboard controller failure.<br />
1-2-2-3 BIOS ROM error.<br />
1-2-3-1 System timer error.<br />
1-2-3-3 DMA error.<br />
1-2-4-1 IRQ controller error.<br />
1-3-1-1 DRAM refresh error.<br />
1-3-1-3 A20 gate failure.<br />
1-3-2-1 Faulty motherboard or one of its components.<br />
1-3-3-1 Extended memory error.<br />
1-3-3-3<br />
1-3-4-1<br />
1-3-4-3 Error in first 1MB of system memory.<br />
1-4-1-3<br />
1-4-2-4 CPU error.<br />
1-4-3-1<br />
2-1-4-1 BIOS ROM shadow error.<br />
1-4-3-2<br />
1-4-3-3 Level 2 cache error.<br />
1-4-4-1<br />
1-4-4-2<br />
2-1-1-1 Faulty motherboard or one of its components.<br />
2-1-1-3<br />
2-1-2-1 IRQ failure.<br />
2-1-2-3 BIOS ROM error.<br />
2-1-2-4<br />
2-1-3-2 I/O port failure.<br />
2-1-3-1<br />
2-1-3-3 Video system failure.<br />
2-1-1-3<br />
2-1-2-1 IRQ failure.<br />
2-1-2-3 BIOS ROM error.<br />
2-1-2-4 I/O port failure.<br />
2-1-4-3<br />
2-2-1-1 Video card failure.<br />
2-2-1-3<br />
2-2-2-1<br />
2-2-2-3 Keyboard controller failure.<br />
2-2-3-1 IRQ error.<br />
2-2-4-1 Error in first 1MB of system memory.<br />
2-3-1-1<br />
2-3-3-3 Extended memory failure.<br />
2-3-2-1 Faulty motherboard or one of its components.<br />
2-3-2-3<br />
2-3-3-1 Level 2 cache error.<br />
2-3-4-1<br />
2-3-4-3 Motherboard or video card failure.<br />
2-3-4-1<br />
2-3-4-3<br />
2-4-1-1 Motherboard or video card failure.<br />
2-4-1-3 Faulty motherboard or one of its components.<br />
2-4-2-1 RTC error.<br />
2-4-2-3 Keyboard controller error.<br />
2-4-4-1 IRQ error.<br />
3-1-1-1<br />
3-1-1-3<br />
3-1-2-1<br />
3-1-2-3 I/O port error.<br />
3-1-3-1<br />
3-1-3-3 Faulty motherboard or one of its components.<br />
3-1-4-1<br />
3-2-1-1<br />
3-2-1-2 Floppy drive or hard drive failure.<br />
3-2-1-3 Faulty motherboard or one of its components.<br />
3-2-2-1 Keyboard controller error.<br />
3-2-2-3<br />
3-2-3-1<br />
3-2-4-1 Faulty motherboard or one of its components.<br />
3-2-4-3 IRQ error.<br />
3-3-1-1 RTC error.<br />
3-3-1-3 Key lock error.<br />
3-3-3-3 Faulty motherboard or one of its components.<br />
3-3-3-3<br />
3-3-4-1<br />
3-3-4-3<br />
3-4-1-1<br />
3-4-1-3<br />
3-4-2-1<br />
3-4-2-3<br />
3-4-3-1<br />
3-4-4-1<br />
3-4-4-4 Faulty motherboard or one of its components.<br />
4-1-1-1 Floppy drive or hard drive failure.<br />
4-2-1-1<br />
4-2-1-3<br />
4-2-2-1 IRQ failure.<br />
4-2-2-3<br />
4-2-3-1<br />
4-2-3-3<br />
4-2-4-1 Faulty motherboard or one of its components.<br />
4-2-4-3 Keyboard controller error.<br />
4-3-1-3<br />
4-3-1-4<br />
4-3-2-1<br />
4-3-2-2<br />
4-3-3-1<br />
4-3-4-1<br />
4-3-4-3 Faulty motherboard or one of its components.<br />
4-3-3-2<br />
4-3-3-4 IRQ failure.<br />
4-3-3-3<br />
4-3-4-2 Floppy drive or hard drive failure.<br />
3-Beep Codes<br />
Beep Code Meaning<br />
1-1-2 Faulty CPU/motherboard.<br />
1-1-3 Faulty motherboard/CMOS read-write failure.<br />
1-1-4 Faulty BIOS/BIOS ROM checksum error.<br />
1-2-1 System timer not operational. There is a problem with the timer(s) that control functions on the motherboard.<br />
1-2-2<br />
1-2-3 Faulty motherboard/DMA failure.<br />
1-3-1 Memory refresh failure.<br />
1-3-2<br />
1-3-3<br />
1-3-4 Failure in the first 64K of memory.<br />
1-4-1 Address line failure.<br />
1-4-2 Parity RAM failure.<br />
1-4-3 Timer failure.<br />
1-4-4 NMI port failure.<br />
2-_-_ Any combination of beeps after 2 indicates a failure in the first 64K of memory.<br />
3-1-1 Master DMA failure.<br />
3-1-2 Slave DMA failure.<br />
3-1-3<br />
3-1-4 Interrupt controller failure.<br />
3-2-4 Keyboard controller failure.<br />
3-3-1<br />
3-3-2 CMOS error.<br />
3-3-4 Video card failure.<br />
3-4-1 Video card failure.<br />
4-2-1 Timer failure.<br />
4-2-2 CMOS shutdown failure.<br />
4-2-3 Gate A20 failure.<br />
4-2-4 Unexpected interrupt in protected mode.<br />
4-3-1 RAM test failure.<br />
4-3-3 Timer failure.<br />
4-3-4 Time of day clock failure.<br />
4-4-1 Serial port failure.<br />
4-4-2 Parallel port failure.<br />
4-4-3 Math coprocessor.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mumyls.com/2009/03/beep-code-manual/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

