B
Bill Kearney
A hearty thanks goes out to Ramesh for this suggestion to use regmon. He
suggested using it for an unrelated problem (desktop .url shortcuts) and that
put me onto the right trail.
I loaded up regmon and ran it, first while using the problem account. Then
again while using the working account. I pulled the logs into excel and did
some formatting and comparisons.
I found differences in how the HKCU calls for the working account were different
for the failing one. I did shortcut the solution a little bit (deleting wildly
out of frustration) but the I think the fix came when I deleted the values in
HKCU:Software\Microsoft\Internet Explorer\International
The problem account had a number of values there that the working account did
not. I deleted those values and, voila, now it works.
I should also point out Tim K's early suggestion on checking encoding. He
raised the warning flag that it might be encoding related and, sure enough, it
was. Thanks also go out to PA Bear and Jim Pickering for their suggestions.
Thanks everyone, hopefully this will propogate into the search engines and help
someone else.
OE, OE6, IE, IE6 messages displaying raw HTML source instead of plain text.
As to /how/ this problem developed is anyone's guess. I've loaded nothing
lately that I expected to be fiddling in these keys. Nor have I been mucking
about with IE's i18n settings. Go figure. Perhaps it was something related to
a recent Automatic Update.
What this DOES tell me is I need to get this profile's settings out of this
particular profile. I've wasted two days untangling this bastard but that's a
far cry from the hassles I'd have had setting everything back up again. So what
do folks suggest for 'more effective' profile management? Just how 'safely' can
one go from using a local profile to one that's domain based? As in, can I move
this one up to the domain controller without a lot of anguish?
Thanks again,
-Bill Kearney
-Bill Kearney
suggested using it for an unrelated problem (desktop .url shortcuts) and that
put me onto the right trail.
I loaded up regmon and ran it, first while using the problem account. Then
again while using the working account. I pulled the logs into excel and did
some formatting and comparisons.
I found differences in how the HKCU calls for the working account were different
for the failing one. I did shortcut the solution a little bit (deleting wildly
out of frustration) but the I think the fix came when I deleted the values in
HKCU:Software\Microsoft\Internet Explorer\International
The problem account had a number of values there that the working account did
not. I deleted those values and, voila, now it works.
I should also point out Tim K's early suggestion on checking encoding. He
raised the warning flag that it might be encoding related and, sure enough, it
was. Thanks also go out to PA Bear and Jim Pickering for their suggestions.
Thanks everyone, hopefully this will propogate into the search engines and help
someone else.
OE, OE6, IE, IE6 messages displaying raw HTML source instead of plain text.
As to /how/ this problem developed is anyone's guess. I've loaded nothing
lately that I expected to be fiddling in these keys. Nor have I been mucking
about with IE's i18n settings. Go figure. Perhaps it was something related to
a recent Automatic Update.
What this DOES tell me is I need to get this profile's settings out of this
particular profile. I've wasted two days untangling this bastard but that's a
far cry from the hassles I'd have had setting everything back up again. So what
do folks suggest for 'more effective' profile management? Just how 'safely' can
one go from using a local profile to one that's domain based? As in, can I move
this one up to the domain controller without a lot of anguish?
Thanks again,
-Bill Kearney
-Bill Kearney