First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is.
Although I have a minimum of 26 programs running (don't yell, I know it's too much)
If with the "26 programs" you are referring to the processes running on your XP, that is entirely normal, nothing to worry about, and not "too much" at all. An operating system is supposed to run processes, not sit around and do nothing.
none of these programs appear either
They don't appear where?
According to my System Summary Information, my Microsoft XP Professional was REMOVED on October 12, 2001.
Seriously, though, that System Summary Information is notoriously unreliable, and reports all sorts of nonsense on just about any machine. Don't worry about it.
That is where ALL history for my system stops
What history?
I downloaded the WMI Tools from Microsoft for XP, but this has not resolved the issue
What issue?
On an online diagnostic tool (PC Pit Stop), it is claiming I have 413 MB of Junk Files
[Shrug.] Who knows what this "online diagnstic tool" is doing. My advice: Forget it.
This is crazy, as I clean my computer of ALL Temp Internet Files, ALL Cookies, ALL History, ALL c:\windows\prefetch fles, ALL Trash, ALL Recent Documents, etc.....
Why? You have what sounds like a more or less empty hard drive. Do you need the space for anything? Or is it just that you like the feeling of pristine emptiness on a hard drive?
I am not sure if these issues are related
I am sorry, and maybe I am missing something important, but I cannot see any issues that you would have. Is something not working on your machine? Is it extraordinarly slow? Any crashes?
Actually, the C Drive is running at only 22% of it's capacity - yes - that is slow! It's running at 1.05 MB/s instead of 4.94 MB/s (uncached speed).
Ahah, now that is telling me something. I am sorry, but I did not get what you meant by "running at 22% of its capacity" at first. I thought you were talking about it being 78% empty. One MB/s is indeed on the slow side, and you should get around 5MB/s.
Now, the first thing to find out is if PC Pitstop is not simply reporting nonsense, as it is wont to... There are a number of ways to do this, but you could simply find (or create) a large file (say, 20MB or so) on your computer and load it into notepad or Word while timing how long that takes. If you don't have anything handy then use the file OEMBIOS.BIN in C:\Windows\System32, and load it into WordPad. This is not a very accurate method, but it will give you a rough idea of whether PC Pitstop is right.
Dietmar, you wrote: "First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is."
You know, somehow I missed that on the first round! WMI v1.5: Included as a standard feature in Windows Server 2003, Windows XP, Windows 2000. It is the nice little tool that lets me know what is going on with my system, do I don't have to rack my brain in trying to get answers from forums which somehow became uninstalled. That is why I re-downloaded it.
Windows Managemet Instrumentation is a semi-intregal part of my computer for diagnostics. Ummm .... you did know that ....
Yes, I did know that. That is why I wrote what I wrote the way I wrote it.
P.S.: I'll give you a hint: What you installed were the WMI Tools, not XP's WMI component. The latter is not available for separate install, as far as I know. But maybe I don't know that...
Dietmar, you wrote: "First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is."
You know, somehow I missed that on the first round! WMI v1.5: Included as a standard feature in Windows Server 2003, Windows XP, Windows 2000. It is the nice little tool that lets me know what is going on with my system, do I don't have to rack my brain in trying to get answers from forums which somehow became uninstalled. That is why I re-downloaded it.
Windows Managemet Instrumentation is a semi-intregal part of my computer for diagnostics. Ummm .... you did know that ....
The following info may help when getting that error message.
---------------------------------------------------------------------
Question:
When trying to use System Information, I get the following error:
( Can't Collect Information... )
Answer:
Try the following steps to resolve this issue.
Procedure 1:
Click Start, click Control Panel.
On the left hand side of control Panel, click Switch to Classic View.
Double click Administrative Tools, and double click Services.
-In the right pane, find the entry for Event Log.
Right click Event Log, click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
-In the right pane, find the entry for Windows Management Instrumentation.
Right click Windows Management Instrumentation, click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
-In the right pane, find the entry for Remote Procedure Call (RPC).
Right click Remote Procedure Call (RPC), click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
*Warning*
There will be two listings for the (RPC) file, and both listings must
be modified using the above steps.
Once you are done, close all open Windows and restart the system.
When you get back into Windows, try getting system information again.
Procedure 2:
If you use a password for your user account, you may also want to
check the password status box.. This should only be uses if you have
multiple user accounts on your system, and each account requires a
password.
Log on with the account that is having the problem.
Click Start, click Control Panel.
On the left hand side of control Panel, click Switch to Classic View.
Double click Administrative Tools, and double click Services.
-In the right pane, find the entry for Event Log.
Right click Event Log, click on Properties.
Click the Log On tab, put a check in the box for "This Account."
Type in the password that you use to log on to your user account.
Re-type the password to confirm it, and then click Apply and Ok.
Reboot the system and see if the problem still occurs.
*You must repeat this step for Windows Management Instrumentation,
and both Remove Procedure Call Files.
Related Microsoft Articles:
1.Msinfo32.exe Generates a "Can't Collect Information" Error Message
http://support.microsoft.com/default.aspx?scid=kb;en-us;q323209
2."Event ID: 7000" or "Event ID: 7013" Error Message When You Attempt to Start a Service.
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q314357
Thanks to LPORT for providing additional information.
---------------------------------------------------------------------
Dietmar
224 Posts
0
January 20th, 2003 19:00
First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is.
Although I have a minimum of 26 programs running (don't yell, I know it's too much)
If with the "26 programs" you are referring to the processes running on your XP, that is entirely normal, nothing to worry about, and not "too much" at all. An operating system is supposed to run processes, not sit around and do nothing.
none of these programs appear either
They don't appear where?
According to my System Summary Information, my Microsoft XP Professional was REMOVED on October 12, 2001.
That is where ALL history for my system stops
What history?
I downloaded the WMI Tools from Microsoft for XP, but this has not resolved the issue
What issue?
On an online diagnostic tool (PC Pit Stop), it is claiming I have 413 MB of Junk Files
[Shrug.] Who knows what this "online diagnstic tool" is doing. My advice: Forget it.
This is crazy, as I clean my computer of ALL Temp Internet Files, ALL Cookies, ALL History, ALL c:\windows\prefetch fles, ALL Trash, ALL Recent Documents, etc.....
Why? You have what sounds like a more or less empty hard drive. Do you need the space for anything? Or is it just that you like the feeling of pristine emptiness on a hard drive?
I am not sure if these issues are related
I am sorry, and maybe I am missing something important, but I cannot see any issues that you would have. Is something not working on your machine? Is it extraordinarly slow? Any crashes?
Message Edited by Dietmar on 01-20-2003 03:56 PM
Dietmar
224 Posts
0
January 20th, 2003 20:00
Actually, the C Drive is running at only 22% of it's capacity - yes - that is slow! It's running at 1.05 MB/s instead of 4.94 MB/s (uncached speed).
Ahah, now that is telling me something. I am sorry, but I did not get what you meant by "running at 22% of its capacity" at first. I thought you were talking about it being 78% empty. One MB/s is indeed on the slow side, and you should get around 5MB/s.
Now, the first thing to find out is if PC Pitstop is not simply reporting nonsense, as it is wont to... There are a number of ways to do this, but you could simply find (or create) a large file (say, 20MB or so) on your computer and load it into notepad or Word while timing how long that takes. If you don't have anything handy then use the file OEMBIOS.BIN in C:\Windows\System32, and load it into WordPad. This is not a very accurate method, but it will give you a rough idea of whether PC Pitstop is right.
Message Edited by Dietmar on 01-20-2003 04:41 PM
CrystalSky
3 Posts
0
January 20th, 2003 20:00
Actually, the C Drive is running at only 22% of it's capacity - yes - that is slow! It's running at 1.05 MB/s instead of 4.94 MB/s (uncached speed).
Link to test results:
http://www.pcpitstop.com/pcpitstop/Summary.asp?TechExpress=4VPHWW4Y7T0SLVVD
Message Edited by CrystalSky on 01-22-2003 12:35 AM
Dietmar
224 Posts
0
January 22nd, 2003 11:00
Dietmar, you wrote: "First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is."
You know, somehow I missed that on the first round! WMI v1.5: Included as a standard feature in Windows Server 2003, Windows XP, Windows 2000. It is the nice little tool that lets me know what is going on with my system, do I don't have to rack my brain in trying to get answers from forums which somehow became uninstalled. That is why I re-downloaded it.
Windows Managemet Instrumentation is a semi-intregal part of my computer for diagnostics. Ummm .... you did know that ....
Yes, I did know that. That is why I wrote what I wrote the way I wrote it.P.S.: I'll give you a hint: What you installed were the WMI Tools, not XP's WMI component. The latter is not available for separate install, as far as I know. But maybe I don't know that...
Message Edited by Dietmar on 01-22-2003 07:34 AM
CrystalSky
3 Posts
0
January 22nd, 2003 11:00
Dietmar, you wrote: "First question: What do you need WMI for? You have to excuse me, but you do not sound like you need to worry about it, let alone know what it is."
You know, somehow I missed that on the first round! WMI v1.5: Included as a standard feature in Windows Server 2003, Windows XP, Windows 2000. It is the nice little tool that lets me know what is going on with my system, do I don't have to rack my brain in trying to get answers from forums which somehow became uninstalled. That is why I re-downloaded it.
Windows Managemet Instrumentation is a semi-intregal part of my computer for diagnostics. Ummm .... you did know that ....
Karell
2 Intern
•
2.5K Posts
0
September 15th, 2003 15:00
The following info may help when getting that error message.
---------------------------------------------------------------------
Question:
When trying to use System Information, I get the following error:
( Can't Collect Information... )
Answer:
Try the following steps to resolve this issue.
Procedure 1:
Click Start, click Control Panel.
On the left hand side of control Panel, click Switch to Classic View.
Double click Administrative Tools, and double click Services.
-In the right pane, find the entry for Event Log.
Right click Event Log, click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
-In the right pane, find the entry for Windows Management Instrumentation.
Right click Windows Management Instrumentation, click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
-In the right pane, find the entry for Remote Procedure Call (RPC).
Right click Remote Procedure Call (RPC), click on Properties.
Under the General Tab, make sure that "Startup Type" is set to (Automatic).
Click the Log On tab, click Local System account, and then click OK.
*Warning*
There will be two listings for the (RPC) file, and both listings must
be modified using the above steps.
Once you are done, close all open Windows and restart the system.
When you get back into Windows, try getting system information again.
Procedure 2:
If you use a password for your user account, you may also want to
check the password status box.. This should only be uses if you have
multiple user accounts on your system, and each account requires a
password.
Log on with the account that is having the problem.
Click Start, click Control Panel.
On the left hand side of control Panel, click Switch to Classic View.
Double click Administrative Tools, and double click Services.
-In the right pane, find the entry for Event Log.
Right click Event Log, click on Properties.
Click the Log On tab, put a check in the box for "This Account."
Type in the password that you use to log on to your user account.
Re-type the password to confirm it, and then click Apply and Ok.
Reboot the system and see if the problem still occurs.
*You must repeat this step for Windows Management Instrumentation,
and both Remove Procedure Call Files.
Related Microsoft Articles:
1.Msinfo32.exe Generates a "Can't Collect Information" Error Message
http://support.microsoft.com/default.aspx?scid=kb;en-us;q323209
2."Event ID: 7000" or "Event ID: 7013" Error Message When You Attempt to Start a Service.
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q314357
Thanks to LPORT for providing additional information.
---------------------------------------------------------------------
Inspiron_Dude
7 Posts
0
July 31st, 2004 01:00