FahMon 2.2.1a

Snapshot · 26 Jun 2007 at 15:57

Is anyone else having problems with this? It just doesn't run properly on my main PC - it starts in the task bar and system tray but doesn't appear on the screen (shortcut is set to 'normal window'). If I click on the task bar entry it disappears so is presumably minimised. Click on the system tray icon and the task bar entry re-appears but nothing on the desktop. It did work vaguely properly at one point as I was able to configure it but it seems to have degraded now. On the second PC it works better but there's a very long delay after clicking on the system tray icon before the desktop window appears. I'll have to go back to 2.2.0...

Mattus · 26 Jun 2007 at 18:29

I just downloaded 2.2.1a and it's giving me the exact same issues. Looks like there's a bug somewhere!

Fortunately the website has a lot of past versions

2.2.1 seems to work OK.

Snapshot · 26 Jun 2007 at 18:52

Thanks. It's always helpful to know it's not a local conflict. I'll try 2.2.1.

WoZZeR · 26 Jun 2007 at 19:08

I haven't set up a shortcut to mine and it hasn't had any problems at all (XP)

oceaness · 26 Jun 2007 at 19:48

Wheres Uncy Fungus

PhillyDee · 26 Jun 2007 at 19:57

Mines fine with Vista x64. and talking to an XP pro machine in the other room.

Snapshot · 26 Jun 2007 at 19:59

WoZZeR said:
I haven't set up a shortcut to mine and it hasn't had any problems at all (XP)

I've tried the .exe straight from the fahmon folder as well - made no difference. It must be some sort of interaction depending on what's installed locally and I'm guessing it's something to do with wxWidgets, whatever they may be.

<Later> 2.2.1 works but gives the file access problems that were why UF created 2.2.1a. I'd put 2.2.1 in a clean folder rather than on top of 2.2.0 so I copied the .exe for 2.2.1a over the top and it still works. I now suspect the problem is something to do with having inaccessible clients in the the client list as I'd created a new list for the 2.2.1 installation. I could experiment further but I'd rather leave it working for the moment.

rich99million · 26 Jun 2007 at 21:28

2.2.1a seems to be working fine for me still - bit of a delay if it can't contact networked machines when it first starts but other than that seems ok on XP 32-bit for me

I'm sure unky fungus will have the answer (just like smarties do)

WoZZeR · 26 Jun 2007 at 21:36

I have to log into My Network Places 'warren on Folding server (Samba, Ubuntu) (Folding)' before Fahmon can see the SMP Client. That hasn't changed since the earlier version of Fahmon.

uncle_fungus · 26 Jun 2007 at 23:42

@WoZZeR, thats thats just the way windows does shares. They need authenticating before you can access them, and FahMon isn't able to do that itself.

I sort of know about the minimized to tray bug, although I can't reproduce it (I'll try again later).

My best guess for the moment to resolve the issue, is stop FahMon, trash the prefs.dat file in the config folder and restart FahMon.

I've also noticed that if you enable "start minimised" without enabling "enable tray icon", FahMon disappears altogether, so that needs fixing too.

@rich99million, yes that was something I broke this time, I've unbroken it for 2.2.2 you'll be glad to know.

Edit: I've just added these to the online "known bugs" list

Snapshot · 27 Jun 2007 at 07:31

uncle_fungus said:
I sort of know about the minimized to tray bug, although I can't reproduce it (I'll try again later).

My best guess for the moment to resolve the issue, is stop FahMon, trash the prefs.dat file in the config folder and restart FahMon.

Tried this and it made the bad instance of 2.2.1a work although it's still slow to restore from minimised. The obvious difference between it and the good instance is that it has inaccessible clients in the list. It may be that your fix for Rich's 'slow to load' bug will fix this too.

I've also noticed that if you enable "start minimised" without enabling "enable tray icon", FahMon disappears altogether, so that needs fixing too.

Seems logical to me.

Mattus · 27 Jun 2007 at 12:12

I'm gonna have to downgrade to 2.2.0 - this window keeps popping up and it's driving me crazy:

All the clients are accessible and FAHMon shows their data, but I get this every minute or so.

oceaness · 27 Jun 2007 at 13:00

Mattus said:
I'm gonna have to downgrade to 2.2.0 - this window keeps popping up and it's driving me crazy:

All the clients are accessible and FAHMon shows their data, but I get this every minute or so.

Thats the problem I've been having.

uncle_fungus · 27 Jun 2007 at 13:12

oceaness said:
Thats the problem I've been having.

2.2.1 shouldn't be used for precisely that reason, 2.2.1a fixed the problem caused by wxwidgets not playing nice on windows.

I'll try and get 2.2.2 out soon which will heopfully fix all of the above bugs.

Also what do you mean by "slow to restore from minimised"?

Do you mean that the FahMon window takes ages to actually appear when you restore it, or that the contents take ages to refresh?
I haven't noticed either of the above behaviour (although I run it on Linux not Windows).

Mattus · 27 Jun 2007 at 13:49

uncle_fungus said:
Also what do you mean by "slow to restore from minimised"?

Do you mean that the FahMon window takes ages to actually appear when you restore it, or that the contents take ages to refresh?
I haven't noticed either of the above behaviour (although I run it on Linux not Windows).

When I start 2.2.1a, the window appears without any data in it, then hangs for about ten seconds until it updates with the client data.

Restoring it from the taskbar or system tray, it takes ten seconds for anything to show at all.

I think it's related to file access because removing unavailable clients from FahMon's list seems to solve the problem.

uncle_fungus · 27 Jun 2007 at 18:01

Mattus said:
When I start 2.2.1a, the window appears without any data in it, then hangs for about ten seconds until it updates with the client data.

Restoring it from the taskbar or system tray, it takes ten seconds for anything to show at all.

I think it's related to file access because removing unavailable clients from FahMon's list seems to solve the problem.

Ah ok, in that case I think the problem has already been fixed for 2.2.2.
Inaccessible clients seem to cause a problem in 2.2.1a, although the problem I noticed isn't related to showing data, rather updating it.

I've just added some code that should completely remove the bug that causes the FahMon window to disappear even when its present in the taskbar, but since I can't replicate it, I can't be 100% sure. (It works in theory).

Snapshot · 27 Jun 2007 at 18:44

Mattus said:
When I start 2.2.1a, the window appears without any data in it, then hangs for about ten seconds until it updates with the client data.

Restoring it from the taskbar or system tray, it takes ten seconds for anything to show at all.

I think it's related to file access because removing unavailable clients from FahMon's list seems to solve the problem.

I agree with all that.