View Full Version : .dll replacement
Michael
December 5th 03, 12:16 AM
Re: Microsoft Picture It! Publishing 2001
Norton Win Doctor advises that the above named program is
missing mhputilu.dll
I have downloaded this file in archive form from an online
site, and saved it to my desktop. Can you please tell me,
step-by-step, how to place this file?
OS : Windows XP Home
Thank you.
Walter Clayton
December 5th 03, 12:16 AM
First, dump Win Doctor and the rest of Norton suite. You can keep Norton AV,
but that's not a product I recommend people keep either. That alone will do
wonders for your system. Also, delete the file you just downloaded. No
telling where it came from nor what kind of surprise package it may be
bearing.
Follow the instructions here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274461
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"Michael" > wrote in message
...
> Re: Microsoft Picture It! Publishing 2001
>
> Norton Win Doctor advises that the above named program is
> missing mhputilu.dll
>
> I have downloaded this file in archive form from an online
> site, and saved it to my desktop. Can you please tell me,
> step-by-step, how to place this file?
>
> OS : Windows XP Home
>
>
>
> Thank you.
JBM
December 5th 03, 12:16 AM
Walter -
I've been happy (or satisfied, at least) with Norton AV - what do you
recommend and why?
Jonny May
"Walter Clayton" > wrote in message
...
> First, dump Win Doctor and the rest of Norton suite. You can keep Norton
AV,
> but that's not a product I recommend people keep either. That alone will
do
> wonders for your system. Also, delete the file you just downloaded. No
> telling where it came from nor what kind of surprise package it may be
> bearing.
>
> Follow the instructions here:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274461
>
> --
> Walter Clayton - MS MVP(WinXP)
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone
> Any technology distinguishable from magic is insufficiently advanced.
> http://www.dts-l.org
> http://support.microsoft.com/servicedesks/fileversion/default.asp
>
>
> "Michael" > wrote in message
> ...
> > Re: Microsoft Picture It! Publishing 2001
> >
> > Norton Win Doctor advises that the above named program is
> > missing mhputilu.dll
> >
> > I have downloaded this file in archive form from an online
> > site, and saved it to my desktop. Can you please tell me,
> > step-by-step, how to place this file?
> >
> > OS : Windows XP Home
> >
> >
> >
> > Thank you.
>
>
Wislu Plethora
December 5th 03, 12:16 AM
>-----Original Message-----
>First, dump Win Doctor and the rest of Norton suite. You
can keep Norton AV,
>but that's not a product I recommend people keep either.
That alone will do
>wonders for your system. Also, delete the file you just
downloaded. No
>telling where it came from nor what kind of surprise
package it may be
>bearing.
>
>Follow the instructions here:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;274461
>
>--
>Walter Clayton - MS MVP(WinXP)
>Associate Expert
>http://www.microsoft.com/windowsxp/expertzone
>Any technology distinguishable from magic is
insufficiently advanced.
>http://www.dts-l.org
>http://support.microsoft.com/servicedesks/fileversion/defa
ult.asp
>
This is a misleading and irresponsible load of crap. There
are legions of satisfied users of the Norton Suite, and I
count myself among them. Note that the page referred to
above very clearly states that the problem is with the
MS products referred to, not the Symantec products. What
does MS offer as a "solution"? Stop using the Norton
products.
I understand that unabashed sycophancy is a requirement for
"achieving" and maintaining Microsoft Junior Fire Chief
(MVP) status, but to malign a creditable and highly
successful third-party product--clearly without knowing
what you're talking about--is pretty low.
Walter Clayton
December 5th 03, 12:16 AM
Don't take my word for it. ;-)
Uninstall all the Norton utilities and see if your machine doesn't behave
better. As for this specific issue, notice that it's caused by Norton and
one of the reference products has specifically been dropped by Norton when
they finally realized the product was incapable of doing what was claimed.
As well it seems you didn't read far enough. To quote
<Quoute>
MORE INFORMATION
It is found that the programs listed at the beginning of this article will
run smoother if Norton CrashGuard, Norton WinDoctor or Dr. Watson are turned
off prior to running the programs listed at the beginning of this article.
</quote>
There is no need and never has been a need for a 3rd party product to
"correct" system problems on the file. They actually introduce an extra
layer of complexity and mask the actual underlying issue. Far better to
actually correct the problem.
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"Wislu Plethora" > wrote in message
...
>
> >-----Original Message-----
> >First, dump Win Doctor and the rest of Norton suite. You
> can keep Norton AV,
> >but that's not a product I recommend people keep either.
> That alone will do
> >wonders for your system. Also, delete the file you just
> downloaded. No
> >telling where it came from nor what kind of surprise
> package it may be
> >bearing.
> >
> >Follow the instructions here:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;274461
> >
> >--
> >Walter Clayton - MS MVP(WinXP)
> >Associate Expert
> >http://www.microsoft.com/windowsxp/expertzone
> >Any technology distinguishable from magic is
> insufficiently advanced.
> >http://www.dts-l.org
> >http://support.microsoft.com/servicedesks/fileversion/defa
> ult.asp
> >
>
> This is a misleading and irresponsible load of crap. There
> are legions of satisfied users of the Norton Suite, and I
> count myself among them. Note that the page referred to
> above very clearly states that the problem is with the
> MS products referred to, not the Symantec products. What
> does MS offer as a "solution"? Stop using the Norton
> products.
>
> I understand that unabashed sycophancy is a requirement for
> "achieving" and maintaining Microsoft Junior Fire Chief
> (MVP) status, but to malign a creditable and highly
> successful third-party product--clearly without knowing
> what you're talking about--is pretty low.
Walter Clayton
December 5th 03, 12:16 AM
http://www.kaspersky.com
I've seen, personally and with different clients and end users too many
issues with Norton products in general.
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"JBM" > wrote in message
...
> Walter -
>
> I've been happy (or satisfied, at least) with Norton AV - what do you
> recommend and why?
>
> Jonny May
>
>
>
> "Walter Clayton" > wrote in message
> ...
> > First, dump Win Doctor and the rest of Norton suite. You can keep Norton
> AV,
> > but that's not a product I recommend people keep either. That alone will
> do
> > wonders for your system. Also, delete the file you just downloaded. No
> > telling where it came from nor what kind of surprise package it may be
> > bearing.
> >
> > Follow the instructions here:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;274461
> >
> > --
> > Walter Clayton - MS MVP(WinXP)
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone
> > Any technology distinguishable from magic is insufficiently advanced.
> > http://www.dts-l.org
> > http://support.microsoft.com/servicedesks/fileversion/default.asp
> >
> >
> > "Michael" > wrote in message
> > ...
> > > Re: Microsoft Picture It! Publishing 2001
> > >
> > > Norton Win Doctor advises that the above named program is
> > > missing mhputilu.dll
> > >
> > > I have downloaded this file in archive form from an online
> > > site, and saved it to my desktop. Can you please tell me,
> > > step-by-step, how to place this file?
> > >
> > > OS : Windows XP Home
> > >
> > >
> > >
> > > Thank you.
> >
> >
>
>
Jon
December 5th 03, 12:16 AM
"Walter Clayton" > wrote in message =
...
> First, dump Win Doctor and the rest of Norton suite. You can keep =
Norton AV,
> but that's not a product I recommend people keep either. That alone =
will do
> wonders for your system. Also, delete the file you just downloaded. No
> telling where it came from nor what kind of surprise package it may be
> bearing.
>=20
> Follow the instructions here:
> http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;274461
That's interesting!
You blame Norton's for what the MS kb article clearly shows as being an =
MS problem.
Excerpt from the article;
"Microsoft has confirmed that this is a problem in the Microsoft =
products that are listed at the beginning of this article."
Do you see it saying that Norton's should be removed or is the cause of =
the problem the OP posted? Did you also note that "Dr. Watson" will =
report such an issue if it is running too? (an MS creation!!)
Walter Clayton
December 5th 03, 12:16 AM
Take a look at what the MS fix does. And read just a bit further down in the
article. ;-)
And while at it, ask Symantec why they dumped Crashguard.
But again, don't take my word for it. Dump Norton from your system and see
what happens to overall performance and stability.
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"Jon" > wrote in message
...
"Walter Clayton" > wrote in message
...
> First, dump Win Doctor and the rest of Norton suite. You can keep Norton
AV,
> but that's not a product I recommend people keep either. That alone will
do
> wonders for your system. Also, delete the file you just downloaded. No
> telling where it came from nor what kind of surprise package it may be
> bearing.
>
> Follow the instructions here:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274461
That's interesting!
You blame Norton's for what the MS kb article clearly shows as being an MS
problem.
Excerpt from the article;
"Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article."
Do you see it saying that Norton's should be removed or is the cause of the
problem the OP posted? Did you also note that "Dr. Watson" will report such
an issue if it is running too? (an MS creation!!)
Wislu Plethora
December 5th 03, 12:16 AM
>-----Original Message-----
>Don't take my word for it. ;-)
>
>Uninstall all the Norton utilities and see if your
machine doesn't behave
>better. As for this specific issue, notice that it's
caused by Norton and
>one of the reference products has specifically been
dropped by Norton when
>they finally realized the product was incapable of doing
what was claimed.
>As well it seems you didn't read far enough. To quote
>
><Quoute>
>MORE INFORMATION
>It is found that the programs listed at the beginning of
this article will
>run smoother if Norton CrashGuard, Norton WinDoctor or
Dr. Watson are turned
>off prior to running the programs listed at the beginning
of this article.
></quote>
>
>There is no need and never has been a need for a 3rd
party product to
>"correct" system problems on the file. They actually
introduce an extra
>layer of complexity and mask the actual underlying issue.
Far better to
>actually correct the problem.
>
>--
I can read. My point, which you apparently missed, is that
Microsoft's "solution" is to recommend not running the
programs--not because of any inherent defects in the
programs, but because of problems with the MS applications
in question. It is true that one of the Norton products
has been withdrawn, which is, in my opinion, to Symantec's
credit. Contrast Microsoft's general strategy of blaming
their problems on someone else, or worse, denying that
there *is* a problem.
There is no appreciable difference in the way my system
runs now and the way it ran before the Norton suite was
installed. And btw, your last paragraph makes no sense
whatsoever.
Walter Clayton
December 5th 03, 12:16 AM
Hmm. Odd that the only time this particular fix needs be applied is when
using Symantec applications that are intended to correct MS problems. ;-)
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"Wislu Plethora" > wrote in message
...
>
> >-----Original Message-----
> >Don't take my word for it. ;-)
> >
> >Uninstall all the Norton utilities and see if your
> machine doesn't behave
> >better. As for this specific issue, notice that it's
> caused by Norton and
> >one of the reference products has specifically been
> dropped by Norton when
> >they finally realized the product was incapable of doing
> what was claimed.
> >As well it seems you didn't read far enough. To quote
> >
> ><Quoute>
> >MORE INFORMATION
> >It is found that the programs listed at the beginning of
> this article will
> >run smoother if Norton CrashGuard, Norton WinDoctor or
> Dr. Watson are turned
> >off prior to running the programs listed at the beginning
> of this article.
> ></quote>
> >
> >There is no need and never has been a need for a 3rd
> party product to
> >"correct" system problems on the file. They actually
> introduce an extra
> >layer of complexity and mask the actual underlying issue.
> Far better to
> >actually correct the problem.
> >
> >--
>
> I can read. My point, which you apparently missed, is that
> Microsoft's "solution" is to recommend not running the
> programs--not because of any inherent defects in the
> programs, but because of problems with the MS applications
> in question. It is true that one of the Norton products
> has been withdrawn, which is, in my opinion, to Symantec's
> credit. Contrast Microsoft's general strategy of blaming
> their problems on someone else, or worse, denying that
> there *is* a problem.
>
> There is no appreciable difference in the way my system
> runs now and the way it ran before the Norton suite was
> installed. And btw, your last paragraph makes no sense
> whatsoever.
Jim Carlock
December 5th 03, 12:17 AM
Just speaking from personal experiences in the past with 1000s of machines
and customers, I recommend staying away from all Norton products. I've have
seen bugs in almost all of their products. Spending hours upon hours of
research, I've found they have not supported thier products very well
either.
From personal experience, dealing with 1000s of systems, and dealing with
problem programs, Norton products rank in there with those products that try
to make other protective products that have failed. Microsoft, included!!!
Especially with their DLLCACHE and their creation of 1000s of new "My
Documents" folders when a server is brought down and restarted, with their
installation programs that never really do any installation but prefer to do
a bunch of date/time checks on files instead, and other such problems.
I'm still looking for help regarding how to fix systems so that there is
only one "My Documents", only one "Start Up Programs", and only one registry
on any system within an organization.
Jim Carlock
BASH them all. Don't just limit it to Norton! LOL
Jon
December 5th 03, 12:17 AM
"Walter Clayton" > wrote in message =
...
> Take a look at what the MS fix does. And read just a bit further down =
in the
> article. ;-)
>=20
> And while at it, ask Symantec why they dumped Crashguard.
>=20
> But again, don't take my word for it. Dump Norton from your system and =
see
> what happens to overall performance and stability.
I don't know why they dumped it, because I never used it, or NSW, or any =
product that attempts to maintain an OS is a no-no in my book. I also =
read the whole article, I am still unconvinced since MS placed a fix for =
their problem (Dr Watson). I do use NAV, and am very happy with it. But =
note that MS listed "Dr Watson", an MS program that caused this problem =
also. The fact that MS released a fix, should be testament to their =
culpability in this particular issue (like the 811493 problem). Removing =
NAV has little to no effect on my current system. If I turn off =
automatic startup, I save maybe 1-2mgs of RAM. All AVs use memory to run =
in the background.
What you use is preference and any AV or system utility can cause =
issues. But this is a case of MS admission IMHO.
Wislu Plethora
December 5th 03, 12:17 AM
>-----Original Message-----
>Hmm. Odd that the only time this particular fix needs be
applied is when
>using Symantec applications that are intended to correct
MS problems. ;-)
>
Usually, when it becomes apparent that I am entering into
a battle of wits with an unarmed person I will just let
it go. But because the response above is so egregiously
stupid, I feel a final response is in order.
Odd, you say? Odd that the ONLY apps involved are the ones
listed in the referenced article. In other words, this
problem, according to your idols in Redmond, does not
exist with Word, or Excel, or Pacman, or any of about
a million other applications. Only with the ones listed.
And it exists with the ones listed BECAUSE OF A PROBLEM
WITH *THEM*. This is according to Microsoft. You claim
to be interested in finding the root cause of problem and
fixing it, but Microsoft's official position, at least in
this case, is to advise users to stop using the Symantec
products, and to stop using Dr. Watson, a Microsoft
product.
Walter Clayton
December 5th 03, 12:17 AM
Careful with assumptions. ;-)
OP had issues with Norton's products. Yes, DrW is listed as problematic, but
only if it's actually running. No one, unless in the middle of doing a
serious diag session, launches DrW and leaves it running. Fact is, >99% of
the users don't even know how to run DrW in the background much less what it
does and to further complicate the matter, no one seriously relies on DrW
for diagnostics either.
Yes, in this specific instance there was in fact an issue with how a dll
registered itself, but the applications still ran correctly. At least as
long as there was no low level monitoring activity taking place looking for
nonexistent faults and interfering with the normal operation of
applications.
Broadening the issue though begs the chicken or egg question. To put it
another way, if it takes a low level diagnostic tool to detect a problem
that has absolutely no impact on normal functionality, then where is the
problem?
--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp
"Wislu Plethora" > wrote in message
...
>
> >-----Original Message-----
> >Hmm. Odd that the only time this particular fix needs be
> applied is when
> >using Symantec applications that are intended to correct
> MS problems. ;-)
> >
>
> Usually, when it becomes apparent that I am entering into
> a battle of wits with an unarmed person I will just let
> it go. But because the response above is so egregiously
> stupid, I feel a final response is in order.
>
> Odd, you say? Odd that the ONLY apps involved are the ones
> listed in the referenced article. In other words, this
> problem, according to your idols in Redmond, does not
> exist with Word, or Excel, or Pacman, or any of about
> a million other applications. Only with the ones listed.
> And it exists with the ones listed BECAUSE OF A PROBLEM
> WITH *THEM*. This is according to Microsoft. You claim
> to be interested in finding the root cause of problem and
> fixing it, but Microsoft's official position, at least in
> this case, is to advise users to stop using the Symantec
> products, and to stop using Dr. Watson, a Microsoft
> product.
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.