Hey there everyone :)

I wanted to offer some help if it's needed/wanted.

First of all I am also working on a project which is simular to this one, but I don't feel like we should try to compete as I'm not in this for the 'glory'. So, I'm going to remake the offer to jedi95 to help him with coding if needed, and if not I'll just bug him with things I would do in a certain way ( untill he maybe say's fine then you do it yourself ).

But before I do that, I think I have to make sure no one here will think I'm here to ease drop on you to improve my own project.

My project is cftUnity, console from tray unity, which is fTray ( http://code.google.com/p/mtray/ ) converted to a usercontrol which is placed on tabpage's ( determined by number of clients installed/managed ), with a main tab page consisting of a listview indicating client status/ppd/eta/eue statistics/environment(sensor) readings ect.

My project collects system information from multiple sources, openclnet is used to determine availabele gpu clients, and where in the past cpu information was gotten through wmi win32_processor ( much better then with .net managed code but raises the bar on os requirements ) now it will collect information through openhardwaremonitorlid.dll and also use this to collect and display sensor information about load, temperature and fan settings ( filterd per client offcourse ).

fTray also collects all client settings and stores them together with the parsed environment information, and I'm working on a dnn module to collect this information and make it searchable. Like, fahinfo.org, just automated with client tracking ( you will have the option to either allow or disallow the uploading of statistics ). If security permits I might make the clients controlable through the website as well, also per descretion of the user.


Jedi95 told me before the aim of his project is to have a very simple gui which will just get people folding easilly, mine is to have an extended gui with extensive tracking and monitoring functions, which will allow extended data mining. I see v3 is changing towards this as well but it's not yet in a territory where it would compete with my project ( if not for the status of gpu tracker, then for the single reason my project is not ready for alpha testing ( fTray is, and I wouldn't mind getting feedback from people who want to try it to control/track a single client )).

I am changing the way I do things, basicly I always just coded as one big binary with all internal classes. But I'm now changing that to making every component as a seperate project, for easier maintenance and also to make it easier for anyone who thinks he could make use of some feature. With that, I might make something available for gpu tracker in the form of an dll, if there would be a need/request for anything.

For instance, I have a full eula compliant configuration screen I already posted on google code a long long time back, but which is now revised to allow writing client settings defined as a public structure, and also reading client settings into the structure without the need to show the gui ( but you need to check the return values when writing settings that way, as only the gui does a double check on the settings/console output and is able to detect if something goes wrong/where it went wrong! ).

And the hardware detection and monitoring will also be done as seperate assembly, I'm sure that would come in handy. But that's not done yet ( if it was, my project would be online now instead of in my ide ).

Maybe there are other things as well, we'll see I guess

Either way, it's good to see a project like this have a good community behind it, and I will try to be a part of it in a constructive manner.

Hi,

Thanks for the offer to help improve the Tracker.

As far as these projects go, I think it would be of mutual benefit to share ideas and/or code that could be used for both projects. Competing with your project wouldn't help anyone since there is simply nothing to be gained by doing so. In the end both projects will end up being better as a result, which will be better for the FAH community as a whole.

From what I can gather cftUnity will offer more detailed and advanced options that the Tracker does.

I am interested in the OpenCL GPU detection and hardware monitoring, since these are things I have been looking into adding to the Tracker. I already have CUDA GPU detection in the latest beta, but that only works on Nvidia cards obviously.

I will add you to the beta team group so you can see the beta section of this forum. You have the SVN information for the Tracker already, so I won't repeat that here.

jedi95

Opencl works now, but only with stream sdk installer ( which is a pretty big download ). Cal detection also works now so that should make simkple hw detection ready in the next build I suppose.

I will be working on a opencl burn in to be able to match gpu's to ohm sensor output for clock, load and temperate readings for both projects I guess.

I might put some effort in first finalizing my usercontrol of ftray so it's going to be ready when I make those additions ( as there is gui space now with 'purty gauges' which don' work yet which just bugs me ).

Btw, this is the output from computer.getreport on my system
[code]
Open Hardware Monitor Report

--------------------------------------------------------------------------------

Version: 0.2.1.0

--------------------------------------------------------------------------------

Common Language Runtime: 2.0.50727.4952
Operating System: Microsoft Windows NT 6.1.7600.0
Process Type: 32-Bit

--------------------------------------------------------------------------------

Sensors

|
+-+ ASUS P5Q DELUXE (/mainboard)
| |
| +-+ Winbond W83667HG (/lpc/w83667hg)
|
+-+ Intel Core 2 Quad Q6600 (/intelcpu/0)
| +- Clock[0] : 400.0366 : 400.0366 : 400.0366 : Bus Speed
| +- Clock[1] : 3200.293 : 3200.293 : 3200.293 : CPU Core #1
| +- Clock[2] : 3200.293 : 3200.293 : 3200.293 : CPU Core #2
| +- Clock[3] : 3200.293 : 3200.293 : 3200.293 : CPU Core #3
| +- Clock[4] : 3200.293 : 3200.293 : 3200.293 : CPU Core #4
| +- Temperature[0] : 61 : 61 : 61 : CPU Core #1
| +- Temperature[1] : 59 : 59 : 59 : CPU Core #2
| +- Temperature[2] : 57 : 57 : 57 : CPU Core #3
| +- Temperature[3] : 52 : 52 : 52 : CPU Core #4
| +- Load[0] : 100 : 100 : 100 : CPU Total
| +- Load[1] : 100 : 100 : 100 : CPU Core #1
| +- Load[2] : 100 : 100 : 100 : CPU Core #2
| +- Load[3] : 100 : 100 : 100 : CPU Core #3
| +- Load[4] : 100 : 100 : 100 : CPU Core #4
|
+-+ NVIDIA GeForce 9600 GT (/nvidiagpu/0)
| +- Clock[0] : : : : GPU Core
| +- Clock[1] : : : : GPU Memory
| +- Clock[2] : : : : GPU Shader
| +- Temperature[0] : : : : GPU Core
|
+-+ WDC WD10EADS-00L5B1 (/hdd/0)
| +- Temperature[0] : 35 : 35 : 35 : HDD
|
+-+ WDC WD10EAVS-00D7B1 (/hdd/1)
| +- Temperature[0] : 36 : 36 : 36 : HDD
|
+-+ Maxtor 6V080E0 (/hdd/2)
| +- Level[0] : : : : HDD

--------------------------------------------------------------------------------

Parameters

