Ha! Ok, you're better at this than I am. That said, you gave me an idea so I went to the Asus site and found this thread page: ht tps://w ww.asus.com/us/support/FAQ/1031506/ (sorry, apparently I can't post links ) It gave me the idea to check all of the driver device IDs under Human Interface Devices. Sure enough, there was one device in there with an identical device ID (0B05:1837) and I was actually able to successfully force the driver installation! I thought I had it for a second but it didn't work
Tried more drivers from this package h ttp://ivanrf.co m/en/asus-smart-gesture-and-windows-10/ No dice. Thought I was getting closer :/
Yeah, I actually already have the ATK drivers installed and they are working great. I kinda think the problem is with the mouse drivers since I can't get them to install at all unless I force an install with the .inf file. No problem, man. Thanks for the help! Yeah, it did say other stuff was missing. A lot of things. I downloaded some of those touchpad files and it didn't really seem to do anything. I think tonto might be right about the ATK stuff. Wow, I don't know anything about editing bios stuff. Is that something you can do right from the menu or would a guy have to modify weird files in obscure boot folders or something? I'm using Daz's windows loader. I'll have to look into clover. I'm wondering if it's worth the trouble. Would be awesome to get this stupid touchpad working though.
yes have to do intel iasl and edit.. its been a while but i do it for mac os x on some pcs in past and i noticed how _OSI can cause some devices to show different hardware id or named different for different os.
You're a braver man than I. Since my D610 experience from which you rescued me I have a room full of ten foot poles for not touching the bios, ...T
One other thing: If you don't make sure the drivers you installed that didn't work, are completely renoved they will remain and give the same problem by not letting the new ones replace them and work So among other things check control panel, categories, remove software, to be sure no drivers are left there ...T
You know, that had occured to me so I put the Win10 HDD back into the machine and booted it up. It shows the same hardware ID in windows 10 as it does in windows 7. Still think Bios stuff needs to be edited? There could be other stuff with different names that I don't know to look for but the basic Hardware ID looks identical. I've tried a whole ton of different things but I'll try that package and see what happens I definitely wasn't doing that. But then again, it has never been the case of a successful install followed by something not working. Every single time the install has failed, I'm guessing due to either an OS check or a Hardware Name check.
omfg I just typed out a whole reply and the connection failed when I hit submit so I lost it all So here goes again Yeah, I'm glad I installed win7 on another HDD, it was def a good move. So I'm actually on win10 right now because I want to get win7 on this drive (because it's larger) so I can start using it for work. This $2500 machine has been sitting around collecting dust for 3 months because of Windows 10. Anyway, what I may not have mentioned yesterday is that there are actually 3 mice that show up in the device manager on Win10. I didn't look very closely at the 3rd because disabling it had no effect where as disabling the 0B05 device stopped the touchpad from working so I naturally assumed that it's the device we're interested in looking at (the 3rd is just my logitech USB mouse). So upon closer investigation this morning it turns out that the other mouse device that shows up is actually the Elan1203! It's interesting that disabling that device has no effect. The other interesting thing is that the Elan1203 device does not show up in windows 7!! So are we back to editing Bios stuff to get the hardware to recognize? I also noticed that there is one extra line in the device ID for the 0B05 device in Win10. Take a look at this: Win7 DevID from DM Code: HID\VID_0B05&PID_1837&REV_0004&MI_02 HID\VID_0B05&PID_1837&MI_02 HID_DEVICE_SYSTEM_MOUSE HID_DEVICE_UP:0001_U:0002 HID_DEVICE Win10 DevID from DM for both mice Code: Disabling this in win10 stops touchpad HID\VID_0B05&PID_1837&REV_0004&MI_02 HID\VID_0B05&PID_1837&MI_02 HID\VID_0B05&UP:0001_U:0002 <---Notice the extra line HID_DEVICE_SYSTEM_MOUSE HID_DEVICE_UP:0001_U:0002 HID_DEVICE Disabling this in Win10 has no effect HID\VEN_ELAN&DEV_1203&Col01 HID\ELAN1203&Col01 HID\*ELAN1203&Col01 HID\VID_04F3&UP:0001_U:0002 HID_DEVICE_SYSTEM_MOUSE HID_DEVICE_UP:0001_U:0002 HID_DEVICE Win10 mouse output from MSINFO32 Code: Hardware TypeUSB Input Device Number of Buttons0 StatusOK PNP Device IDUSB\VID_0B05&PID_1837&MI_02\6&D51E9F7&0&0002 Power Management SupportedNo Double Click ThresholdNot Available HandednessNot Available Driverc:\windows\system32\drivers\hidusb.sys (10.0.14393.0, 37.50 KB (38,400 bytes), 7/16/2016 4:41 AM) Hardware TypeHID-compliant mouse Number of Buttons0 StatusOK PNP Device IDHID\ELAN1203&COL01\5&6DECF3A&0&0000 Power Management SupportedNo Double Click ThresholdNot Available HandednessNot Available Driverc:\windows\system32\drivers\mouhid.sys (10.0.14393.0, 31.50 KB (32,256 bytes), 7/16/2016 4:41 AM) Hardware TypeHID-compliant mouse Number of Buttons0 StatusOK PNP Device IDHID\VID_046D&PID_C52B&MI_01&COL01\7&3245F6DC&0&0000 Power Management SupportedNo Double Click ThresholdNot Available HandednessNot Available Driverc:\windows\system32\drivers\mouhid.sys (10.0.14393.0, 31.50 KB (32,256 bytes), 7/16/2016 4:41 AM) (my logitech mouse is shown in there) So does this mean anything to you guys? Is there anything else I should check before wiping this crappy OS off my harddrive? Also, I just wanted to thank everyone for all the help! I'm shocked at how helpful you guys are and how quickly you reply! Super awesome!
Oh, I'll also mention that Win10 is installed with a GRP file system and UEFI bios and for Win7 I'm just running the old bios and MBR because it was easy to install.
In the interest of science it might be useful to ghost your Win7 onto an image on a portable drive so you can get it back easily, or to use a third hard drive to clean install Win10 Enterprise LTSB. that might enable you to see what gives with the touchpad drivers while avoiding the win7/win10 complication I have LTSB on another drive and find it very close to win7 in functionality even the start menu can be used more easily than 8 or 10 and you can get rid of those @#%% icons on a cellphone fine, but on a pc yukk on a Dell 1501 LTSB had drivers for everything but the touchpad, no Dell driver would work but a Toshiba driver did. go figger I realize this is a solid gold computer you have and you don't want to mess with it more than necessary I think you got the message from my exchange with LatinMcG that he's a real super guru in the field of bioses and I have a great aversion to touching them I once got stuck with a bios I really didn't want, and couldn't get rid of, but eventually did. You can't beat Daz' loader ...T
the only way i could see it working is on EFI w7 and possibly with clover bootloader and adding the driver efi modules.. its a big mess