OEM*.INF file generator

[RJN]

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?

[heirloom]

Are you using Norton System Doctor? If so that is possibly the cause of
this
problem.

Does your windows\inf folder contain thousands of 0 byte oem*.inf files? If
so
then that's the probable cause of your problems.

Why has this happened? Did you perhaps forget to disable System Doctor
before
updating your system from the Windows Update site? Delete these 0 byte
oem*.inf
files and hopefully you should resolve your problems.

For more details see the Symantec site:
http://service1.symantec.com/SUPPORT/nunt.nsf/docid/2000120915010309&src=n
and
also MS KB Q281967 - "Computer Stops Responding (Hangs) During Setup,
Installing
Updates, or Adding New Hardware"
(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281967). Contact
Microsoft mentioning Q281967 and also KB Q301540 - "CreateFile Improperly
Returns ERROR_ALREADY_EXISTS if the Drive Is Locked and the File Did Not
Exist"
(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q301540) and ask
for
them to let you have the updated file ifsmgr.vxd. There will be no charge
for
this call.
--
Mike Maltby MS-MVP


--------------------------
See MS KB Q283069 - "Error Message: Windows Could Not Upgrade the File
%1from
%2 %1: %2"
(http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q283069),
Do
you have a wininit.ini file in your windows folder? If so rename to
wininit.old and reboot. If this is the reason it appears that your last
software install or update may not have been completed correctly and perhaps
needs repeating.

If a wininit.ini file isn't the cause of the problem do you use Norton
products, especially Live Update? If yes read on.

Others experience the %1 %2 error after using Norton/Symantec's Live Update.
Whilst the MS KB only mentions NSW 2000 other users have confirmed that the
problem still exists with NSW2002 or rather LiveUpdate 2002. KB Q290664 -
"Norton System Works 2000 Is Not Compatible with Windows Millennium Edition"
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;q290664) which
states:
"SYMPTOMS
When you start a Windows Millennium Edition (Me)-based computer after you
run
the Norton System Works 2000 Live Update feature, you may receive the
following error message:
Windows could not upgrade the file from percent 1 to percent 2 and your
computer may stop responding.
CAUSE
This issue occurs because Norton System Works 2000 is not compatible with
Windows Me."

Norton mention the same problem but offer no solution at
http://service4.symantec.com/SUPPORT/sharedtech.nsf/pfdocs/2000122608485706
other than stating:
"In the cases that have been reported, this has been caused because of
damage
to the Windows Me System Restore feature. This results in the error message
after LiveUpdate is run."

Finally, if neither of the above apply have you disabled System Restore in
any
way including possibly removing the _RESTORE folder structure from your
windows drive? Doing this has also been demonstrated to cause similar
problems.

Newest info:
Open Windows Explorer (not Internet Explorer but Windows Explorer as in
the
file management program). From there go to C:/Program Files/Internet
Explorer/Uninstall Information. Right click on the Uninstall
Information
folder and select Properties. Uncheck the Hidden box and then click OK
or
Apply. A confirmation screen will come up. Select the Apply changes to
this folder, subfolders and files button. This will unhide all of the
files
in the Uninstall Information folder. You then need to move (not delete)
all
of these files to another folder that is empty. Any one will do or make
a
new temporary folder. It doesn't really matter just as long as the
Uninstall Information folder is empty. Reboot your computer. After
rebooting double check and make sure that the Uninstall Information
folder
is empty. You should then be able to install all of the troublesome
components (hopefully). If everything goes well you can then move all
of
those files that you moved previously back into the Uninstall
Information
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++
Probably more info than you needed, but, you should be covered. Special
thanks to Mr. Maltby, MS-MVP.
Heirloom, old and seen it


"RJN" > wrote in message
...
> 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?

[Mike M]

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?