Dave-H

Your install INF for ETDSimpleUI works fine. The uninstall INF works fine apart from leaving the HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266} key behind, which results in a dead blank icon in the Windows Control Panel. I'm sure you're right about those four video files not being used by ETDSimpleUI, I seem to remember that I found that as well. Unfortunately if you install the ETDSimpleUI, its settings are not used by the driver! It's back to the same problem we had with the Asus UI and the Elan UI before, where the Asus UI actually changed the settings, but the Elan one didn't, although it appeared to. Now the Elan UI changes the settings, and the ETDSimpleUI doesn't, although it appears to. I guess they're changing different things in the registry again!

Sorry @RainyShadow, I should have thanked you for your suggestion. I think we're OK with this now though.

I've now tried your uninstall modifications to the INF, and I'm pleased to say that the ETD.sys file and the ETD service registry entries are now removed! Why this did not happen before I'm at a loss to understand, every single driver we've tried left those behind when it was uninstalled, even the later Asus drivers we tried on 8.1, they left the equivalent AsusTP.sys file behind! Very strange, if it was just laziness on the part of the INF programmers, why are all the drivers like that? Anyway, what you've done now is a great improvement! I used the default "simple" setup.ini from 11.5.20.3 and it works fine, so I can't see any obvious reason not to use it.

Yes indeed! So to be sure we need to supply a setup.ini file as well as an ETD.inf file to replace the default ones in 11.4.14.1. I'm puzzled as to why we didn't run into this problem before now. Did we perhaps copy the setup.ini file from 11.5.20.3 as well as the INF when we made the "Frankendriver", and that version just stayed there throughout the subsequent tests?

"CheckHWID=0" would presumably result in hardware compatibility not being checked at all, which isn't good as the driver could potentially then just apparently install OK anyway but not work, and the user wouldn't know why. Does "CheckHWID=1" just check that the hardware is referenced in the INF? I would have thought that would be OK.

OK, I found the problem! Setup.ini needs to have "String28=*ETD0108" added at the end of it, then it works! I guess we'll have to either provide a modified setup.ini or add that to the instructions.

Sorry for the delay again! After completely uninstalling the driver, I'm trying to do the installation as a new user would, just following the steps in your previous post, not using any files already downloaded. I used innounp and that worked fine, although the command as you wrote it (innounp -x tp118w7) doesn't seem to work, it only works if you add ".exe" to the end of it. So I now have the folder with all the 11.4.14.1 files in it, and I've replaced ETD.inf with your most recent version. However, when I run setup.exe, all that happens is that a message pops up saying "The driver version doesn't suit the Touch-Pad. Please check the device in system and install the suitable driver." I don't think I've done anything wrong or missed anything. Was there something else we had to do other than just replace the INF?

But the file is in the actual "untouched" \tp118w7\{app}\Elantech\11.4.14.1\X86\, right? It was missing in your "frankendriver" folder only because of all the various tests. Yes, that's right. As I said I'm now using the "ETD_new" folder as the source, which came after the "Frankendriver" folder. ETDMcpl.dll wasn't in there for some reason, I think at that time we thought it wasn't needed, but it's there now. Yep, and - additionally - it leaves the \Program Files\Elantech folder untouched AFAICT (and also the .HKLM\System\CurrentControlSet\Control entries ) Actually it does always remove the entire Elantech folder from Program Files on every uninstall, and it removes all the registry entries too, except for the ETD service entry. Apart from the anomalies I mentioned, I've actually always thought that the drivers' uninstall routines were pretty good, some uninstallers leave a huge amount of rubbish behind!

I substituted your new INF for the previous one in the "ETD_new" folder where I had been installing from before, and it works! The only file I had to add to the folder because it couldn't find it the first time was ETDMcpl.dll, which wasn't originally included. One thing I have noticed, which I mentioned in passsing before ages ago, is that the uninstallation routine does not remove ETD.sys from the System32\Drivers folder, and I've since found that it doesn't remove the "ETD" service entry from HKLM\System\CurrentControlSet\Services in the registry either. This appears to be the same with all the drivers I've experimented with, and it would be nice to fix it!

Personally I wouldn't bother with any control panels that use AVI demonstration videos. ETDSimpleUI.exe seems to be the only one where they work on XP anyway, I have never seen them work with Asus_UI.exe, even when they're all present in the Elantech folder. DellTpad.exe doesn't display properly in 120dpi scaling mode, which makes it useless for me anyway. Lenovo.exe and ToshibaTp.exe don't seem to give any control over the "tap to click" function, so are also useless as far as I'm concerned! The default Elan control panel is absolutely fine, no videos, works fine at 120dpi, looks good, and seems to cover everything. The only anomaly with it is that the button options, to disable them or change their functions, doesn't seem to work. That is puzzling, but not a problem as far as I'm concerned (it doesn't work on the "simpler" version either BTW). I agree with your "INF pruning" suggestions.

