[General Topics] Menneisyys:
2.1.2 Wacom pressure sensitivity support

As with XP, the factory driver available at the official HP download page doesn't support pressure sensitivity. You must download the XP driver from HERE (if the link doesn't work, go HERE and select Tablet PC from the left and Windows XP from the right list). (I've used XP SP2 compatibility mode and installed it as an administrator.) It's the driver that is automatically installed when you right-click the unknown devices in the device manager after installing W7 and force a driver update.

I've tested it work with Corel Painter X, in Edit / Preferences / Bush Tracking. With a non- pressure sensitive (HP) driver, the lowermost two sliders will remain the same, no matter how much hard you press the pen on the screen on the scrap field; with the Wacom driver, they'll move just like the uppermost sliders. (Photoshop users should take a look at THIS, should they not know how pressure sensitivity can be utilized. A not that interesting video is HERE)

2.1.3 I've tried to hack the following video drivers…

I present you a detailed explanation of what video drivers I've tried to hack to gain both orientation change support (which, again, is supported by the stock HP driver when manually installed) and full video acceleration. So far, I had absolutely no success. Hope the TC1100 folks I've posted my premilinary results to (see THIS and THIS threads) will have more success than me.

2.1.3.1 The laptopvideo2go driver hack

I've thoroughly tested the laptopvideo2go driver hack mentioned at http://www.tabletpcbuzz.com/showthread.php?t=36154&page=2 and explained at http://www.laptopvideo2go.com/forum/index.php?showtopic=9547 . I've downloaded 84.43 from http://www.driverheavendownloads.ne...ile=84.xx/84.43_forceware_winxp2k_english.zip ( linked from http://www.driverheavendownloads.net/nvidia.htm ) and let it decompress itself to under c:\NVIDIA (of course, it couldn't install as it's incompatible with the system). I've replaced the INF file (after changing the two (!) occurrences of Rotateflag in the file from 4 to 0x40) and, after renaming, I've copied the DLL file to the same directory. After this, I've run setup.exe in the same c:\NVIDIA\some subdirectory as an administrator.

It didn't really work – I couldn't find any difference from the stock HP driver (also installed as Administrator, in XP SP2 compatibility mode). While it does support rotation (unlike the standard, stock driver installed by Win7 by default), it also crashes on D3D / movie playback with a nv4_mini.sys BSOD (page fault in nonpaged area).

2.1.3.2 Mobility Modder hack attempts

Also tested with the latest Vista driver (178.24_geforce_winvista_32bit_english_whql.zip) with the driverheaven.net "Mobility Modder" hack. A no go - not even orientation changing is supported.

I've done the same to ForceWare 93.71 WHQL as it's the last driver to support the GeForce 4 MX series, according to the page HERE) – a no-go either.

Note that I haven't tested GeForce Release 179 for Notebooks (see THIS). Dunno if they would work.

2.1.4 Sleep problems

W7 seems to have major sleep problems (note that hibernation is working just great). In many cases, when you resume the notebook from sleeping, it just won't display anything and you'll end up having to restart the entire device by long-holding the Power slider.

That is, don't use Sleep mode for the time being. Also make sure you disable automatic sleep timeouts. Always use hibernation instead.

2.2 IBM ThinkPad t42p

Unlike with the TC1100, I had absolutely no problems with the t42p (and don't have since then, except for some file integration problems. I will keep my eyes open to

The Windows Experience Index (WEI) isn't at all bad, given that it's a 2004 model:

Everything is working (including the volume / ThinkLight / backlight buttons and hibernation / sleeping), except for the additional, IBM-specific functionality like Fn +Space (to quickly switch between the UXGA (1600*1200) and SVGA (800*600) resolution) or Fn + F3 (to dim the screen). There're no on-screen controls for the volume / backlight buttons either.

(Note that the situation is exactly the same on the a31p.)

2.2.1 Emulating the Windows key

As you probably know, Windows 7 uses a lot of keyboard shortcuts to access some advanced functionality. With Windows Aero, one of them is Flip 3D, requiring you to use Win+Tab.

To map an existing button to the Windows button, use THIS utility. It worked flawlessly on my t42p (as usual, installed in XP SP2 compatibility mode and as an administrator). After installing and restarting your PC, go to All Programs / ThinkVantage / Keyboard Customizer Utility, check the Enable key assignments checkbox and select a button to map to the Windows key (uppermost drop-down list):

After this, among other things, Flip 3D will work just fine:

(click the image for a full-sized version)

(Incidentally, if you have a PC with a comparatively good video card but Aero still isn't enabled, you can give a try to the Aero-enabling hack described in the article Hack to Force Enable Aero in Windows 7)

2.2.2 Other stuff to install

You'll want to install the two files (Hotkey Driver and System Interface Driver) also linked from the first post HERE. Note that, as has also been explained in the post, you'll need to execute c:\DRIVERS\WIN\HOTKEY\SETUP.exe and c:\DRIVERS\WIN\SMIIF\SETUP.EXE – that is, simply downloading and executing the two installers won't suffice as all they do is decompressing their content. After this, not only the standard (sleep / hibernation / backlight / volume / Fn + F7 [switching between internal and external monitors]) hotkeys will work (or, on the A3x-series like the a31p, the app buttons on the left), but also for example zooming (Fn – Space; it's also used as sending the current window to the other desktop.) Also note that, during install, Hotkey Driver may display an error message. (This happened on my t42p but, interestingly, it didn't do the same on my a31p.

Incidentally, external monitors will work just fine. I've tested this with an external Viewsonic monitor with the native resolution of 1680*1050 (WSXGA+). When duplicating the built-in display's content, UXGA was used on both (the built-in and external) monitors (meaning a bit suboptimal, but still pretty good rendition on the external one); when extending the desktop, both LCD's were driven at their native resolution (UXGA for the built-in and WSXGA+ for the external one):