jaclaz

Always here means "ONLY when UI_ThemeOption=0" And now, for no apparent reason, a new test IF the issue is that with this (or that) setting the key changed by ETDSimpleUI changes between: 1) HKLM\Software\Elantech\Smartpad\Tap_Enable and: 2) HKLM\Software\Elantech\Smartpad\Tap_One_Finger_Enable BUT only the former actually affects the driver behaviour, THEN what about making the second a link to the first? (or the first a link to the second) https://github.com/tenox7/regln Please note how here (in my half-@§§edly installed driver) the ETDSimpleUI accesses and saves settings in HKCU, not HKLM. (and regln cannot be used on HKCU) About hosting it, if we put it on archive.org, there won't be size limits. jaclaz

Yes and no. "PST" seems to be related elsewhere to the PointSTick (the little thing - usually red - that is in the middle of the keyboard) Good idea. jaclaz

I don't know. The .inf ('s) and setup.ini once zipped will be what? 50 KB or less and can be posted as direct attachment in a new, final thread without issues. The ETDUI.cpl is some 6-7 MB, zips to 2 MB. I don't see problems about redistributability of the files, the only limitation in the EULA you get when you run Setup is about the need to use them with Elan hardware (as if they had *any* use with *any* other hardware ). So, in theory we could provide the whole set of driver files (in both versions) the problem - as often happens - is where to upload it so that is accessible (in a "stable" manner). jaclaz

The problem with that is that the "poor" user will need to get also the Z11542 (in addition to the "Lenovo" tp118w7) only to run (maybe) the same settings panel that he/she can already access via double click on tray -> Mouse Control Panel -> Elan tab -> Options ->Settings panel. OR: Control Panel -> Mouse Control Panel -> Elan tab -> Options ->Settings panel VS. Control Panel -> Added Elan Touchpad item -> Settings panel (one click saved in the latter) The idea (mine at least) was that "simple" people will need to download only the tp118w7 in order to have a working driver and settings panel. Those looking for more "bells and whistles" can download the Samsung driver (in all its bloat) but at least will be rewarded by the "nicer" ETDSimpleUI and its .avi files. jaclaz

At the end of the day, so: 1) ETD.inf using ETDmcpl.dll: CustomerDefinition=0 UI_ThemeOption=0 NO additional Control Panel Item <- that is unless we find a way to run the ETDmcpl.dll 2) ETD.inf using ETDSimpleUI.exe: CustomerDefinition=5 UI_ThemeOption=5 additional Control Panel Item calling ETDSimpleUI.exe (in this - in order to avoid the double clicking on the tray icon to open the mouse control panel without any "Elan" or "Touchpad" tab) it would maybe possible to disable the tray Icon, you will have to try if this works (it is in the Samsung driver .inf): HKLM,"%ServiceRoot%\Elantech\OtherSetting",IconType,%REG_DWORD%,2 ; 0 = Dynamic Trayicon, 1 = Static Trayicon, 2 = Do Not Display Trayicon OR: 3) (the workaround you used earlier, to be confirmed if it is still working): CustomerDefinition=5 UI_ThemeOption=5 ETDSimpleUI.exe renamed to Asus_UI.exe <- not correct, but in love, war and stupid Elan drivers .... optionally additional Control Panel Item calling ETDSimpleUI.exe Asus_UI.exe As a side note, I have made in the meantime a comparison between the various "OtherSetting" and "SmartPad" registry settings in the two "reference" .inf's, the Samsung one against the one we are using (derived from 11.5.20.3) and whilst I could find nothing that can apparently change the behaviour you just documented, there are a couple that seem like worth an experiment (only to see if changing them changes anything in the behaviour of the trackpad): HKLM,"%ServiceRoot%\Elantech\OtherSetting",EnableASUSNotifyFunction,%REG_DWORD%,1 <- this is 0 on the Samsung HKLM,"%ServiceRoot%\Elantech\DriverOption",DualModePSTModuleType,%REG_DWORD%,3 <- this is 1 on the Samsung, description is ; 1 = NXP, 2 = STek, 3 = ELAN3003 All the rest look like (minor) tweaks to the functions and responsiveness of the Touchpad, these are however interesting: Samsung: HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Tap,%REG_DWORD%,300 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Move,%REG_DWORD%,300 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Gesture,%REG_DWORD%,300 Asus: HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_Enable,%REG_DWORD%,0 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Tap,%REG_DWORD%,750 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Move,%REG_DWORD%,750 HKLM,"%ServiceRoot%\Elantech\SmartPad",DisableWhenType_DelayTime_Gesture,%REG_DWORD%,750 At face value the first seems to disable the touchpad when typing and doing so much faster (maybe it is also a setting in one of the control panels, but I thought it worth to mention) jaclaz

