Upcoming version 7? (Cleaning & Purging)

[guest3412]

For cleaning out the old version, since I use the console version, I simply set the "asknet=no" flag to"asknet=yes" and then when the notification box pops up asking me to connect I give it permission then after the results are sent, I shut down the core, delete the folder and all contents, and make a new one where I put the new client, starting from anew.

EDIT: I've since found that shutting down the client and re-starting the client with the "-oneunit" flag works alot better, the current WU will finish and stop, at which point you can install the new client with minimal problems.

I would like to know where there is a discussion area regarding the new v7 client.

Some suggestions I'd like to see in the new version, especially if it combines all the single core, smp, and gpu clients into one gui.

1) a profile selector: where you can select a program, when it loads, pause the gpu client, set cpu to 25% (or whatever % user selectable) max use. The profile selector should be able to do any function from pausing the whole client to reducing how much the client can use of the cpu/gpu and should be able to do this on the fly with out any user interaction. - just like the gaming keyboard - G15? - it would be nice if there could be separate profiles, to be able to select, user nameable even (say gaming 1, gaming 2, movie, surfing web, ect) then when you select a game executable for the profile to load, you don't have to reselect what profile settings for all the games. when I watch a BD movie I have to shut down all my fah clients or I'll get a BSOD from time to time, I don't watch a movie every day, maybe once a week... but still for that 2hrs I have to shut down fah if I don't want to have to shutdown my system and recover from the BSOD.

2) incorporate functions from the fahmon, so you can see what % the client is at (both for the GPU and SMP, or each single CPU client). what ppd you are getting, what the deadline is for each work unit, both preferred and final deadline would be nice. If you really want to get some bonus points, you can list TPF current, average, min, max - for the current project (you could click on it like GPU-Z to change between them). Include the current points that the user has generated - with out having to go to my folding page. Include the amount of work units the smp, gpu, single core client - has finished.

3) when the user sets up their client for the first time, make suggestions based on questions of how the user uses their system, ie: dedicated folder, part time folder - 4,8, 12hrs/day, run during work hours only, run as service (so that it runs even when logged out), these should be options that the user can choose and change whenever. you could have a setup wizard, and an advanced setup, for people that run servers 24/7 and know what all that advanced stuff means can choose it threw the gui. You should be able to dock the client in the sys tray.
If the user selects dedicated server and runs smp, but is too heavily using the computer to make the deadline, a notification balloon should pop up at the bottom, upon user return that they can click on or dismiss notifying them that they missed the preferred/final deadline, and they should consider a different setup. If they dismiss the notification, they should still see the message when they open the client, it should not be another intrusive message box they have to dismiss, but instead be a note on the screen they can see and click to re-run the wizard, or make advanced changes. The client should learn how the user uses their computer, by how much they are pausing the clients, or using cpu time and request appropriate work units with deadlines that would coincide with the average usage. just because today I used my computer more than usual, or was working on my computer with some issue, or upgrading it, should not affect the average greatly. neither should it if I am away from my computer for the whole day unusually. Deadline should have more time to complete than the average would allow, for instance, if the user completes a WU in 1hr, there should be a 24-36hr window for final deadline, if the WU is usually completed in 48hrs there should be at least a 60-72hr final deadline. preferred deadline should be at least the average, or the server should not send the WU. If there is no average then of course send a longest deadline project to test the waters. The client should keep track of the average for that machine, to offload any additional tracking, so the only thing the server has to do is decide what project to give the client with x deadline. since every project can have a different tpf the client can take that into account when computing the average for the project deadline and request the server for a different deadline project if it knows it will be unable to complete the given project before final deadline.

4) although unnecessary, it would be nice if the user could put in a custom skin on their gui client, firefox has really come up with some nice ones and it would be neat for sure to be able to use a custom skin! Think of it, the teams could make those and cokes you to be a member for the use of their skin? or just give them out and make them a publicity item. the floating balls that the protein map does, would make a interesting screen saver, but those truly interested in folding, do not wish to spare the cpu/gpu cycles for something that is relatively useless.

I guess that's all I can think of for now, let me know what you think, I'm no programmer, but I am a dreamer, an idea guy maybe, I'll admit I have no idea what goes into making these clients or the gui, but I do know what I like and that is customization!

[parkut]

V7 coming "soon" announcement in the news blog (Link at the top of this page) http://folding.typepad.com/news/2010/06 ... lient.html