OK Jonah, I?ll tell you a story (it?s saturday and we can relax in the weekend).
You?re talking about an old IE plague. If you?d search for this one in google you?ll find around 300 000 hits. Under CNet (ZDNet) Forums probable there were several thousands.
Now, there is a standard procedure for temporarily correct this. This standard procedure was promoted by several regular posters (and up) and presented as X?s fix, later X said that it was Y?s fix, Y?s fix was probable Z?s fix and so on. So what?s the deal with this ?
Is the standard procedure:
- Working ? Yes, it is because it?s easy to test it.
- Efficient ? Nope, it?s not because sooner or later this will happen again.
So, the next step it?s to find out a better approach for this. Here there are several better solutions:
1. Some kibitz will tell that you shouldn?t use IE, e.g. "No woman, No cry" philosophy.
2. Other insiders that know the kitchen, can find a registry solution (I don?t know if this solution was ever posted but never mind).
3. Others will suggest using a third party utility that will keep IE maximized.
However, there is one which is the best. It was posted here soon after Service Pack 2 release, so I?ll let all the kibitz finding it.
Finally what?s this all talking about ? Quite simple, it?s about: "Giving the credit to whom it belongs".
Trying to unweave, unwind, unravel
And piece together the past and the future,
T. S. Eliot