Prev: Max size limit on MicroDIMM memory modules?
Next: Missing system32\drivers\ntfs.sys
From: Trent on 28 Nov 2006 08:13
On Fri, 24 Nov 2006 15:32:40 +1100 Franc Zabkar
<fzabkar(a)iinternode.on.net> wrote in Message id:
<i8scm2l4j28ebh46gbroh87uo452q090v8(a)4ax.com>:

>In your original post you stated that "the beep codes are produced by
>the keyboard MCU and that will beep a 'CPU not present' if it is not=20
>contacted by the CPU after a certain time".
>
>After pondering this statement, it occurs to me that it cannot
>possibly be correct. If the keyboard MCU "is not contacted by the CPU
>after a certain time", then it has no way of distinguishing between
>any of several possible causes including "CPU not present", "CPU
>dead", "BIOS chip missing/corrupt", or "bad flash".

Or, as I said to Tony, you could pry every other chip off the motherboard
and get the same result. IOW, completely meaningless.
From: Mark Conrad on 10 Dec 2006 23:02
In article <d6onl29ud43g58o3ol77plid32c3ckkt3t(a)4ax.com>,
<"nobody(a)nowhere.net"> wrote:

> Smell the power supply. If it smells like something is burned,
> probably it is.

That figures <g>
First  |  Prev  | 
Pages: 1 2 3 4 5 6 7 8 9
Prev: Max size limit on MicroDIMM memory modules?
Next: Missing system32\drivers\ntfs.sys