You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A year ago we tackled an issue where GPU detection failed if the client was started from the command line with "boinc", rather than "boinc.exe"
The problem has been re-reported for BOINC v7.10.2 and v7.12.1, but this time when the invocation is from a batch file or from BoincTasks, if the correct working directory is not used. Compare these screenshots (from Process Explorer)
After all the multiple restarts to detach from the command window and do the GPU detection, the final running client instance was still started with the full path on the command line (D:\BOINC... on my machine). By contrast, v7.12.1 starts with the now hard-wired "boinc.exe", but no path.
I think commit 7930686 just moved the problem around a bit, without fully fixing it. We need both the path and the .exe
The text was updated successfully, but these errors were encountered:
Previous references: issue #2029 , PR #2036.
A year ago we tackled an issue where GPU detection failed if the client was started from the command line with "boinc", rather than "boinc.exe"
The problem has been re-reported for BOINC v7.10.2 and v7.12.1, but this time when the invocation is from a batch file or from BoincTasks, if the correct working directory is not used. Compare these screenshots (from Process Explorer)
After all the multiple restarts to detach from the command window and do the GPU detection, the final running client instance was still started with the full path on the command line (D:\BOINC... on my machine). By contrast, v7.12.1 starts with the now hard-wired "boinc.exe", but no path.
I think commit 7930686 just moved the problem around a bit, without fully fixing it. We need both the path and the .exe
The text was updated successfully, but these errors were encountered: