Posts by Brian D from Georgia

1) Message boards : Number crunching : Longer Tasks????? (Message 34176) Posted 4 Dec 2009 by Brian D from Georgia Post: The new WU's are roughly 4 times as long to crunch and give you 4x the old fixed credit per WU. Seems reasonable as a way to keep traffic off the server. This is with CPU crunching, I don't have GPU's that are worthy... :(
2) Message boards : Number crunching : When will the deadline be extended? (Message 4742) Posted 16 Aug 2008 by Brian D from Georgia Post: Thanks Travis - 3 days is perfect to allow unattended weekend crunching for modem users like myself. As I originally stated though, if the science needs the shorter deadline then that's what counts and I'll move to another project for the weekend on my office cluster.
3) Message boards : Number crunching : When will the deadline be extended? (Message 4732) Posted 15 Aug 2008 by Brian D from Georgia Post: how about 2.5 days? that should allow WUs that started sometime on friday to be finished up sometime monday morning and reported? Friday afternoon to Monday morning is about 2.75 days, that's my story and I'm sticking to it!!! LOL Don't think 2.5 days will quite cut it, remember with dial up it may take an hour on the u/l and d/l with 6 hosts and many wu's. Thanks for the reply, hope 2.75 can be made.
4) Message boards : Number crunching : When will the deadline be extended? (Message 4719) Posted 15 Aug 2008 by Brian D from Georgia Post: It's obvious that the admin's aren't aware of something called dial up internet connections and a 3 day weekend. This new 2 day deadline just killed my active participation with 6 hosts at work as I am gone 2.75 days over the weekend and can't dial up until Monday morn's. Oh well, if the science dictates the shorter deadlines, then I'll accept it and choose another favorite project to crunch.
5) Message boards : Number crunching : application v1.21/v1.22 errors/memory leaks/crashes here (Message 2068) Posted 7 Mar 2008 by Brian D from Georgia Post: Three of my hosts running W2K just picked up the 1.22 app and it is working fine. They were crashing on 1.21 immediately and 2 of 3 have just completed their first 1.22 wu and returned it w/o a prob. Good work, so far, so good! Milkyway@home 3/7/2008 3:53:34 PM 29424 Finished download of parameters_generated_1205012780_27620 Milkyway@home 3/7/2008 4:05:19 PM 29455 Computation for result gs_292_1205012795_27865_0 finished Milkyway@home 3/7/2008 4:05:19 PM 29456 Starting result gs_292_1205012795_27866_0 using astronomy version 122 Milkyway@home 3/7/2008 4:05:22 PM 29457 Started upload of gs_292_1205012795_27865_0_0 Milkyway@home 3/7/2008 4:05:48 PM 29458 Finished upload of gs_292_1205012795_27865_0_0 Milkyway@home 3/7/2008 4:08:06 PM 29460 Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi
6) Message boards : Number crunching : application v1.21/v1.22 errors/memory leaks/crashes here (Message 2012) Posted 7 Mar 2008 by Brian D from Georgia Post: Hi all, 32-bit Windows application (windows 2000) crashes with following error: 3/7/2008 11:27:08 AM\|Milkyway@home\|Starting task gs_281_1204857426_46066_0 using astronomy version 121 3/7/2008 11:27:09 AM\|Milkyway@home\|Computation for task gs_281_1204857426_46066_0 finished 3/7/2008 11:27:09 AM\|Milkyway@home\|Output file gs_281_1204857426_46066_0_0 for task gs_281_1204857426_46066_0 absent 3/7/2008 11:27:09 AM\|Milkyway@home\|Starting gs_283_1204858594_47973_0 3/7/2008 11:27:09 AM\|Milkyway@home\|Starting task gs_283_1204858594_47973_0 using astronomy version 121 3/7/2008 11:27:10 AM\|Milkyway@home\|Computation for task gs_283_1204858594_47973_0 finished 3/7/2008 11:27:10 AM\|Milkyway@home\|Output file gs_283_1204858594_47973_0_0 for task gs_283_1204858594_47973_0 absent 3/7/2008 11:27:10 AM\|Milkyway@home\|Starting gs_280_1204858588_47922_0 3/7/2008 11:27:10 AM\|Milkyway@home\|Starting task gs_280_1204858588_47922_0 using astronomy version 121 3/7/2008 11:27:12 AM\|Milkyway@home\|Computation for task gs_280_1204858588_47922_0 finished 3/7/2008 11:27:12 AM\|Milkyway@home\|Output file gs_280_1204858588_47922_0_0 for task gs_280_1204858588_47922_0 absent 3/7/2008 11:27:12 AM\|Milkyway@home\|Starting gs_280_1204859966_49995_0 3/7/2008 11:27:12 AM\|Milkyway@home\|Starting task gs_280_1204859966_49995_0 using astronomy version 121 3/7/2008 11:27:13 AM\|Milkyway@home\|Computation for task gs_280_1204859966_49995_0 finished 3/7/2008 11:27:13 AM\|Milkyway@home\|Output file gs_280_1204859966_49995_0_0 for task gs_280_1204859966_49995_0 absent 3/7/2008 11:27:13 AM\|Milkyway@home\|Starting gs_280_1204859966_49987_0 3/7/2008 11:27:13 AM\|Milkyway@home\|Starting task gs_280_1204859966_49987_0 using astronomy version 121 3/7/2008 11:27:14 AM\|Milkyway@home\|Computation for task gs_280_1204859966_49987_0 finished [edit]The procedure entry point LogonUserExA could not be located in the dynamic link library ADVAPI32.dll [/edit] I have 3 nearly identical hosts (P4 3.0Ghz Northwood's). Two are running XP (one Home and one Pro) and 1.21 seems to be working very well on these two. The other host is running W2K and I am seeing the same immediate app crash as the above user. I tried detaching and reattaching but this didn't help. That W2K host was working okay at app 1.19 as far as I know.