Windows Beta Client [v2.5.08]
This is just a stand alone exe. It's not an installer.
Caveats (for v2.5.08): Fixed a bug prohibiting entering a long username. Fixed a bug in the GUI that was cutting off 'test' in the config screen.
Caveats (for v2.5.07): The ones below still apply. This version has support for changing how many intermediate blocks between server reports, similar to the other clients. Under the config button, you will now see a place where you can set the amount of blocks next to 'Trans Int. Blocks' where it says "Freq:"
Caveats (for v2.5.06): YMMV. This is even more beta. This uses updated math libraries which should result in a speed improvement. I have not done calculations to figure out how much faster it is, but if other people would like to that'd be great. Because of the updated libraries, I need to do more testing on this client to make sure things are reported properly. Please test with it, but don't deploy widely.
http://www-personal.umich.edu/~mcgar...2.5.08-win.zip
How To Speed Up Windows Shutdown
If you shutdown the clients first, that wouldn't happen. ;)
You could always use an old hack of your registry - warning, you could crash your system if you don't know what you are doing.
This is used to speed up the Windows shutdown wait period.
Click Start button > Run > and type "regedit.exe" and hit the <enter> key, then browse to the following key:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control
Click on the Control key and in the right hand window you will see this key "WaitToKillServiceTimeout". Double click that key and set it to 200.
Close regedit.exe and then restart your computer.
:D
Request Machine Name Option in New Release
I am very happy with the new Beta Clients and have installed them at all locations. They have been stable and appear to give better performance, both due to new (better) algorithms and by using less resources for intermediate block communications. All my performance issues with the client have been address at this point. I have one maintenance/tracking issue that I have had concerns with from the start. That is keeping track of all of my clients. Although we can track by IP address, in most cases it is not that useful. Home based machines tend to be on a dynamic IP that change often. Work based machines sit behind a firewall/NAT so they all appear to all have the same IP address. I would love a machine name or nickname that I could give to each client instance, it would allow me to easily determine client problems, either stuck/stopped clients or orphaned tests. It would also give me an easier way to track performance per machine or instance. I understand that this change would not improve performance ...other then being able to detect stopped clients and restart them quicker. I would argue that if you are going to change the client with a formal release, and one encompassing so many different and new architectures an addition of an optional machine (instance) name would make client identification an maintenance much easier for the end user.