Well if we're going to add any files from outside the 11.4.14.1 driver, how about just adding ETDUI.cpl to the Elantech folder? The last version we have seems to be version 10.0.0.64, from driver version 11.5.4.2. Then running <rundll32.exe shell32.dll,Control_RunDLL "%ProgramFiles%\Elantech\ETDUI.cpl"> launches it from the Windows Control Panel icon. It may not be exactly the same control panel as is being launched by the Mouse Properties tab Options button, but it certainly looks like it, and it does work! It is just a nicety, as you say, it's not strictly needed as the control panel access seems to be intended to be via the Mouse Properties with many of the drivers anyway. Only some of the early drivers had icons for their control panels in the Windows Control Panel

Here's the Filemon log for the operation of pressing the "Options" button on the Mouse Properties tab. As you can see it appears to be looking for the control panel executables, and when it can't find any of them it presumably defaults to its own internal control panel. How to replicate that with a command though? One workaround would be to include ETDAniConf.exe in the installation. That is a file in 11.4.14.1 so doesn't complicate things too much. When that is run, it launches the simpler Elan control panel, so that could easily be run from the Windows Control Panel icon, when in the Elantech folder it also now runs that interface when the system tray icon is double clicked, instead of launching the Mouse Properties. I'm not sure that's ideal though. Filemon.Log

Sorry, it's only the "UI_Theme" setting I've changed. Setting the "CustomerDefinition" setting to "0" doesn't seem to alter anything, but I guess it should now be set to "0" as we're working with the default Elan branding. Would it be possible to get your Windows Control Panel icon to now bring up the Elan control panel do you think? There is no executable to directly run from it now. I've tried <rundll32.exe "D:\Program Files\Elantech\ETDMcpl.dll"> and that doesn't work.

Hi Jaclaz, sorry for the delay again, but I have good news! It seems that by setting the registry entry to "0" the Elan control panel then does work properly, and the settings are being changed by it. I think my mistake before was not rebooting after changing the settings. I assumed as the cosmetic changes were there just by changing the settings, that was it. Obviously not! The only setting on the control panel which still doesn't seem to do anything is the "Button Setting" option, which still doesn't seem to change anything, but I'm not worried about that, I can't imagine I'd ever want to turn off the touchpad buttons or change their functions! So, what I have now is a driver with looks like an Elan one, in that it's an Elan icon in the system tray. Doubly clicking that produces the mouse properties, and then clicking "Options" launches the Elan full control panel to change the settings. That's exactly how some of the Elan drivers were when installed and used normally on Windows 8.1. It's all fine with only seven files in the Elantech folder, all from driver version 11.4.14.1. So, as long as the INF is as optimised as it can be, are we there?

OK, fair enough! I guess I just assumed it was older than the Asus Smart Gesture control panels because it looks a lot more basic and primitive and it's included only in the driver with the lowest version number by quite some way (4.9.0.0). Of course as we've seen the stated driver version numbers don't seem to mean a lot anyway!

One other really strange thing is that ETDSimpleUI.exe does change the "Tap_One_Finger_Enable" setting, even though it's a much older (and more basic) control panel than the Asus one! I will play with those other settings and see if they change the behaviour.

Running ETDUI.cpl launches a full Elan control panel, perhaps not unexpectedly. I've attached two Regmon logs, one using the Asus control panel, the other using the full Elan control panel, just changing the "tap to click" option on both of them. Also I've confirmed in the registry itself, the Asus control panel is changing the "HKCU\Software\Elantech\SmartPad\Tap_One_Finger_Enable" value. The Elan control panel is changing the "HKCU\Software\Elantech\SmartPad\Tap_Enable" value. Only changing the former actually changes the touchpad behaviour. So, the Asus and Elan control panels are changing different registry keys to apparently change the same setting. RegmonAsus.log RegmonElan.log