WHICH following command? You just gave a label to the Vhd partition, so you should be able to use *any* tool that outputs the Volume label AND the drive letter. Which OS? Is Powershell available? https://docs.microsoft.com/en-us/powershell/module/storage/get-volume?view=win10-ps Is WMI available? for /f "delims=" %D in ('wmic LogicalDisk get Caption^, VolumeName ^| find "Win10x64-WB"') do ECHO %D for /f "tokens=1,2" %D in ('wmic LogicalDisk get Caption^, VolumeName ^| find "Win10x64-WB"') do ECHO %D %E WMIC logicalDisk where Volumename="Win10x64-WB" get DeviceID /format:list FOR /F %A IN ('WMIC LogicalDisk where "Volumename='Win10x64-WB'" get DeviceID /Format:list') DO @SET %A>NUL SET DeviceID or similar. Are you on "plain command line" only? Something *like*: FOR /F "skip=4 delims=\" %A IN ('mountvol ^| FIND ":"') DO @VOL %A 2>NUL | FIND "Win10x64-WB" should do. jaclaz

Vista and UEFI/GPT is tricky (if it works at all). In practice there is the need of a number of concurrent settings in the UEFI and these may not be possible on your specific machine. Try reviewing this thread, maye something there helps. https://msfn.org/board/topic/176341-windows-vista-sp1sp2-uefi/ jaclaz

Yep , the Aston Martin DB5 actually was "The" Bond car : https://en.wikipedia.org/wiki/Aston_Martin_DB5 https://en.wikipedia.org/wiki/Aston_Martin_DB5#James_Bond's_DB5 Later models had not the same iconic relevance, in later movies Bond drove *anything* including BMW's and Land Rovers, besides new models of Aston Martin. but none remained "memorable". jaclaz

Let's say that IF abandonware existed, that site would be the central repository for it. I understand how you are trying to help (and you actually did help more than once on this thread ), but, as said, hearsay is normally not admissible: https://en.wikipedia.org/wiki/Hearsay and even when it supposedly provides an operative fact: https://en.wikipedia.org/wiki/Operative_fact the fact itself needs to be checked/verified. Let's say, that - since I don't trust my Opel Vectra to start tomorrow morning: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1181878 I procured myself an Aston Martin DB5 (possibly with licence plate BMT-216A ) jaclaz

Good, Now try the other two possibilities. I.e.: CustomerDefinition=0 UI_ThemeOption=5 or: CustomerDefinition=5 Ui_ThemeOption=0 That "switch" between "HKLM\Software\Elantech\Smartpad\Tap_Enable" and "HKLM\Software\Elantech\Smartpad\Tap_One_Finger_Enable" is likely due to only one of the two setttings set to 5. Hopefully one setting affects the key used, and the other the behaviour of the doubleclicking on the tray icon, and - if this is the case, then there are also to try: CustomerDefinition=4 UI_ThemeOption=5 CustomerDefinition=5 UI_ThemeOption=4 Anyway, this confirms (and at the end of the day it is also the simpler approach ) that the "final" version is better made out of two alternative, monolithic ETD.inf's, one for the "plain" 11.4.14.1 "Lenovo only" driver with ETDmcpl.dll as setting panel and one for the same but running the added ETDSimpleUI from "Samsung". @RainyShadow Please do check the actual source of that stuff, before suggesting its use, though there can be exceptions, I tend to reject hearsay . ZaPbuzz is talking about a (btw enterprise/top of the range) proprietary, commercial program not available since several years (and BTW largely obsolete): https://en.wikipedia.org/wiki/Wise_Solutions as at a certain point it was acquired (and duly killed) by Symantec, and - if I recall correctly - had a list price of several hundreds US$, something like 700-800. jaclaz

