well, that's exactly my point: the RAM is from the same manufacturer, has
exactly the same electrical characteristics than the 256 modules that came
with my PB G4, therefore if it works on one machine (as it does) and not on
the other there's something wrong with the machine and/or OS design.
Maki
Curious . . was the 512 module recommended by the manufacturer for
both machines?
dklj
On Apr 12, 2005, at 11:39 AM, Francesco sciacca wrote:
thanks for all the suggestions. After way too long down time, it turns
out
that the 512 RAM module I has added appears to be the culprit. Disk
turned
ou
thanks for all the suggestions. After way too long down time, it turns out
that the 512 RAM module I has added appears to be the culprit. Disk turned
out to be fine, checked with SMARTD. Replacing the original 256 MB module
restored stability.
I'm puzzled as the 512 module is a 512mb PC133 SO-DIM
I had a similar experience on an older PB about a month ago. Stability
was good before I increased the RAM. Very poor stability with the new
RAM. Stability returned with the original chips. As it turned out the
backward compatibility as shown on the packaging was wrong.
dklj
On Apr 8, 2005,
On 08/04/05 12:40, "Francesco sciacca" <[EMAIL PROTECTED]> wrote:
[snip!]
> Given the symptoms reported above, what could be my next best bet move
> before I head directionless at guessing fixes, maybe creating more damage? I
> thought first that the file system was corrupted, but in that case a cl
> Well, for one thing, disk problems are never good. So, you are saying that
> while copying the installers to another machine, it crashed? What crashed
> exactly? The Finder? When talking about installers, I'm assuming you mean
> "packages" (.pkg)?
yes, there was a kernel panic while copying the
Check system profiler or "about this Mac" and see if all your ram shows up.
AlBooks are starting to show up with lower ram slot failures. Other
possibility is the hard drive is failing.
John
>>> It sounds like a fairly complex issue, so does anyone have suggestions
>> about
>>> where to look (cr
On 07/04/05 11:02, "Francesco sciacca" <[EMAIL PROTECTED]> wrote:
>>> It sounds like a fairly complex issue, so does anyone have suggestions
>> about
>>> where to look (cryptic logs, etc) or what to do to toubleshoot this? I
>> would
>>> not really think it's the RAM the issue here... I mean, OS X
> > It sounds like a fairly complex issue, so does anyone have suggestions
> about
> > where to look (cryptic logs, etc) or what to do to toubleshoot this? I
> would
> > not really think it's the RAM the issue here... I mean, OS X installed
> fine
> > eventually... or?
>
> Have you checked the cra
On 07/04/05 08:50, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I've installed this yesterday and it seemingly ended up jumbling my 1GHz
> powerbook OS 10.3.8. The installer reported a failure, while other installs
> initiated with "software update" went ahead fine (one of them after the
> sec
I've installed this yesterday and it seemingly ended up jumbling my 1GHz
powerbook OS 10.3.8. The installer reported a failure, while other installs
initiated with "software update" went ahead fine (one of them after the
security update, according to the logs).
I've seen no reports of complaints a
11 matches
Mail list logo