Follow the Australian Telecommunications scene NEWSLETTER- FREE TRIAL
 |
 Stephen Withers turns his gaze on the world of Apple, with
detours into other aspects of IT and communications as they catch his
attention. |
Technology news and Jobs 
Our Blogs Core Dump Safari 3.2.1: fix or no fix?
Our Blogs Core Dump Safari 3.2.1: fix or no fix? | Safari 3.2.1: fix or no fix? |
|
| Core Dump - Apple and anything else | |
| by Stephen Withers | |
| Wednesday, 26 November 2008 | |
|
Page 2 of 2 Trouble is, these add-ons use Input Managers to alter the way Safari works. Unlike a conventional plug-in scheme, the Input Manager architecture actually changes the code executed by an application.Featured Whitepaper
5 Best Practices for Smartphone Support
Other users (me included) have found that Safari 3.2 and 3.2.1 seem to work just fine, that is at least as well as version 3.1 did. The quick arrival of 3.2.1 means there were obviously specific problems with Safari 3.2 that have now been addressed, but what if the issue you were experiencing with 3.2 persists? If 3.2.1 doesn't do the trick for you, I'd suggest that the problem may not be in Safari itself. If removing any and all Input Managers, and running Safari from an account that you use only for troubleshooting (this rules out corrupted preferences and problems with other user-specific files) fails, it's quite possible that another system component has become corrupted and that's what is causing Safari to fail. In that case, the answer may be to reapply the appropriate combo update for the operating system (eg, Mac OS X 10.5.5) and any subsequent security updates. If you haven't yet downloaded Safari 3.2.1, you can do so via Software Update (Apple Software Update on Windows), or from Apple Support Downloads. Separate versions are available for Mac OS X 10.5 Leopard, 10.4 Tiger, and Windows XP/Vista. |
|
Tags
| < Next story in category | Previous story in the category > |
|---|
