jaclaz

Well, you make it sound like it was from before the war . ETDSimpleUI.exe dated 08/10/2012 version 10.0.0.31 in an archive with ETD.sys version 10.0.0.197 Asus_UI.exe dated 03/01/2013 version 10.0.0.26 in an archive with ETD.sys version 11.0.0.6 (and both used with an actual ETD.sys dated 05/03/2013 version 11.0.0.31 Everything is within a 6 months period. jaclaz

Probably in Cheshire: https://en.wikipedia.org/wiki/Ashley,_Cheshire and here we have a rare image of the Cheshire cat: jaclaz

UNexpected or not, that "full" control panel is EITHER: 1) exactly the same as the one that comes up with UI_ThemeOption=0 (which should mean that ETDUI.cpl has been "phased out" becsause its functionalities have been included in ETDmcpl.dll OR: 2) an even slighlty different one Yep, and this was actually "expected". The point is whether changing the one, or the other or both the: CustomerDefinition=5 UI_ThemeOption=5 to either: CustomerDefinition=0 UI_ThemeOption=0 or: CustomerDefinition=1 UI_ThemeOption=1 or possibly: CustomerDefinition=4 UI_ThemeOption=4 changes the way the settings are read by the driver. jaclaz

I don't know. It is possible that (like seemingly half the files in the install) there are several layers of "cruft" and that simply the driver doesn't "talk" with this (or that) control panel, or maybe the issue is with the "missing" ETDCtrlHelper.dll and/or ETDService.exe. Setting "0" : the ETDmcpl.dll is definitely BOTH the added tab in "Mouse" AND a Control panel of sorts, possibly what you call the "complex" control panel. Setting "1": and definitely the ETDaniconf.exe is another control panel, possibly the "simple" one that is "inserted" before the above (if the file is present and setting is 0) Setting "2": Dell Setting "3": Dual mode Setting "4": Needs some other file, very likely ETDUISimple.exe (the one we found only on the Samsung driver. Setting "5": Asus_UI.exe or similar .NET based control panel Then there remains the (possibly the oldest) ETDUI.cpl <- can you try this? that may be nto working at all. There is another key that RainyShadow pointed out earlier: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/page/17/?tab=comments#comment-1180835 maybe that one must be changed also - in "sync" with UI_Theme one. In the .inf of "Asus" drivers we have: CustomerDefinition=5 UI_ThemeOption=5 in the .inf of "Samsung" drivers we have: CustomerDefinition=4 UI_ThemeOption=4 in the .inf of "Lenovo" driver we have: CustomerDefinition=0 (and also have a different "definition" of the values) UI_ThemeOption= various values, 1, 6, 3, 8 in the .inf of "Toshiba" drivers we have: CustomerDefinition=7 UI_ThemeOption=7 in the .inf of "Dell" drivers we have: CustomerDefinition=2 UI_ThemeOption=2 in the .inf of "Medion" and "Gigabyte" those keys are nowhere to be found, I am assuming that to be equivalent to have both of them 0. You could try using Regmon to see which keys the: ETDmcpl.dll ETDAniconf.exe Asus_UI.exe ETDUISimple.exe try to access when you change a single setting through them. I suspect that the Asus_UI.exe (and the ETDSimpleUI.exe) use different paths from the other ones, and there must be a setting (possibly the CustomerDefinition key) that changes this behaviour. If we take the "Medion" and "Gigabyte" drivers (which are the "simpler" ones and have no "fancy" OEM branded settings tools included in the .inf) they must *somehow* work on the supported hardware, and they miss both these keys, maybe setting them both to 0 makes the ETDmcpl and/or ETDAniconf keep the settings. jaclaz

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? From what I understand (but I may well be wrong, and I am now confused by the reports) the famous key settings are: 0 = Mcpl UI <- uses *somehow* ETDmcpl.dll 1 = Animation UI <- uses *somehow* ETDaniconf.exe 2 = Dell UI <- uses *somehow* DellTpad.exe (or something like that) 3 = Dual Mode <- ?? but from what you report it is something that uses *something* for the trackpoint and ETDAniconf.exe for the smartpad 4 = Simple UI <- uses *somehow* ETDSimpleUI.exe 5 = ASUS UI <- uses *somehow* Asus_UI.exe Excluding setting 2 (DELL) and setting 5 (Asus) which are fine (the first doesn't work - probably beacuse it wants the DellTpad.exe), the second does work, though without animations, what happens with the other ones? In theory: 0 should work as long as ETDmcpl.dll is in the folder 1 should work as long as ETDAniconf.exe (and possibly a number of stupid .avi files) is in the folder 3 Whatever, we don't want/need it 4 should work as long as ETDSimpleUI.exe is in the folder (but to get the ETDSimpleUI.exe file one would need to additionally get the Samsung driver) Can you re-check? Back to *needed* files: ASUS_UI.exe 10.0.0.26 -> from Z11566 ETDCtrl.exe 11.0.0.13 -> from tp118w7 ETDUn_inst.exe 10.0.0.9 -> from tp118w7 ETDApix.dll 11.0.0.8 -> from tp118w7 ETDCmds.dll 11.0.0.8 -> from tp118w7 ETDFavorite.dll 11.0.0.7 -> from tp118w7 ETDMcpl.dll 11.0.0.10 -> from tp118w7 <- actually optional if Asus_UI.exe is used ETDUninst.dll 10.0.0.1 -> from tp118w7 Optional files: Aniconf.exe 11.0.0.7 -> from tp118w7 ETDSimpleUI.exe 10.0.0.31 -> from Samsung 4.9.0.0 Correct? Then, to install (i.e. in the source files) there are: Setup.exe 11.0.0.4 -> from tp118w7 Setup.ini as follows: (should work also with CheckHWID=1 unREMmed) ETD.sys 11.0.0.31 -> from tp118w7 ETD,inf <- the actual edited ETD_XP.inf renamed to ETD.inf Correct? So, all files either come from tp118w7 or are home-made, exception made for the ASUS_UI.exe. In order to replicate your setup, one would need to: 1) download the tp118w7.exe from Lenovo: https://pcsupport.lenovo.com/hn/en/products/laptops-and-netbooks/lenovo-g-series-laptops/lenovo-g505s-notebook/downloads/ds035770 and expand it with Universal Extractor 2) download the Z11566 from either: http://dlcdnet.asus.com/pub/ASUS/nb/DriversForWin8/Touchpad/Touchpad_Elantech_Win7_8_32_VER11566.zip http://ftp.tekwind.co.jp/pub/asustw/nb/DriversForWin8/Touchpad/Touchpad_Elantech_Win7_8_32_VER11566.zip and get from it just the Asus_UI.exe. So I am assuming that the "\Elantech\UIFunctionOption,UI_Theme" should be set in the .inf as 5. Now the big question (same as the one at the beginning of the post, re-worded), if anyone only gets the tp118w7.exe (and doesn't want the Asus_UI.exe) is there any other setting 0,1,2,3 for the "\Elantech\UIFunctionOption,UI_Theme" key that produce a (even if simplified) control settings change tool (that saves and keeps settings)? And the other big question, what does the ETDUI.cpl (coming from either the Samsung driver or from the Z11542 or from some other files) does? This file is a mistery as it is in the Samsung driver but there is no reference to it in the .inf. (in the Z11542 and in earlier drivers there is a reference to it but it is remmed out). jaclaz

No, thanks. jaclaz

Surely someone does, now if you could actually ask a proper question, explaining what the issue is, then those people may be put in the condition to understand what the problem is. All I can see that may be vaguely relevant is this oneliner on RyanVM: jaclaz

I am confused. Anyway, maybe, without the ToshibaTp.exe, the current set of files (but with the ETD.sys from 11.4.14.1) work "better" with the key set to 0,1,2,3,4? I guess that you are ready for the final verdict? (so that we can have a "final" configuration for the .inf) ETDSimpleUI.exe or Asus_UI.exe? And with which setting of the \Elantech\UIFunctionOption",UI_Theme, key? Which final version of each file do you want to use? Which exact files do you want to use? (or which files are not needed?) Do you need/want the added Control Panel item as in: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1182136 What do you think, can we remove the whole "[ETD_APOptimize.AddReg]" from the .inf? jaclaz

Well, all you will obtain will be an updated definition , something like "some selfish teenage indian dude who watches anime". The "teenage" becoming (already or soon) inaccurate, time passes faster than one would expect ... Haters are gonna hate anyway. jaclaz

The PackardBell one doesn't seem anyway to offer *any* advantage, whilst the Toshiba one may. Using the Toshiba 11.8.16.2 files, restore only the (working) 11.4.14.1 ETD.sys and try only running the Toshiba settings tool, only to see if it is actually more responsive than the Asus one. If the newer files still don't work restore also the other files from 11.4.14.1 and try again. And of course you need to change: HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",UI_Theme,%REG_DWORD%,7 (it has to be seen if the option 7 is connected to the ETD.SYS or - more likely - to the ETDCtrl.exe version) BTW this option 7 should imply that also an option 6 exists ... jaclaz

Using two separate partitions/volumes, 1 for Vista and 1 for 8.1 would be needed. The Vista install (unlike 7 and later) does not create the (second - third in this case) separate "boot" volume (What MS calls "System") on unpartitioned devices which actually, in this case might be useful . http://www.multibooters.co.uk/system.html The possible issue (and a decision to be made) is whether: 1) having Vista on C: and Windows 8.1 on D: (and have each system "see" the other volume) and with the BOOTMGR and \boot\BCD on C: or 2) having Vista on C: and Windows 8.1 on C: hiding the "other" partition to the "other" OS and with separate BOOTMGR and \boot\BCD on each volume, using a third party boot manager such as grubdos to hide the other volume or 3) having either of the above and a third volume with a "common" BOOTMGR and \boot\BCD, with or without a drive letter normally assigned to it. jaclaz

Yep, right now the "ETD_XP.inf" works just fine, it is only a matter of choosing which files (and which versions of files) to add in the source directory, how to set the two or three Registry Keys we have seen as being the "mode selection" and which ones to REM (or to UNREM) in the .inf according to what the "final UI" is desired. And yes, you can use the "ETD_XP.inf" with the files from those two latest drivers and see if they are in any way "better" (maybe - and if actually works/runs - the "Toshiba" UI is better than the Asus_UI or than the ETDSimpleUI). jaclaz

Maybe that is a more general issue with XP and .avi files (and the mechanism that the Asus_UI.exe uses to show them, or the relatively poor support of .Net in XP)? Anyway, now you have an almost complete panoramic view of the various options, and - right when you think it's over - what if I told you about later driver versions seemingly XP compatible (5.1)? 11.8.16.2 actual ETD.sys version 11.98.8.3 dated 26/03/2013 And that has in its .inf: https://drivers.softpedia.com/get/KEYBOARD-and-MOUSE/Elantech/Toshiba-Elantech-TouchPad-Driver-118162.shtml and 11.6.28.201 actual ETD.sys version 11.116.0.0 dated 02/10/2013 And that has in its .inf: http://global-download.packardbell.com/GDFiles/Driver/TouchPad/TouchPad_ELANTECH_11.6.28.201_W81x64_A.zip?acerid=635170560607154373 I remain curious about the set of dices the good guys at Elantech use for assigning versions to their drivers ... jaclaz

Yep, maybe something else has been changed in all the tests. jaclaz

I don't know, try with 4. jaclaz

The second Registry file should be enough. The REG_EXPAND value is "%ProgramFiles%\Elantech\ETDMcpl.dll" So you need to have there the ETDMcpl.dll. The idea is to have two .reg files (that can later be translated to .inf's, possibly including the addition or deletion of ETDmcpl.dll) that can switch the Mouse Control Panel Elan tab on and off. Yep , but you should also try: Z11542 Asus_UI.exe version 10.0.0.23 Z11566 Asus_UI.exe version 10.0.0.26 though maybe it makes no difference. Anyway, try running the "best" Asus_UI.exe with and without the asgesture.dll, it shoudl make no difference. jaclaz

Maybe I was not clear, try this: Close (if open) the Mouse Control Panel. Import this reg file. Windows Registry Editor Version 5.00 [-HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}] [-HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}\InProcServer32] [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved] [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\Mouse\shellex\PropertySheetHandlers\ETD] Open the Mouse Control Panel. NO "Elan" tab anymore. Close (if open) the Mouse Control Panel. Import this .reg. Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}] [HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}\InProcServer32] @=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,\ 00,73,00,25,00,5c,00,45,00,6c,00,61,00,6e,00,74,00,65,00,63,00,68,00,5c,00,\ 45,00,54,00,44,00,4d,00,63,00,70,00,6c,00,2e,00,64,00,6c,00,6c,00,00,00 "ThreadingModel"="Apartment" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved] "{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}"="ELAN Control Panel" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\Mouse\shellex\PropertySheetHandlers\ETD] @="{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}" Open the Mouse Control Panel. The "Elan" tab should be back. jaclaz

