I concur with Norman Miller with this reservation:
If the Win9X machine is adversely affected by KB891711, use the
msconfig/startup checkbox to disable its launch at boot. This permits an
easy reversion, if needed later.
In addition, I recommend increasing the amount of memory in each machine to
at least 256 MB to improve performance, and upgrading to IE6 SP1 for
security issues, even if most users are using Firefox. You will have to
decide about these, since you may be buying new boxes soon.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you:
http://www.dts-L.org/goodpost.htm
http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
"N. Miller" <> wrote in message
news: om...
> In article <>, Nate Goulet says...
>
> > Should I install KB891711 or leave it out? Need to protect small
> > corporate network.
>
> I would install the patches separately; KB888113 first. I don't anticipate
> any problem with that patch.
>
> I would install the KB891711, but watch what happens with the computer.
You
> should reboot after installation to be sure the patch is running; it
doesn't
> alter system files, it runs as a resident process.
>
> On any computer which starts having blue screen issues, such as on browser
> launch (which is the effect that I see), or on boot, use the "Add/Remove
> Progams" list in the Control Panel to remove the patch. I don't know how
to
> stop Windows Udate from offering the patch again in Automatic Update mode
if
> you remove the entire patch. Leaving the .exe and .dll files on the system
> will satisfy the Windows Update site for the Automatic Update offering.
They
> won't cause a problem as long as they don't load.
>
> I am not sure what the problem is, now. I have two identical computers;
and
> the patch breaks one, but not the other. It does offer protection against
a
> critical vulnerability, so I am leaving it in place on the computer which
it
> isn't breaking. The problem is only evident while the application is
> running; it does not permanently break anything, and should not require
> anything more drastic than a Safe Mode boot for removal. I didn't have to
go
> even that far.
>
> --
> Norman
> ~Win dain a lotica, En vai tu ri, Si lo ta
> ~Fin dein a loluca, En dragu a sei lain
> ~Vi fa-ru les shutai am, En riga-lint