Thanks for your advice, once again. What you've helped me to understand is
that I can either go with what I have or reinstall Windows. It's too bad that
Microsoft does not offer a WMI Redistributable for WXP like the one they do
for earlier versions of Windows. I will abide with what I've got for now,
considering that none of my current computing activity is impaied, & engage
in a full-throttle wipe & reload in August to coincide with upgrading NIS to
a new version. Cheers, John John.
--
Joe Davis


"John John - MVP" wrote:

If you did the comprehensive rebuild as shown in the link, and if WMI is
still bugged up, then an in-place upgrade is the only thing else that I
can suggest.

http://support.microsoft.com/kb/978788
How to perform an in-place upgrade (reinstallation) of Windows XP

John

Joe wrote:
-Thank you, John John, for your help & links.
I ran the command you suggested but it did not help.
I then copied the core WMI files from another system & began working with
the WMI Diagnosis Tool to affect repair. This was cumbersome because the "for
%i in (*.dll) do RegSvr32 -s %i" AND "for %i in (*.exe) do %i /RegServer"
scripts did not work on my computer, meaning that I had to register the
components one-by-one.
The WMI Service is now up & running, though I still have some problems
(e.g., nothing is listed on the Dependencies tab of any Service). For some
reason, a few .dll & .exes continue to be flagged by the Tool as needing to
be registered, most notably WINMGMT.EXE & UNSECAPP.EXE. Addionally,
registration for FASTPROX.DLL & WBEMPROX.DLL won't take for all classes.
I also notice that none of the .mfl, .mof, or .xsl files that exist on my
other identically set up computer are present in my reconstructed WBEM
folder. Should I simply copy these over as well?
Appreciate any further advice.
.