Re: ForceX System Monitor v3.0.6(Feb-20-2013)
Posted: August 25th, 2013, 7:15 pm
lodctr /R itself does not work on XP. It needs a filename.ini as an argument. But I am still not sure what to enter there.
Yes, I am using network interface 0, and I did cycle through all of them. Only "0" shows any form of activity. The speeds are doubling my ISP limits, so Im failry sertain it's an read issue. I can say that this is an issue I find on all the other skins I've tested. All except one; think it was called BlueVision V0.2. Once I find time I will be comparing codes.ForceX wrote: @warjar : Are you using network interface 0. Because 0 monitors all interfaces sometimes it seams to give the wrong info. Try to find your exact interface number if you haven't already and see what happens.
First, if you have Interface=0 or just leave off the Interface option, the the measurement of NetIn/NetOut/NetTotal is done on all available physical and virtual network interfaces. This is almost always going to be inaccurate on most modern computers, generally double or even triple the real numbers, due to some virtual interfaces that Windows uses. It pays to find out what interface number your actual physical NIC card is.warjar wrote: Yes, I am using network interface 0, and I did cycle through all of them. Only "0" shows any form of activity. The speeds are doubling my ISP limits, so Im failry sertain it's an read issue. I can say that this is an issue I find on all the other skins I've tested. All except one; think it was called BlueVision V0.2. Once I find time I will be comparing codes.
While we're on the subject: Is it possible for me to change the time intervall the DL/UL speeds are based upon? As I find the numbers beeing quite spiky. Beeing able to increase the time divied on will give me a more average and sensable number. For all I know this could, in theory, also be a possible solution to my initial issue.
Code: Select all
DBUG (00:00:00.031) : 8: Realtek PCIe GBE Family Controller
DBUG (00:00:00.031) : Alias: Ethernet
DBUG (00:00:00.031) : Type=Ethernet(6), Hardware=Yes, Filter=No
Code: Select all
[Rainmeter]
Update=1000
DynamicWindowSize=1
AccurateText=1
[MeasureNetIn]
Measure=NetIn
Interface=8
AverageSize=5
UpdateDivider=1
[MeasureNetOut]
Measure=NetOut
Interface=8
AverageSize=5
UpdateDivider=1
[MeasureConvertIn]
Measure=Calc
Formula=([MeasureNetIn] * 8)
DynamicVariables=1
[MeasureConvertOut]
Measure=Calc
Formula=([MeasureNetOut] * 8)
DynamicVariables=1
[MeterBackIn]
Meter=Image
W=170
H=34
SolidColor=60,60,60,255
[MeterNetInLabel]
Meter=String
X=5
Y=5
FontSize=14
FontColor=60,60,60,255
SolidColor=200,200,200,255
Padding=2,2,3,2
StringAlign=Left
AntiAlias=1
Text=Dn:
[MeterNetIn]
Meter=String
MeasureName=MeasureConvertIn
X=165
Y=7
FontSize=14
FontColor=200,200,200,255
StringAlign=Right
AutoScale=1
NumOfDecimals=2
Text=%1bps
AntiAlias=1
[MeterBackOut]
Meter=Image
Y=([MeterBackIn:Y] + [MeterBackIn:H] + 3)
W=170
H=34
SolidColor=60,60,60,255
[MeterNetOutLabel]
Meter=String
X=5
Y=5r
FontSize=14
FontColor=60,60,60,255
SolidColor=200,200,200,255
Padding=2,2,4,2
StringAlign=Left
AntiAlias=1
Text=Up:
[MeterNetOut]
Meter=String
MeasureName=MeasureConvertOut
X=165
Y=2r
FontSize=14
FontColor=200,200,200,255
StringAlign=Right
AutoScale=1
NumOfDecimals=2
Text=%1bps
AntiAlias=1
Thanks for your attention. This is a newly built installation of Windows XP. So was wondering why is it broken? Ah... never mind, it is Windows after allForceX wrote:@sling-shot : The skin uses rainmeters plugin to access Windows perfmon. If for what ever reason your perfmon is broken you can try and follow the steps here.
http://support.microsoft.com/kb/300956
I do not know if there are any differences between XP & Vista/W7/W8 perfmon access names but I know I wrote the code in Vista and it has worked in W7 / W8 as well.
Sure thing. The Interface number is certainly not "always" important, and many folks will find it works just fine leaving it off or setting it to "0". If you get unexpected results though, it is generally that Interface index that is the culprit, and finding the right one can often be the difference.ForceX wrote:@jsmorley : Thanks for your feedback on the network interface, it is very informative!
@sling-shot : Sorry I can't be of more help. I haven't used XP in a very long time and just don't have a good answer for you at this time. Perhaps someone else can chime in?
@warjar : When I get home I can tell you how to increase the update rate. If I'm not mistaken its currently set to once every second.
Tnx for your reply, but this will not help in my case. This was also the first ting i tried, and it seems the update intervall has no influence on how the speed is calculated, only when it is presented/printed. I wanted to average out the speed value, as it was too spiky to give any sensable information. jsmorley was so kind as to give me the solution I was looking for; "AverageSize"ForceX wrote:@winjar : To increase the update interval for any of the components in the skin you can simply do this.
1. Right click on the component you want to edit and click on Edit Skin.
2. At the very top find [Rainmeter]
3. Right below [Rainmeter] you will see Update=1000. This is currently one second. You can reduce this to 500 for 1/2 second, or lower for faster update intervals ect.
4. Save and refresh the skin.