|
+-+ ASUS P5Q DELUXE (/mainboard)
| |
| +-+ Winbond W83667HG (/lpc/w83667hg)
|
+-+ Intel Core 2 Quad Q6600 (/intelcpu/0)
| +- Temperature[0] : CPU Core #1
| +- TjMax [°C] : 100 : 100
| +- TSlope [°C] : 1 : 1
| +- Temperature[1] : CPU Core #2
| +- TjMax [°C] : 100 : 100
| +- TSlope [°C] : 1 : 1
| +- Temperature[2] : CPU Core #3
| +- TjMax [°C] : 100 : 100
| +- TSlope [°C] : 1 : 1
| +- Temperature[3] : CPU Core #4
| +- TjMax [°C] : 100 : 100
| +- TSlope [°C] : 1 : 1
|
+-+ NVIDIA GeForce 9600 GT (/nvidiagpu/0)
|
+-+ WDC WD10EADS-00L5B1 (/hdd/0)
|
+-+ WDC WD10EAVS-00D7B1 (/hdd/1)
|
+-+ Maxtor 6V080E0 (/hdd/2)

--------------------------------------------------------------------------------

Mainboard

BIOS Vendor: American Megatrends Inc.
BIOS Version: 2005

Mainboard Manufacturer: ASUSTeK Computer INC.
Mainboard Name: P5Q DELUXE
Mainboard Version: Rev 1.xx

SMBIOS Table

ABgAAAECAPADH5Dei38BAAAAMwUUBf//QW1lcmljYW4gTWVnYXRyZW5kcyBJbmMu
ADIwMDUgICAAMDMvMjUvMjAwOQAAARsBAAECAwRglAAejAABadSBACIVdu3+BgUG
U3lzdGVtIG1hbnVmYWN0dXJlcgBQNVEgREVMVVhFAFN5c3RlbSBWZXJzaW9uAFN5
c3RlbSBTZXJpYWwgTnVtYmVyAFRvIEJlIEZpbGxlZCBCeSBPLkUuTS4AVG8gQmUg
RmlsbGVkIEJ5IE8uRS5NLgAAAg8CAAECAwQFCQYDAAoAQVNVU1RlSyBDb21wdXRl
ciBJTkMuAFA1USBERUxVWEUAUmV2IDEueHgATUItMTIzNDU2Nzg5MABUbyBCZSBG
aWxsZWQgQnkgTy5FLk0uAFRvIEJlIEZpbGxlZCBCeSBPLkUuTS4AAAMVAwABAwID
BAMDAwMRAAAAAAEAAENoYXNzaXMgTWFudWZhY3R1cmUAQ2hhc3NpcyBWZXJzaW9u
AENoYXNzaXMgU2VyaWFsIE51bWJlcgBBc3NldC0xMjM0NTY3ODkwAAAEKAQAAQPC
AvsGAAD/++u/A42QAdgOgAxBAQUABgAHAAQFBgQEBAQATEdBIDc3NQBJbnRlbCAg
ICAgICAgICAgIABJbnRlbChSKSBDb3JlKFRNKTIgUXVhZCBDUFUgUTY2MDAgQCAy
LjQwR0h6ICAgICAgICAgAFRvIEJlIEZpbGxlZCBCeSBPLkUuTS4AVG8gQmUgRmls
bGVkIEJ5IE8uRS5NLgBUbyBCZSBGaWxsZWQgQnkgTy5FLk0uAAAHEwUAAYABgACA
AAEAAQAABAQHTDEtQ2FjaGUAAAcTBgABgQEAIAAgAQABAAAFBQhMMi1DYWNoZQAA
BxMHAAECAwAAAAACAAIAAAICAkwzLUNhY2hlAAAFGAgABgQDAwsBAAABAgQJAAoA
CwAMAAQAAAYMCQABAR4AAYuLAERJTU0wAAAGDAoAASMeAAGLiwBESU1NMQAABgwL
AAFFHgABi4sARElNTTIAAAYMDAABZx4AAYuLAERJTU0zAAAICQ0AAQACDw1QUy8y
IEtleWJvYXJkAFBTLzIgS2V5Ym9hcmQAAAgJDgABAAISEFVTQjEyAFVTQjEyAAAI
CQ8AAQACEhBVU0IzNABVU0IzNAAACAkQAAEAAhIQVVNCNTYAVVNCNTYAAAgJEQAB
AAISEFVTQjc4AFVTQjc4AAAICRIAAQACEhBVU0I5MTAAVVNCOTEwAAAICRMAAQAC
Cx9MQU4gMQBHYkUgTEFOIDEAAAgJFAABAAIcHVNQRElGX09VVABTUERJRl9PVVQA
AAgJFQABAAL/HUFVRElPAEFVRElPAAAICRYAAQACCAlDT00gMQBDT00gMQAACAkX
AAEAAh8dQXVkaW8gTGluZSBPdXQxAEF1ZGlvIExpbmUgT3V0MQAACAkYAAEAAh8d
QXVkaW8gTGluZSBPdXQyAEF1ZGlvIExpbmUgT3V0MgAACAkZAAEAAh8dQXVkaW8g
TGluZSBPdXQzAEF1ZGlvIExpbmUgT3V0MwAACAkaAAEAAh8dQXVkaW8gTGluZSBP
dXQ0AEF1ZGlvIExpbmUgT3V0NAAACAkbAAEAAh8dQXVkaW8gTGluZSBPdXQ1AEF1
ZGlvIExpbmUgT3V0NQAACAkcAAEAAh8dQXVkaW8gTGluZSBPdXQ2AEF1ZGlvIExp
bmUgT3V0NgAACAkdAAEAAiERSUUxMzk0XzEASUUxMzk0XzEAAAgJHgABAAIhEUlF
MTM5NF8yAElFMTM5NF8yAAAICR8AAQACCx9MQU4gMgBHYkUgTEFOIDEAAAgJIAAB
IgAAIFNBVEExAAAICSEAASIAACBTQVRBMgAACAkiAAEiAAAgU0FUQTMAAAgJIwAB
IgAAIFNBVEE0AAAICSQAASIAACBTQVRBNQAACAklAAEiAAAgU0FUQTYAAAgJJgAB
IgAAIFBSSV9FSURFAAAICScAASIAACBTQVRBRTEAAAgJKAABIgAAIFNBVEFFMgAA
CAkpAAEXAAD/RkxPUFBZAAAICSoAARwAAB1DRAAACAkrAAEfAAAdQUFGUAAACAks
AAH/AAD/Q1BVX0ZBTgAACAktAAH/AAD/UFdSX0ZBTgAACAkuAAH/AAD/Q0hBX0ZB
TjEAAAgJLwAB/wAA/0NIQV9GQU4yAAAICTAAAf8AAP9DSEFfRkFOMwAACAkxAAEc
AAAdRlBfQVVESU8AAAkNMgABpQUEAwEADAFQQ0lFWDE2XzEAAAkNMwABpQYEAyIA
DAFQQ0lFWDFfMQAACQ00AAGlBQMDIwAMAVBDSUVYMV8yAAAJDTUAAaUFAwMCAAwB
UENJRVgxNl8yAAAJDTYAAQYFAwMDAAwBUENJXzEAAAkNNwABBgUDAwQADAFQQ0lf
MgAACQ04AAGlBQMDBgAMAVBDSUVYMTZfMwAACgY5AIUBIE9uYm9hcmQgRXRoZXJu
ZXQAAAsFOgAEVG8gQmUgRmlsbGVkIEJ5IE8uRS5NLgBUbyBCZSBGaWxsZWQgQnkg
Ty5FLk0uAFRvIEJlIEZpbGxlZCBCeSBPLkUuTS4AVG8gQmUgRmlsbGVkIEJ5IE8u
RS5NLgAADAU7AAFUbyBCZSBGaWxsZWQgQnkgTy5FLk0uAAANFjwAAf8AAAAAAAAA
AAAAAAAAAAABZW58VVN8aXNvODg1OS0xAAAPNz0A8AMQIBAgoAEAAAAAAMD9/wAJ
AgEDAgMDAgUCCAQJAwoDEAagBP//////////////////AAAQDz4AAwMDAABAAP7/
BAAAABMPPwAAAAAA//9/AD4ABAAAERtAAD4A/v9AAEAAAAgJAAECE4AAmwIDBAUG
RElNTTAAQkFOSzAATWFudWZhY3R1cmVyMDAAU2VyTnVtMDAAQXNzZXRUYWdOdW0w
AE1vZHVsZVBhcnROdW1iZXIwMAAAFBNBAAAAAAD//x8AQAA/AAEAAQAAERtCAD4A
/v9AAEAAAAgJAAECE4AAmwIDBAUGRElNTTEAQkFOSzEATWFudWZhY3R1cmVyMDEA
U2VyTnVtMDEAQXNzZXRUYWdOdW0xAE1vZHVsZVBhcnROdW1iZXIwMQAAFBNDAAAA
IQD//0AAQgA/AAEAAQAAERtEAD4A/v9AAEAAAAgJAAECE4AAmwIDBAUGRElNTTIA
QkFOSzIATWFudWZhY3R1cmVyMDIAU2VyTnVtMDIAQXNzZXRUYWdOdW0yAE1vZHVs
ZVBhcnROdW1iZXIwMgAAFBNFAAAAIQD//0AARAA/AAEAAQAAERtGAD4A/v9AAEAA
AAgJAAECE4AAmwIDBAUGRElNTTMAQkFOSzMATWFudWZhY3R1cmVyMDMAU2VyTnVt
MDMAQXNzZXRUYWdOdW0zAE1vZHVsZVBhcnROdW1iZXIwMwAAFBNHAAAAIQD//0AA
RgA/AAEAAQAAIBRIAAAAAAAAAAAAAAAAAAAAAAAAAH8ESQAAAA==