I meant, I thought that the Asus_UI.exe needed some of the additional files: to work "better", hence removing files should go back to running "worse", or it is the Asus_UI.exe from 11.5.2.1 that "works better"? The asgesture.dll being present or not should not change anything in the behaviour of Asus_UI.exe, the only file I found that calls it is ETDGesture.exe. jaclaz

Small update. The added "Elan" tab to the "Mouse" Control Panel should be this Registry Entry: HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0} Try deleting it (if you have it). Then open the Mouse Control Panel. No "Elan" Tab. now, save this as .reg and import it: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}] [HKEY_CLASSES_ROOT\CLSID\{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}\InProcServer32] @=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,\ 00,73,00,25,00,5c,00,45,00,6c,00,61,00,6e,00,74,00,65,00,63,00,68,00,5c,00,\ 45,00,54,00,44,00,4d,00,63,00,70,00,6c,00,2e,00,64,00,6c,00,6c,00,00,00 "ThreadingModel"="Apartment" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved] "{0066D4B3-8DE0-4D08-AA83-EDD50E2431F0}"="ELAN Control Panel" Open the Mouse Control Panel The Elan tab should be there alright. jaclaz

Yep, and what happens when you remove the Asus_UI.exe but set the key to 4? The ElanSimpleUI should come up, either directly or via the mouse control panel "touchpad tab". If the latter, try removing the other added files from \Program Files\Elantech (leave the ETDMcpl.dll), one by one, until the mouse control panel "touchpad tab" disappears, so we'll know which file is responsible for that (unless it is directly the ETDUIsimple.exe). Then, set the key to 5, re-add the Asus_UI.exe and the other removed files and try this .inf: So that you have a Control Panel link also for the Asus settings. Again, start removing files until *something changes*. And yet another experiment, what happens if you double click on the ETDUI.cpl? Maybe it is the simple (or complex) non-functional control panel you saw when the key was set to 0 or 1 (I suspect that it uses "other" Registry paths). Same - more or less - goes for ETDAniconf.exe, for *some reasons* it seems to be using the HKCU (as opposed to the HKLM) hive. Try, create in registry the following keys: HKEY_CURRENT_USER\Software\Elantech HKEY_CURRENT_USER\Software\Elantech\OtherSettings HKEY_CURRENT_USER\Software\Elantech\Smartpad then double click on ETDAniconf.exe and click on the left button on "set default values" (or whatever that comes out in English), then check the contents of: HKEY_CURRENT_USER\Software\Elantech\Smartpad As a side note, it seems like the asgesture.dll is only called by the ETDGesture.exe. jaclaz

