Thanks for the feedback Kathie and I'm pleased to read that your HP
scanjet software is now working as it should.

Can you make a recommendation for a replacement to NAV?

Well, I've seen too much damage caused to Win Me caused by running
Symantec software with LiveUpdate being perhaps the worst of the bunch.
As for alternatives there are plenty to choose from although a couple of
them do have slight downsides. Products I would suggest you have a look
at include:
Avast! (www.avast.com). Free and paid for. Note that Avast currently
inhibits the creation of automatic system restore checkpoints so you will
have to remember to make these manually.
AVG (www.grisoft.com and http://free.grisoft.com) both free and paid for
eTrust EZAV from Computer Associates. For a free one year offer see
http://store.digitalriver.com/DRHM/S...PCtrialUS.html
NOD32 (http://nod32.softwaresecuritysolutions.com/)
Panda (www.pandasoftware.com)
etc.
--
Mike Maltby
MS-MVP Windows [2001-2006]



Kathie wrote:

Hi Mike,

I will try the KB912812 install again as you suggest with NAV
disabled. When I do this, I will let you know.

In regard to KB911562 issue. YES YES YES simply installing MDAC 2.8
SP1 resolved the script errors in my HP Scanjet 3970 software (HP
Director) !!! THANK YOU SO VERY MUCH. I informed HP Tech Support (via
Chat) that they initially pointed me to the wrong version of MDAC 2.8
(they pointed me to the version dataed 8/4/03). I also told them that
they need not have customers uninstall their scanner software prior
to installing MDAC 2.8 SP1.

Also, I have a contact in HP Quality Care support and I called him
direct to let him know of what I learned from you. He was very
thankful for he did not realize that there was a SP1 so he will
store that in his bag of tricks. And I let him know about Component
Checker utility and that customers don't have to uninstall their
scanner software.

Can you make a recommendation for a replacement to NAV?

Thank you again!!!!

~ K




"Mike M" wrote:

Kath,

No reply other than to say I'm sorry but I am unable to support those
using NAV other than to urge them dump it and use an AV application
that actually works with Win Me rather than destroying the system.

I would nevertheless strongly urge you to uninstall 912812 (or use
system restore and roll back to a checkpoint created before you
first installed this patch) and then try download again and
reinstall 912812 but this time with NAV disabled for the entire
duration of the download and install.

Ah I see you have already uninstalled 912812 so you can ignore the
first part of the paragraph above.

Regards,
--
Mike Maltby



Kathie wrote:

Hi Mike,

Thanks so very much for the reply and your guidance. I will try what
you suggest, and then post back.

Because of your reply regarding the Kernel32.DLL errors, I may have
not been clear regarding my anomaly. It is KB912812 that is somehow
causing the KERNEL32.DLL errors. I initially talked with Manju of
Windows ME technical support on 4/17/06 regarding my sporadic "I.E.
has caused an error in KERNEL32.DLL" errors upon close of I.E. She
advised at that time to disable my Norton AV whenever installing an
update. After my call to her, I disabled Norton AV and re-installed
KB912812 - but the errors continued. Although it is not clear in my
notes, I believe I installed KB912812 over the top (in other words,
I did not back out the KB912812 that I initially installed with my
Norton AV having been ENABLED).

Thus I had this scenario:
Installed KB912812 with Norton AV enabled.
Encountered KERNEL32.DLL messages.
Called MS support.
Disabled Norton AV.
Installed KB912812. Errors continued.

I backed out KB912812 a couple of days ago via use of the Control
Panel - Add/Remove programs and I no longer get the KERNEL32.DLL
errors.

Do you think/know that we can't re-install an update without first
backing out the same update, such as described above with KB912812.
At the time, I did not think I needed to first uninstall KB912812
prior to re-installing it again.

As an aside, up until the other day, I never disabled Norton AV
prior to doing the MS updates - and I guess I have been fortunate
to not experience any adverse fallout over the years.

Thanks for your help and I await your reply.