Dave-H

OK, I replaced all the exe and dll files except ETD_DLL.dll, ETD_Aniconf.exe and ETD_Api.dll with the versions from the Lenovo driver (which actually appears to be version 11.4.36.1, not 11.4.38.2). It still worked fine, even the Asus hotkey still worked. I then replaced the three files I didn't replace the first time, and the driver still works fine, but the error message now comes up again from ElanTPCfg.exe, and the hotkey no longer works. There must be something in one of those three files it doesn't like! The versions i have running now are - ETD_DLL.dll 11.10.0.0 ETDAniConf.exe 11.40.4.2 ETDApi.dll 11.5.0.0 ETDApix.dll 11.27.4.1 ETDCmds.dll 11.29.4.1 ETDCtrl.exe 11.41.4.3 ETDCtrlHelper.exe 11.15.0.0 ETDDeviceInformation.exe 11.143.0.0 ETDFavorite.dll 11.11.0.0 ETDMcpl.dll 11.18.0.0 ETDService.exe 11.8.0.0 ETDUn_inst.exe 11.4.0.0 ETDUninst.dll 11.1.0.0 I had a bit of a problem getting at the actual files for the Lenovo driver, as it's an exe, not a zip. 7-zip didn't help, but good old Universal Extractor did!

OK, I've now reinstalled the 11.5.20.3 driver, which is working fine. Is the next step to replace all the exe and dll files with the ones from the Lenovo driver 11.4.38.2?

No, it's isn't actually working, in that I can't change any settings, either with the UI or by registry editing. The touchpad is back in its default configuration. When I only substituted ETDApix.dll with version 10.0.0.98 the settings were still "held", although I couldn't change them. Substituting the other exe and dll files with the version 10 versions resulted it it reverting to as it is now. I think that the Mouse Properties tab is somewhat significant in that none of the versions working on 8.1 have it, and none of the ones which do have it work. Whether it's there or not seems to depend on the version of ETD.sys being used. The Elan drivers have it, the Asus versions don't. This probably directly correlates with whether they have ETD0108 in the INF file or not.

OK, thanks @jaclaz. FWIW, doing the final file substitution, replacing the ETD.sys file from 11.5.20.3 with the one from 11.2.2.1 produced a disabled touchpad. I thought it was dead, but it only needed re-enabling in the Mouse Properties tab. Interestingly, the system tray icon had returned, but it was now the Elan-style one, not the Asus-style one as it was before. It was still "dead" though. Also the Elan tab had reappeared on the Mouse Properties. That at least indicates (I think) that the versions of ETD.sys are either "Elan versions" or "Asus versions". I would suggest that it's highly possible that the Asus versions work on 8.1, and the Elan versions don't, perhaps because of tailoring to the hardware. I think maybe we need to identify what the very earliest "Asus" version of ETD.sys is, as I suspect that no "Elan" version will talk to the hardware properly, which is one of the reasons that we've been having so many problems. That will have the best chance of working on XP, and if it doesn't, we may be doomed to failure.

So am I supposed to be using yet another driver now? Have we aborted what we were doing before? I replaced all the dll and exe files in 11.5.20.3 with those from 11.2.2.1. I then replaced just the ETDApix.dll with the one from 11.5.2.1. I then replaced all the exe and dll files with those from 11.5.2.1. I was now going to try replacing the ETD.sys with the one from 11.5.2.1 as well and report back again when I'd done that. Isn't that what you wanted me to do?! If my reports as to the effects of each change are inadequate for you then I'm sorry, but I genuinely don't know what else I can tell you other than describing how the driver is now behaving after each change. If I say "no change" all I'm saying is that the behaviour other than anything that I specifically report as different is the same as it was the last time I reported.

It's usually part of the aspect ratio controls. If your graphics hardware is set to the monitor's native resolution, which it appears to be in this case, the image should be exactly pixel mapped to the screen, so there should be no borders.

I really would still like to know if anyone has this version of Java working properly on XP! I can't see that anything has become XP incompatible, but I still can't get it working. At least if someone can tell me that they do have it working, I'll know that it is a problem just on my system and not a general problem. Anyone??

I only replaced ETDApix.dll with the one from 11.5.2.1, I left the other files as they were. I will try replacing the others as well. UPDATE: Replaced all the files, and the "tap to click" function is now back on again, and can't be turned off. Otherwise the same.

