No. 1 Story
ACCC clears Optus to scrap HFC network and use NBN instead
The ACCC has cleared, provisionally, the proposed deal between Optus and NBN Co under which Optus is to be paid around $800m to shut down its HFC network and transfer customers onto the NBN. read moreMore From
Safari 3.2.1: fix or no fix?
Stephen Withers
Wednesday, 26 November 2008 06:14
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.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.
You think you have a disaster recovery plan?
Think again. Most businesses only have PART of a DR plan - and this spells business disaster in the event of an IT disaster.
Download The Seven Sins of Disaster Recovery White Paper now and find out how you can prevent this happening to you.
