I discovered some bugs which PPA causes in the system after installation. I don't know if you're aware of them but here goes. Firstly, after installing PPA, Windows doesn't know its own edition i.e. when you check under Windows Activation, Windows edition is blank.
And, when I run Windows Experience Index, it doesn't complete. It used to complete before installing PPA.
I have pinpointed these errors to PPA because I did a clean installation and these happened right after the restart which succeeds PPA. I guess something with the way you fixed the Test Mode watermark is causing this. I'm just guessing here. I don't have a clue. Also, you migt be aware of sfc /scannow which we run in a command prompt to find any system errors. When I run sfc /scannow, it says errors found and fixed, tells me to restart and the Test Mode watermark is back . I used your fix for that
Now, there are some bugs in PPA itself. I like to turn off the option in PPA which disables adjustment of keyboard backlight. After I turn this off, whenever PPA starts on startup it kills the Bootcamp process and I have to manually start it. Why is that? Please look into this
You have been very helpful listening to our errors, bugs and problems, so please help me on this one. I'm using a Mid 2012 MacBook Pro non-retina 15-inch and the OS is Windows 8 Pro with Media Center.
@pratnala: This appears to be Windows 8 specific. And, actually, the answer is simple - the edititon name is blank because this is the same string which is the part of "Test Mode" desktop message. I can leave this part of the message, but you will see the Windows edition on your desktop. Also, you have to know, this has nothing to do with system identification, activation, etc. The fix only removes certain text from the dll resource, i.e. precisely the test mode and version display text that is shown on the desktop.
Now I will investigate the second issue.
Thanks for reporting, highly appreciate this.
@pratnala: Windows experience index seems to internally use the same string, too. This is the reason.
But, you know, we shall thank God there exists at least this kind of the solution for not having the test mode message on the desktop. No other ways to remove it are known.
Regarding the Bootcamp.exe effect: I am sorry to announce this, but the option you mentioned will most probably be removed from PPA soon (because of the compatibility). The future PPA will act as a disabler of keyboard backlight, but you will be able to turn it on and adjust its intensity on demand (with top keys). Also, keep in mind that it's not mandatory to have PPA running for the Trackpad++ to function properly. You can just install the PPA, then remove it.
Thanks for the prompt reply Vlad. I understand that the Test Mode removes the entire string. But, I must add that it prevents activation as well. After reinstalling Windows and before activation, I had installed PPA for Trackpad++ (I'm highly addicted to Trackpad++!!) and then I couldn't activate the system. I had to reinstall Windows again, activate Windows and then install these 2 things. So, please kindly look into this. Things like Windows Edition and Windows Experience Index are trivial things but activation is a serious issue.
And, also now I understand why PPA 3.0a showed the Windows edition on my desktop but not the Test Mode message! I always wondered how it disappeared after 3.0b! Ha!
Now, regarding Bootcamp.exe, are you saying that keeping that option will necessarily kill the Bootcamp process and hence, that's why it is being removed?
@pratnala: Not exactly. This option stands for enabling/disabling automatic adjustment of the keyboard backlight intensity, right? But, in fact, older and newer Macbooks have different behavior. Pro and Air also have slightly different behavior. This is why I'm talking about the compatibility.
Activation just works for me, strange! I will definitely take a deep look on this.
@all: Posted earlier in this topic, but new people still ask me a lot, so I think I will simply re-publish this time after time.
So, for the new people, here are the current capabilities of the Trackpad++ for Windows 8 specifically.
Supported Apple Macbook Pro generations: Early 2009, Mid 2009, Mid 2010, Early 2011, Late 2011, Mid 2012 / Retina, Late 2012 / Retina.
Supported Apple Macbook Air generations: Mid 2009, Late 2010, Mid 2011, Mid 2012.
Improved basics (vs. Boot Camp drivers 4.x):
1.) Accelerated/natural scrolling model implemented;
2.) Better pointer ballistics (i.e. how a pointer speed depends on a finger speed; six optimal presets built-in);
3.) Bug-free dragging with two fingers (both fingers allowed to move freely, unlike with Boot Camp-native driver), plus a unique option to increase the pointer speed while dragging;
4.) User-customizable option to ignore accidental trackpad input when typing, option to eliminate accidental drag'n'drop actions (for tap-style dragging);
Advanced multitouch gestures:
1.) Horizontal 2-finger swiping to the left from outside the right edge (action: show/hide Charms Bar, the gesture shall be performed like this: http://powerplan7.com/OutsideSwipe.gif)
2.) Horizontal 2-finger swiping to the right from outside the left edge (action: show/hide Metro Switcher if at least 1 Metro app is running)
3.) Horizontal 3-finger swiping (action: back / forward)
4.) Vertical 3-finger swiping (action: zoom in / zoom out)
5.) 3-finger tap (action: middle mouse button)
6.) Horizontal 4-finger swiping (action: show/hide Charms Bar)
7.) Vertical 4-finger swiping (action: minimize/restore open windows)
8.) 4-finger tap (action: show/hide Start screen)
So, I just started using Trackpad++. 15" MacBook Pro Aluminum. Early 2011. Win 7 Pro.
It seemed to install correctly, but if Trackpad++ Control Module is running, it consumes 12% of the CPU and my fan always runs noisily. Not good.
Is this an expected level of cycles consumption? Seems like a lot, and the fan/heat is a show-stopper.
I like what the software does. I hate the side-effects. I'm hoping there's a fix, or that you'll say this is a big surprise and offer some advice for how to possibly address this issue.
@jdbeltranstudio: this is highly abnormal. Trackpad++ normally consumes 0% CPU even on the oldest Macbooks from 2009. There exists, however, a very-very rarely happening glitch of the installer, it causes such the behavior. Please exit the Trackpad++ Control Module from the system tray and reinstall the Trackpad++ using the latest available build. The CPU load shall go away.
Please, could you return here and let me know if this helps...
Ok, whatever that obscure installer bug is, I had tickled it. I do have a 64-bit OS, but I'd followed the instructions carefully and had installed Power Plan Assistant first, as directed.
What matters to me most is that Trackpad++ is no longer at the top of my task manager. We fixed it!
Thanks so much.
Hey vladimir, I've been using your Trackpad++ for a while now, and while I did try your workaround for the two-finger right click (not tap), the result is both a left click and a right click (if I were to "right click" a shortcut on the superbar, the right click menu pops up but also minimizes the window). Is it possible to make an option to have the two-finger right click as a separate option? Thanks!
First, a small preamble regarding the right-click in Boot Camp. There are actually four types of right-click on a Mac, and all four shall now work under Windows with Trackpad++:
1. Control + click (oldest method of right-click that originated on the first Macintosh)
2. Two finger tap (second oldest method of right-click that originated on the first non-unibody MacBook)
3. Two finger click (third oldest method of right-click that originated on the first unibody MacBook)
4. Lower right region click (implemented at the same time as above method)
Over all 4 methods, I would choose 2-finger tap. It works quite reliably (actually, I don't think in the Mac OS X it is any better).
The problem with physical click method (3) is that lower HID stack driver (Apple's) seems to trigger this extra left click. It's Boot Camp-inherited issue. So, it cannot be fixed that easily. You have to know, the Trackpad++ is not a completely standalone driver. It to some extent depends on the existing functionality of the lower level (Apple-provided) driver. The gestures, for example, are completely independent. But some basics like the clicking are not. It's difficult to explain why, but for now this is the most reliable way. I mean, to have the Trackpad++ driver integrated, thus not overwriting the entire HID stack built by the Apple Boot Camp package installer.