--------------------------------------------------------------------------------

LPC W836XX

Chip ID: 0xA510
Chip revision: 0x13
Base Adress: 0x0290

Hardware Monitor Registers

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00 04 FF 04 FF 00 00 3C 20 01 9B 01 01 3C 3C 04 04
10 04 FF 30 00 00 01 01 3C 43 17 00 00 28 FF FF C9
20 AE D7 D1 CF CD FF 9E 27 FF FF FF DA 00 01 00 88
30 12 95 A1 00 06 E1 03 E2 00 04 00 28 41 84 A4 54
40 03 00 00 FF FF 00 3F 35 2D 21 20 40 10 95 00 A3
50 FF FF 00 FF FF FF 00 80 C1 6F FF FF 19 44 04 05
60 04 FF 50 00 01 01 3C FF 0A FF 01 FF FF FF FF 00
70 00 00 00 00 00 FF FF FF FF FF FF 4B 22 00 27 FF
Bank 1
50 29 80 00 4B 00 50 05 BE FF FF FF FF FF FF FF FF
Bank 2
50 18 00 00 4B 00 50 1A 00 FF FF FF FF FF FF FF FF
Bank 3
50 06 02 06 04 04 04 05 06 02 00 00 D0 27 0A 00 00
Bank 4
50 00 13 FF 00 00 F2 00 0C 67 DE 19 AB 09 5F 20 7F
Bank 5
50 D4 0C 00 FF 2C 03 00 01 00 04 00 00 A0 00 00 00
Bank 6
50 7F 7F 7F 7F 7F 7F 00 02 00 01 00 0A 07 D8 00 02
Bank 7
50 67 E9 0C 10 3C A3 C4 84 80 64 08 68 22 0F 00 00
Bank 8
50 08 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 9
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 10
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 11
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 12
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 13
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 14
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Bank 15
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

--------------------------------------------------------------------------------

CPUID

Processor 0

Processor Vendor: Intel
Processor Brand: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Family: 0x6
Model: 0xF
Stepping: 0xB

CPUID Return Values

CPU Thread: 0
APIC ID: 0
Processor ID: 0
Core ID: 0
Thread ID: 0

Function EAX EBX ECX EDX
00000000 0000000A 756E6547 6C65746E 49656E69
00000001 000006FB 00040800 0000E3BD BFEBFBFF
00000002 05B0B101 005657F0 00000000 2CB43049
00000003 00000000 00000000 00000000 00000000
00000004 0C000121 01C0003F 0000003F 00000001
00000005 00000040 00000040 00000003 00000020
00000006 00000001 00000002 00000001 00000000
00000007 00000000 00000000 00000000 00000000
00000008 00000400 00000000 00000000 00000000
00000009 00000000 00000000 00000000 00000000
0000000A 07280202 00000000 00000000 00000503
80000000 80000008 00000000 00000000 00000000
80000001 00000000 00000000 00000001 20000000
80000002 65746E49 2952286C 726F4320 4D542865
80000003 51203229 20646175 20555043 51202020
80000004 30303636 20402020 30342E32 007A4847
80000005 00000000 00000000 00000000 00000000
80000006 00000000 00000000 10008040 00000000
80000007 00000000 00000000 00000000 00000000
80000008 00003024 00000000 00000000 00000000

