The halt setting won't prevent the POST codes from being output. Basically, you just changed it so that it won't halt if it can't perform a floppy disk seek. The system still needs RAM to get to the post codes, just not very much of it, and in very specific places. Changing the order of the DIMMS is sometimes enough to get a machine to post, depending on the memory configuration and where the failed chip is, but you would need something like Linux BADRAM support to get the initial BIOS screen. <div class="gmail_quote">On Sat, Feb 19, 2011 at 12:51 PM, Phil Smith <<a href="mailto:smithp67@yahoo.com">smithp67@yahoo.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Well I got my computer working again. I purchased another stick of ddr2 ram and put it in and it started right up. Previously, it would power on, but there was no post. I was skeptical that the ram chip would simply cause it to not post, no beeps or anything. I checked everything I could on the system and was ready to purchase a new bios chip if possible. Once it was operational again, I looked at the bios. In the bios there is the "Halt on" feature. Mine was set to halt on any error other than keyboard. I am assuming it was halted instead of going to post. So that was stupid. I set it now to "Halt on: No Errors" so if there are any in the future, it will just run until in can't anymore I guess. Weird that the ram chip would go, this is a very low power system, no overclocking or anything and a low power Core Duo cpu. Anyways, maybe this will help someone else. Phillip Smyth _______________________________________________ linux-user mailing list <a href="mailto:linux-user@egr.msu.edu">linux-user@egr.msu.edu</a> <a href="http://mailman.egr.msu.edu/mailman/listinfo/linux-user" target="_blank">http://mailman.egr.msu.edu/mailman/listinfo/linux-user</a> </blockquote></div>