Attach to project:

2005-12-23 22:13:02 [---] Starting BOINC client version 5.2.13 for windows_intelx86
2005-12-23 22:13:02 [---] libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
2005-12-23 22:13:02 [---] Data directory: E:\\BOINC
2005-12-23 22:13:02 [---] Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3400+
2005-12-23 22:13:02 [---] Memory: 255.49 MB physical, 620.33 MB virtual
2005-12-23 22:13:02 [---] Disk: 13.48 GB total, 11.34 GB free
2005-12-23 22:13:04 [---] No general preferences found - using BOINC defaults
2005-12-23 22:13:05 [---] Remote control not allowed; using loopback address
2005-12-23 22:13:05 [---] This computer is not attached to any projects.
2005-12-23 22:13:05 [---] There are several ways to attach to a project:
2005-12-23 22:13:05 [---] 1) Run the BOINC Manager and click Projects.
2005-12-23 22:13:05 [---] 2) (Unix/Mac) Use boinc_cmd --project_attach
2005-12-23 22:13:05 [---] 3) (Unix/Mac) Run this program with the -attach_project command-line option.
2005-12-23 22:13:05 [---] Visit http://boinc.berkeley.edu for more information
2005-12-23 22:13:08 [---] Running CPU benchmarks
2005-12-23 22:14:06 [---] Benchmark results:
2005-12-23 22:14:06 [---] Number of CPUs: 1
2005-12-23 22:14:06 [---] 2109 double precision MIPS (Whetstone) per CPU
2005-12-23 22:14:06 [---] 3933 integer MIPS (Dhrystone) per CPU
2005-12-23 22:14:06 [---] Finished CPU benchmarks
2005-12-23 22:14:07 [---] Fetching config info from http://setiathome.berkeley.edu/get_project_config.php
2005-12-23 22:14:07 [---] Resuming computation and network activity
2005-12-23 22:14:07 [---] request_reschedule_cpus: Resuming activities
2005-12-23 22:14:30 [http://setiathome.berkeley.edu/] Master file download succeeded
2005-12-23 22:14:30 [http://setiathome.berkeley.edu/] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-12-23 22:14:30 [http://setiathome.berkeley.edu/] Reason: Requested by user
2005-12-23 22:14:30 [http://setiathome.berkeley.edu/] Requesting 8640 seconds of new work
2005-12-23 22:14:32 [http://setiathome.berkeley.edu/] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2005-12-23 22:14:32 [SETI@home] General preferences have been updated
2005-12-23 22:14:32 [SETI@home] New host venue: home
2005-12-23 22:14:32 [---] General prefs: from SETI@home (last modified 2005-12-19 08:58:17)
2005-12-23 22:14:32 [---] General prefs: using your defaults
2005-12-23 22:14:32 [SETI@home] Successfully attached to SETI@home

Note: No work and no indication of why no work.

All kinds of work from P@H:

2005-12-23 22:20:04 [---] Fetching config info from http://predictor.scripps.edu/get_project_config.php
2005-12-23 22:20:30 [http://predictor.scripps.edu/] Master file download succeeded
2005-12-23 22:20:30 [http://predictor.scripps.edu/] Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
2005-12-23 22:20:30 [http://predictor.scripps.edu/] Reason: Requested by user
2005-12-23 22:20:30 [http://predictor.scripps.edu/] Requesting 172800 seconds of new work
2005-12-23 22:20:33 [http://predictor.scripps.edu/] Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
2005-12-23 22:20:33 [Predictor @ Home] New host venue: home
2005-12-23 22:20:33 [Predictor @ Home] Successfully attached to Predictor @ Home
2005-12-23 22:20:35 [Predictor @ Home] Started download of mfoldB125_4.28_windows_intelx86.exe
2005-12-23 22:20:35 [Predictor @ Home] Started download of rebuild.dat

Ten minutes later S@H deigns of disgorge two (2) WUs:

2005-12-23 22:24:43 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-12-23 22:24:43 [SETI@home] Reason: To fetch work
2005-12-23 22:24:43 [SETI@home] Requesting 172800 seconds of new work
2005-12-23 22:24:48 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2005-12-23 22:24:50 [SETI@home] Started download of setiathome_4.18_windows_intelx86.exe
2005-12-23 22:24:50 [SETI@home] Started download of better_banner.jpg
2005-12-23 22:24:52 [SETI@home] Finished download of better_banner.jpg
2005-12-23 22:24:52 [SETI@home] Throughput 11634 bytes/sec
2005-12-23 22:24:52 [SETI@home] Started download of setiathome_4.18_windows_intelx86.pdb
2005-12-23 22:24:58 [SETI@home] Finished download of setiathome_4.18_windows_intelx86.exe
2005-12-23 22:24:58 [SETI@home] Throughput 113576 bytes/sec
2005-12-23 22:24:58 [SETI@home] Started download of 15fe05aa.15267.5554.729828.1.86
2005-12-23 22:25:02 [SETI@home] Finished download of 15fe05aa.15267.5554.729828.1.86
2005-12-23 22:25:02 [SETI@home] Throughput 104353 bytes/sec
2005-12-23 22:25:02 [SETI@home] Started download of 16dc04aa.15349.21120.240896.1.90
2005-12-23 22:25:07 [SETI@home] Finished download of 16dc04aa.15349.21120.240896.1.90
2005-12-23 22:25:07 [SETI@home] Throughput 84240 bytes/sec
2005-12-23 22:25:13 [SETI@home] Finished download of setiathome_4.18_windows_intelx86.pdb

Machine can process 33 WUs per day.

---

The deferral of 10 minutes is normal. It's intended.

If you want a bigger WU cache, go to 'your account' -> 'general preferences' and set the value for 'Connect every...' to more than 0.1 days (default). You can set it to 10 days max, but it is recommended to stay below that. BOINC will then try to keep always enough work for the indiacated period on stock.

For my machines I have set it to 1 day.

Oh, and don't forget to press 'update' in BOINCmanager after the change.

:-)= Greybeard

---

All about BOINC: BOINC-Wiki (by Paul D. Buck)

So why not check back in a day orso? 2 WUs is more than what some people here get.
2WUs isn't what I call no work on a machine that's just been attached and of which BOINC has no idea how long the work units are really going to take.

Even that takes a while to figure out. So be patient.

---

One difference in the amount of work you get from Predictor vs. SETI is that the Predictor results take about half the time that SETI results do. BOINC downloads based on an estimate of how long the work will take, so it doesn't get so much that you miss deadlines.

MJ

---