Dave-H

I've just realised that 11.5.20.3 is showing as not signed on XP even with its original INF. Is that what you would expect? Anyway, I installed it using its normal INF file, and then copied all the files from 11.4.14.1 to the Elantech folder, and replaced the ETD.sys file with the 11.4.14.1 version as well. And............ IT WORKS! I now have a working driver in Windows XP!! I cannot thank you enough Jaclaz! Having worked with you so often here in the past, I cannot believe that this was just a speculative shot in the dark. You must have known that this might work, and it has! I am so happy!

The Device Manager is fine, it's saying the device is working properly. It's the old problem that the device isn't being identified correctly by the tab in the Mouse Properties. I'm pretty sure that as long as it's appearing just as a generic "Standard PS/2 Mouse", it will not work. The installation log looks OK. 10.0.5.4Install.txt

Your modified INF (327KB) is actually bigger than the original (325KB) is that right? Anyway, installing through Device Manager with your INF sadly does not produce a working driver. There is an icon in the system tray, an Elan style one, not an Asus style one, but it doesn't animate when the touchpad is used. There is an Elan tab on the Mouse Properties again, but again it stows the device as a "Standard PS/2 Mouse" not a smart pad, and the options button is greyed out. Right clicking on the icon has an "Asus Smart Detector" option which I've not seen before, and that brings up a control panel, but it has no options in it. "ETD Control Center" and "ETD Control Center Helper" are both running, which is a good sign! Device Manager says the mouse is now an "Elan PS/2 Port Smart-Pad".

Tried that, I then had to OK the install, as expected, but the driver still installed and is working fine!

OK, here's the logs. I hope they provide some clues. The log of the default install is a lot bigger than the log of the modified install! NormalInstall.txt NormalUninstall.txt ModifiedInstall.txt ModifiedUninstall.txt

OK I did my registry restore test, and restoring the registry does make the driver work again. So I think that proves that the problem with the modified INF is in its registry sections, not anything to do with what files are copied or not copied. One other thing I've now noticed is that when the driver is uninstalled after an install with the default INF, the mouse correctly reverts to its previous name in Device Manager (Microsoft PS/2 Mouse). After an uninstall of an installation with the modified INF, it remains as "Elan Input Device" and the driver has to be manually rolled back to revert it correctly. Another symptom of a problem with the registry entries in the modified INF I assume, in the uninstall section.

Certainly the driver signing is broken when the install is done with the modified INF, I have to OK the install, which I don't have to with the default INF. I assume that's expected behaviour, as the driver cannot be considered to be still signed if the INF has been "tampered with"!

Yes, that certainly seems to be the case! How about I reinstall the driver from the default INF, using Device Manager, and then when I have a working driver I back up the whole registry with ERUNT, then uninstall the driver and do the same install with your INF, which will presumably result in a non-working driver, and then restore the whole registry back again from the backup I made while the driver was working? If the driver then works, presumably that will prove that the problem is in the registry, not missing files or anything like that. If the driver still doesn't work, that means it's a file problem, not a registry problem. That will at least narrow things down a bit perhaps.

OK, I uninstalled, and reinstalled using the default INF. I went and checked, and the ETDService service wasn't installed! I hadn't noticed until then that it wasn't actually there any more with a normal INF-only install. So, it must be another thing (along with the avi files) that is installed by the setup program, not by the INF! More significantly, it also means that it's not necessary, as the driver was still working fine! Anyway, attached is the differences between the two registry snapshots, only including the entries which appeared to be Elan related. The whole thing was huge of course! HTH. ElanDifferences.reg

OK, I'll uninstall again and then install using the original INF, and make a registry snapshot. I'll then uninstall again, and reinstall using your cut down INF. I'll then do another registry snapshot and use Nir Sofer's program to compare them, and see if we can see what the relevant differences are.

OK, I think I see how it works now! Running <ETDService.exe -install> installs the service, <ETDService.exe -uninstall> removes it. If I install it and reboot, the service is then running fine. So, somehow when the normal INF is used, that <ETDService.exe -install> command is presumably being run, but I can't see where it is! The driver still isn't working, ETDCtrlHelper.exe isn't running, and starting it manually does not make any difference.

11.5.20.3 installs from Device Manager using the default INF absolutely fine, fully working. I then tried installing exactly the same way using your latest INF, and again the service was not installed. The data for it is not in the registry. It's the service called "ETDService" which is missing, the service called "ETD" is installed fine. As you say "ETDService" isn't mentioned in the default INF, only as a file name, which is odd!

