FahMon 2.3.99.1 gone bonkers
Leonardo
Wake up and smell the glaciersEagle River, Alaska Icrontian
I'm running FahMon 2.3.4 to monitor my SMP and GPU2 Folding clients. It has served me well, but progress is progress, and version 2.3.99.1 seemed a logical upgrade. But now, what grief.
I've tried the newer version on two occasions, the last time just this last weekend. I had to remove it and revert to 2.3.4. 2.3.99.1, at least on my system, randomly renames the client names. When you have many clients running, it's just too time consuming to constantly make corrections.
Anyone know of a fix? I did an Internet search, found others reporting the same problem, but found no solution.
The computer running FahMon is operating on WinXP SP3. It's on a home Ethernet LAN, router auto-assigned IPs. The computer is connected to a switch, which is directly connected via Ethernet to the router in another room. Three computers are connected to the switch and one computer is connected directly to the router. None of the clients, monitored through switch or router, are immune to having the client names randomly changed.
I previously experienced the same problem when none of the computers where on a switch.
Any ideas?
I've tried the newer version on two occasions, the last time just this last weekend. I had to remove it and revert to 2.3.4. 2.3.99.1, at least on my system, randomly renames the client names. When you have many clients running, it's just too time consuming to constantly make corrections.
Anyone know of a fix? I did an Internet search, found others reporting the same problem, but found no solution.
The computer running FahMon is operating on WinXP SP3. It's on a home Ethernet LAN, router auto-assigned IPs. The computer is connected to a switch, which is directly connected via Ethernet to the router in another room. Three computers are connected to the switch and one computer is connected directly to the router. None of the clients, monitored through switch or router, are immune to having the client names randomly changed.
I previously experienced the same problem when none of the computers where on a switch.
Any ideas?
0
Comments
I pointed each FAHMon-monitored client at each individual client folder in each computer over the network.
Try setting 2 of the problem computers to static IP addresses and see if that makes a difference.