Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem(s)?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
- Be sure your Mac is shut down.
- Press the power button.
- Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
- Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, you can’t boot in safe mode.
Test while in safe mode. Same problem(s)?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.
The results of my tests are not positive.
Step1, same results
Step2, unable to test because the wifi is not activated on my computer whle in safe mode. Unable to get a hard wire connection to the internet.
As an update, I notice a few minutes ago that Safari still asks me to save certain password. Don't know if it is related to the web site I visit. For example, I have two gmail accounts, the first account's password is save in keychain ut not the second one. As i visited gmail a few minutes ago, Safari asked me to save the password of the second gmail account. Going to http://www.l-camera-forum.com does not generate the "save password question" and my account on this site is brand new, so I was never asked to save the infos.
Same with Hotmail, no question .
Like Linc has already stated, my AT&T update for my Yahoo DSL account asks me to sign in each time I pull up the Home page. When I click on the "Keep me signed in" box, it does nothing. It just explains what keeping "signed in" means.
Also, Safari will not accept my home page as a default when choosen in preferences. Just keeps going to the AT&T page to let me sign in. Very annoying. But have too much data at this site to bother changing. I don't have this problem with FireFox.
When asked at the AT&T help site, they stated they had problems with Safari and were working on it. That was over a month ago. I think this was planned when AT&T/Yahoo updated their webb site which is when this problem first appeared.