*Beta* Want to check your EUE rate?

[catawalks]

sounds great. Keep up the good work. I like that alerts option since I have a few network clients that are down myself.

[MikeB12]

I think the windows update yesterday fubbared this app.. I tried it this morning and all I get is a quick flash and it shuts down..
so I updated to the latest here just now and same thing. all it does is flash the window for a microsecond and close.

[Marvin_The_Martian]

Ow uhm.. that's not a fluke, I had the expiration date set to 11-11-08, only one with a working copy atm is WFO I think

Reason: wanted to make sure people would update to the latest version, and I been just to stressed due to people making 'mistakes' which cause me to be unable to pay bills or buy food for the kid. It's not that bad, I got my money just today ( 9 weeks to late though ) and we weren't starving or close to being in real trouble, just had some bills bounce because of the debit limit, and well the only bday gift I threated myself on is still not in but even that's a luxery compared to what I know some other people have to live with.

I got a problem with finishing things I start with but the changes I made were pretty simple and I could just the version wfo also has online, but half the extra options don't work ( haven't been tested to say the least ). It's not the windowsupdates, I should have it put up an "expired" message but I just let it check and exit sorry for that.

Brb

edit: done uploaded the intermediate build but did not change version info. If it works as it should it will pop up on new found eue's ( tbh I forgot to have it running as well, so the 2 eue's it picks up in my logs now were never detected as new during runtime.. so I haven't confirmed it works but uhm.. it should

[Marvin_The_Martian]

