Also read this:
WaitToKillServiceTimeout registry value does not work in Windows 7 (Hotfix Download Available)
http://support.microsoft.com/kb/2549760

Note:
On XP WaitToKillServiceTimeout is 20 seconds (20000 ms) by default
On Windows 7 it seems to be only 5 seconds (5000)

Obviously Microsoft thinks than today computers are fast but if there are many processes to end at restart then 5 seconds is too little time


The direct link to this Hotfix is (I think):
http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix367694/7600/free/435571_intl_x64_zip.exe

Use at your own risk! - I do not have Windows 7

The file is 435571_intl_x64_zip.exe
It is 'SFX ZIP archive' and contains one file Windows6.1-KB2549760-x64.msu dated 19.07.2011
so this may be already installed by Windows auto-updates (e.g. if you see KB2549760 installed in history of updates)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I made those changes.

However, I failed to say that while I have Win 7 64 bit home premium, I "had" tried the 64 bit version of BOINC, and had worse trouble. So I am running the 32 bit version.

How do I make changes to the 32 bit segment of the registry?

How do I make changes to the 32 bit segment of the registry?

The above registry changes are not related to BOINC, they jut tell Windows how long to wait before it kills any program at Windows restart/shutdown

So (I think) you don't need to find 'the 32 bit segment of the registry'.
Do you see those keys/values in your registry? (probably yes as you say: "I made those changes")
What delays did you set?

If you want to find all occurrences of e.g. WaitToKillAppTimeout in a single list use:
RegScanner
http://www.nirsoft.net/utils/regscanner.html

(I used just WaitToKill as a search string)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

The game is no permanently called due to technical difficulties!

All the registry entries has NOT fixed this issue.

The Hotfix doesn't seem to have done anything to resolve it either!

Please delete me from your system!

I'm uninstalling BOINC.

It's a darn shame that Win 7 64 bit is NOT compatible with this.

The 64 bit version of BOINC is just as bad!

This old SYSADMIN has had more than enough!

B-Squared

The game is no permanently called due to technical difficulties!

All the registry entries has NOT fixed this issue.

The Hotfix doesn't seem to have done anything to resolve it either!

Please delete me from your system!

I'm uninstalling BOINC.

It's a darn shame that Win 7 64 bit is NOT compatible with this.

The 64 bit version of BOINC is just as bad!

This old SYSADMIN has had more than enough!

B-Squared

It seems to be just your machine. I have BOINC running on Win 7 64 bit with no problems.

No, accounts are not deleted.

---

BOINC WIKI

If one reads the *fixes* that have been suggested, and the FACT that they *HAVE* been applied, PLUS that when a restart occurs ALL projects STILL disappear, *THEN* BOINC does NOT PROPERLY function, despite YOUR assertions.[/b]

Then why this happens only on your computer? (at least you are the only one posting about this AFAIK)

Why 431882 computers can use Microsoft Windows 7 for BOINC/SETI?:
http://boincstats.com/en/stats/0/host/breakdown/os/

Mind that we (posters here) are not BOINC developers.

Something on your system kills the processes (instead of sending them Exit signal/request)
(may be some other program, do you have some tool that claims to do 'fast/quick shutdown/restart'?)
Or your antivirus is deleting files?

And is it so difficult to exit BOINC manually before Windows restart?


Most 'tech experts' read the 'Number crunching' forum so you may ask there:
http://setiathome.berkeley.edu/forum_forum.php?id=10

If you do - give (in your post/thread) this link to your first post (so people will know what is already discussed and done):
http://setiathome.berkeley.edu/forum_thread.php?id=68120&postid=1326143#1326143

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

If one reads the *fixes* that have been suggested, and the FACT that they *HAVE* been applied, PLUS that when a restart occurs ALL projects STILL disappear, *THEN* BOINC does NOT PROPERLY function, despite YOUR assertions.[/b]

Where is your DATA directory?

---

BOINC WIKI

If one reads the *fixes* that have been suggested, and the FACT that they *HAVE* been applied, PLUS that when a restart occurs ALL projects STILL disappear, *THEN* BOINC does NOT PROPERLY function, despite YOUR assertions.[/b]

Where is your DATA directory?

You suspect it is on RAM drive? Or disk cache is not written to disk?

By "ALL projects disappear" I think he means "ALL tasks disappear"

From his first post: "I lose ALL tasks, and end up with "Lost tasks loading"."
If he loses DATA directory then he have to attach to projects again possibly getting new HostID (in which case "Lost tasks loading" ('Resent lost task') will not happen)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

If one reads the *fixes* that have been suggested, and the FACT that they *HAVE* been applied, PLUS that when a restart occurs ALL projects STILL disappear, *THEN* BOINC does NOT PROPERLY function, despite YOUR assertions.[/b]

Where is your DATA directory?

You suspect it is on RAM drive? Or disk cache is not written to disk?

By "ALL projects disappear" I think he means "ALL tasks disappear"

From his first post: "I lose ALL tasks, and end up with "Lost tasks loading"."
If he loses DATA directory then he have to attach to projects again possibly getting new HostID (in which case "Lost tasks loading" ('Resent lost task') will not happen)

I was suspecting something like this. Possibly a write access problem of some sort.

---

BOINC WIKI