The "fix" is to stop (or preferably permanently uninstall) Norton System
Doctor whenever making installs or updates to your system.

You could contact Microsoft and ask to be given access to an updated copy of
the file ifsmgr.vxd (v4.90.3003). Mention KB 281967 and also 301540 and ask
for a copy of the new ifsmgr.vxd. You will then either be sent the file or
told
how and where to download a copy. There should be no charge for this call
other than for the cost of the phone call. Alternatively do yourself and your
PC a favour and dump System Doctor.

For more details see MS KB 281967 - "Computer Stops Responding (Hangs) During
Setup,
Installing Updates, or Adding New Hardware"
(http://support.microsoft.com/?kbid=281967).
--
Mike Maltby MS-MVP



RJN wrote:

About a month ago (through this forum) I was informed on
how to eliminate downloading 'freezes' ...thousands of 0-
KB oemxxx.inf files in the WINDOWS/INF folder. The
solution worked great! But now and then when I do a
download (especially a Microsoft Update), the problems
comes back and I have to go through the same procedure of
eliminating the 0-KB oem.inf files. Once the 0-KB oem.inf
files start being produced, the only way I can stop the
process is to shut down the computer. [After logging off
of the internet during a download (because of a
download 'freeze'), the 0-KB oem.inf files continue to be
generated ...as seen at the MS-DOS prompt]. What can be
done to prevent the generation of 0-KB oem.inf files?