IE6 history fixed thanx karen jo etc

  • Thread starter Thread starter mike ring
  • Start date Start date
M

mike ring

While trying to find a way to get history bac, wich a number of you tried
to help with, I found this: knowledgebase q193278.

And I had my email address as my username, though I don't know how
dreamweaver crashing did it; I certainly didn't.

So I changed my username to mike, and it didn't work.

But following up the idea, I looked for my email address everywhere, and it
turned up here

localmachine\system\current control set\control\current user

so I changed it to mike and presto! the history looked good, folders etc,
even the history of what I'd done when history wasn't working.

But I couldn't click on the links, and I saw the target URL had btinternet@
added to the front. So I went to beer and bed.

Bur next day after starting up that had fixed itself; so all is well.

I thought I'd better report back, in case someone else has dreamweaver, and
to thank you for all your help.

Now to reinstall Avant, ...or maybe the other one

mike
 
mike ring said:
While trying to find a way to get history bac, wich a number of you tried
to help with, I found this: knowledgebase q193278.
http://support.microsoft.com/support/kb/articles/q193/2/78.asp

And I had my email address as my username, though I don't know how
dreamweaver crashing did it; I certainly didn't.

So I changed my username to mike, and it didn't work.

But following up the idea, I looked for my email address everywhere, and it
turned up here

hkey_local_machine\system\current control set\control\current user

so I changed it to mike and presto! the history looked good, folders etc,
even the history of what I'd done when history wasn't working.
Click to expand...

Good news. And thanks for posting the outcome.

Regarding the mskb article, I did read it at the time I'd done a Google
on your msie history prob. The primary reason I didn't decide it to have
significant chance of being applicable, this was due to my thinking to
maybe take msft at its word, about the issue being fixed in versions of
MSIE later than 5.01. Silly me. Now I'll leave it the remaining task up
to you. Take a trip over to that top-posting nutfarm of the microsoft.*
windows groups, and engage those delightful MS-MVP's in a discussion on
MSIE weakness.... ;)
 
Regarding the mskb article, I did read it at the time I'd done a
Google on your msie history prob. The primary reason I didn't decide
it to have significant chance of being applicable, this was due to my
thinking to maybe take msft at its word, about the issue being fixed
in versions of MSIE later than 5.01. Silly me.
Click to expand...

Wasn't it lucky I didn't read down that far?
Now I'll leave it the remaining task up to you. Take a trip over to that
Click to expand...
top-posting nutfarm of the microsoft.* windows groups, and engage those
delightful MS-MVP's in a discussion on MSIE weakness.... ;)

Since when I posted my problem there I got a coat of complete ignoring, I
don't think I'll bother, I guess the question was too tough for them, or
they're trained like psychiatrists and can tune out pain

mike
 
Back
Top