:funknana: 
That’s with a load still turned off !!! Top on the weekly, now I never thought I’d be able to oust OHS - hoping there is not a big problem over there :xfinger:
DT.
Well done.
Now to keep it going and catch up! 
oh all right then, I’ll switch back to folding and show DT how it’s really done 
seriously though, top folding DT 
Curly
Well done, DT
Get them back on D2OL now ya slacker! 
too hot - and tbh they are all durons that are turned off as they are good little test rigs but awfull crunchers !!!
Output from tomorrow will be even higher Beck and the kids are going away so moving all said unused machines into the kids room to crunch 24/7 for a week !!!
DT.
Parents go away next week as well 
Aiming to put brother’s machine onto Folding for the week and set up a connection between my PC and his.
OUCH :lol: the things I do
12pc’s currently sharing a 56K modem feed in order to send and get some new folding units !!!
:cuckoo:
DT.
Great work DT
The infrastructure upgrade has thrown the folding engines a curve. Our proxy server address changed, but even if I update a machine with the new proxy address in -config, it cannot connect to Stanford. The only way I can get it to connect is to tell it to use the IE settings, but the problem there is that it only KNOWS the IE settings when someone has logged in. Where machines used to happily crunch away at the Windows login screen before, the FAH log just fills with a bunch of “Unable to connect” error messages now. 
I’m looking into it, but there may not be an improvement until the students return in September and the computers actually start to get used again. If that’s the case, we still won’t get back to the “glory days” of 18K days for OHS.
darn - that’s not good news. Take a look at the new beta core that is available on the forums/stanford site somewhere. I’m pretty sure I saw a release log that had some proxy code changes. With any luck that will do the job.
http://folding.stanford.edu/beta
not sure whether this from the news page was client or server related
7/18/2005 Proxy bug fixed
Adam has fixed a proxy bug recently reported and we are now testing this fix gradually. First the port 80 AS and certain work servers, then the main AS. So far, everything seems ok on our end, but it will take more of a complete roll out for donors to see a difference.
DT.
Thanks, I’ll try it. It seemed wierd that the static proxy setting would fail but the IE setting (which pointed to the same proxy address) would work. This could indeed be the problem.
The 5.04 beta does the same thing as 5.02 
I looked for info on where I could comment on the beta but I didn’t find anything. 
I’ll post something in the Forum once I can get to a machine that has an example of the errors in the log.