CPU Thread: 1
APIC ID: 1
Processor ID: 0
Core ID: 1
Thread ID: 0

Function EAX EBX ECX EDX
00000000 0000000A 756E6547 6C65746E 49656E69
00000001 000006FB 01040800 0000E3BD BFEBFBFF
00000002 05B0B101 005657F0 00000000 2CB43049
00000003 00000000 00000000 00000000 00000000
00000004 0C000121 01C0003F 0000003F 00000001
00000005 00000040 00000040 00000003 00000020
00000006 00000001 00000002 00000001 00000000
00000007 00000000 00000000 00000000 00000000
00000008 00000400 00000000 00000000 00000000
00000009 00000000 00000000 00000000 00000000
0000000A 07280202 00000000 00000000 00000503
80000000 80000008 00000000 00000000 00000000
80000001 00000000 00000000 00000001 20000000
80000002 65746E49 2952286C 726F4320 4D542865
80000003 51203229 20646175 20555043 51202020
80000004 30303636 20402020 30342E32 007A4847
80000005 00000000 00000000 00000000 00000000
80000006 00000000 00000000 10008040 00000000
80000007 00000000 00000000 00000000 00000000
80000008 00003024 00000000 00000000 00000000

CPU Thread: 2
APIC ID: 2
Processor ID: 0
Core ID: 2
Thread ID: 0

Function EAX EBX ECX EDX
00000000 0000000A 756E6547 6C65746E 49656E69
00000001 000006FB 02040800 0000E3BD BFEBFBFF
00000002 05B0B101 005657F0 00000000 2CB43049
00000003 00000000 00000000 00000000 00000000
00000004 0C000121 01C0003F 0000003F 00000001
00000005 00000040 00000040 00000003 00000020
00000006 00000001 00000002 00000001 00000000
00000007 00000000 00000000 00000000 00000000
00000008 00000400 00000000 00000000 00000000
00000009 00000000 00000000 00000000 00000000
0000000A 07280202 00000000 00000000 00000503
80000000 80000008 00000000 00000000 00000000
80000001 00000000 00000000 00000001 20000000
80000002 65746E49 2952286C 726F4320 4D542865
80000003 51203229 20646175 20555043 51202020
80000004 30303636 20402020 30342E32 007A4847
80000005 00000000 00000000 00000000 00000000
80000006 00000000 00000000 10008040 00000000
80000007 00000000 00000000 00000000 00000000
80000008 00003024 00000000 00000000 00000000

CPU Thread: 3
APIC ID: 3
Processor ID: 0
Core ID: 3
Thread ID: 0

Function EAX EBX ECX EDX
00000000 0000000A 756E6547 6C65746E 49656E69
00000001 000006FB 03040800 0000E3BD BFEBFBFF
00000002 05B0B101 005657F0 00000000 2CB43049
00000003 00000000 00000000 00000000 00000000
00000004 0C000121 01C0003F 0000003F 00000001
00000005 00000040 00000040 00000003 00000020
00000006 00000001 00000002 00000001 00000000
00000007 00000000 00000000 00000000 00000000
00000008 00000400 00000000 00000000 00000000
00000009 00000000 00000000 00000000 00000000
0000000A 07280202 00000000 00000000 00000503
80000000 80000008 00000000 00000000 00000000
80000001 00000000 00000000 00000001 20000000
80000002 65746E49 2952286C 726F4320 4D542865
80000003 51203229 20646175 20555043 51202020
80000004 30303636 20402020 30342E32 007A4847
80000005 00000000 00000000 00000000 00000000
80000006 00000000 00000000 10008040 00000000
80000007 00000000 00000000 00000000 00000000
80000008 00003024 00000000 00000000 00000000

--------------------------------------------------------------------------------

Intel CPU

Name: Intel Core 2 Quad Q6600
Number of Cores: 4
Threads per Core: 1
Timer Frequency: 3.515556 MHz
Time Stamp Counter: Not Invariant
Time Stamp Counter Frequency: 3600.33 MHz

MSR Core #1

MSR EDX EAX
000000CE 001B0926 7F7F071A
00000198 09260926 06000826
0000019C 00000000 88250000
000001A2 00000000 00001200

MSR Core #2

MSR EDX EAX
000000CE 001B0926 7F7F071A
00000198 09260926 06000826
0000019C 00000000 88280000
000001A2 00000000 00001200

MSR Core #3

MSR EDX EAX
000000CE 001B0926 7F7F071A
00000198 09260926 06000826
0000019C 00000000 882A0000
000001A2 00000000 00001200

MSR Core #4

MSR EDX EAX
000000CE 001B0926 7F7F071A
00000198 09260926 06000826
0000019C 00000000 88300000
000001A2 00000000 00001200

--------------------------------------------------------------------------------

AMD Display Library

Status: -1

--------------------------------------------------------------------------------

NVAPI

Version: NVidia Complete Version 1.10
Number of GPUs: 1

--------------------------------------------------------------------------------

Nvidia GPU

Name: NVIDIA GeForce 9600 GT
Index: 0
Driver Version: 258.96
Driver Branch: r256_stable_charlie-83

Thermal Settings

Sensor[0].Controller: GPU_INTERNAL
Sensor[0].DefaultMinTemp: 0
Sensor[0].DefaultMaxTemp: 127
Sensor[0].CurrentTemp: 61
Sensor[0].Target: GPU

Clocks

Clock[0]: 650000
Clock[1]: 1
Clock[8]: 900000
Clock[9]: 3
Clock[10]: 277780
Clock[11]: 1
Clock[12]: 416666
Clock[13]: 1
Clock[14]: 1600000
Clock[15]: 1
Clock[16]: 187005
Clock[17]: 1
Clock[18]: 375000
Clock[19]: 1
Clock[24]: 450000
Clock[25]: 1
Clock[26]: 450000
Clock[27]: 1
Clock[64]: 650000
Clock[92]: 900000
Clock[99]: 277780
Clock[106]: 416666
Clock[113]: 1600000
Clock[120]: 187005
Clock[127]: 375000
Clock[148]: 450000
Clock[155]: 450000

Tachometer

Status: NOT_SUPPORTED

P-States

Percentage[0]: 0
Percentage[1]: 1
Percentage[2]: 0

Usages

