It's been a while since I upgraded my NVidia Opencl app and have a question prior to upgrading to r1764, which is -- Why do we need 2 cmdline txt files when one is empty?. The following was introduced in the r1761 version

<file_name>ap_cmdline_win_x86_SSE2-OpenCL_NV.txt</file>
<open_name>ap_cmdline.txt</open_name>

All cmdline text is in the <file_name>, while the file named in <open_name> is empty. When I upgraded to r1761, I renamed what was then the cmdline text file to <file_name> and created a new empty cmdline.txt <open_name>.

---

I don't buy computers, I build them!!

That mechanism basically tells Boinc to use the full versioned name, by creating a boinc softlink in the slot with the generic open name expected by the app.

That allows the app to just use the generic name, but Boinc links it to & opens the appropriate file, usually in the project directory. The reasoning I believe is that firstly the Boinc server infrastructure doesn't like name clashes across app versions, while adjusting the name in every app build is not easy/practical.

A potentially positive side effect is that it allows you to use different apps with versioned files perhaps with differing settings.

[In the server distributed case] The settings files are distributed as 0 length files so that the client doesn't 'freak out' and try to redownload when you modify it.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

That mechanism basically tells Boinc to use the full versioned name, by creating a boinc softlink in the slot with the generic open name expected by the app.

That allows the app to just use the generic name, but Boinc links it to & opens the appropriate file, usually in the project directory. The reasoning I believe is that firstly the Boinc server infrastructure doesn't like name clashes across app versions, while adjusting the name in every app build is not easy/practical.

A potentially positive side effect is that it allows you to use different apps with versioned files perhaps with differing settings.

[In the server distributed case] The settings files are distributed as 0 length files so that the client doesn't 'freak out' and try to redownload when you modify it.

Thanks Jason, I will carry on with the upgrade.

---

I don't buy computers, I build them!!