>> Used to be that newsgroups were a good resource for figuring out
>> problems.
>They still are - especially if one uses groups.google.com to search them.
I did, and didn't get any usable answers. Where I did find something
useful was on a web site, I think it was xlr8yourmac.com. But now that
I've come back and posted to the newsgroup, it should be easier for the
next newsgroup searcher to find.
>> I'm kinda disappointed about the lack of meaningful
>> response here, and having to struggle with a week of hours-a-day
>> internet searching and an irate wife...
>
>So how much have you contributed to the newsgroups lately?
Fair enough, not much lately. Back when I was younger and had more
time on my hands, much more. On the other hand, I tend to keep my
mouth shut when I'm not totally sure of what I'm saying...
>To your great credit, you did come back and share the solution to
>your particular problem.
Thanks.
>But if you don't participate on a regular basis yourself, you
>really don't have grounds to complain about the lack of assistance
>by others.
Well, it's hard to participate in a meaningful way when you're spread
really thin. I have many interests -- Macs, NetBSD, SGI, helicopters,
classic cars (Chevelle and Pontiac, mostly); then there's the family,
house maintenance, yard work... There's just not enough time in the
day to do justice to all of them, so the more important ones get
attention first, the rest get a share of the little time left.
>Unplugging USB devices is a pretty standard debugging technique for
>OSX - that and removing/swapping out 3rd party RAM are the two bog-
>standard techniques for resolving OS X crashes.
Considering that I've had Macs from MacOS 4 through 10.4.4 and the
only problems I've had in that time is the occasional disk failure
and a SCSI problem or two, I hope you'll excuse me for not knowing
that. And no, I've not seen that mentioned anywhere in the many
hours that I've spent reading newsgroups and websites.
>Finally, if you expect an answer that will help you resolve "my G3
>periodically pauses", then don't post it under a subject line like
>"forcing g3 firmware update?". Those of us who have no idea how
>to force a G3 firmware update, and no particular likelyhood of
>ever needing to do so ourselves, are unlikely to bother reading
>such a posting.
The problem with the pausing didn't show up until the exact point
in time when I applied the update and installed the accellerator.
Why would I not think they were related?
>Convincing 95% of your potential readers to skip the entire thread
>is not very conducive to finding an answer. And, as it turns out,
>the firmware had _nothing_ to do with your actual problem, AFAICT.
That's right, it had nothing to do with the firmware. But that was
not obvious when I asked the question. If the pausing had started
some other time, it would have been a more obvious thing to ask
about.
>The Usenet Mac groups are still a great resource - for those who
>know how to compose a subject line... :-)
I do. I was looking to eliminate what appeared at the time to be
the most likely source of the problem (given the timing of it).
And that is what the subject line was aimed at. It wasn't until
several days later and many email exchanges with the Sonnet
technician that my firmware was confirmed to be back to original
state and the pausing still happening that it became apparent to
me that the problem lay elsewhere. And you notice that I did
manage to find the answer to that on my own.
~Steve