jaclaz

Good. Also run: https://www.nirsoft.net/utils/driverview.html and look for ETD.sys jaclaz

Sure it does (on smartpad I mean). It is very probable that the driver - for whatever reasons - is not installed or not started (or both)[1] i have no way to go "deeper", but from the driver package (expanded in a directory) if I run DellTpad.exe (and not ETDctrl.exe which is also present), depending on what setting I try to change I can see it accessing both HKEY_CURRENT_USER\Software\Elantech\Smartpad and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Elantech\Smartpad Besides HKEY_CURRENT_USER\Software\Elantech\DeviceInformation HKEY_CURRENT_USER\Software\Elantech\OtherSetting jaclaz [1] maybe trying to reinstall after having modified the .inf?: [ELAN.Mfg] ... %PS2.ELANDeviceDesc% = ETD0105_Inst, *ETD0105 ; Image Sensor adding a line: %PS2.ELANDeviceDesc% = ETD0105_Inst, *ETD0108 ; Image Sensor Also try modfying the ETD.infdrp and use dpinst.exe to install.

Try checking it with Regmon to see what it actually does. Could it be an issue with Registry permissions? jaclaz

Another - different - approach. This driver here: http://dl.drp.su/driverpacks/repack/Touchpad_Elan/Elan/Allx86/Gigabyte_nb/10.5.2.0/Elan-Allx86-Gigabyte_nb-10.5.2.0-drp.zip Contains - besides the "usual" drivers also a DELL touchpad utility that seemingly runs under XP. Actually the tool is marked Dell, but it is a re-branded Elantech. The driver has an entry for ETD0105. Of course no idea if this will work "better" or "at all", but at least runs on my XP and it tries to access the "right" Registry parhs. jaclaz

That is in two places: MajorOperatingSystemVersion 5 MinorOperatingSystemVersion 1 MajorSubsystemVersion 5 MinorSubsystemVersion 1 jaclaz

Yep. No, let's first see how the CFF modified files behave. What I was hinting is that - maybe, just maybe - there is a more complete package for XP without the ETD0108 but with the ETD0105, which this finding demonstrates using the same driver. jaclaz

It seems like ASUS has its own version of the touchpad driver, called AsusTP.SYS. Here: https://www.driverscape.com/manufacturers/asus/laptops-desktops/tp300la/186917 is such a driver - allegedly for XP - that has ACPI\ETD0108 listed. Queerly, this is seemingly a "one size fits all" driver: i.e. *any* from 0105 to 0111 use the same "ATP0105" install and driver. jaclaz

Maybe it is only a matter of the compiler, get CFF explorer and try setting 5.1 on those .exe's. Sometimes the minimum OS version is set to 6 or higher only because it is the default setting for the particular compiler used, of course if the executable calls some post-XP kernel functions, that is appropriate. jaclaz

Post a link to that installer. (maybe - just maybe - it is only one of the stupid compiling options for a single .exe) jaclaz

Yep, That would be consistent with the fact that the driver installed "the same" with or without the ETD0108 addition. Somehow the driver must have a "basic" mode, unaffected by the settings or "fixed", that is "good for all devices", and that is what you are now using, though I don't think it is an Asus thing, I believe it is more like an Elan "fallback feature". Try adding an USB mouse (personally I cannot even think of using a laptop if not in emergencies/quick things, without a mouse), two possible scenarios: 1) the USB "prevails" i.e. the "fixed" mode is set to DisableWhenUSBMouse (I doubt it as the setting in "Driver Status Information" is 0x00000000 (0)) 2) you can disable the port and use the mouse All in all, it may be that the driver has "inside" these "default" settings, still I would try tracing the files with Regmon/Filemon. jaclaz

Yep. (if it installs on 8.1) but you mentioned before that you wanted to boot also Win7 on this notebook, or do I remember wrong? And the change is now recorded/shown by ETDDeviceInformation.exe? Yet the touchpad behaves as before? jaclaz

READ (already posted): https://superuser.com/questions/877664/how-do-i-make-my-asus-touchpad-behave-in-a-reasonable-way jaclaz