Usage[1]: 1
Usage[3]: 58
Usage[4]: 23
Usage[5]: 1
Usage[6]: 1
Usage[7]: 58
Usage[8]: 23
Usage[9]: 1
Usage[11]: 58
Usage[12]: 23

Cooler Settings

Cooler[0].Type: 1
Cooler[0].Controller: 1
Cooler[0].DefaultMin: 35
Cooler[0].DefaultMax: 100
Cooler[0].CurrentMin: 35
Cooler[0].CurrentMax: 100
Cooler[0].CurrentLevel: 39
Cooler[0].DefaultPolicy: 16
Cooler[0].CurrentPolicy: 16
Cooler[0].Target: 7
Cooler[0].ControlType: 2
Cooler[0].Active: 1

Memory Info

Value[0]: 524288
Value[1]: 499264
Value[2]: 0
Value[3]: 3669564
Value[4]: 175672

--------------------------------------------------------------------------------

S.M.A.R.T Data

Drive name: WDC WD10EADS-00L5B1

ID RawValue WorstValue AttrValue Name
1 00 00 00 00 00 00 200 200 ReadErrorRate
3 98 1A 00 00 00 00 160 163 SpinUpTime
4 CF 05 00 00 00 00 99 99 StartStopCount
5 00 00 00 00 00 00 200 200 ReallocatedSectorsCount
7 00 00 00 00 00 00 253 100 SeekErrorRate
9 7A 2F 00 00 00 00 84 84 PowerOnHours
10 00 00 00 00 00 00 100 100 SpinRetryCount
11 00 00 00 00 00 00 100 100 RecalibrationRetries
12 AC 02 00 00 00 00 100 100 PowerCycleCount
192 03 01 00 00 00 00 200 200 192
193 CC 05 00 00 00 00 200 200 193
194 23 00 00 00 00 00 87 115 Temperature
196 00 00 00 00 00 00 200 200 ReallocationEventCount
197 00 00 00 00 00 00 200 200 CurrentPendingSectorCount
198 00 00 00 00 00 00 200 200 UncorrectableSectorCount
199 00 00 00 00 00 00 200 200 UltraDMACRCErrorCount
200 00 00 00 00 00 00 200 200 WriteErrorRate
132 7B 03 00 01 00 02 1 91 132
5 00 00 00 00 00 00 0 0 ReallocatedSectorsCount
1 00 00 00 00 00 00 0 0 ReadErrorRate

Drive name: WDC WD10EAVS-00D7B1

ID RawValue WorstValue AttrValue Name
1 00 00 00 00 00 00 200 200 ReadErrorRate
3 AF 19 00 00 00 00 158 168 SpinUpTime
4 BD 01 00 00 00 00 100 100 StartStopCount
5 00 00 00 00 00 00 200 200 ReallocatedSectorsCount
7 00 00 00 00 00 00 253 100 SeekErrorRate
9 40 1A 00 00 00 00 91 91 PowerOnHours
10 00 00 00 00 00 00 100 100 SpinRetryCount
11 00 00 00 00 00 00 100 100 RecalibrationRetries
12 8D 00 00 00 00 00 100 100 PowerCycleCount
192 4B 00 00 00 00 00 200 200 192
193 7F 01 00 00 00 00 200 200 193
194 24 00 00 00 00 00 93 114 Temperature
196 00 00 00 00 00 00 200 200 ReallocationEventCount
197 00 00 00 00 00 00 200 200 CurrentPendingSectorCount
198 00 00 00 00 00 00 200 200 UncorrectableSectorCount
199 00 00 00 00 00 00 200 200 UltraDMACRCErrorCount
200 00 00 00 00 00 00 200 200 WriteErrorRate
130 7B 03 00 01 00 02 1 91 130
5 00 00 00 00 00 00 0 0 ReallocatedSectorsCount
1 00 00 00 00 00 00 0 0 ReadErrorRate

Drive name: Maxtor 6V080E0

ID RawValue WorstValue AttrValue Name
3 4C 1F 00 00 00 00 221 224 SpinUpTime
4 1A 07 00 00 00 00 253 253 StartStopCount
5 D0 03 00 00 00 00 176 176 ReallocatedSectorsCount
7 00 00 00 00 00 00 252 253 SeekErrorRate
8 12 F4 00 00 00 00 232 247 SeekTimePerformance
9 54 7D 00 00 00 00 161 161 PowerOnHours
10 00 00 00 00 00 00 252 253 SpinRetryCount
11 00 00 00 00 00 00 252 253 RecalibrationRetries
12 E3 08 00 00 00 00 248 248 PowerCycleCount
189 00 00 00 00 00 00 100 100 189
190 28 00 1D 31 00 00 39 60 AirflowTemperature
192 00 00 00 00 00 00 253 253 192
193 00 00 00 00 00 00 253 253 193
194 28 00 00 00 00 00 253 33 Temperature
195 C7 49 00 00 00 00 252 253 HardwareECCRecovered
196 00 00 00 00 00 00 253 253 ReallocationEventCount
197 1F 00 00 00 00 00 200 251 CurrentPendingSectorCount
198 01 00 00 00 00 00 252 252 UncorrectableSectorCount
199 00 00 00 00 00 00 199 199 UltraDMACRCErrorCount
200 00 00 00 00 00 00 252 253 WriteErrorRate
201 00 00 00 00 00 00 252 253 201
202 00 00 00 00 00 00 250 253 202
203 00 00 00 00 00 00 252 253 203
204 00 00 00 00 00 00 252 253 204
205 00 00 00 00 00 00 252 253 205
207 00 00 00 00 00 00 252 253 207
208 00 00 00 00 00 00 252 253 208
210 00 00 00 00 00 00 252 253 210
211 00 00 00 00 00 00 252 253 211
212 00 00 00 00 00 00 252 253 212
130 5B 03 00 01 00 02 1 3 130
59 56 E9 08 06 00 00 25 0 59
191 00 00 00 00 00 00 0 9 191[/w]

Using that to complement opencl/cal readings, and with a proper way to load up all the gpu's, binding specific sensor readings to any client is not that hard even without having to rewrite ohmlib.

The opencl toolkit comes with some samples which can easilly be converted in a simple burn in module ( maybe memtest opencl as well even if it's not a core benchmark it does cause load and it will be visible in the sensor reports ( no, you don't have to parse that text file each run, but you already seen that I hope ).

