Message boards : Questions and problems : how to install on drive other than "C"?
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Mar 12 Posts: 1 ![]() |
I have boinc up & running on my "C" drive. The only problem now is that the "c" drive has very little space on it. Would it be possible to install boinc on a drive other than "C"? Ideally, I would like to install a second instance of boinc on my "E" drive (a 200 GB drive; "C" is only 80 GB)and run them both at the same time. If it is only possible to run one boinc manager, then can you tell me how to install and run it on the "E" drive (it has 150GB open)? Thanks in advance.... |
![]() Send message Joined: 29 Aug 05 Posts: 15628 ![]() |
When you install BOINC, you can choose where to put its parts, e.g. the programs directory and the data directory. You will want to move the data directory, as this takes up the most room. To do so, uninstall BOINC through Add/Remove Programs or Uninstall a program (depending of Windows version... you don't say what OS you run, so I just assume Windows). Next first move the data directory to wherever you want it to go sit. Do this by moving the whole BOINC directory with all files and sub-directories in it. Default places for the data directory are in this FAQ. Next you go install BOINC and in the third screen in the installer, click the Advanced button. That'll open the options for you to change. ![]() ![]() Change the path to the data directory to where you put it on the other drive, then continue the BOINC installation. As far as running multiple BOINC clients, may I ask why? It won't speed up any work, more so even slow it down. If you want to do so to work on one project with one GPU and another only with another, then install BOINC 7.0.20. It may still be development, albeit with less bugs than before, it also comes with the <exclude_gpu> option. Running multiple BOINC clients together seems to work OK on some Linux versions, but not so on Windows. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.