Next time you start BOINC Manager it start just BOINC Manager. If you want a quick and easy life, go for option four.īOINC Manager->Options->Other options->uncheck "Run the client?"->OKīOINC Manager->File->Exit->check "Stop running tasks when exiting the manager?"->OK It all depends on your knowledge of Windows installation and deployment issues. The third option would put the right files in the right places, and even create launch icons. A tool like Dependency Walker will help you with either option. With the second option, the DLLs will be included in the admin image, but you still need to deploy them manually. With the first option, you'd have to find and deploy the right DLLs yourself. It's normally the job of an installer to supply and deploy these DLLs to the right place.
The problem with the first two is that Windows programs aren't simple self-contained binaries: they rely on a complicated set of 'DLLs', or 'Dynamic Link Libraries'. * Install an alternative third-party Manager like BoincTasks * Install the combined BOINC package, then disable the client part * Download the combined BOINC installer from, and run it with the /a admin installation switch to extract files only * Download the Manager directly from the source repo: currently, I'd recommend I have already joined otherwise I wouldn't be able to post here, and also I have installed, configured and it's running tasks, of boinc-client on my headless Ubuntu server, what I wanted was to install just the boinc manager on my windows workstation to control boinc-client on my Linux server, I do NOT want to install boinc on my workstation I only want to install only the manager for remote control of the boinc client on my linux server.You have multiple options, but none of them are clean or simple: none of them have a clean, "Manager only", installation route.
0 kommentar(er)