Sorry that's an awful lot to try to answer, I'll do it in stages if that's OK? But, once you have it, what happens when you click on it? I mean, does it "produce" something if not better, different from Asus_UI.exe or it does nothing useful? ETDMcpl.dll doesn't do anything if you click on it, why would it as it's a dll file? Is that what you meant? If you meant what happens when you (double) click on the Windows Control Panel icon, it launches the Asus control panel, as specified in the relevant registry entry. I've tried removing Asus_UI.exe from the folder, so there are now no extra control panel files. I thought it might be useful to see whether it's possible to get away without having to separately source any of them. With registry setting "0" the system tray icon now produces the Mouse properties. Clicking "Options" on the Elan tab produces the full complex Elan control panel. Removing EDTMCpl.dll removes the tab, so I suspect that the control panel UI data is in that file. All very good of course, as it's a good control panel and is available with no additional files from other drivers, but unfortunately although you can change its settings, and they are remembered, they are not actually changing the behaviour of the touchpad. Perhaps as this is an Asus based driver it stores its settings in one place in the registry, and the Elan CP is writing them somewhere else? With registry setting "1" there appears to be the same result as "0". With registry setting "4" we now have a "Touchpad" tab in Mouse Properties instead of an "Elan" tab. It carries Samsung branding. "Options" also brings up the complex Elan CP. BUT, if ETDAniConf.exe is added to the Elantech folder, the behaviour changes, and with the registry vale at "0" double clicking the system tray icon directly brings up the control panel, but it's the simpler version of the Elan control panel! However the "Options" button on the Elan Mouse Properties tab still brings up the full version! With the registry value is 1, both the system tray icon and the Options button on the tab produce the simpler control panel. With the registry value "4" the behaviour is the same as when it's at "0". Confused? I certainly was! Anyway, it does look as if it's possible to have a control panel without having to bring in any files from outside version 11.4.14.1, where the other files are from, which is good. Incidentally, Lenovo.exe, which is the control panel packaged with 11.4.14.1, looks to be pretty much the same as ToshibaTP.exe, same window with the same options. I mentioned that there was no checkbox next to the "Tapping" option, but now having looked at its "help" text, it says that "One-Finger tapping always performs point/click/select function...." (my emphasis), which implies to me that with this control panel the "tap to click" function cannot be disabled, which makes it completely useless as far as I'm concerned! So, we can have perfectly good control panels without any extra files, but that's no good if you can't actually change the "live" settings with them! Is it worth investigating why that is?

Well all I have in the Program Files\Elantech folder now is - ASUS_UI.exe 10.0.0.26 ETDCtrl.exe 11.0.0.13 ETDUn_inst.exe 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 That is it, nothing else, and the driver works fine with the Asus control panel (without any videos, but who cares!) ETDMcpl.dll is only there to support your icon in the Windows Control Panel, I don't think it's needed otherwise. Actually I think the sluggishness of the control panel could very well be being caused by the fact that if you remember I'm using a very basic graphics driver at the moment, where the refresh rate is extremely poor. I'm sure if we can ever magic up a proper working graphics driver it will be a lot better! Only ETDSimpleUI.exe works well with its videos, so would be the only other one I'd want to use, but it's missing a couple of three finger options which are on the Asus control panel. I actually think that's OK, it does the job, and at least as far as I'm concerned I won't be changing the settings at all anyway once I've got them the way i want them (basically that's everything on the touchpad disabled apart from the basic mouse functions!)

The files from the Toshiba driver don't work even if ETD.sys remains the older version. ETDCtrl.exe is running but there is no system tray icon and the settings have reverted to the defaults. The error in Device Manager has gone away though, so I guess that was being caused just by the incompatible ETD.sys. I've put the original versions back. With the registry entry at "7" I now have an Elan style icon in the system tray instead of the Asus style one, which is working, and an Elan tab on the Mouse Properties, which is also working. I moved the ToshibaTp.exe file into the Elantech folder and removed the others, and all its video files, replacing the others. I had to add ETD_DLL.dll to the Elantech folder as the control panel said it was missing. That control panel is very slow and unresponsive though, and seems to be missing some items. There is no check box beside the "tapping" label for instance. It's also not showing any videos, like the Asus control panel. The Elan Simple Control Panel seems to be the only one where the videos are actually working. Frankly I don't think what I've got now is any improvement on what we had before.

Always remember Dibya that those criticising your work, usually unjustifiably as the issues have been caused by them, almost certainly wouldn't have been able in their wildest dreams to do what you've done. Please don't let a few id*** stop you sharing your work, the vast majority really appreciate your efforts I promise!

I'm now really convinced that the ETD.sys that we're using (11.0.0.31) is the only version that will actually work for us on XP. I don't think we've had any functional driver at all on XP with any other version. I think it's possibly the one and only version at the very start of the 11.x series that happens to work on XP and can also talk to my hardware. Possibly all the earlier ones won't talk to the hardware, and all the later ones just don't work on XP. Whether it works on XP by accident or design I don't know, I'm just glad that it does! I will try experimenting with the other files.

No luck with the files from those newly discovered drivers I'm afraid. I replaced the two exe files, the five dll files, and the etd.sys, and the result was the same with both. In both cases ERDCtrl.exe is running fine, but there is no icon in the system tray and Device Manager is showing a corrupted driver message, and the touchpad is dead.

OK, I'll try substituting the files from those later drivers, and report back!

As I'm sure you've already determined, neither of those drivers have ETD0108 in their INF files, so definitely won't work on my system without modification I wouldn't have thought. I guess I could try just substituting the files we're using from 11.4.14.1 with the equivalent files from either or both of those drivers to see if it still works. That would be justified I think as we will then be used later XP compatible versions.