Oh, I see, and if you open the Control Panel and choose to see its contents as "details" you have no "name" (on the left near the small icon) while you have "comments"on the right? For *some reasons* the key is not assigned a value in the .inf entry (maybe it is taken from somewhere else in the process of a "real" install). Anyway open with Regedit: HKEY_CLASSES_ROOT\CLSID\{3EA22083-D5BF-411b-A6D6-A27541794266} And assign value to: LocalizedString Let's say "dave's Elan CPL" (without double quotes) and everything should be cool again. About asgesture.dll, like the other files, you can only understand if it is *needed* if you compare how the thingy works with and without it, but specifically I presume that is not needed if not som eexoteric three/four finger swipe 'n tap gesture is set. jaclaz

What do you mean "unlabelled" icon? Blank? If yes, is that with or without the ETDMcpl.dll? It seems to me like the icon(s) are taken from that file. Yep, breaking down and translating the possible settings they should mean. more or less: 0 = Mcpl UI <- uses *somehow* ETDmcpl.dll 1 = Animation UI <- uses *somehow* ETDaniconf.exe 2 = Dell UI <- uses *somehow* DellTpad.exe (or something like that) 3 = Dual Mode <- ?? but from what you report it is something that uses *something* for the trackpoint and ETDAniconf.exe for the smartpad 4 = Simple UI <- uses *somehow* ETDSimpleUI.exe 5 = ASUS UI <- uses *somehow* Asus_UI.exe So, you need to re-explore each options after having added (temporarily) to the \Program Files\Elantech folder all the files that we have for the moment excluded (coming from 11.4.14.1): ETDAniconf.exe ETDApi.dll ETDCmds.dll ETDApi32.dll ETDCtrlHelper.exe ETDGesture.exe ETDIntelligent.exe ETDMcpl.dll ETDService.exe ETD_DLL.dll AND the (from Z11521) ETDUI.cpl AND you need BOTH: ETDSimpleUI.exe <- (from Samsung 4.9.0.0 driver) as itself ETDSimpleUI.exe <- (from Samsung driver) renamed to Asus_UI.exe (OR - again temporarily - the Asus_UI.exe from - say - 11.5.20.3 and - probably the asgesture.dll) as it is possible that some of these are part of the "chain" that currently does not "work", like the "0" and "1" choices. The "2" and "3" we don't actually need/want to know. The "4" is the most interesting one to explore, as it seems to be the "correct" way to use the ETDSimpleUI.exe, whilst the current "5" using the ETDSimpleUI.exe renamed to Asus_UI.exe is a "hack". jaclaz