Just figuring out what to do now, have it generate charts itself (bitmaps.. making charts isn't that hard I can save the content of a form as a picture ).

And I just noticed that due to the 3 updates the program missed during the night my 'totalpointsincontest' are off as well ( yeah I know, calculate it from new 'total points' minus 'total points at contest start' instead off adding up each update to get the number, that's an alternative way ).

But the way I had the download function work is the reason it chocked during the night, changed it to be allot more forgiving and keeping the application responsive.. but that means the download and subsequent processing takes close to 15 minutes or so

I wonder how quick the back end of eoc processes an entire update, and then to think I only do the donor list not the teams list ( thoug.. donor list is 25mb of text.. team list is a couple off hundred kb afaik ).

I can take 25% of the parsing time needed to process the statistics but that means the application will show up as 'hung' or not responsive during the parsing and I want to prevent that.

Just to be clear, it processes the entire donor list and fillters out xs members, saves them to a seperate datapoints text file for each update ( each datapoint is about 13kb, so it won't fill up that quick and I haven't thought about implementing a limit but I can in the future, just need time ( and not go around work on this and then on something else lol ).

You like Mike? It's ment to help you, I won't give this to everyone as it's get's the 25mb list from their servers each update, think if every xs member would have it the strain would be to high. It's abit like a stats generator, but then really focused on our contests.

[catawalks]

Nice work Marvin. That looks amazing. What do the charts look like that it generates?

[MikeB12]

yay! We have a new scorekeep volunteer.

that's nice, work on it for the next comp and showcase it... I've done these last 2 races manually, so that would be an excellent tool to use on the next one... and who better to utilize it than the man himself. we need some new volunteer blood on the field as refs..

[Marvin_The_Martian]

No I don't think you want me to do it, I'm abit unreliable

You see Team Tracker, but the assembly name is 'Mike Helper'

catawalks it currently just gives numbers.. not charts. Trying to work out wether to do charts using a form and dynamic controls on them or by using a 3rd party rapport generator

What do you think

Edit: btw idk if you noticed but the server binary for fahwatch was updated after you reminded me about it.

Edit2: Another option is to generate an html page on each update and upload that to my server, then I could run it after a contest is set up (need to define teams and members & start date) and it would run unattended. Problem is I got a bandwidth limit on my isp's webspace and their monitor doesn't work so it's impossible to check how much bw is used

[Marvin_The_Martian]

Updated fahWATCH, now reliable pops up on new eue's. Still not working with the own clients list hat some bug which bugged me and I didn't want to mess with it now. So that's still disabeld, as is the export and 'send repport' option ( which will be included in a future version which will have an installer included since I use a 3rd party zip lib. )

Working on the stats keeper is more interesting atm, also hit a bug.. somehow my contest members during an update now include every fah donor listed.. easy fix but I was wondering why it took so long to fill a listbox with team members

[MikeB12]

just dl'ed the new ver..
got new prob...

On launch I get this error..



full text of the error:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: String was not recognized as a valid DateTime.
   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at g.c(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
    Assembly Version: 1.0.0.7
    Win32 Version: 1.0.0.7
    CodeBase: file:///D:/Software/Folding/fahwatch/fahwatch.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

so I click continue and get here, but it's not reading anything.

[Marvin_The_Martian]

30-12-08 isn't really a valid date there... I knew that but still, I also knew I had to use an unc time and convert the local date to that but I didn't.

Should not error now. <- means server has updated binary

[MikeB12]

I PWN EUE !

[Marvin_The_Martian]

If I had more clients my percentage.. naw ok I'm trying to feel less bad hehe. 3 from 27 here, two on the 9600gt and a smp wu failed. That's not counting the vm on the other rig, which I don't have acces to anyway.

Mike play around with it, besides the unabeld features I think it's abit as it should be, I mean it should be stable and do as advertised without strange issues.

Edit: nope 2 from 27 not 3. Still high though, especially after reading how each eue is for the singularity of the gpu wu's. ( which I already knew though but needed a reminder ).

[Marvin_The_Martian]

Jezus am I psychic.. it eue'd just the second after I posted.. well ok not exactly but still

-FAHMON NAME:	9600GT
INDEX:		1
LOCATION:	C:\Program Files (x86)\Electronic Arts\
LOCAL CLIENT:	True
CLIENT:		Windows GPU Console Edition - Folding@Home Client Version 6.20r1
FLAGS:		-forceasm -verbosity 9 
CORE:		Folding@Home GPU Core - Beta - Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
StartTime:		21:09:30
StartPercentage:		35
EndTime:			21:09:31
EndPercentage:		35
-VIDEO CARD
Caption		NVIDIA GeForce 9600 GT
Description	NVIDIA GeForce 9600 GT
AdapterRam	512MB
DriverVersion	7.15.11.7784
DriverDate	20080806232600.000000-000
Index		0
InfSection	nv_G9x_HD
COMPILER:	Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
BUILDHOST:	amoeba
BOARD:		Nvidia
PROJECT:	Project: 5506 (Run 0, Clone 169, Gen 310)
CORESTATUS:	CoreStatus = 7A (122)
TIMESTAMP:	[21:09:34] 
[21:09:18] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[21:09:18] 
[21:09:18] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 
[21:09:18] Build host: amoeba
[21:09:18] Board Type: Nvidia
[21:09:18] Core      : 
[21:09:18] Preparing to commence simulation
[21:09:18] - Assembly optimizations manually forced on.
[21:09:18] - Not checking prior termination.
[21:09:19] - Expanded 45485 -> 246249 (decompressed 541.3 percent)
[21:09:19] Called DecompressByteArray: compressed_data_size=45485 data_size=246249, decompressed_data_size=246249 diff=0
[21:09:19] - Digital signature verified
[21:09:19] 
[21:09:19] Project: 5506 (Run 0, Clone 169, Gen 310)
[21:09:19] 
[21:09:19] Assembly optimizations on if available.
[21:09:19] Entering M.D.
[21:09:24] Will resume from checkpoint file
[21:09:27] Working on p5506_supervillin_e1
[21:09:30] Client config found, loading data.
[21:09:30] Resuming from checkpoint
[21:09:30] Starting GUI Server
[21:09:31] Verified work/wudata_08.log
[21:09:31] Verified work/wudata_08.edr
[21:09:31] Verified work/wudata_08.xtc
[21:09:31] Completed 35%
[21:09:31] mdrun_gpu returned 
[21:09:31] Calculated & specified T inconsisitent
[21:09:31] 
[21:09:31] Folding@home Core Shutdown: UNSTABLE_MACHINE
[21:09:34] CoreStatus = 7A (122)

Frsshly downloaded wu btw, not a checkpoint to resume from It got the same prcg again and it picked it up as it should now. Strange ( and reported ).

[Marvin_The_Martian]

Team tracker is fully working ( eg, no missed updates and I got the memory usage down to 300mb at peak ( with 112xxxx donors updates all in memory, before I sort it. Talking about working backwards.. think I did that so I could generate more graphs as well but it's not really needed ). Think I'm going to put it on the gf's rig after I upgraded her ram. Got some initial results with that chart lib as well, it's allot easier then I thought

[road-runner]

What files does this thing use in fahmon? After usong fahwatch once and closing it then trying open it again a few minutes later it hung and now fahmon is borked it seems, I have rebooted 4 times trying to get my network straitened out, is there something I can delete?

Edit: Nevermind, looks like my router, modem and switches needed another power cycling after the power outage last night...

[Marvin_The_Martian]

Lol I only read that text file for clients name and location I don't write to anything involving fahmon. Every file I create is located in appdata\fahwatch\

I just noticed I made a lil oops on the update, as it pops out of the tray every update and not only when a new eue is found brb

[coo-coo-clocker]

Great work Marvin - the tool is now running fine across all clients.

I did find a defect, however. When I clicked "options", there was an exception generated:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
   at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
   at g.d(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
    Assembly Version: 1.0.0.7
    Win32 Version: 1.0.0.7
    CodeBase: file:///C:/Documents%20and%20Settings/Mike/My%20Documents/fahwatch.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

[Marvin_The_Martian]

1.0.0.8 up. minor changes ( mostly small bug fixes ).

Coo-coo-clocker thanks for the bugreport I know what caused it and it's now fixed. And I added proper error handling to that sub

[MikeB12]

down to 3% eue

[WFO]

I'm down to 6% of 2264. I hit a high of 13% when G0-3 was acting up. Fahmon still wants a 100% of 1 core on my quad so I won't be running this the way I would like to for a while.

LOL...FahWatch just alerted on an outdated core. I still had a 1.15 on one of my 9600GSO. Oh noes further points reductions starting now.

[catawalks]

uh oh. 1.0.0.8 when I pressed on the options button:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
   at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
   at g.d(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
    Assembly Version: 1.0.0.8
    Win32 Version: 1.0.0.8
    CodeBase: file:///C:/Users/Administrator/Downloads/fahwatch.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Marvin_The_Martian]

uh oh. 1.0.0.8 when I pressed on the options button:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
   at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
   at g.d(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
    Assembly Version: 1.0.0.8
    Win32 Version: 1.0.0.8
    CodeBase: file:///C:/Users/Administrator/Downloads/fahwatch.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

See coo-coo-clockers post on page 2, it's fixed if you download again. Sorry for not updating build number

[MaK2000]

I downloaded from the link on the first page and get a FAHwatch has encountered a problem and needs to close error. Is there another client I should be getting or is it the current one? XP32

[catawalks]

Marvin, I got that error when I ran the one from the first page yesterday. I posted like 3 minutes after downloading and running it last night.

[Marvin_The_Martian]

I downloaded from the link on the first page and get a FAHwatch has encountered a problem and needs to close error. Is there another client I should be getting or is it the current one? XP32

Nope should be good. You haven't downloaded/ran this before? If you did, try deleting the folder %application data%\fahWatch as that might cause an error, even if I thought I cleanly handeld any settings not being in the file.

Marvin, I got that error when I ran the one from the first page yesterday. I posted like 3 minutes after downloading and running it last night.

Yeah but I updated it seconds after coo-coo-clocker posted, I had an initial value set to 0 for a property which is teid to a numeric up and down control with a min value off 1. That property is now always 1 if there is no settings file, so either you have a bad settings file and you need to do delete it and start new, or you need to post more data because atm I don't know what's exactly happening

Working on a stats page for xs now to, and a signature generator, have to admit I should concentrate on fahwatch first that's something which could be usefull I think more so then the other things

Thanks for the raports both Keep em coming