I also updated my repo copy to latest, I had a very old version I guess. I think you could make use of my config screen as well, if not entirely then partia;;y that's up to you. fTray is GPL but I will make an exception for you if you need anything from it ( as lonh as you.. uhm do as I asked you in pm and remove that distrurbing post ).

Really man, that's not the way to move forward. I know I been dissapointed more then once by PG probaly more then others as well but I still resopect their work to much to put it on the line for some personal conviction that they are wrong ( in not releasing something when I feel it should be released ).

Adding to that, I am also a beta tester for folding forum, don't make it hard for me to be around here I would really dislike being forced away, you got a good project going on and I want to help if I can and if time/other projects permit.

something I thought about when I was walking the dog, need to post it now as I will forget it otherwise I'm afraid..

The source for that configuration form is rather old, started it with the old smp clients and that's why I have wait statements ( need to edit those back to doevents, process.sleep messes things up more then it fixes ) and more importantly I also attach standard out to a streamreader so I could 'check' when the client was ready for input. I notice you have a 500ms wait before sending settings to the console clients but that was not enough with the old smp clients and sometimes the gpu clients as well, they can 'hang' on startup. If you redirect their standardout as well you can monitor that, have the thread where you write settings wait untill the clients output "CONFIGURING FOLDING@HOME". It's not possible to write step by step after that though, the standardout of the clients didn't recieve each question as when run without redirected output ( or it would be easier to do things, and not require multiple runs to read/write ) so you have to batch write the settings as you're doing now. And you're not actually writing to the parameters field I see so you don't need checks to see if the client accepted the input, you might be fine as is with the new smp client as well as long as you don't actually write to that particular field.

Then again, it's always nice to have certainty the client accepted all the settings aa you gave it so being able to read back is always a bonus, it will also allow you to display a gui for client settings as they are configured right now ( without needing to rely on unreliable storage of settings in any way outside of the client ( as you never know when someone reconfigures a client outside of your program )..

I dont know if this means anything to you but this section is completely open for public viewing.

I hope this doesn't mean bloat being added to the tracker. I like how things presently are unless of course you give the end user a choice like a Lite and Ultimate version.

B2K24 wrote:I hope this doesn't mean bloat being added to the tracker. I like how things presently are unless of course you give the end user a choice like a Lite and Ultimate version.

I won't ever add excessive bloat to the Tracker. I like the way it is now as far as the mix of simplicity and functionality. When I add new features I always consider if the added complexity is worth it.

Perhaps further down the line I may decide to create a lite and advanced version (lite would be for noobs or those just looking for a very simple folding interface, and advanced would be for power users who want advanced features and control)

I would implement this in one of 2 ways:
1. Have an option in the config to enable advanced features (so the advanced stuff would be hidden when this isn't enabled)
2. Have 2 separate programs that you can switch between similar to how the Tracker updates itself

I don't think that having 2 versions is necessary at the moment.

One of the first things that came to mind when I saw these latest comments was "Oh crap were becoming microsoft." But I do have to agree with jedi, we simply dont have the user base or the requests for this complexity or the need to 2 versions. We must alway remember we built the tracker to make it simple to fold so anyone could just set it up easyly and go. There may come a time when we need more than one program interface but it isnt now. To be honest in the terms of a programs life this one is in its infancy. Give it time to mature. We add features at the requests of the users only after considering how it would effect the layout, how we would implement it with an easy to control setup and its effect on user simplicity.

I like the idea of being able to enable an advanced user mode that would allow for more configuration and features. I would love to see the ideas MtM implemented if possible . The Tracker is quite a small download and it being a little bigger I do not believe a slightly larger download would turn anyone off from the Tracker, and may get more users if it had all the possible features MtM talks of. I trust Jedi will use his best judgement and not let the Tracker become bloated and bug prone. The website ability MtM is particularly interesting to me as I have a lot of machines at different locations that fold for me and members of my team. Hope this all can be worked in a constructive productive manner.

JayCop wrote:I like the idea of being able to enable an advanced user mode that would allow for more configuration and features. I would love to see the ideas MtM implemented if possible . The Tracker is quite a small download and it being a little bigger I do not believe a slightly larger download would turn anyone off from the Tracker, and may get more users if it had all the possible features MtM talks of. I trust Jedi will use his best judgement and not let the Tracker become bloated and bug prone. The website ability MtM is particularly interesting to me as I have a lot of machines at different locations that fold for me and members of my team. Hope this all can be worked in a constructive productive manner.

MtM is developing his own program that is separate from the Tracker. Those features will be a part of his program. As for the size of the program I wasn't talking only about the resulting filesize. The total amount of code would also end up getting significantly larger. This can make fixing problems a lot more work.

Some clarification, for if things were not clear already from Jedi's comments.

I see gpu tracker as a 'lite' version of what I am working on, I said that in the first post as well. The main idea of gpu tracker is setting up clients and make them fold, the main idea of cftUnity is to do the same, and then add these functions ->

1. Advanced GUI for tracking single clients

* note this is fTray which is put on the backburner, it's now a usercontrol ( object usable in/on other form's/projects and that version will offer sensor readings from the hardware the client is running on -> load,temperate, fan speed. The heat control from gpu tracker is set up according to preset work unit's ranges, the heat control I will offer is set up by maximum allowed temperate aka it will be fully automatic.
2. The above view will be put in a tabcontrol, with the main tab offering a list of running clients containing client state's/ppd/eta's ect abit like this ->

* Note - but then without fahlog and queue.dat summary view, but with added sensor readings from the hardware each client run's on.

The diffrences are getting smaller with all additions Jedi95 is making, but I do not mind that at all. I would not get upset if all the things I plan on doing will also be a part of gpu tracker, I feel the things I plan on doing are usefull and therefore it should not matter where it's done or by who. My intentions with helping and offering some pointers or information are simply because I see gpu tracker is being actively developed and has a people actually using it and giving good feedback on it. That also helps me to get a feeling of what people want and how they want it.

The biggest diffrence at this time is that I plan on making a web back end for cftUnity, I have hosting but since I only program in .net a php site is over my head ( and getting asp.net hosting costs allot of money ). So I have a home server and 120/10mbit connection, and plan on hosting the main cftUnity site with the hosting company and have an iframe relaying some functions from my home server.

The intentions of the back end is collecting statistics as here ->

* Note this an old screen shot of a working copy of maxTray ( one of my abandond projects, so don't get caught up in how it's not finished or how it looks totally unusable with the frame time's for each project not being distinquisable from the others ( you can lower the amount of projects shown in the view by selecting diffrent settings ). Also, there is no hardware information displayed as it was not gatherd yet.

Some of my code is quite old and originates from an earlier attempt ( on of many ) to make an installer/manager )


The code for this installer is here -> http://code.google.com/p/maxfah/source/browse/#svn/trunk

Maybe that will also explain why I reacted abit negative when I heard about gpu tracker, not only does it look like something I wrote even before maxFah ( the gui ), it's also using code changes from that project ( hw detection I wrote for maxFah is almost a complete match with GPU tracker, down to using cuda.net and wmi for cpu information ).

Again, it's not important to me anymore nor am I saying Jedi95 is using code from my earlier programs as GPU tracker is a very much stand alone project which he is actively developing and making additions to on his very own ( the biggest one which I hadn't looked at is the heat control he's offering which is a great addition even if it's only done on a preset user definied manner ).

