Ah, yes. The checksum might be on the CMOS NVRAM settings rather than the BIOS executable code. If the BIOS considers the settings invalid (by comparing to some stored checksum - also stored in the CMOS NVRAM) then it might failing back to what you are seeing. This can be confirmed by defaulting the BIOS settings (making sure you have recorded any system specific settings that are important, such as drive geometry) and rebooting. If you keep system power on between reboots and the problem does not reoccur, yet does have problems when your system gets powered down (and the CMOS NVRAM needs to rely on the battery) then it could well be your battery is at the end of its useful life. (Usually the first sign is the system clock no longer operates when powered down).
Regards, Martin [email protected] On Mon, Aug 30, 2010 at 8:59 AM, Jake Anderson <[email protected]>wrote: > On 29/08/10 18:48, Jonathan wrote: > >> BTW, just realised I typed the motherboard code wrong, its actually: >> GA-7VT600 1394 >> >> cheers >> >> Jon >> >> > Just checking, its not the CMOS battery gone flat causing your problems is > it? > It sounds similar in symptoms. > > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
