Update on Safari 3.2 Fixes

Question

http://www.macfixit.com/article.php?story=2008111400261368

Answer 1

Issues with InputManagers like these may arise from installing bad Dashboard Widgets that haven't been updated, Netflix Freak, which uses Webfoundation, and has terminated its continued updating, or using specialty web browser addons such as PithHelmet without keeping them up to date, or Speed Download, or any other application that addresses that system of InputManagers and Webfoundation. Some programmers attempt to address InputManagers and Webfoundation as if 10.4.11 was still current, only to not address the differences in 10.5. If you look at http://www.haxies.com/ many of their InputManager based programs have stopped their support at 10.4.11, since they are still after a year learning how to deal with the new InputManager system.
The issue here is that some people desire more customization with their system than the system can handle with stability. Granted sometimes it is nice to have new window designs. I suggest that until you isolate what is causing issues with your web browser, to try a different web browser*:
http://www.macmaps.com/browser.html
That would not make sense that the Bugreporter doesn't work with Apple's web browser unless, there is some intervening factor causing instability for the system. It may also indicate that something was not prepared right when you updated*:
http://www.macmaps.com/upgradefaq.html
Regardless, this behavior is not normal, in spite of others appearing to have these same problems. Many people try to add addons to their systems, without regard for the fact that when they update their system, many third party addons never do get tested with new operating system updates. There are more Apple compatible software titles than can be tested jointly in the age of the universe. Apple issues Developer guidelines to avoid such issues on http://developer.apple.com/
If developers fail to test and make sure those guidelines are followed, it is hard for Apple to do anything about it. So my suggestion is to simplify your system and find out if it works as a bare bones system. Add bells and whistles sparingly, and only on backed up systems*:
http://www.macmaps.com/backup.html
So that if you find that after updating the bells and whistles don't work, you can remove them by restoring your backup.
Edit:
Since you seem to have it on "clean" drives, and it is assuming that you actually erased the hard drive, installed the operating system, and then the Safari update, it may indicate you have a hardware problem with your computer.
Further reading your profile, it looks like you have an upgrade CPU. I wonder if the firmware for that CPU doesn't support the prebinding code as it may have changed.
- * Links to my pages may give me compensation.
Message was edited by: a brody
Message was edited by: a brody