Dunno - which client are you using? I vaguely remember that there was one which tended to throw his files in root directories of the hard drive, but that should long have been fixed...
Did you try starting BOINC from a DOS prompt? When you were at D:\\?
BOINC doesn't change the directory, so whatever directory is the "current directory" when it starts is where it writes those files, and looks for the ones it uses. Do you also now have "Projects" and "Slots" directories along with a couple of .....xml files?
Another way it can happen is by creating a shortcut by copying an existing shortcut, changing it to point to the BOINC program, but forgetting to change "working directory".
What timestamps do the files have? And whats the first line in stdout.txt? Thats when those files were created, and which version created them. Time might correspond with something you remember happening. The rest of stdout.txt should show some kind of error. If so, what?
I had this happen to me when I tried running BOINC from the command line to "control" another instance running. I found it doesn't work that way, the command line options aren't used to control another instance already running.
BOINC is being started from a .bat file which is on D:/. I do it with:
cd "C:/Program Files/BOINC"
"C:/Program Files/BOINC/boinc_gui.exe"
Files have timestamp of the last time BOINC was started. First line of stdout.txt is:
2005-02-26 08:53:40 [---] Starting BOINC client version 4.19 for windows_intelx86
I'm going to start it using the shortcut it created and see what happens.
> BOINC is being started from a .bat file which is on D:/. I do it with:
> cd "C:/Program Files/BOINC"
> "C:/Program Files/BOINC/boinc_gui.exe"
>
Thats your problem.
You're changing the current directory on the C: drive, but you stay on the D: drive which is used by BOINC. Use this:
c:
cd "C:/Program Files/BOINC"
boinc_gui
> Files have timestamp of the last time BOINC was started. First line of
> stdout.txt is:
> 2005-02-26 08:53:40 [---] Starting BOINC client version 4.19 for
> windows_intelx86
>
> I'm going to start it using the shortcut it created and see what happens.
Did the first suggestion. (Sometimes I surprise myself at being able to do dumb things. I've only been writing batch files for 22 years. You'd think I would remember simple stuff like this.)
lockfile, stdout.txt, and stderr.txt on wrong disk
)
Dunno - which client are you using? I vaguely remember that there was one which tended to throw his files in root directories of the hard drive, but that should long have been fixed...
BM
BM
This is version 4.19 of the
)
This is version 4.19 of the BOINC code and 4.79 of Einstein. Downloaded from the Einstein@Home web site on 2/24/05.
Did you try starting BOINC
)
Did you try starting BOINC from a DOS prompt? When you were at D:\\?
BOINC doesn't change the directory, so whatever directory is the "current directory" when it starts is where it writes those files, and looks for the ones it uses. Do you also now have "Projects" and "Slots" directories along with a couple of .....xml files?
Another way it can happen is by creating a shortcut by copying an existing shortcut, changing it to point to the BOINC program, but forgetting to change "working directory".
What timestamps do the files have? And whats the first line in stdout.txt? Thats when those files were created, and which version created them. Time might correspond with something you remember happening. The rest of stdout.txt should show some kind of error. If so, what?
I had this happen to me when I tried running BOINC from the command line to "control" another instance running. I found it doesn't work that way, the command line options aren't used to control another instance already running.
BOINC is being started from a
)
BOINC is being started from a .bat file which is on D:/. I do it with:
cd "C:/Program Files/BOINC"
"C:/Program Files/BOINC/boinc_gui.exe"
Files have timestamp of the last time BOINC was started. First line of stdout.txt is:
2005-02-26 08:53:40 [---] Starting BOINC client version 4.19 for windows_intelx86
I'm going to start it using the shortcut it created and see what happens.
> BOINC is being started from
)
> BOINC is being started from a .bat file which is on D:/. I do it with:
> cd "C:/Program Files/BOINC"
> "C:/Program Files/BOINC/boinc_gui.exe"
>
Thats your problem.
You're changing the current directory on the C: drive, but you stay on the D: drive which is used by BOINC. Use this:
c:
cd "C:/Program Files/BOINC"
boinc_gui
> Files have timestamp of the last time BOINC was started. First line of
> stdout.txt is:
> 2005-02-26 08:53:40 [---] Starting BOINC client version 4.19 for
> windows_intelx86
>
> I'm going to start it using the shortcut it created and see what happens.
EDIT:
Or, start the link in the start menu directly:
start "c:/windows/start menu/programs/boinc/boinc.lnk"
Put that in your batch file instead of the stuff up on top.
Did the first suggestion.
)
Did the first suggestion. (Sometimes I surprise myself at being able to do dumb things. I've only been writing batch files for 22 years. You'd think I would remember simple stuff like this.)
Thanks to the folks that answered my post.