You mean the .inf, not the .sys . This basically means: [Manufacturer] %INTEL%=INTEL_HDC,ntx86 Look in sections: [INTEL_HDC] and [INTEL_HDC.ntx86] depending on the OS. Then in this: [INTEL_HDC] [INTEL_HDC.ntx86] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 the INTEL_HDC section is empty, but Windows 2000 will try loading that one. So - at least in theory - this should do: [INTEL_HDC] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 [INTEL_HDC.ntx86] %PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104 %PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104 %PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104 %PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104 jaclaz

So, the only way out - maybe - is to make the two alternative ETD.inf's, it might mean that for *some* reasons the ETDUIsimple.exe needs to be installed by the Setup.exe, but this makes NOT any sense , as earlier in tests you had not any ETDUIsimple.exe in the ETD.inf and you plainly copied it manually to the \Program Files\Elantech\ folder, there must have been something that you did that made it work. Or maybe the two Registry settings: CustomerDefinition=4 UI_ThemeOption=4 need to be set at 5 at install time and can only be changed later. Another possibility is that for *some* reason the ETDSimpleUI.exe needs a number of keys pre-made and these keys are actually created NOT by the ETD.inf, but rather by the Asus_UI.exe. I think the only way to understand that you need to trace the ETDSimpleUI.exe as it is now (not saving settings) and then uninstall everything, re-install with the "original" method (first install the 11.5.20.3 and then replace manually files) and see (if now the ETDSimpleUI.exe works, saving settings). jaclaz

Maybe there needs to be "more" keys in HKCU , anyway I think that a possible way out at this point will be to make two different "monolithic" ETD.inf's, both to be installed (the one or the other) via Setup.exe. The first, the current one, without the ETDSimpleUI nor any .avi files. [1] The second including the ETDSimpleUI and the .avi files. [2] It is possible that the "key" is again in the two Registry settings: CustomerDefinition=4 UI_ThemeOption=4 (those that are in the Samsung driver, from which the ETDSimpleUI comes from). Try changing those two keys and try again (probably you will need a reboot). If this works, these can be added to the ETDSimpleUI.inf and keep it "self-standing". Change in the ETDsimpleUI_remove.inf this line: HKLM,Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266},,0x00000000,"Elan Control panel" to: HKLM,Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{3EA22083-D5BF-411b-A6D6-A27541794266} (my bad). Do also this test: copy manually the ETDsimpleUI_remove.inf to the \Program Files\Elantech\ folder uninstall the driver via the ETD_uninst.exe Is the \Program Files\Elantech\ folder deleted anyway AND is the Control Panel icon/etc. also removed? jaclaz [1] and with the two keys set to 0 [2] and with the two keys set to 4