So, Jedi95 put me in the developers user group ( even if I already had repository acces ) and as such I can see the source code but I can not commit any changes, he's doing all the actual code writing for gpu tracker on his own. The thing I can and am offering is giving advice or sending small snippets of code on how to do certain things but I do not plan on actually incorporating them into the gpu tracker code ( first of all, it's well written but not that easy to add/change portions if you're not familiar with the entire project, it's not that much object based not as much as I would like to be able to change things quickly ). I already advices Jedi95 to make it more object based and move more code to seperate classes instead of the main form but that would mean rewriting it from scratch, something which will take time. It would certainly be easier for him to maintain gpu tracker in the long run if he did that but I think it also goes against his intent with the project. He will add functions which are asked for but wants to keep it very minimal, and for minimal changes a rewrite is not needed.

On the opposite end of that spectrum is my project, I do want it to be very easy to make changes to, as I hope that at one point I will get permission and put the entire project as open source project on google code and get other people to join as members/committers. My earlier attempts at doing that failed because I programmed much like gpu tracker, which is fine for a project maintained by a single person, but not so much for a collateral project for the reason explained above.

A last note on code size, gpu tracker source code is 1.8MB and for fTray it's 2.4MB, don't think that's a big diffrence, if I would not include the code from the configuration form it would be almost the same. If I would include the tracker classes for statistics from maxTray ( which I can't just attach as maxTray was so nested it took me a long time to just extract the parts now used in fTray ) the diffrence would be much larger, and if I would compare it the code in cftUnity which is not yet ready for even showing some screenshots of it ( later today, on the cftunity site if I get time to put that online ) the diffrence would be noticable.

But, what are you talking about... as the executable will still be much smaller then the netload you will see from running the folding clients, it should not matter that much how big the project file is?

Edit:

@CadBane, the idea of both projects ( gpu tracker and my own ) define a need for anything related to it being public no? If Jedi95 does not want certain aspects of both programs being discussed in a public place, maybe he does not want to talk about the source code or how gpu tracker does certain things, you and he have full control over the contents of my posts. I don't think keeping anything behind the curtains will help though, not with getting a good community behind the project(s) nor with obtaining permission from PandeGroup to download clients. Hiding things makes things look suspicious is my opinion, and that is also a reason for making my project open source ( cftUnity will be made publicly accesible when it's in alpha stage, aka when it's able to compile and be tested ).

The diffrence in intention behind both projects may influence how Jedi95 looks at making his project open source for the public not only those in the developer group at his website. Yes, there is a chanche someone will rip him off, and that will not be a pleasant experience I know all about that, but does it weigh up against the benefits of being transparant and maybe getting more people to help him/give advice.

MtM wrote:
@CadBane, the idea of both projects ( gpu tracker and my own ) define a need for anything related to it being public no? If Jedi95 does not want certain aspects of both programs being discussed in a public place, maybe he does not want to talk about the source code or how gpu tracker does certain things, you and he have full control over the contents of my posts. I don't think keeping anything behind the curtains will help though, not with getting a good community behind the project(s) nor with obtaining permission from PandeGroup to download clients. Hiding things makes things look suspicious is my opinion, and that is also a reason for making my project open source ( cftUnity will be made publicly accesible when it's in alpha stage, aka when it's able to compile and be tested ).

I don't have any problem with discussing how the Tracker works in the public forum, CadBane just wanted to make sure you realized that this section was public.

MtM wrote:
The diffrence in intention behind both projects may influence how Jedi95 looks at making his project open source for the public not only those in the developer group at his website. Yes, there is a chanche someone will rip him off, and that will not be a pleasant experience I know all about that, but does it weigh up against the benefits of being transparant and maybe getting more people to help him/give advice.

I may open source the Tracker eventually, but as you said it isn't exactly in a state where it would be easy to work on without understanding how the entire thing works. This project has been a learning experience for me as a programmer. If I were to redo the Tracker from scratch today I would do a lot of things differently.

I will open source the Tracker if either of the following happens:

1. I move on from this project and as a result I no longer maintain it.
2. I clean up the code to the point where it is possible for other developers to easily understand how things work.

I didn't say it's impossible to work on, it's just not something which you can make quick changes on. The ohm issue I linked you to explains that better then I can.

About publicity, maybe cadbane was pointing out that I made somewhat of a change in percievement. I been quite negative about gpu tracker before, reasons above, and maybe he wanted to point out to me I'm now actually supporting it publicly? If that is the reason he wanted to make it clear, well I did already tell Jedi95 I do not object if he took parts of the source from fTray or maxFah to put in gpu tracker, infact it would be stupid if I did. Tbh, gpu tracker = maxFah without the bloat, it uses the same methods to do things with the big diffrence being gpu tracker is working since the bloat was causing maxFah to be a project which I could not support. I could not replicate issues reported and even if I could, making changes to maxFah prooved to be such a pain stacking endavour since it was to nested. Changing a small thing in the setup procedure made the client control class not work, since the client control class also was part of the setup class. Maybe that's not saying much to those who have no understanding of programming but here comes the anticipated car anologie... maxFah was a car where all parts where welded together. If you had to change a tire, you would have to unweld some parts of the body to get acces to the wheel, then cut of the weel, change the tire and then weld everything back into place. With the problem that if you put on a bigger tire, you needed to change the whole body work.

Now I know car analogies don't always work for those who already understand it, but maybe it's easier to understand for others.

I could work on gpu tracker now, but I would rather spend time coding for cftUnity and make that project public when it's alpha ready. And Jedi95 is perfectly capable of making changes/additions himself to gpu tracker where he sees a need for them, and if he needs help getting something working only have to give a snippet explaining how something works without putting it in the tracker code. Gpu tracker is his project, I'm supporting it and would make code changes when asked but there as of now is no need for it.

