@superkrups20056: It's true that the currently shipped driver is not Microsoft-cross-signed, so Windows doesn't trust it, as explained in detail during the prerequisite Power Plan Assistant install. That's how it's been working all these years. Since you chose to not follow the first installation chain requirement (where it's needed to first install the Power Plan Assistant, and then Trackpad++), you are therefore observing such behavior (the watermark). The TESTSIGNING shall be enabled, or the driver will not be functional. One of the reasons why the Power Plan Assistant is the prerequisite component is that it (asks you and then) prepares the system so that no TESTSIGNING watermark is shown. Also there exists a standalone watermark remover, I can email it to you if you wish.
Alternatively, very recently it's become possible to request the Microsoft-cross-signed trackpad driver (basically, it's the same-as-current driver, every bit is the same, just signed by an authority and with Microsoft's own cross-certificate). You can contact me via email if interested in this option. Again, I can't put all the details there (see my previous posts).
@calkenneth: To check that this option is really working: please set it to 'Ignore All Trackpad Input', apply, then open e.g. Notepad, and start typing (better simply hold some letter) while moving the pointer. The pointer should stop immediately, and continue moving only after approximately one second after the key is not pressed anymore. Does this option work for you in such scenario?
@calkenneth: Yes, it's the simplest test. I suppose after Boot Camp update something went wrong with your instance of Trackpad++. May I suggest the following: please quit the Trackpad++ Control Module from tray icon, then delete the folder C:\Program Files\TrackpadPlusPlus, then reinstall the Trackpad++ using the latest build from November 26.
Please let me know if this feature works for you now. Thank you.
Hi,
Followed those steps and it's working again. Why would the feature suddenly disappear? If that were to happen again, is the solution to simply reinstall or will a reboot be enough?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80041313): The task object version is either unsupported or invalid. (Exception from HRESULT: 0x80041313)
at TaskScheduler.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, _TASK_LOGON_TYPE LogonType, Object sddl)
at TPPLauncher.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Trackpad++ Control Module
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/TrackpadPlusPlus/Trackpad++%20Control%20Module.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Interop.TaskScheduler
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/TrackpadPlusPlus/Interop.TaskScheduler.DLL
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8693 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Has anyone tried out the microsoft signed driver that avoids the need for power plan assistant? Would be interested in how well it works out.
@BatKing: Thank you for the feedback!
Thanks. I'll give it a try at work tomorrow and report back.@stridemat: Could you try to delete the folder "C:\Program Files\TrackpadPlusPlus" and then re-run the installer of the Trackpad++. Actually in the recent build the sources related to supporting the 2013 generation of the Macbook Air were not touched all, so everything should install just as properly as in the previous builds.
Could you let me know if this helps? Thank you.