Good. Back to this test, and if it works, we are all set for a "final" version: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/page/38/?tab=comments#comment-1182336 Note, when trying here (BOTH with devcon and with Setup.exe), there is a "queer" behaviour, they *somehow* install - besides ETD.inf, also ETDsimpleUI.inf AND ETDSimpleUI_remove.inf (which of course makes the ETDSimpleUI.exe install a non-install), it is like the Setup.exe (but also devcon.exe, notwithstanding the command line devcon install .\x86\ETD.inf *ETD0108) runs all .inf files in the folder, i.e. *.inf. The ETDSimpleUI.exe needs the .avi files that are present in the "main" \x86\ folder and even if we make an \x86\ETDsimpleUI\ subdirectory, the path to the higher level \x86\ subdirectory is not a valid one in .inf files syntax (AFAICT), not really a problem as the .inf will ask for the first .avi file and the user will need to point to the higher level directory, then all other .avi files will be copied from there. The ETDSimpleUI_remove.inf can instead be put in a subdirectory, no problem with that. We'll have to think about a way out for this CATCH22 , we could well replace the two .inf files with a small batch or a couple .reg files. Also, it has to be tested if the ETD_Uninst.exe is "smart" or not, i.e. if it deletes ONLY the files mentioned in oemnn.inf AND IF the \Program FIles\Elantech\ directory is empty THEN it removes it OR if it simply deletes the \Program FIles\Elantech\ directory, no questions asked. About ETDSimpleUI.exe, it seems like in order to run it needs to access an (empty) HKEY_CURRENT_USER\Software\Elantech key, this is not (here) created by the ETD.inf (but it may well be created on your system by the actual ETD.sys or ETDCtrl.exe running, cannot say). jaclaz

Yep , in the Frankendriver tests we used as base the 11.5.20.3 and either deleted unneeded files or overwrote selected/needed ones from 11.4.14.1 (or from some other older "Asus" drivers), so - at least here - the Setup.ini in use remained (or became) the *catch all*: [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 Anyway, it is an interesting philological experiment, undoubtedly the "base" (original) Setup.ini is something like: [Setup_Config] CheckHWID=1 CheckMode=1 String1= ... Stringn= ResetPreviousRegistry=1 the (diligent) Lenovo guy filled the blanks, the (lazy) Asus guy removed the CheckMode and Stringn lines, the (lazier) Samsung guy changed only the CheckHWID=0. Three different solutions/workarounds for a non-problem (as AFAIK a .inf for a driver won't install anyway if it doesn't find the hardware - hence the need for me to create the device via devcon) . The difference is AFAICT only that the Setup.exe outputs a "Cannot install" window earlier if the hardware is checked (CheckHWID=1) and if the list is in Setup.ini (and CheckMode=1). jaclaz

A (oldish, circa 2012) link casually dropped out of my bag o' links: http://reboot.pro/topic/17655-boot-into-3rd-party-efi-application-via-bcd/ anyone wanting to read it may learn something. jaclaz

I don't know, that should be it, BUT (I guess) that IF: CheckMode=1 the Stringn= entries in the Setup.ini are checked (instead/overriding ETD.inf ones or - more likely - as a pre-requisite). My personal vote is on the "exact" (for what it costs) Setup.ini: [Setup_Config] CheckHWID=1 CheckMode=1 ResetPreviousRegistry=1 String1=*ETD0000 String2=*ETD0101 String3=*ETD0102 String4=*ETD0105 String5=*ETD0106 String6=*ETD0107 String7=*ETD0108 String8=*ETD0109 String9=*ETD010A String10=*ETD010B String11=*ETD010C String12=*ETD010E String13=*ETD010F String14=*ETD0111 String15=*ETD0112 String16=*ETD0113 String17=*ETD0114 sometimes (not always, but often enough) it is gratifying to be plus royaliste que le roi : https://www.oxfordreference.com/view/10.1093/oi/authority.20110803100332506 jaclaz

The Disk Manager in Windows 7 (and later) is quite good, and - even if a tad bit complex to use - Diskpart (also built-in) can do even more things, there is no need for a third party partition manager normally. About the dual boot, basically: 1) the boot related files for XP and earlier are NTLDR and BOOT.INI 2) the boot related files for Vista and later are BOOTMGR and \boot\BCD The normal booting sequence of XP is: MBR->PBR of active partition->NTLDR->BOOT.INI (choices)->Windows XP The normal booting sequence of Vista (and later) is: MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->Windows Vista+ The normal bootng sequence of a dual boot like yours is: 1) MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->Windows Vista+ 2) MBR->PBR of active partition->BOOTMGR->\boot\BCD (choices)->(NTLDR)->BOOT.INI-> XP The NTLDR is between brackets because it depends on the specific item and on the Windows version if it is used or not. Without knowing the specific, exact situation of your system (now and how it will be) it is not possible to provide you with exact advice on what to do. Your best choice would be to use BootIce that can manage the PBR's, the NTLDR and BOOTMGR and the settings files BOOT.INI and \boot\BCD via a nice GUI: http://reboot.pro/topic/21956-bootice-v1332/ you want the 1.332 version, but you will need to learn a bit about the principles and the usage of the tool. Depending on the exact setup, you may also want to introduce a separate boot manager (grub4dos) as primary boot manager, that would allow to have the two systems (XP and 7 or 8.1) completely independent. jaclaz

