Tuesday, December 25, 2012
Lenovo X220T Tablet win8 wifi driver issue
The issue manifest as lost of network connection, unable to connect, or "limited connection" upon resume from sleep. Work around includes resetting NIC through NetSh, turning off and on wifi NIC, or going into and out of airplane mode.
After some digging, it appears that the Realtek driver fixes this issue. The 1x1 NIC in the X220T uses Realtek RTL8188CE chipset. The driver was last found on Dec 23, 2012 at:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true
Saturday, January 21, 2012
ASUS Zenbook Touchpad Hack
Some adjustments that can be made to help it work better are:
- Tapping - disable two finger tap for popup menu
This helps prevent the action of putting your thumb on the "left button" being mistaken as a two finger tap. - Drag and Drop - disable to avoid dragging windows if you are fast, where you double-tap and move the cursor, and the Smart-Pad thinks you are dragging.
- Smart Detector - enabled, and change the detect area to where you actually put your finger.
You can tell after some moderate use by looking at the smartpad and seeing an area of "clean" (or grease - ewww). This is the area you most likely actually are putting your pointer finger.
However, if that's NOT enough, here's one more. It's a good one. Hack the registry. This will allow you to see all the functions the smart-pad software can control, but for whatever reason ASUS or Elantech disabled for the Zenbook
- Go to HKEY_CURRENT_USER\Software\Elantech\SmartPadDisplay, and change all values to "1"
- Go to the Elan Smart-Pad's properties by using the Mouse Properties dialog box
- Now you'll see all the hidden options
Once all the options are enabled, you'll see "Palm Tracking" under Additional tab. Turn that up one notch, and it'll make the smart pad less sensitive, but it also makes accidental brushing less likely to register as a mouse movement.
Interesting note on this. Once you make changes to whatever formerly hiddened options and click OK or Apply, the previously modified registry keys will revert back to the way "they want it". If you want to experiment, it's best to change all the values to 1's, export the registry key, and use that to change all the keys at once.
Not all the newly activated options will work with the Zenbook's Elan Smart-Pad, but the Palm Check is tested to work on my UX31. Hopefully this will help you get better control over your Zenbook.
Thursday, March 10, 2011
Remove ToughBook CF-W8 Hard Drive
- Remove the battery.
- Take out 6 screws securing the HDD cover. There are 4 screws on the bottom of the laptop(chrome), and two on top (silver). The two screws on top are above the "F7" and "PrtSc/SysRq" button.
- Slide the HDD cover off the bottom. There should not be any need to pry it.
- Gently slide the HDD out of the cushioned caddy.
- Remove cable from HDD. Reverse to install.
Thursday, February 3, 2011
IAS Error Reason-Code = 65
Once user has been confirmed to be member of proper AD group with permission in IAS' Remote Access Policies (RAP), check user's AD account to confirm their "Dial-In" setting to be "Control access through Remote Access Policy".
Wednesday, September 22, 2010
Excel "File not Found" when running a Macro (*.tmp)
Remove BlackBerry IT Policy
If you are decommissioning an corporate /BES based Blackberry to personal BIS use, you may need to remove the existing IT Policy. The easiest way to do this is:
- Ensure BB has OS 4.5 or newer.
- Connect BB computer
- in command prompt, goto
c:\program files\common files\research in motion\apploader
(64 bit OS should go to c:\program files (x64)\common files\...) - run "LOADER.exe /resettofactory"
Thursday, December 17, 2009
Windows 7 and KIX scripts
Turns out to be a UAC related issue. As explained in MS KB 937624, with UAC enabled, users with administrative membership are logged in with two access tokens, restricted and administrative. When the logon script runs, it runs with the administrative token. When the desktop starts, it starts with the restricted token. Because the two events were started with different access tokens, it's like two different users logged on. They can't see each others drives.
So, the fix is to enable "EnableLinkedConnections". In the registry, set it this way:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -This "links" the connections made with one access token to another.
EnableLinkedConnections =(dword)1