Sharon... this is the same problem I've having but I'm using WXP and IE6,
not ME with IE 5. I don't know if this is the exact same MS page as I was
on last time - but this is pretty much the *SAME* problem. I can't locate
anything for XP but was having the SAME problem known with W-ME......

http://support.microsoft.com/?kbid=265244
http://support.microsoft.com/?kbid=298098

I will try and locate more tomorrow.

FS..........

On Mon, 15 Mar 2004 04:06:36 -0600, "~ FreeSpirit ~"
<(E-Mail Removed)> wrote:

>Sharon... this is the same problem I've having but I'm using WXP and IE6,
>not ME with IE 5. I don't know if this is the exact same MS page as I was
>on last time - but this is pretty much the *SAME* problem. I can't locate
>anything for XP but was having the SAME problem known with W-ME......
>
>http://support.microsoft.com/?kbid=265244
>http://support.microsoft.com/?kbid=298098
>
>I will try and locate more tomorrow.
>
>FS..........
>

As I mentioned in your thread located elsewhere in this group, mshtml
errors in XP are very rare. I don't know how/why you started to get
them but you did and they caused you a lot of trouble. One possibility
would be the browser was branded incorrectly by HP but I'd hate to
point fingers without facts.

By the way, SFC worked exactly as it was supposed to. If it does not
find anything wrong with your files, it doesn't bother you. If it had
found files that needed replacing, you would have seen that text on
the screen. If it finds a source for files that it can use to do the
replacing -- again, it wouldn't bother you.

When it can't find good copies to do the replacing, it prompts you for
a source. That prompt is what Michael was referring to when he said
"point it to."

Also... When you do a google search or any internet search, it pulls
up matches based on text. Those matches could be 6 years old or 6 days
old. If you don't watch the dates on the sources, it could get
confusing. A "known issue" could be mentioned in a year old document
and the relevant update has been available for 11 months. Both would
show up in the search results.

You have had us really perplexed with your problem because recently we
haven't seen mshtml issues with IE and XP in these newsgroups or in
our recent readings of technical documents.

Suggestion for you: Next time that you have a problem with Internet
Explorer (and I hope that's a long time away), visit the Internet
Explorer newsgroups on this server. That's where the IE experts hang
out and they are very helpful with issues particular to the browser.
You can still ask here - we'll do our best. But you definitely want to
check in with the IE folks when having an IE problem.


Sharon F
MS MVP - Windows XP

"Sharon F" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Mon, 15 Mar 2004 04:06:36 -0600, "~ FreeSpirit ~"
> <(E-Mail Removed)> wrote:
>
> >Sharon... this is the same problem I've having but I'm using WXP and IE6,
> >not ME with IE 5. I don't know if this is the exact same MS page as I
was
> >on last time - but this is pretty much the *SAME* problem. I can't
locate
> >anything for XP but was having the SAME problem known with W-ME......
> >
> >http://support.microsoft.com/?kbid=265244
> >http://support.microsoft.com/?kbid=298098
> >
> >I will try and locate more tomorrow.
> >
> >FS..........
> >
>
> As I mentioned in your thread located elsewhere in this group, mshtml
> errors in XP are very rare. I don't know how/why you started to get
> them but you did and they caused you a lot of trouble. One possibility
> would be the browser was branded incorrectly by HP but I'd hate to
> point fingers without facts.

## Well the fix/patch seems to have worked. We haven't had an error since.

> By the way, SFC worked exactly as it was supposed to. If it does not
> find anything wrong with your files, it doesn't bother you. If it had
> found files that needed replacing, you would have seen that text on
> the screen. If it finds a source for files that it can use to do the
> replacing -- again, it wouldn't bother you.

## Oh, ok! I thought there should be some window to say no errors were
found.

> When it can't find good copies to do the replacing, it prompts you for
> a source. That prompt is what Michael was referring to when he said
> "point it to."

## OHHHHH!! :-) Gotcha now! So we cannot use SFC as it is used in
W98SE to *replace* a DLL if we wanted to,... Or so it appears since there
is no "System File Checker" under Start/Programs/Acc'/Tools/Sys' Info/....
in XP. ===================
IN WIN98SE:
1.. Quit all running programs.
2.. Click Start, point to Programs, point to Accessories, point to System
Tools, and then click System Information.
3.. In Microsoft System Information, click System File Checker on the
Tools menu.
4.. In the System File Checker dialog box, click Extract one file from
installation disk.
5.. In the Specify the system file you would like to restore box, type
Mshtml.dll, and then click Start.
6.. In the Extract File dialog box, type drive:\Win98 in the Restore from
box, where drive is the drive letter of the CD-ROM or DVD-ROM drive that
contains your Windows 98 CD-ROM, and then click OK.

NOTE: If your computer has an Original Equipment Manufacturer (OEM)
installation of Windows 98, the Windows installation files may also be found
in the following folder: SNIP
====================
This is how we replaced the bad one on PC #2 with the good one from PC #1.
Evidently we can't do anything like this with XP.

> Also... When you do a google search or any internet search, it pulls
> up matches based on text. Those matches could be 6 years old or 6 days
> old. If you don't watch the dates on the sources, it could get
> confusing. A "known issue" could be mentioned in a year old document
> and the relevant update has been available for 11 months. Both would
> show up in the search results.

## Thanks! I didn't know this.

> You have had us really perplexed with your problem because recently we
> haven't seen mshtml issues with IE and XP in these newsgroups or in
> our recent readings of technical documents.

## I got that impression. Sorry for the confusion. My fault.

> Suggestion for you: Next time that you have a problem with Internet
> Explorer (and I hope that's a long time away), visit the Internet
> Explorer newsgroups on this server. That's where the IE experts hang
> out and they are very helpful with issues particular to the browser.
> You can still ask here - we'll do our best. But you definitely want to
> check in with the IE folks when having an IE problem.

## Again - thank you Sharon. I'll definitely check in there.

> Sharon F
> MS MVP - Windows XP

FS.......

On Mon, 15 Mar 2004 17:25:47 -0600, "~ FreeSpirit ~"
<(E-Mail Removed)> wrote:

>## Well the fix/patch seems to have worked. We haven't had an error since.

Good! I hope it stays fixed for you.

>## OHHHHH!! :-) Gotcha now! So we cannot use SFC as it is used in
>W98SE to *replace* a DLL if we wanted to,...

This function is moved to MSCONFIG. The Expand button does relatively
the same thing. For future reference, the procedure is explained in
this article:

Description and Explanation of a Cabinet File
http://support.microsoft.com/default...&Product=winxp

>## I got that impression. Sorry for the confusion. My fault.

No problem! The important thing is that this error is no longer
troubling you.

Take care,

--
Sharon F
MS MVP - Windows XP