Very good. Yep, that "Lenovo" setup.ini is an "exception" as all the "Asus" ones are *just*: [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 Whilst the "Samsung" one is: [Setup_Config] CheckHWID=0 CheckMode=1 String1= String2= String3= String4= String5= String6= String7= String8= String9= String10= String11= String12= String13= String14= String15= String16= String17= String18= String19= String20= String21= String22= String23= String24= String25= ResetPreviousRegistry=1 Good catch . Though adding the "String28=*ETD0108" is a nice solution, it would cover only the ETD108, whilst the .inf - in theory - at the moment covers: *ETD0000 *ETD0101 *ETD0102 *ETD0105 *ETD0106 *ETD0107 *ETD0108 *ETD0109 *ETD010A *ETD010B *ETD010C *ETD010E *ETD010F *ETD0111 *ETD0112 *ETD0113 *ETD0114 so, since we have anyway to provide the modded ETD.inf we can add a pre-made simple Setup.ini file either according to the "Asus" philosophy (lousy/loose): [Setup_Config] CheckHWID=1 ResetPreviousRegistry=1 a (lousier/looser) "one size fits all": [Setup_Config] CheckHWID=0 ResetPreviousRegistry=1 or an "exact" one: [Setup_Config] CheckHWID=1 CheckMode=1 ResetPreviousRegistry=1 String1=*ETD0000 String2=*ETD0101 String3=*ETD0102 String4=*ETD0105 String5=*ETD0106 String6=*ETD0107 String7=*ETD0108 String8=*ETD0109 String9=*ETD010A String10=*ETD010B String11=*ETD010C String12=*ETD010E String13=*ETD010F String14=*ETD0111 String15=*ETD0112 String16=*ETD0113 String17=*ETD0114 jaclaz

Sure , I would say it is "normal". The prefetch folder is where Windows automagically creates *something* (let's call for the moment this *something* "links") connected to frequently used executables. Cmd.exe and Timeout.exe are the command processor (that runs the batch) and the command you used in the batch, conhost.exe is as well connected to the command processor (it is the console host) and dllhost.exe (likely, haven't checked) is connected to timeout.exe (or as well to cmd.exe). If you don't want them to be recreated you need to disable prefetch: https://www.technipages.com/windows-enable-disable-superfetch It may also depend on its actual setting, check the values in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\PrefetchParameters EnablePrefetcher EnableSuperfetch https://www.tomshardware.com/reviews/ssd-performance-tweak,2911-5.html jaclaz

It is possible that (one way or the other) you managed to make a "dual boot system" or actually more a "dual boot single system", tha can boot BOTH in BIOS and in UEFI mode. Files used are different, in BIOS: \BOOTMGR \Boot\BCD vs. \EFI\Microsoft\boot\bootmgfw.efi \EFI\Microsoft\Boot\BCD In the booted system you should be able to see if you booted BIOS (please read as CSM) or UEFI, on 7 you will need to check SetupAct.log: https://www.eightforums.com/threads/bios-mode-see-if-windows-boot-in-uefi-or-legacy-mode.29504/ jaclaz

And what have you tried (that presumably did not work as you expected)? Or is the request slightly different, more *like* "please write for me a batch that does this ..." Anyway, see if any of the solutions here fits your usage: https://stackoverflow.com/questions/6836566/batch-file-delete-all-files-and-folders-in-a-directory Easiest is to use RD and the re-create the "base folder", but it is to be seen if that is OK in your situation (basically the recreated "base" directory will have a different creation date", Additionally if the volume - as it is likely the case - is NTFS, there might be the need to check for hardinks before deleting files unconditionally . jaclaz

Good , but for further tests you need to imagine being a "final" user, knowing nothing of this thread and that follows these instructions: 1) get the tp118w7 from https://support.lenovo.com/cz/en/downloads/ds035770 2) use Universal Extractor (or maybe easier use http://innounp.sourceforge.net/ ) to extract the contents, innounp -x tp118w7.exe 3) replace the ETD.inf in the directory \{app}\Elantech\11.4.14.1\X86\ with the new one 4) run the Setup.exe in \{app}\Elantech\11.4.14.1\X86\ Then, optionally, 5) get the Samsung driver 4.9.0.0 from https://www.helpjet.net/Fs-52207751-65343120-34459956.html 6) open it in 7-zip and copy the ETDSimpleUI.exe from \Elan\X86\ to the directory \{app}\Elantech\11.4.14.1\X86\ 7) Add the two ETDSimpleUI .inf files and right click/install the ETDSimpleUI.inf This is interesting , as it means that the Uninstaller likely has a number of "internal" settings that are not in the ETD.inf. It has to be seen if it does everything in the actual .inf. Try in the .inf: 1) add: ETDSys.DelFiles = 12 ; Driver directory at the end of: [DestinationDirs] 2) change: DelFiles = No_Files to: DelFiles = ETDSys.DelFiles in: [Uninstall] 3) add: [ETDSys.DelFiles] ETD.sys,,,0x00000001 after: [No_Files] 4) add: HKLM,"SYSTEM\CurrentControlSet\Services\ETD" at the end of: [Uninstall_DelReg] jaclaz

