still having problems?!!!!
18 Jun 2005 1:14:17 UTC
Topic 189369
(moderation:
iam still having problems iam still getting can't wright to state file-109.iuninstalled the old 4.25 and installed 4.45 tha did not change any thing but made it worses. after i install it and restarded the computer boinc starded 2 times i had 2 boinc programs runing at same time had to go into config and un check one of the start up so i could get only one to start.i have done just about ever thing i can think of but it just does not work.also it also deattch both set and einstein when it connected.
still having problems?!!!!
)
BOINC ยป BOINC Messages
Couldn't Write State File: -109
Message Type: Error
This error is a write protection error encounted by the BOINC Daemon. Possible causes include:
Improper termination of the BOINC Daemon.
Improper shutdown of the computer.
Use of anti-spyware or anit-virus applications.
One of the most likely causes is the use of anti-virus/anti-spyware tools. Turn off the "Real Time Protection" mode (the name may vary depending on the product) and restart the BOINC Software.
Last update: 2005-03-02 14:14
Author: Paul D. Buck
Link to Unofficial Wiki for BOINC, by Paul and Friends
thanks for the info but have
)
thanks for the info but have used my spysweeper and norten internet2004 along with boinc for a long time did not cause any problems untill about 2 week a go.just about the time einstein@home server went down? i tryed to go back to a system restore point but now i can not even do a restore.so i am going to renstall windows may have a bad driver or as any one ever check the servers for a root viruses that may be why they have so many sutdowns.iam going to be down for a bit.thaink so much for info will deside if iam going to stay with boinc.
RE: thanks for the info but
)
Grab FileMon from SysInternals and run it. Set the include filter to boinc* and have it running when you start BOINC. Then look for error messages associated with writing the files. That will show the exact error.
In running it, the magnifying glass shaped icon starts and stops the trace, so you can get FileMon started but not tracing until BOINC starts. And once you have some trace info from the time you see the error, you can stop the trace and view the output.
If you can't interpret the output, you can save the trace to a log file and send it to me at wgdebug (at) yahoo (dot) com. Say something here so I know to check the account, I don't check it every day.
Since I do not know what you
)
Since I do not know what you have tried.
You are running under an administer account? Installing using an admin id and running with a user id can cause this problem.
Are you installing in a directory under c:\program files\....? If so try installing at root; c:\boinc; or on a differctn drive d:\boinc. Programs installed under c:\program files\.... have different security permissions.
You like Myst? Uru Live returns! www.urulive.com