Asus Trackpad
Background: So my place of employment decided to buy 500 Asus net-books (1005HA) without asking me to test them. Once they arrived I had to put an image on them(XP SP3) so they would be ready for deployment. The only issue is that when you log in as a domain user, the track pad turns itself off. I tried a few different steps such as using an older driver and removing the other Asus track-pad driver (1005PE which works fine on that model) from the drivers folder but I still have not resolved the issue.
does anybody have any suggestions?
does anybody have any suggestions?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
hunter.mclaughlin
14 years ago
I figured out the issue a few days ago. Asus has two different versions of their ACPI driver which inherently controls the power saving and devices. I used the newest version in my image which was the culprit. when I switched to the old one the issue was resolved.
Posted by:
dunnpy
14 years ago
Are you able to turn the track pad back on?
You say that when you log in as a domain user it occurs, does that mean if you log in as a local user it continues to work as expected? That would seem to point to a setting in the default user profile pertaining to the mouse/trackpad, that isn't set in the admin profile (which I'm guessing is already on the image and not created as part of the login process from the default user profile).
Is there anything that runs when the user logs in that could be causing it? Domain login script, active setup, runonce, startup etc?
Can't think of anything specific, but hope that helps,
Dunnpy
You say that when you log in as a domain user it occurs, does that mean if you log in as a local user it continues to work as expected? That would seem to point to a setting in the default user profile pertaining to the mouse/trackpad, that isn't set in the admin profile (which I'm guessing is already on the image and not created as part of the login process from the default user profile).
Is there anything that runs when the user logs in that could be causing it? Domain login script, active setup, runonce, startup etc?
Can't think of anything specific, but hope that helps,
Dunnpy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.