Back a few (several) posts: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1180835 Try playing with: jaclaz

Ok, I am still trying to understand how the "Lenovo.exe" is used/invoked, but the "Samsung" driver .inf (the 4.9.0.0 version from which the ETDSimpleUI.exe comes from) has an interesting section in the .inf (that is nowhere to be found in the "Asus" drivers). Maybe the key "Lenovo part" is this one: To be compared to what we have in ETD_XP.inf Somehow the ETDMcpl.dll comes out again. Can you try, after having added the ETDMcpl.dll to the \Program Files\Elantech\ folder (and having there ETDSimpleUi.exe) to run this .inf: and see if it changes anything? You can later delete the two keys: HKLM,Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266} HKCR,CLSID\{3EA22083-D5BF-411b-A6D6-A27541794266} manually in Regedit. jaclaz

OK. Another queer thing, as the 11.4.14.1 comes from Lenovo and actually includes the Lenovo.exe program, maybe then it is a key in the Registry that "switches" from one program to the other? I'll check if I can find something in the .inf's. Otherwise it would be (IMHO) advisable to leave the file (in source) as ETDSimpleUI.exe and change in the .inf: ASUS_UI.exe = 1 -> ETDSimpleUI.exe=1 and ASUS_UI.exe,,,0x00000001 -> ASUS_UI.exe,ETDSimpleUI.exe,,0x00000001 ;We are using here ETDSimpleUI.exe from Samsung driver but rename it to ASUS_UI.exe Or, maybe even better, if you can recall "which" driver in 8.1 tests (I will review the thread to see if by any chance you posted about it) managed to show the "mouse control panel added tab" we could see if it is reproducible in this driver, and downright remove the references above in the .inf (since the ETDSimpleUI.exe comes from another driver package and can be simply copied to the \Program Files\Elantech directory, renamed as ASUS_UI.exe. making it an option). Another random question, the ETDSimpleUi.exe (as is or renamed as Asus_UI.exe) runs if double clicked (from Explorer in \Program Files\Elantech\ or it only runs from the taskbar icon? I know that it seems like I am nitpicking, mainly because I am actually nitpicking but calling things with their names and documenting what is done has historically proved to be "better", About the other tests, I also know that I sound like a bit (please read as "a lot") picky, but when it comes to removing things, I have always the fear to fall in the case of Chesterton's fence: https://en.wikipedia.org/wiki/Wikipedia:Chesterton's_fence jaclaz