Error parsing at startup


Doesn't appear to work for me on Win7 x64. Error parsing processor time at startup then I can't add any memory counters. Lots of input string not in correct format.

file attachments

Closed Nov 10, 2011 at 4:19 AM by RudolfHenning
Not reproducable


RudolfHenning wrote Mar 7, 2011 at 11:07 AM

I'm developing on a 64-bit platform so it is not that. How do you specify the startup parameter? Best is to use the qpmset type of files as it eliminate the need for escaping some reserved characters (but not all).

thnk2wn wrote Mar 7, 2011 at 12:35 PM

It was quite a while ago, I don't remember. But I don't think I specified any startup parameter. I just ran the exe directly.

RudolfHenning wrote Mar 8, 2011 at 8:20 AM

Do you still have the same issue and/or have you tried the latest version?

thnk2wn wrote Mar 23, 2011 at 2:08 PM

I still have the same issue after downloading the latest copy just now.

RudolfHenning wrote Mar 23, 2011 at 3:49 PM

I've tested the download and run (as is) on a Win 7 x64 machine without issue. There must be something different in your environment - perhaps regional settings or so. What language/region settings are you using for your OS?

wrote Mar 24, 2011 at 1:50 PM

thnk2wn wrote Mar 24, 2011 at 1:50 PM

Standard stuff there, English (United States). I dug into the code and that lead me to http://stackoverflow.com/questions/3121688/performance-counter-input-string-was-not-in-a-correct-format-c which lead me to http://drayblog.gotdns.com/index.php/2010/02/04/diagnostics-performancecounter-input-string-was-not-in-a-correct-format/ which fixed the issue. It appears that maybe if you monkey with perf mon counters that this can happen both in perfmon and this tool.

RudolfHenning wrote Nov 9, 2011 at 2:39 PM

Can I mark this as closed/fixed?

thnk2wn wrote Nov 9, 2011 at 3:04 PM


wrote Nov 10, 2011 at 4:19 AM

wrote Feb 13, 2013 at 10:56 PM

wrote May 16, 2013 at 4:57 AM