Ok, in the meantime the ETDSimpleUi.exe install and uninstall files. Expand the .zip in the "source" 11.14.4.1 directory together with the drivers files and add the ETDSimpleUI.exe, and right click->install on the ETDSimpleUI.inf. Of course the driver needs to be already installed. Then, to remove, right click->install on the ETDSimpleUI_remove.inf It remains the doubt about these .avi files: Button_SmartPad.avi Clicking_2F.avi Scroll_Reverse_H.avi Scroll_Reverse_V.avi i.e. if they are actually used by ETDsimpleUI.exe or not. jaclaz ETDSimpleUI.zip

Good. 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. Yep, and - additionally - it leaves the \Program Files\Elantech folder untouched AFAICT (and also the .HKLM\System\CurrentControlSet\Control entries ) The issue might be how the ETD_Uninst.exe behaves, i.e. if it executes the commands in: before or after: 1) having stopped or killed the ETDctrl.exe <- if it does this 2) having uninstalled the device (and having deleted the \WINDOWS\system32\DRVSTORE\etd_<stupid_long_string> and the \WINDOWS\inf\oemnn.inf :unsure:) When using devcon.exe/manually you *need*: 1) devcon remove *ETD0108 2) devcon dp_delete C:\WINDOWS\inf\oemnn.inf 3) rd /s C:\WINDOWS\system32\DRVSTORE\etd_<stupid_long_string> 4) taskkill /F /IM ETDCtrl.exe 5) rd /s %ProgramFiles%\Elantech And then remove the various Registry entries. Maybe this can be done with a batch and DPINST.EXE (which we already have in the tp118w7), I'll have a look at it. jaclaz