1) Questions and Answers : Getting started : There was work but not enough disk space (Message 55514) Posted 4 Sep 2008 by JAllan32 Post: Windows XP with SP3; BOINC 6.2.16 when problem first appeared, upgraded to 6.2.18 which did not change the result. After moving all files in the Rosetta data file folder to recycle bin (not total delete), to synch with the aborted task, message changed from 263 MB needed to 202 MB needed.

2) Questions and Answers : Getting started : There was work but not enough disk space (Message 55506) Posted 3 Sep 2008 by JAllan32 Post: After upgrading to latest BOINC manager and (I assume this is done automatically) the latest Rosetta client, Rosetta server refuses to send me any work. I have 5.66 GB free out of 28.5 GB on my C: drive, of which BOINC is currently using 72.38 MB, including 5.77 MB for SETI and 61.12 MB left over from the last Rosetta project (which was aborted because it was overdue anyway). My global preferences are to use at most 1 GB, leave at least 0.2 GB free, and use at most 80 percent of total space. SETI is set to use 20% of resources, and Rosetta 80% (these were set after aborting the task, which obviously had not gotten enough CPU time, especially with my computer powered down for four days due to T.S. Fay). The following number was significantly larger (340 MB) before expanding the resources, but it has not been reduced to zero. Both projects have been UPDATEd, SUSPENDed and then RESUMEd, and Rosetta has even had NO NEW TASKS followed by ALLOW NEW TASKS, since the preferences were updated on both web sites. Pasted from both (matched character by character): Global preferences (same for both SETI@home and Rosetta@home) Disk and memory usage Use at most 1 GB disk space Leave at least (Values smaller than 0.001 are ignored) 0.2 GB disk space free Use at most 80% of total disk space Write to disk at most every 60 seconds Use at most 50% of page file (swap space) Use at most Enforced by version 5.8+ 40% of memory when computer is in use Use at most Enforced by version 5.8+ 80% of memory when computer is not in use Pasted from SETI web site: SETI@home preferences Resource share If you participate in multiple BOINC projects, this is the proportion of your resources used by SETI@home 20 Is it OK for SETI@home and your team (if any) to email you? Emails will be sent from setiweb@ssl.berkeley.edu; make sure your spam filter accepts this address. yes Should SETI@home show your computers on its web site? no Default computer location home Graphics preferences Select Custom to edit individual parameters SETI@home classic Color preferences: Select Custom to edit individual parameters Rainbow URL of background image This image (JPEG, Targa, BMP or PPM format) will be displayed in the background. none URL of logo image This image (JPEG, Targa, BMP or PPM format) will be displayed in the lower corner. none Run only the selected applications SETI@home Enhanced: yes Astropulse: yes If no work for selected applications is available, accept work from other applications? yes Pasted from Rosetta web site: Rosetta@home preferences Resource share If you participate in multiple BOINC projects, this is the proportion of your resources used by Rosetta@home 80 Is it OK for Rosetta@home and your team (if any) to email you? Emails will be sent from Rosetta/BOINC Admin ; make sure your spam filter accepts this address. yes Should Rosetta@home show your computers on its web site? no Default computer location home Percentage of CPU time used for graphics 20 Number of frames per second for graphics 20 Target CPU run time 4 hours Pasted from message log after above changes were applied: 9/3/2008 14:28:09|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 9/3/2008 14:28:14|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:35:30|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 9/3/2008 14:35:35|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:40:48||Resuming computation 9/3/2008 14:40:50|rosetta@home|Sending scheduler request: To fetch work. Requesting 959 seconds of work, reporting 0 completed tasks 9/3/2008 14:40:55|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:40:55|rosetta@home|Message from server: No work sent 9/3/2008 14:40:55|rosetta@home|Message from server: There was work but you don't have enough disk space allocated. 9/3/2008 14:40:55|rosetta@home|Message from server: An additional 263 MB is needed. 9/3/2008 14:45:01|rosetta@home|Sending scheduler request: To fetch work. Requesting 957 seconds of work, reporting 0 completed tasks 9/3/2008 14:45:06|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:45:06|rosetta@home|Message from server: No work sent 9/3/2008 14:45:06|rosetta@home|Message from server: There was work but you don't have enough disk space allocated. 9/3/2008 14:45:06|rosetta@home|Message from server: An additional 263 MB is needed. 9/3/2008 14:49:11|rosetta@home|Sending scheduler request: To fetch work. Requesting 955 seconds of work, reporting 0 completed tasks 9/3/2008 14:49:16|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:49:16|rosetta@home|Message from server: No work sent 9/3/2008 14:49:16|rosetta@home|Message from server: There was work but you don't have enough disk space allocated. 9/3/2008 14:49:16|rosetta@home|Message from server: An additional 263 MB is needed. 9/3/2008 14:53:22|rosetta@home|Sending scheduler request: To fetch work. Requesting 953 seconds of work, reporting 0 completed tasks 9/3/2008 14:53:27|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:53:27|rosetta@home|Message from server: No work sent 9/3/2008 14:53:27|rosetta@home|Message from server: There was work but you don't have enough disk space allocated. 9/3/2008 14:53:27|rosetta@home|Message from server: An additional 263 MB is needed. 9/3/2008 14:57:32|rosetta@home|Sending scheduler request: To fetch work. Requesting 951 seconds of work, reporting 0 completed tasks 9/3/2008 14:57:37|rosetta@home|Scheduler request succeeded: got 0 new tasks 9/3/2008 14:57:37|rosetta@home|Message from server: No work sent 9/3/2008 14:57:37|rosetta@home|Message from server: There was work but you don't have enough disk space allocated. 9/3/2008 14:57:37|rosetta@home|Message from server: An additional 263 MB is needed. Any ideas how to get some work from Rosetta?

3) Questions and Answers : Windows : Etra Instance of BOINC Manager Window? (Message 14958) Posted 29 Apr 2006 by JAllan32 Post: I have it running as a single user installation. The BOINC manager program is in my startup folder ("C:Program FilesBOINCboincmgr.exe" /s), but I don't remember if it was put in automatically by the install program, or if I put it there myself. If you recommend taking it out, I will do so. BTW I didn't notice the typo of "EXTRA" in the title until it was too late to change it. Thanks for your help; standing by before taking any action.

4) Questions and Answers : Windows : Etra Instance of BOINC Manager Window? (Message 14715) Posted 27 Apr 2006 by JAllan32 Post: BOINC Manager 5.2.13 under Windows XP Pro, set up to start with boot-up. After boot-up, the circle-B icon is found in the tray, but a 'visible' button is also found on the taskbar. The taskbar button has all options on right-click except Restore. Selecting Close has no effect. Selecting Maximize restores a full-screen window with NO DATA on any tab. This window CAN be Restored to normal size, but cannot be closed, only Minimized to the taskbar. Surprisingly, after much trial and error, I found that if the circle-B in the TRAY is double-clicked, the Restore-sized BOINC Manager window appears, with all tab data present. This window appears to BE the phantom window, since there is no additional button on the taskbar. AFTER performing this non-intuitive procedure, the window CAN be closed as expected, making the taskbar button disappear, while leaving the circle-B icon in the tray. Everything is now normal until I reboot again. If this is unavoidable Windows behavior, it might be a good idea to note this in the instructions so the users don't try wierd things like playing with the MSCONFIG to try to get rid of it.

©2024 University of Washington
https://www.bakerlab.org