Just tested in Internet Explorer 11 on Windows 10 and the behaviour is exactly the same! I guess this has been changed, and the warning now only appears once even if you don't check the "do not show again" option.

I've now tried installing 11.5.20.3 using Device Manager. Two versions of "Elan Input Device" were offered (not "Elan PS/2 Port Input Device", which must be something different!) This time it didn't transfer the AVI files, so it looks as if you were right about the setup.exe doing it intrinsically, which is rather odd I would have thought when they are normally in the INF! Unfortunately, it's also not working. Again the Elan Service hasn't been installed. Only ETDCtrl.exe is running. Running ETDCtrlHelper.exe still works, but doesn't change anything.

I installed by running "setup.exe". I've just tried with version 11.5.6.6, using your INF and it didn't work. Again the completed window showed two devices, but this time one had failed! Previously with 11.5.20.3 there were also two devices, but both had apparently succeeded. The mouse was "Elan PS/2 Port Smart-Pad", not showing any errors. The touchpad worked but the settings are at default and can't be changed. There was a "dead" icon in the system tray. ETDCtrl.exe and ETDCtrlHelper.exe are both running, but not the Elan Service. It doesn't seem to have been installed as it's not in the Services list as it normally is. I then tried updating the mouse driver in Device Manager, as "Elan PS/2 Port Input Device" is also offered, which is what it is with 11.5.20.3. (I'm wondering if "Elan PS/2 Port Smart-Pad" and "Elan PS/2 Port Input Device" are the two devices being displayed on the installation completed window? ) Doing that produced the same result as before, although I now seem to have "ETD Gesture" running, which I didn't think was before! Still no Elan Service though.

It's working fine with the modified INF. It did take an extraordinarily long time to install though, I was on the point of giving up on it when it suddenly completed! The install completed window showed two identical instances of the device, which I've not seen before, there's always been only one before. It seems to be installed and working normally though. It has still transferred the AVI files. I will now do the second part of the test.

ETDAniConf.exe 11.0.0.7 ETDCtrl.exe 11.0.0.13 ETDCtrlHelper.exe 11.0.0.7 ETDDeviceInformation.exe 11.19.0.1 ETDService.exe 11.0.0.4 ETDUn_inst.exe 10.0.0.9 ETD_DLL.dll 11.0.0.4 ETDApi.dll 10.0.0.6 ETDApix.dll 11.0.0.8 ETDCmds.dll 11.0.0.8 ETDFavorite.dll 11.0.0.7 ETDMcpl.dll 11.0.0.10 ETDUninst.dll 10.0.0.1 ETD.sys 11.0.0.31 This combination is working fine. ETDCtrl.exe and ETDCtrlHelper.exe are both running. ------------------------------------------------------------------ TEST 1 ETDAniConf.exe 11.0.0.7 ETDCtrl.exe 10.0.0.117 ETDCtrlHelper.exe 10.0.0.73 ETDDeviceInformation.exe 11.19.0.1 ETDService.exe 11.0.0.4 ETDUn_inst.exe 10.0.0.9 ETD_DLL.dll 11.0.0.4 ETDApi.dll 10.0.0.6 ETDApix.dll 11.0.0.8 ETDCmds.dll 11.0.0.8 ETDFavorite.dll 11.0.0.7 ETDMcpl.dll 11.0.0.10 ETDUninst.dll 10.0.0.1 ETD.sys 11.0.0.31 No icon in the system tray. Driver not functioning. ETDCtrl.exe is running at the start, but then closes, ETDCtrlHelper.exe not running at all. If ETDCtrl.exe is subsequently run manually, it starts but then stops. If ETDCtrlHelper.exe is run manually, it runs and stays running. I'm guessing that it's normally started by ETDCtrl.exe. --------------------------------------------------------------------------------------------- TEST 2 ETDAniConf.exe 11.0.0.7 ETDCtrl.exe 10.0.0.101 ETDCtrlHelper.exe 10.0.0.67 ETDDeviceInformation.exe 11.19.0.1 ETDService.exe 11.0.0.4 ETDUn_inst.exe 10.0.0.9 ETD_DLL.dll 11.0.0.4 ETDApi.dll 10.0.0.6 ETDApix.dll 11.0.0.8 ETDCmds.dll 11.0.0.8 ETDFavorite.dll 11.0.0.7 ETDMcpl.dll 11.0.0.10 ETDUninst.dll 10.0.0.1 ETD.sys 11.0.0.31 No icon in the system tray. Driver not functioning. ETDCtrl.exe is running at the start, but then closes, ETDCtrlHelper.exe not running at all. If ETDCtrl.exe is subsequently run manually, it starts but then stops. If ETDCtrlHelper.exe is run manually, it runs and stays running. ------------------------------------------------------------------------------------------- TEST 3 ETDAniConf.exe 11.0.0.7 ETDCtrl.exe 11.0.0.13 ETDCtrlHelper.exe 11.0.0.7 ETDDeviceInformation.exe 11.19.0.1 ETDService.exe 11.0.0.4 ETDUn_inst.exe 10.0.0.9 ETD_DLL.dll 11.0.0.4 ETDApi.dll 10.0.0.6 ETDApix.dll 11.0.0.8 ETDCmds.dll 11.0.0.8 ETDFavorite.dll 11.0.0.7 ETDMcpl.dll 11.0.0.10 ETDUninst.dll 10.0.0.1 ETD.sys 10.0.0.188 No icon in the system tray. Driver not functioning. ETDCtrl.exe is running at start, and now stays running, ETDCtrlHelper.exe not running at start. If ETDCtrlHelper.exe is run manually, it runs and stays running. Even when the two files are running (and the Elan Service which always runs) the system tray icon does not come back, and the driver is still not working. Running the Asus control panel manually and changing the settings does nothing, and does not change the settings in the registry. Changing the registry setting manually also has no effect.

