Click to See Complete Forum and Search --> : Fresh XP install ... what are these errors?
Skelator
03-26-2003, 05:57 AM
I just formatted my HD and installed XP Pro. I then installed SP1 and my mobo and vidcard drivers. There is absolutly nothing extra installed at the moment.
Can anyone give me any help as to what these two error messages are all about? I tried sending the info to MS but there was nothing found.
See attached picture.
BipolarBill
03-26-2003, 07:24 AM
The second can be ignored.
The first refers to either an application you installed or spyware. If the application works, don't worry. If you don't know what that app is, use Spybot to scan for nastyware.
You can paste those errors into Google for more info.
Skelator
03-26-2003, 10:05 AM
Thanks Bill. I did a google search and came up with this from the MSDN site. Can anyone translate this to english, or more importantly, tell me what steps to take to remedy the problem?
Cooked Counter Provider
The Cooked Counter provider is a high-performance provider for the Windows 2000 platform that provides calculated ("cooked") counter data, such as the percentage of time a disk spends writing data. This provider is the preferred source of calculated data in Windows XP and later. The __Win32Provider instance name is "HiPerfCooker_v1".
The Cooked Counter provider calculates the raw data obtained from the Performance Counter provider according to the counter type of the property, and stores it in classes derived from Win32_PerfFormattedData. WMI places the counter objects in the \root\cimv2 namespace. For more information, see Making an Instance Provider into a High Performance Provider. The objects themselves are derived from Win32_PerfFormattedData. The WMI class name for a counter object is of the form Win32_PerfFormattedData_<service_name>_<object_name>. For example, the WMI class name that contains the logical disk counters is Win32_PerfFormattedData_PerfDisk_LogicalDisk.
You can determine what formula the Cooked Counter provider uses by looking up the value of the CookingType qualifier in WMI Performance Counter Types. or by looking up the value in Winperf.h. This qualifier is the same as the CounterType qualifier in the Win32_PerfRawData classes.
Data from a new WMI performance provider can appear in System Monitor only if a raw data class and a corresponding cooked data class are defined. You can write a high-performance provider to access cooked data using the same IWbemServices interfaces and high-performance APIs as the Performance Counter provider uses. For information on how to create schema and write a provider that uses the Cooked Counter provider to calculate meaningful data, see Making an Instance Provider into a High Performance Provider. For information on how to write a client that can access cooked data, see Writing a Client for the Cooked Counter Provider.
As a high-performance provider, the Cooked Counter provider implements the standard IWbemProviderInit interface, as well as the IWbemRefresher::Refresh method and the following IWbemHiPerfProvider methods:
CreateRefreshableEnum
CreateRefreshableObject
CreateRefresher
GetObjects
QueryInstances
StopRefreshing
Requirements
Client: Included in Windows XP, Windows 2000.
Server: Included in Windows Server 2003.
Windows Me/98/95: Unsupported.
Namespace: Included in \root\cimv2.
rraehal
03-26-2003, 01:21 PM
First Error:
It looks like the "Cooker" gathers performace data to give to applications such as Task Manager looking at the CPU monitor or in a Benchmark for data writing retreival.
It is a standard part of windows now according to the article. It looks like it is for programming with the variables anf classes listed in that article.
Normal error when you set up applications that require system level access. I get this all the time when I install my tape backup software. It is only giving you the Info that this particular installed service has full access to the PC.
Second Error:
Not all the information in RAM was saved to your registry as expected when expected. A process was reading or writing the registry when windows tried to save it to disk and was telling you it had to wait to make sure the registry was correctly saved to disk. It may have taken a few extra secoinds to shut down but it keeps the registry from getting cortrupt with these checks.
BipolarBill
03-26-2003, 07:03 PM
I'm wondering if you have performance monitor (PERFMON) enabled. If so, you should disable it. It should only be used for short periods.
SysOpt.com
Copyright Internet.com Inc. All Rights Reserved.