I was puzzled by ElanTPCfg.exe as well, I wasn't even aware it existed! It's not part of any of the touchpad drivers, it's part of the "Asus ATK Package" which enables the hot keys on the keyboard to work. It's actually pretty redundant with Windows 8.1 or 10 (don't know about 7) as their functionality seems to be built into the OS anyway to do things like volume control and muting and disabling the wi-fi and switching screens. Anyway, I'm not worried about it as I would probably live without that on XP anyway. The ETDApix.dll was version 11.32.0.0. I substituted it with 10.0.0.98, and there is no longer any icon in the system tray, so I can't use it to invoke the control panel. If I run Asus_UI_Win8.exe, the control panel still appears and appears functional, but when the settings are changed there is no change to the touchpad behaviour. Strangely it does change some of the registry settings, but not others. For instance, "tap enable" is set to 1 and seems to be fixed, changing that setting on the UI does not change it. However the "tap activate" setting below that setting does change the equivalent registry setting (although not the touchpad behaviour as far as I can see). BUT, the tap to click function is still disabled! That's good, because that is what I want. The registry setting says it's enabled but it isn't. If that can be replicated on XP, that will do me fine!

Possibly, but I've always assumed that a dead touchpad is because there's no working mouse driver installed for it. The touchpad is usually dead if there's an error on the mouse driver in Device Manager.

Looked in the event logs about the failure of ElanTPCfg.exe. The log says - Faulting application name: ElanTPCfg.exe, version: 1.0.87.1, time stamp: 0x558cc4a5 Faulting module name: ETDApi.dll, version: 11.5.0.0, time stamp: 0x5215dd50 Exception code: 0xc0000005 Fault offset: 0x000012e7 Faulting process ID: 0x66c Faulting application start time: 0x01d61ff5e55c8521 Faulting application path: C:\Program Files\ASUS\ATK Package\ATK Hotkey\ElanTPCfg.exe Faulting module path: C:\Program Files\Elantech\ETDApi.dll Report ID: 2e3d3ef1-8be9-11ea-a458-40167e954b3b Faulting package full name: Faulting package-relative application ID: I suspect this is something to do with the Asus hotkey which enables and disables the touchpad. It isn't working, but that wouldn't be an issue on XP of course.

OK, I reinstalled 11.5.20.3, and it was working fine. I then substituted all the exe and dll files that were in 11.2.2.1 for their equivalents in the Program Files\Elantech folder. It still works! The only thing that popped up on boot was that ElanTPCfg.exe had performed an illegal operation and had to be closed, but the driver is still working. That's a bit of a breakthrough I hope!

@jaclaz OK, I will try that. @cc333 I am getting warnings about drivers not being signed on some (but not all) of the installs. I'm just over-riding them.

No joy I'm afraid, the install fails. No reason given.

Trying to install 11.5.2.1 with the INF from 11.5.20.3 doesn't work, the install fails. Incidentally, all of these drivers when they are uninstalled, the uninstall routine does not remove ETD.sys (or AsusTD.sys) from the system32\drivers folder. Rather sloppy I would have thought! I've taken to always removing it manually, to make sure that it does get replaced. Anyway, I'll give that other driver you've found a try.

OK, I tried on 8.1 with 11.5.2.1 again. A normal unmodified install appeared to work OK, but the the control panel cannot be invoked using the system tray icon, which is "dead" (it doesn't show any animation when a finger is moved on the touchpad or the buttons pressed, as it should do). I tried with Device Manger and changed the mouse from "Elan PS/2 Port Smart-Pad" to "Elan PS/2 Port Input Device", which is what makes 11.5.20.3 work IIRC. No difference. "Elan Service", "ETD Control Center", ETD Control Center Helper" and "ETD Gesture" are all running in Task Manager. Directly editing the settings in the registry makes no difference. I then tried again with the INF file modified, just replacing "NTx86.6.2" with "NTx86.6.3". Same result. Version 11.5.20.3 has a much bigger equivalent section in its INF file, with separate sections for 8, 8.1, and 10 (which it amusingly calls "NTx86.6.4" of course!) I wonder if 11.5.2.1 would work with that INF file?

Well I'm pretty sure that I only ever got two versions of the "normal" Elan driver working on 8.1 (disregarding the later Asus Smart Gesture versions, which work of course). Originally it was just 15.14.4.1 (and even that only when installed through Device Manager, not by the normal installation process) and later we found 11.5.20.3, which also installed, which was quite a breakthrough at the time I'd pretty much given up on any version 11 working on 8.1. I'll give 11.5.2.1 another go with the INF modified to see if I get the same result. It could be that it failed on a normal install the first time, and I hadn't realised then that installing via Device Manager could still work.

I only uninstalled it and reinstalled it because I thought it might produce a different result if I replaced the files in the installation source folder rather than directly in the Program Files folder. Clutching at straws of course, and it didn't do any good! Anyway, I've now copied those files from the 11.5.2.1 installation folder to the Program Files folder, and restored the original unmodified ETD.sys. Still no difference I'm afraid, still the same error in Device Manager, and a dead touchpad. The uninstall routine works again now anyway!

I removed the driver just by rolling back the registry to the "clean" version, and manually deleting all the files. The reason it wouldn't uninstall is because the uninstall routine needs to run ETDUn_inst.exe, which is not XP compatible and throws the same error as ETDCtrl.exe did when the uninstall string is run manually. Why it didn't show the error when invoked from Add/Remove Programs I don't know. Anyway, I reinstalled with the substitute ETDCtrl.exe, and having modified ETD.sys with CFF Explorer. No difference, exactly as before,

Found something puzzling now trying to uninstall the driver in XP. Selecting "Remove" on its entry in Add/Remove Programs now does nothing! Also, the OS version on ETD.sys hasn't been changed, it's not marked to be changed in the spreadsheet. Should it be?

ETDCtrl.exe is now running in the background, and there are no error messages popping up now. The touchpad is still dead though and the Device Manager still shows the error. Should I uninstall and reinstall again with ETDCtrl.exe replaced in the installation folder? Incidentally, I meant to say that the option to disable tap to click is called "Select", under the "One Finger" options on the Asus control panel.

OK, I've done the install on XP. The first thing that pops up on the reboot is from ETDCtrl.exe "The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library Kernel32.dll". The mouse is an "Elan Input Device", but says "The driver may be corrupted or missing (Code 39)." The touchpad is dead.

LOL! I think I can see why! ETDSimpleUI_Win8.exe, which was included with the Samsung driver 4.9.0.0 does work, and can change all the settings just as the Asus control panel does. I'm running in "high" DPI mode as otherwise everything is tiny on the screen, and DellTpad.exe is one of those programs which doesn't cope with that, the interface is cropped and distorted and some buttons are hidden, so would really rather not carry on using it. I'll report back on what happens with XP very soon!

There was a Samsung (?) control panel in one of the other drivers IIRC, I could try that but I suspect it will be the same. Asus_UI_Win8.exe changes all the settings fine on 8.1, but whether it will work on XP I don't know.

Yes, that's almost certainly it!