Now, off to work

No no no it looked like you were posting code and just wanted to make sure you knew this section was public just in case. Jedi explained its not exactly code so its ok. I was just trying to watch out for you in good faith. I wasnt trying to say anything bad, its just at first glance it looked like code so I wanted to warn you.


CadBane

cadBane, my code is publicly accesible anyway.

It's also bound by a gpl license, the repository code I mean not anything I post in a public forum. So, everything I post here people are free to use/abuse in what way they want. Anything anyone wants to use from the repository is bound by the included license conditions. The exception to this is Jedi95 who I've given permission to use portions/pieces without the need to make his entire code open source ( which is a big part of the gpl license ). I make the exception for him becaus he sees his project as a learning project and does not want to make the code public ( yet atleast ). I also make the exception because I don't feel he will abuse it, since we already clearly established that we have diffrent goals in mind.

Hello, been off the internetz for some time, just dropping bye to see how things are. And I like what I see

And that means I have no real reason to keep working on my own project, which got into a stand still trying to develop a skinnable interface ( anti-aliasing didn't seem to work, custom shaped graphicspath just looked bad the way I went about it and I couldn't find anything on how to do it differently.

And, the main difference between jedi's program and what I planned on doing is getting really really small, the only difference at this time is that I wanted/have hw tracking ( temperature/usage ) inside the application. All things I planned.worked on before on my own are now either part the tracker, or being added at this time by others. And tbh, I have more faith in Jedi and you all working on adding/perfecting the tracker application then in my own ability to do everything alone and better ( if it wouldn't be better, why do it in the first place ). There are some things I worked on which I think would be useful for the tracker, like the ohm mod hardware detection and tracking/internal ocl, cuda and cal detection. Think that wouldn't be a straight drop in expansion but it's not allot of work to incorporate it in the tracker.

I also wouldn't mind the tracker to use a graphical representation of the statistics gatherd instead of a list with numbers ( using zedgraph would be the easiest ). Zedgraph is not hard to implement either.

The web back end is btw one of the main reasons I don't feel like persuing cftunity any further, it was the most compelling reason I saw my project as having an added value over tracker, kudo's to the one('s) working on that.

I will change the license attached to any of my code to public domain if Jedi wants to use it, that way it's allot easier to say it's gpl'd but not for person X ( jedi95 ).

Welcome back its been a while.

Thank you, when you talk with Jedi tell him to pm me on msn, things are quicker that way.

I'm offcourse also curious as what you opinion is about extending the tracker with some of the things I wanted to use in my own project. gpu info and ohm interface are drop in additions ( they are a seperate dll, one for hwinfo and the modded openhardwaremonitorlib.dll ). But, the ui for them is the part I couldn't get as I wanted so those two libraries do not include any interface ( but, you could just query numbers and put them on a label, and mostly the thing I think which would be beneficial is the heat control ). And Jedi, yes I found a way to check 100% which gpu is which, using memtestCL. But the memtest wrapper is a stand alone project, but there is an easier way.

On startup, when starting clients, take measurements from all gpu's core load, start clients one at a time wait untill they output that the core is engaged, then check which gpu has their core load measurement increased ( should be 96 to 100 percent ). The delay to start the clients is neglicable, and once you have tied a client with a gpu it's no longer needed ( eg only on app startup, or when you change the gpu x flag for a client. )

I could built that into the current repository version if you think it's a good idea, and you can check the code/debug it and decide if it's something you want to use.

Hey MtM long time no see buddy

Ray!

Long time no see. You do remember my msn don't you? Saw you post on XS, thought heck if you want to get in touch with me don't I have the same addy as I've had for the past couple of years

Noticed you're folding your ass off, my hat's off to you Last thing I heared your circumstances wouldn't allow a farm the size you're running now it seems, glad to notice you're able to now as it means you're doing well!

Now, you can always pm me or try to contact me on msn ( I'm not always reachable the first time but give it a try ).

Btw, I finally got an official report about being autistic, can you imagine me having had that 5 years or more back?! Would have made my life allot easier I can tell you that much. Well atleast I think it would have, not sure, not even sure what the consequences are right now but I won't clutter this forum with my well known ramblings ( other then already done right now ).

And to add something to this post which is more suited for the forums here: hw monitoring through ohm... CHECK! oCL info.... CHECK! CAL info CHECK... CUDA info CHECK! memtestCL wrapper working on ( need to clean my os, wrapper can't be tested if I can't even run the application itself ( mixing openCL.dll from ati/nvidia mixed drivers idk, reinstalling latest whql didn't fix it and a reinstall of the whole os + applications will take me a day or so to get everything back into proper order... bleh!

Things which need doing, since I been out of the fold somewhat I have to recheck arguments needed for specific hardware to run but that's only worth mentioning because it is time consuming. And the client wrapper itself, which monitors and controls the clients, that I think I'll rewrite so it acts as a client container ( run the process inside the wrapper instead of seperate and parsing log output when notified by filesystem watcher ). It will be more reliable and efficient.

I'm pretty stupid btw, again already focussing on non important details ( skins / non standard UI ), and that while I SUCK as photochop! But, can't change who I am.. and while the skin looks UGLY I still like it more then the standard form interface.. And I think I'm done with skinning, only needed one main window skin and two diffrent dialog skins, but then again I haven't tested the monitoring gauges ( temp/load ect ) on the new skin so maybe it won't work and I need to redo everything again. We'll see.

Matey i will read through it laters as my time sucks to be honest
i will sort the MSN out ASAP as i just checked and i can't find you (YET) ...

but i will find you bro as i don't want to lose track (LOL tracker) on you again
but as i said give me some time as i am a full blown Body Builder now

Ow and thanks for the tracker guys and Martin already donated my share

High school diplomas are generally considered more desirable for one entering the work force or hoping to pursue a higher education. About.com's survey suggests that employees with diplomas generally earn significantly more than those without. Students who hope to advance may be required to pursue additional training. Similarly, most students admitted to college have earned their high school diploma, although this does not guarantee acceptance. Coursework, grade point average and extracurricular activities will be important factors during the admissions process.

Our accredited high school diploma online school provides a permanent verification service to all students who graduate from our accredited high school diploma online program. Graduates can use this service throughout their lifetime as many times as as they may need. These services enable the potential employer to speak directly with a guidance counselor at our school to confirm a particular individual graduated with their high school diploma.