1. The article [Q310490] explains the "Performance Logs and Alerts" option a user can use to collect performance data automatically from local or remote computers. Logged counter data can be viewed using System Monitor or export the data to spreadsheet programs or databases for analysis and report generation. The following capabilities are offered when using it:
? Performance Logs and Alerts collects data in a comma-separated or tab-separated format for easy import to spreadsheet programs. A binary log-file format is also provided for circular logging or for logging instances such as threads or processes that may begin after the log starts collecting data. (Circular logging is the process of continuously logging data to a single file, overwriting previous data with new data.)
? You can also collect data in a SQL Database format. This option defines the name of an existing SQL database and log set within the database where the performance data will be read or written. This file format is useful when collecting and analysing performance data at an enterprise level rather than a per-server basis.
? Counter data collected by Performance Logs and Alerts can be viewed during collection as well as after collection has stopped. Because logging runs as a service, data collection occurs regardless of whether any user is logged on to the computer being monitored.
? You can define start and stop times, file names, file sizes, and other parameters for automatic log generation.
? You can manage multiple logging sessions from a single console window.
? You can set an alert on a counter, thereby defining that a message be sent, a program be run, an entry made to the application event log, or a log be started when the selected counter's value exceeds or falls below a specified setting.
2. Similar to System Monitor, Performance Logs and Alerts supports defining performance objects, performance counters, and object instances, and setting sampling intervals for monitoring data about hardware resources and system services. Performance Logs and Alerts also offers other options related to recording performance data:
? Start and stop logging either manually on demand or automatically based on a user-defined schedule.
? Configure additional settings for automatic logging, such as automatic file renaming, and set parameters for stopping and starting a log based on the elapsed time or the file size.
? Create trace logs. Using the default system data provider or another application provider, trace logs record detailed system application events when certain activities such as a disk I/O operation or a page fault occurs. When the event occurs, logs the data to a file specified by the Performance Logs and Alerts service. This differs from the operation of counter logs; when counter logs are in use, the service obtains data from the system when the update interval has elapsed, rather than waiting for a specific event. A parsing tool is required to interpret the trace log output. Developers can create such a tool using application programming interfaces (APIs) provided on the Microsoft Web site.
? You can also produce trace analysis reports from trace log output files using the Tracerpt tool. Use this tool to process kernel, Active Directory, and other transactional based trace event logs, and to generate trace analysis reports and a .csv files from binary logs.
? Define a program that runs when a log is stopped.
? If you want to export log data to Microsoft Excel, the Performance Logs and Alerts service must be stopped because Microsoft Excel requires exclusive access to the log file. Other programs are not known to require this exclusive access; therefore, in general you can work with data from a log file while the service is collecting data to that file.
3. To start or stop a counter log, trace log, or alert manually:
a. Click Start, Control Panel, Performance and Maintenance, Administrative Tools, and then double-click Performance.
b. Double-click Performance Logs and Alerts, and click either Counter Logs, Trace Logs, or Alerts.
c. In the details pane, right-click the name of the log or alert to start or stop, and then either click Start to begin the logging or alert activity defined, or click Stop to terminate an activity.
Note: There may be a slight delay before the log or alert starts or stops, indicated when the icon changes color (from green for started to red for stopped, and vice versa).
4. Command-line tools which can be used in conjunction with, or separate from, System Monitor and the Performance Logs and Alerts snap-in, "Description of the Windows XP Logman.exe, Relog.exe, and Typeperf.exe Tools (Q303133)."
5. Also note, that %SystemRoot%\System32\Perflib_Perfdataxxx.dat files are created by the System Monitor and that when you shutdown normally, the file should be deleted. If however there is an abormal shutdown, and for reasons yet to be determined, these files can become orphaned, and accumulate on your computer, [Q285798].
I have a Maxtor One Touch that started to go bandit on me and corrupt digital image file etc. I tried the usual WINXP tools (diskcheck etc) but kept getting Cannot XXX due to Device I/O Error. I managed to get some files off to another drive, but I have lost thousands of images. Reformatting the drive seems to have stabilized it, in that I can now read/write, but it seems there are still problems. Incidentally, I have now had 3 Maxtors go this way; coincidence?
I am now trialing data recovery software, but keep getting the same I/O error message. My questions are:
a) What might this error be and how can I fix it?
b) What is the best app for getting images back?
They all claim wonderful things on their websites, but I'm not getting any recoverable files listed.
PS I have cross-posted this on the Storage Forum, I hope this is OK.