The problem with Logitech SetPoint 5.20/6.00 (APP auto detection not working properly)

Logitech SetPoint 5.20/6.00設定檔無法自動切換問題

It seems to be a common problem that the “Switch profiles automatically using Application Detection” in the Profile Manager of SetPoint doesn’t work on Vista/Win7 x64.


This problem may due to the loading time of KHALMNPR.exe(Logitech Hardware Abstraction Layer). SetPointII.exe should never be launched before KHALMNPR.exe was completely loaded. It causes the APP auto detection not working. But It seems SetPoint software didn’t consider much about the loading time between these two program.

If you got this problem, try to stop SetPointII.exe in the task manager, restart it again (from the SetPoint installation path). If it solves the problem, you can delete the SetPoint shortcut in Start>Run, and Use Schedule Manager instead to launch SetPointII.exe for a 10~30 sec delay on system startup.

—-
通常會發生在Vista/Win7 x64。

羅技的驅動程式裏面用了一個叫KHALMNPR.exe(Logitech Hardware Abstraction Layer)的東西,這應該是為了讓自家各程式都能夠呼叫所作的一個共通介面。如果SetPoint的偵測程式(SetPointII.exe)在KHALMNPR.exe載入完成之前就被執行,程式自動偵測/設定檔自動切換的功能就失效。

試著從工作管理員裏面把SetPointII.exe關閉,然後再重新執行一次(從SetPoint的安裝目錄)。如果這樣作之後切換設定檔的功能正常了,那就可以試著來修改他啟動的方式:
.先把”開始>啟動”裏面的SetPoint拿掉
.改用”排定的工作”(Win7裏面叫作”工作排程器”)來載入SetPointII.exe,執行時間設為啟動時或登入時,並設定10~30秒的延遲時間,確保他晚一點載入。

這樣就可以修好這問題了。


補充:
KHALMNPR.exe是由登錄檔中HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run載入,而SetPointII.exe則是由”開始>啟動”載入。前者是開機時,後者是在使用者登入時載入,理論上載入的順序是沒有問題;不過KHALMNPR.exe載入”完成”可能需要一些時間,而SetPointII.exe也可能早早就被執行(尤其是像Win7這種開機後馬上就能讓你登入進桌面的系統),羅技的SetPoint在處理這段可能要換個比較好的方式才比較不會出問題。

--
現在還在寫blog分享資訊的人越來越少,如果覺得文章對您有幫助,歡迎在底下留言,這樣我也比較有動力繼續寫下去,謝啦!

發佈留言

發佈留言必須填寫的電子郵件地址不會公開。 必填欄位標示為 *

 

Scroll to Top
%d 位部落客按了讚: