New
#11
Well, at this time I'm not having the problem so I have nothing to compare against using the troubleshooting technique in the link you provided. As I mentioned above in my first post usually a restart fixes the problem and I did restart my computer a couple days ago just before opening this topic on SF which has, at least temporarily, solved the problem to date. The next time this happens I'll try the troubleshooting technique you suggest.
Also, before the restart mentioned above I did eliminate a few programs that wanted to run at start-up so it's possible one of these was the culprit. Time may tell, if I don't have this problem recur I will know it's one of two programs I eliminated from running at start-up.
Thanks very much for your help, I learned something. I'll leave it up to you to close this topic and mark it as solved or not.