Have you made the switch ?

[mountainman]

Have you switched to version 3.24 yet ?

[BaLa]

yes sir

[ScottE]

Yep still works the same though.

[HawaiianGhost]

Yeah, only prob I have is that I have to shut it down to game on "anything". Which is no prob but just gotta try to remember to start F@H again. Love the the new look of v3.24 though and the little added features.

[YARDofSTUF]

not yet but i will soon

[poptom]

Is there any reason to?

I have 3.11 (text).

[Dave's World]

yup

[BaLa]

Folding@Home 3.24
December 23, 2002

----------------------------------------------------------------------

----------------------------------------------------------------------
RECENT CHANGES (Client):
3.24:
- Benchmarking improved in consistency and uniformity.
- Support for sending a measure to the assignment server of time taken on past
work units (a weighted average), to use as a predictor of how large a work unit
can be handled. Can view this measure using verbosity 4 after finished units, but
AS not using yet.
- If bad arguments given, will exit only after a key press.
- If upon startup, FAHlog.txt exceeds 50Kb and a is to be started, the old
one is retained under the name FAHlog-Prev.txt.
- Deadline information included with work (Printed to unitinfo.txt and
available in queueinfo). Active units checked for expiration periodically
all others checked for expiration at autosend time. Configuration option
of ignoring deadline information (to use if system clock is bad -- not just
telling incorrect absolute time, but having an incorrect conception of
what one second is, for instance) if so desired.
- MyFolding.html page written out by client with useful links (which Linux and
Win. console users did not have easy access to before)
- In making request to server for work, inform on whether have units done
waiting to be uploaded to server. If so, servers running new code will
give a new unit instead of giving same (servers will shift over as projects
come up).
- If a work unit is rejected for any reason, server now returns reason
to client, which prints it out. (In this client, and servers will transition
to the new code as projects come online.) If work unit is fatally flawed,
then deleted from queue.
- "Could not transmit unit" statement now also includes date unit was
completed ("Could not transmit unit x (Completed xxxx)").
- Checks for bad URL, port on reception of work unit, deleting it before
even starting work if bad.
- Time stamp on every line of FAHlog.
- Arguments to client printed to log.
- Some log messages modified (like the requested, and deserved, "Thank you"
added!). Some further spacing changes may be desired.
- File "unitinfo.txt" printed and updated, with information and progress
for current work unit. (Had been requested for use by 3rd party people.)
- Client FAHlog output overhauled to use Windows API functions. (Interested
in hearing if you see any change in performance, particularly from those
Win95/98 users who said log froze sometimes.) Log file is locked for
writing by other programs while client running.
- Networking overhaul to give a Configuration option of using whatever proxy
settings are used by Internet Explorer.

GUI specific-
- If choose "Ask before networking" in Configuration, will take effect
even on next get work, without restart needed.
- "Status" menu item to launch MyFolding.html.
- "Status" menu item to view queueinfo added.
- Bug fixed where if click off systray menu, menu did not disappear.
- Tool tip on systray icon now gives program status (including work
progress if currently working)
- When move mouse over hyperlink portions of display, mouse icon becomes a
hand.
- Bug fixed where if move display, then the links at the bottom of the
display (ticker tape ones) did not always work.
- Menu item ("Status") added to give easy access to Team Stats page, User
Stats page, and Logfile.

Console specific-
- Answers to Configuration questions now validated. One letter answers (i.e.
"y" or "Y" instead of "yes") allowed.

http://folding.stanford.edu/winchanges.txt

[poptom]

Thank you, BaLa.

[Encnuk]

One of my 3 machines is running 3.24, the other 2 are still running 3.14. Considering the amount it takes to shut down FireDaemon, change the executable it runs and then restart it, I rather spend the time surfing the boards and playing with my cat.

[btracy]

How long does that process take you Encnuk?

I can change out the executable in about 30 seconds or so including shutting down firedaemon and then starting it back up.

[Encnuk]

Yep, that is 30 secs I am away from reading the boards. :)

[Needlefreak]

Voted NO this morn but I went ahead and changed later...Games and whatnot are running fine....

[koldchillah]

I've never used any other version b/c I just started folding 2 weeks ago.. but 43 WU's later, everything seems fine, just have to shut it down for BF1942 and thats it... other games work fine..:D