drh64 wrote:
Have you taken this up with Apple?
I started my company in July 07. I purchased two IMacs (20"/24"EX)and one MacBook. I swear the 20" runs more stable than the 24" model. The 24" had the hard drive replaced after 4 weeks. It also has a tendency to simply crash and drop out of an app at any moment. It happens in about any application.
Taking it up with Apple is a good idea, yet, it is difficult to repeat the problem because it is so unpredictable.
Hi Dan,
You don't need to reproduce the problems. go to Application > Utilities > Console( Put it in your Doc while your there.) Click on the "Logs" button > and expand ~/Library/Logs and expand crash reporter. Read it and weep. I would like to see any ArchiCAD reports but they would be too long to copy and paste here.
You have a "Skookum" graphics card that makes the "Pro" machines like mine and many others akin to an etch a sketch with a cord. Is the 20" equipped w/ the same card? When they replaced the HDD was it an exact swap or did you get a larger/smaller slower/faster HDD? Do you know what brand HDD it was that failed? Did it start with a long progress balls in the finder and other apps? Very slow graphical response to your input? Did it get to the point of click, click, click, on start up?
I would like to continua a dialogue with you and feel that based upon Karl's statement about "enough truth with misinformation" you would understand the difference between misinformation and outdated information as seems to be the case here although in this particular topic I don't really see where anyone else gave any information other than they've never seen these symptoms and would not have any first hand knowledge to be able to help you. At this point I have very little if any respect for Ralph and do not feel the need to play to his superiority complex as he does not seem to provide much in useful information and if someone were to go back and read many of his post there is no reasoning to much of what he says either along with contradictory statements scattered about this is not an AC problem and is an OS problem.
What you have indicated about your experience should lend at least a little credibility of what I am saying at least to you. 4 weeks and a HDD fails? I do not rely on third party info too much except to see what issues people are having and to see if user error, outdated, underpowered hardware, is the cause, is there an actual solution or if one has to resort to a work around. A Bug in SW like AC is not a security issue though, it can be a major setback, but an error in the OS leads to hardware failures and sometimes even data loss.
So if you would like to continue this in a useful way instead of accepting what the others are saying and that iTunes has nothing to do with it please do so by posting the answers to the questions above as well as the following.
If the 20" has a different graphics card can you please post that as you did the last?
Do you use Bootcamp, and if you do does it indicate 256 MB VRAM or 512 MB VRAM for you GC spec?
As a side note. If you had read my recommendation about including a G4 into an office, for you I would make a new recommendation based upon new information. Everything my machine does (or actualy doesn't do) relies on software emulations. Apple calls these virtual machines. According to ATI and unless Apple has disable these functions you have hardware support for MPEG-2 MPEG-4 H,264 and a list of legacy and modern encoders and decoders. This may even be the reason why you have issues with iTunes as it has it's own SW to provide support for these technologies for the rest of us. Many encoders are only available with their pro software. One thing that I do find odd though is that ATI indicates 1920 x 1200 as the maximum physical display, unless that is for an externally connected one.
Another thing to ponder. Being that ATI's R&D appears to have engineered the technologies that even NVidea uses to keep their portable chip-sets cool if heat is the issue why? One of the reason could be misfiring timers. and the timers could be failing due to an error in a time-formatter somewhere.
Thanks