According to the text file, the DATA IN THE REGISTRY is 1/C8. What IS THE ACTUAL data in the Registry? 1/C8 or 0/D0? It seems like the ETDDeviceInformation.exe agter change and reboot reads the "new" info (0/D0) in the "Driver Information" BUT *something* resets it in the Registry, hence the same exported file shows the Registry path as having (again) 1/C8 (otherwise where the 1/C8 comes from in the section "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Elantech\SmartPad" of the .txt? jaclaz

I don't understand. In the file you posted "afterchangeafterreboot": Anyway, if the settings do not affect the behaviour of the touchpad, there must be *something* else going on. jaclaz

So the actual values you change in Registry are actually (after a reboot) updated on the ETDDeviceInformation.exe view under Driver Information, BUT they are reverted to 0x00000001 and 0x000000C8 in the Registry? Another reason to use Regmon or similar to understand what changes what. What happens running the .cpl? (extracted/copied manually from the driver package) jaclaz

BUT does the ETDDeviceInformation.exe see the change? Try also changing the C8 (presumably 200 milliseconds) to - say - D0 (208 millisecond). Are these changes reflected in ETDDeviceInformation.exe or not? And what happens after a reboot? jaclaz

Good. It seems like a lot of info. Try only changing the those should correspond to: jaclaz

Well, this specific version of the driver is on the Lenovo site described as 7 AND XP and I checked a couple files they have 5.0 or 5.1 as Major/Minor OS version. I also tried running (on my XP SP2) the "ETDDeviceInformation.exe" and it runs just fine (of course doing nothing), "EDTmag.exe" runs and works just fine, etc. As well the .cpl runs just fine (itr is all empty as it is not installed, and there is no hardware connected, of course). jaclaz

Check the ETD.inf of the lenovo driver: You could try removing the ";" and reinstall the driver. jaclaz

Yep. But there could be other explanations: 1) the (stupid) option tab/panel may be able to "refresh on the fly" the settings whilst without it you would need to disable/reenable driver (or reboot) and/or it is capable of only modifying a key if it already exists but the key does not exist for *whatever* glitch in hardware ID or .inf 2) the current driver you have (which works for the touchpad, at least partially) may use another path in the Registry (i.e. maybe as you say it isn't a "Smartpad" that you have currently installed) I would try, on the current driver, using regmon (I personally still prefer the old version - separated filemon and regmon to the newer all in one procmon) to see if clicking in the options panel/tab attempts to access the Registry and if yes to which path. jaclaz

Thanks. that is much better. About amber, I did have (in the good ol' days) a Toshiba T3100 and I have to say that the amber (plasma) screen together with the (very sharp) Toshiba OEM font made it a very, very readable device. For *some* reasons most of the images you can find of it nowadays don't make justice, they all seem a little out of focus and/or the background is too much lighted up/invasive, in reality it had a very good contrast/clearness. Ahh, the good ol' times, when a byte was a byte and a very good text processor/edtor was q (Qedit by Semware, 46,160 bytes of sheer editing power): https://www.pcorner.com/list/WORDP/QEDIT215.ZIP/INFO/ jaclaz

@Dave-H Yep, it is strange that the original driver, missing the hardware ID, installs nonetheless, maybe there is some "comparibility hardware" setting that acts as a sort of "catch all". However, quoting myself: Let us assume that: 1) you have the described Registry structure 2) that what the (not working) options tab does is in a nutshell: a. change some settings in the Registry path b. make the driver re-read the (changed) settings What happens if you change a setting in the Registry and EITHER: 1) disable and re-enable the driver OR: 2) reboot ? jaclaz

Bummer! Which driver (sort of) worked ? Link please. jaclaz

Crap! Driver could be this one (to be tested): http://dl.driverpack.io/driverpacks/repack/Touchpad_Elan/Elan/Allx86/Asus_nb/11.5.21.6/Elan-Allx86-Asus_nb-11.5.21.6-drp.zip Can you confirm that you tried this (and that it doesn't work at all)? jaclaz P.S.: Also check the following path in Registry: HKEY_CURRENT_USER\Software\Elantech\SmartPad https://superuser.com/questions/877664/how-do-i-make-my-asus-touchpad-behave-in-a-reasonable-way

Look, it was you that reported that right after install you can change resolution of the driver without BSOD's. Installing only the driver (bar the stupid Catalyst bloat around it) should be a matter of seconds. Anyway, instead of installing it automatically at each boot, it could be a batch file, so you normally boot with the VGASAVE (and have slower refresh) and only when you really *need* the better driver you install it. You are now introducing another approach, disabling it and re-enabling it, but it seems to me rather obvious that if you disable it when at 640x480 it will re-enable at that resolution, unless you disable it when working fine (just after install) at 1366x768 and when it restarts it defaults back to 640x480? jaclaz