Hallo
Wie siehts allgemein aus, irgendwelche neuen Infos? @MacKimble
Wie ist der aktuelle Stand der Reparatur?
Weitere betroffene User meldeten auf diversen Websites, dass sie auch das Einfrierproblem haben.
jaumeb schrieb am 10.6.05 bei OSNEWS:
My PM G5 SP 1.8 (late 2004) is facing this problem, too.
Since April 29 2005 i can't work with my Mac !!!
mike schrieb am 10.6.05 bei OSNEWS:
My Mac is not usable for video editing anymore. I reported the bug to Apple and they were not able to reproduce it on there computers. This is the response I got:
"We have now had the same machine running for over 24 hours and we are not locking up at all. Can you provide me with more information on what content that was looping or playing for that long, and if possible can we get a copy of it for testing?"
I sent them some more information but never heard anything from them again...I think that's really bad for a company like Apple. The PM was my first Mac and as it looks now, it will also be my last.
Troy schrieb am 11.6.05 bei Apple Discussions:
I can verify that Quicktime freezes my 10.4.1 system on a Single 1.8Ghz PowerMac.
I have not let it sit for long enough to find out what is in the logs. The system is unresponsive and requires a "hard" power cycle to get the system back.
Redstar schrieb am 14.6.05 bei g5support:
Well, so far this new computer has had about 7 freezes (all requiring me to hold the power button until the computer shuts down) in little over a month. Three of which were when I was going into the iTunes full screen visualizer, and the other 4 were when I was downloading/watching Quicktime movie files (not full screen). Both programs are up-to-date, as is my OS.
This computer (SP 1.8 G5, bought in early May 2005) came with Panther 10.3.7 installed and I used the "Update" option to install Tiger.
I run hardware scans with TechTool Deluxe (it came on my Applecare CD) and with the hardware tester.
Since my most recent freeze, which occurred about 20 minutes ago, I ran fsck, repaired permissions, and am currently running a hardware test. So far, nothing is wrong.
What should I do?