R C-R said: "Can you explain more about how & why you used two different system discs with this Mac, each with a different version of OS X on it?"
That is exactly what I explained... and it is clear that you got it, too, but here it is again:
1) I first used the disc labelled "iMac Installation Disk" that came with the machine because I wanted to install the full iLife suite that came with the system originally... and this leads to a 10.4 install (perhaps the 10.4.10 to which you refer, but that's beside the point... though I should add that I used this original system disk to run all the hardware tests that come with it...).
2) I then upgraded using the 10.5 disk that came with the machine simply because I think the machine came with 10.5 already installed... This was followed, by the same logic, by the 10.5.8 Combo Upgrade...
3) I then upgraded to 10.6 using the Snow Leopard disk that I bought after it had became available and Apple stated that my iMac model was compatible and that it would benefit from the upgrade. I did not do all the intermediate upgrades but rather tried the 10.6.3 v1.1 Combo Upgrade directly. I presumed, at this point, that the machine was completely upgraded or that the Software Update monitor would identify further steps (such as the somewhat elusive 1.6.3.1 Security Update that occurred sometime in April after 10.6.3 went online but before v1.1 became available for manual download...).
The result, of course, is that this is where the "freezing" problem occurs... and not intermittently. It occurs with or without attached peripherals (though I never tried without keyboard and mouse). It occurs "randomly" in the sense that it appears at some point between the boot phase, during login, or within the first five to ten minutes of operations, and it presents in different forms (image frozen with mouse sprite still active, image freezes completely, or display goes grey... and in all cases the display anomalies (fonts out of whack, bad line traces, etc.) appear almost immediately before the "freezing up".
As for firmware and the rest, of course I checked all that... but more importantly, so did the people at the Apple Store when I took the machine there about one month ago!
R C-R, I really don't want to challenge your good faith on this matter again but your attitude seems to be that the problem absolutely must be elsewhere than in the 10.6.3 upgrade "simply" because everyone using it has not seen the phenomena. I have friends who have told me directly that they are not having difficulties, but they don't have the same model as mine... but that does not explain the problems that so many of us have described in this forum (and that, of course, is only a small subset of users...)
Your explanation is a rather patronizing repetition of everything that I had already tried and had described when, on the other hand, you ignored my basic question... so here it is again:
1) In previous posts, you discussed two different "versions" of the 10.6.3 v1.1 Combo Update with a "Small Delta" between them, and this is where you lost me. I was simply asking for an explanation with, perhaps, a "simple" alternative recipe that you would endorse (and if the problems reappeared, you would perhaps stop suggesting that we are imagining things or that it must be our hardware...).
2) I would agree that there might be a sequence to upgrade the machine that would skip some of the intermediate steps that I presented... but shouldn't Apple have proposed them directly either at the Apple Store or via the Apple Expert on the telephone of in response to my bug report if any of these options were viable. My goal, in any event, is to establish a reinstallation procedure that I will allow me to install all the software that came with the machine (meaning iLife... and that's on the 10.4.10 installation disk) and that I could reliably repeat in the future...
3) There is one last possibility that I would offer: maybe the 10.6.3 upgrade is no longer compatible with some specific stock systems that were stated to be compatible with 10.6 when it was released. I hope you would agree that this is Apple's problem to fix...
Finally, I must be frank and simply suggest that your mental gymnastics to find fault with everyone else's analysis is tiresome (your last response to "tdowney" being a perfect example). I know a bit about this phenomena as I spent too much of my career chasing down operating system bugs on Unix systems in mission critical operations. My "record", if I may, was 18 months to convince a major manufacturer that a memory leak existed in the networking stack that was demonstrable as a kernel bug... and they never actually admitted it, of course, even though the tests we supplied at the beginning of that experience were as simple as five lines of C code! They simply released a new version of the operating system and told all users to upgrade... and happily for us, this solved our problem.
Just to be clear, I went to Mac OS X for many reasons, but one was that I did not want to have to deal with this sort of obfuscation or disinterest any more. I have been very pleased with the stability of the Macs I've purchased from them up to now and believe that they can still redeem themselves (it has, after all, only been about a month... and this problem does seem to be tough to tie down).
So I'm still willing to try something different that you might wish to suggest as long as it fulfills my goal of installing the software that came with the machine and then updating to the latest version of the operating system in a manner that I can repeat in the future (especially once my Apple Care contract runs out... which for your information is in September 2010)...
... but please do not write another long discursive "lesson" (and don't bother dissecting my logic for some small inconsistency... unless it can lead to a proposal of a solution).