Taking ETDapi.dll down to version 10.0.0.6 was fine. Unfortunately, taking ETDapix.dll down to version 10.0.0.98 stopped the driver from working properly. ETDCtrl.exe and ETDCtrlHelper.exe are no longer running, and there is no longer an icon in the system tray. The touchpad settings have held though, "tap to click" is still disabled. Changing the setting in the Asus control panel now has no effect, and nor does changing the setting in the registry.

OK, well I don't think I'll be losing any sleep about using one out of date file! One other thing I've noticed, which probably isn't related but you never know, is that when you do the Java test page, it puts up a warning for you to accept or cancel, and there is an option to not show it again. I never bother to tick that, but it's now acting as if I have, and after the first time the warning never appears again unless and until I do the "Restore Security Prompts" option on the security tab of the Java control panel. Not a problem of course, but strange! I don't know where the setting to not show the prompt again is stored, and I haven't been able to find out. Anyone know?

Just as a matter of interest, is that file security critical?

It says I'm using 251, and am up to date!

Thank you, so a creeping incompatibility with XP is obviously now being gradually slipped in! I can only assume that more and more files in the new Java installations will start to have this sort of problem as time goes on, until it will get to the point where you'll have to replace so many files for it to work that you might as well just stick with the previous version anyway!

OK, done that, still working! The file versions are now (in a rather more logical order!) - ETDAniConf.exe 11.0.0.7 ETDCtrl.exe 11.0.0.13 ETDCtrlHelper.exe 11.0.0.7 ETDDeviceInformation.exe 11.19.0.1 ETDService.exe 11.0.0.4 ETDUn_inst.exe 10.0.0.9 ETD_DLL.dll 11.0.0.4 ETDApi.dll 10.0.0.9 ETDApix.dll 11.0.0.8 ETDCmds.dll 11.0.0.8 ETDFavorite.dll 11.0.0.7 ETDMcpl.dll 11.0.0.10 ETDUninst.dll 10.0.0.1 ETD.sys 11.0.0.31 These are considerably earlier versions than before, in fact three are version 10 files, I would very surprised if you found an earlier version of version 11 than that!

OK, I've found the problem, it seems to be just one file causing it! The file is "sunmscapi.dll" which is in the \bin folder. If you replace just that file with the version from Update 241, it all comes good! What is actually wrong with the file I'm not sure, according to CFF Explorer it's still superficially XP compatible, but perhaps someone with more knowledge about this sort of thing could analyse it more deeply and tell us! Cheers, Dave.

OK, done that, and the driver is still working fine, although the error message from ElanTPCfg.exe has come back of course. It's now - ETD_DLL.dll 11.10.0.0 ETDAniConf.exe 11.40.4.1 ETDApi.dll 11.5.0.0 ETDApix.dll 11.27.0.0 ETDCmds.dll 11.29.4.1 ETDCtrl.exe 11.41.4.1 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 ETD.sys 11.122.4.2 Most of the files are the same versions as they were before. Should I put ETDApi.dll 11.1.0.0 back to make the hotkey error go away? It is an earlier version that still works. There were two files in 11.4.31.1 which aren't there in the present installation, ETDIntelligent.exe, and ETDApi32.dll. I guess they are irrelevant?