On 7/3/08 1:20 PM, in article
jollyroger-F8F79A.13203303072008@[EMAIL PROTECTED]
"Jolly Roger"
<jollyroger@[EMAIL PROTECTED]
> wrote:
> In article <C4926330.AB35%ghost_topper@[EMAIL PROTECTED]
>,
> George Kerby <ghost_topper@[EMAIL PROTECTED]
> wrote:
>
>> On 7/3/08 9:32 AM, in article
>> jollyroger-15B900.09322503072008@[EMAIL PROTECTED]
"Jolly Roger"
>> <jollyroger@[EMAIL PROTECTED]
> wrote:
>>
>>> In article <C4918A7A.AAC0%ghost_topper@[EMAIL PROTECTED]
>,
>>> George Kerby <ghost_topper@[EMAIL PROTECTED]
> wrote:
>>>
>>>> The cursor freezes. The clock stops. The fans start doing high
excessive
>>>> RPM. The computer becomes a "brick" - until I hold down the start
button
>>>> for
>>>> several seconds for the reboot.
>>>
>>> That's a hardware freeze. Bad RAM chips are the likeliest culprit,
but
>>> there are others as well.
>>
>> That was my first suspicion. I tried running MemTest, but after a 1/2
day, I
>> quit testing. At the time I stopped, I needed the computer for scanning
some
>> pages. It is the only box in the place that is hooked up to the
scanner.
>
> MemTest won't test all of RAM, because some RAM is used (and unavailable
> to memtest) to run the software itself. The "remove half, rinse, lather,
> repeat" method is the only really reliable way to find bad RAM no matter
> where it is.
>
>> But, if it truly a RAM thing, why does the CCC backup I made of 10.4 OS
just
>> before I erased and reformatted the internal main drive not have any
problem
>> running the computer via external FireWire400? I may be wrong, but I
just
>> cannot see why it would run for several days and left on all night
under
>> Tiger without a freeze, while it seizes up moments after Leopard starts
up,
>> if it was faulty/loose RAM. I mean both drives access the same chips.
What
>> might be some other culprits that you mention above that I might try to
>> examine?
>
> It's certainly possible the problem is not with RAM, but with the
> internal hard drive, or some other component.
>
> You might consider booting into Leopard in single user mode, and doing a
> bunch of repeated fsck runs, to see if you can find anything wrong with
> the hard drive.
I have done a disk utility run from The Leopard CD on the internal drive
previously, but will give it a go.
Is it "Command + s" to get the Single User up?
And repeat the prompt (without brackets) <fsck -y> (with space between the
"k" and the "-" until it encounters no problem and re****ts the drive is
OK?
What if it doesn't find anything wrong, or cannot fix it? Does <exit> get
me
out?
|
