System Properties- where's the CPU???

I think the thread title and the attached screen shot say it all (WinXP Home SP2).....

:confused

 

I've already run several scans, and other than some tracking cookies, all was clean.

 

Same here, but I can't find it either at the moment. IIRC, it had to do with a OEMLOGO.SYS file which was located in C:\Windows\System. Ring a bell?

 

Is there a file named "oeminfo.ini" in your windows\system32 folder? If so, perhaps renaming it something else will restore the proper display?

 

Yes.

:confused What is "resource hacker" and where do I get it?

BTW- this problem has been solved, but for future reference I'd like to know what this "resource hacker" thing is all about. I fixed this with a safe reload of XP.....

 

I have the same problem. This happened to me right after I installed XP SP3.

I have a AMD dual-core CPU (Opteron 180) and have tried with "Resource Hacker" to find anything that resembles the lost CPU-info in the "sysdm.cpl"-file, but without success. There is no "oeminfo.ini"-file in "c:\windows\system32".

Is there something else that I can try to revive the CPU-info?

 

Please, there must be something that I can do! I really don't understand why the CPU info disappeared right after I installed SP3 for XP. It just doesn't make any sense.

 

Other than suggesting removing SP3, open regedit and go to;
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0

This is where the information should be. You may be able to edit the appropriate String Value keys to put your info there.

If nothing is there (no keys), seeing as they're String Values, you can probably create new keys with the appropriate string name, and enter the data.

I'll attach a pic of mine so you can see the key names etc. Too big, here's a link;
http://www.d-a-l.com/dan/CPU_Reg.zip

 

Thank you for the help. But I have actually already solved the problem.

It was the "Windows Management Instrumentation" (WMI) that was broken after the install of SP3.

I installed the "WMI Diagnosis Utility" and corrected all the errors that was found in the log-file. It took about 4 hours of register-editing, changing attributes of code in files and creating folders and a couple of files + lots of commands in the Windows Command Prompt until WMI was fixed and the CPU info was back.