LiteStep.net Forums :: Forums List :: The General Forum ::
Search ::

[cpu] stuck @ -1% .......please please please help. Thread last updated on 2004-05-18 04:13:56

Posted by member 135953 on 2004-05-06 17:52:54

All I did was turning off my page file in xp pro then turning it back on, right after I noticed that my litestep took way too long start and does when I have cpu meter in my label module [cpu] it gives me -1.

I dont know what is going on I want to use my [cpu] label, but it slows down my litestep startup and gives me only -1.

now I have to comment out [cpu] so it dosent show on my label

Please help

Posted by member 96591 on 2004-05-09 09:21:01 link

maybe you need to copy PDH.dll file to windows system directory

Posted by member 135953 on 2004-05-09 23:34:08 link

what the pdh.dll file where is it?............I am open to all sugestions I relly wanne get my cpu monitor back

Posted by member 135953 on 2004-05-09 23:37:41 link

ok the pdh.dll is in my system32 folder but just for the record my task manaeger does show accurate cpu monitor its just my cpu monitor from my label module [cpu].......I tried using diff versions of the module but no difference.

Posted by member 135953 on 2004-05-10 20:02:39 link

DAMN I even reinsatlled my litestep and cpu monitor is still stuck at -1%

Posted by member 7223 on 2004-05-10 23:03:30 link

update to xLabel

Posted by member 135953 on 2004-05-11 01:00:17 link

I did and same thing is happening

Posted by member 135953 on 2004-05-17 02:52:09 link

hahahahahahah I did it i am a genius I fixed it lol

Posted by member 45783 on 2004-05-17 03:01:54 link

How?

Posted by member 182 on 2004-05-17 23:02:40 link

sounds like mbm wasn't loaded

Posted by member 135953 on 2004-05-18 03:08:38 link

nope nothing to do with mbm it was an xp thing cuz even mbm coudlnt read cpu performance nor could perfmon.exe I had to chane 2 reg keys it that was it

Posted by member 111 on 2004-05-18 04:13:56 link

> sounds like mbm wasn't loaded
Label doesn't use MBM to obtain CPU usage. It uses system perfomance checker (PDH.dll) instead.