That's a good one and mentioned before on these fora... did disable that as it caused corrupted WU's. It's strange in that in one of the XP's Time & Date applets Internet Clock tab - right click on Time in Start bar - it says that the next sync is 15.3.07 at 21:58.... the default 604800 seconds. Another machine never modified has a schedule of every 24 hours, which is not what the MS KB article indicates as default. May explain the zero state message on this one as i hibernate all every evening and when waking them up, usually have them showing even before I set the activity in BOINC back to "Run Always".

Hey - no problem - hopefully you'll get yours to work - I'm still struggling with mine but working through the diagnostics - if anyone else has any more ideas please let me know

Did you disable the W32Time service? That is what I did and it stopped Windows from using NTP to check the time, but something in Windows started checking the PC's CMOS time every 4 hours. I never did figure out which process in Windows was running that connects to the CMOS. The only way I could get rid of the message was to follow the instructions on the MicroSoft KB, and set the NTP update interval to 1 hour or less.

Ideally with the 6 gb free on disk he should set the virtual memory to be automatic if such a thing is possible in Linux, rather than fixed. As for the latest FAAH, they have been at times 265/270mb thus 248mb free ram + 7.8mb vm will have had it hit the wall. For HDC the needed size is really upwards of 1gb, but that would not run or be received on a 256mb ram anyhow.

As for my zero state problem, worked thru the kb article and set the synching to 3600 seconds. No more occurrence seen, even if coming out of hibernation, when the internet link is up long before taking the BOINC agent out of suspend....excellent reminder.