Message boards :
Number crunching :
Boinc won't run on new install......HELP!
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
rob smith Send message Joined: 7 Mar 03 Posts: 22419 Credit: 416,307,556 RAC: 380 |
One possible solution is to add a start up delay to your cc_config.xml file: <start_delay>nseconds</start_delay> I had to do this on one of my crunchers some time ago for much the same reason as you are suffering just now - I think I used a 120 second delay. The delay gives the drivers time to get going properly before BOINC starts to do its system probing to see what hardware is available. edit: Under Windoze 7 the default location of cc_config is c:\ProgramData\BOINC (by default this folder is hidden) Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
Does anyone have any thoughts on this? Hi Grant. I noticed that too, but disabled the AV program during installation and it makes me wonder why the old version 7.0.46 (I think) will work but not the newer ones. The installation was a clean install to 64 bit Win7, but it was to the same disk drive that the older Vista 32 bit was on. I assume that Win7 automatically reformatted the drive on installation. I'm sure the new d/l of Boinc is 64 bit, but I will d/l it again and try to reinstall per your suggestion. Thanks! Allen |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
The most useful link I've been able to find concerning "Problem Event Name:BEX64" issues. |
The_Matrix Send message Joined: 17 Nov 03 Posts: 414 Credit: 5,827,850 RAC: 0 |
I am always using a videocut software , guess what, i want to install it on W7 64-bit, but the system refuses. I had to download the software new, then it installs. But before it always worked. -,- gremlins.... |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
One possible solution is to add a start up delay to your cc_config.xml file: Some things are just so darn finicky..guess that's another one I'll have to try and since it's the simplest, I guess I'll try it first. Thanks! |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
One possible solution is to add a start up delay to your cc_config.xml file: Rob, That didn't go so well. My c:\ProgramData\BOINC directory doesn't even have a cc_config.xml file in it. Do I need to make one? Allen |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
Just thought that I would get back to you all with my dismal results after checking out all of the suggestions. Unfortunately nothing worked and I am back to running the older version of Boinc. At least I am able to run. Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem. Thanks to all for giving it a shot! Allen |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13831 Credit: 208,696,464 RAC: 304 |
Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem. Process Monitor might be the best option. Fire it up, run the BOINC installer, then check to see what was happening just prior to the BEX64 error. Grant Darwin NT |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
You could check stderrdae.txt in BOINC's data directory if the client had a chance to log the error there. Did you try 7.6.33? |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
You could check stderrdae.txt in BOINC's data directory if the client had a chance to log the error there. I didn't even know there was a 7.6.33. When I try it again, I will check the err file. Thanks! |
AllenIN Send message Joined: 5 Dec 00 Posts: 292 Credit: 58,297,005 RAC: 311 |
Perhaps sometime in the future I will come across some more clues and finally solve this unusual problem. Definitely a good idea. Will try it the next time I go hunting...grin Thanks! |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.