jaclaz

I am clearly missing something, but a (larger) copper shim can be cut to measure, can't it? About thickness of the thermal pad, I believe we are talking between 5% and 20% , that is, starting from 1.5 mm the final, tightened, thickness will be anything between 1.2 and 1.4 mm, but I am perplexed by your expected precision, it is not a (Swiss) mechanical watch, 0.2 mm (two tenths of a millimeter) difference in thickness is unnoticeable/irrelevant, and it also depend on how tightly you screw the heatsink down. @dencorso Sure, sometimes I wonder how we managed to survive[1] at all, with all the lead and asbesto we must have been in contact with in our youth (nevermind no car seat belts, no helmets, no safety breakers on mains, no "use by date" on food, free roaming on the roads as kids, etc.). jaclaz [1] there must be a reason why it is called "survivor bias"

Did you replace ONLY the ETDApix.dll or did you "cold replace" ALL the .exe and .dll's? If you replaced just the ETDApix.dll do try replacing also the other files taking them from the "Medion" drivers, Can you try "cold replacing" also the .sys file (using the one from "Medion")? Another one to try, first "as is" and then doing the same "Frankendriver" approaches seen till now. http://ftp.tekwind.co.jp/pub/asustw/nb/DriversForWin8/Touchpad/Touchpad_Elantech_Win7_8_32_VER11566.zip this has ETSApix.dll version 10.0.0.111 (which is the highest version number of the "10" series found till now). More than that, at face value this has *everything* as 5.1 and the ETD0108 so it may even install to XP "as is" . AND it is the only example till now of "mixed" files versions of the series "10" and of the series "11". Attached the updated spreadsheet. jaclaz

Wait a minute, this: C:\Program Files\ASUS\ATK Package\ATK Hotkey\ElanTPCfg.exe is nowhere in the driver files we have been seeing till now? Is it part of another driver, right? Anyway, now the "problem" files (at least in theory) are : ETDApix.dll ETDCoInstaller.dll <- is this file actually used at all? Most probably not, only in the "original" "Medion" install ETDDeviceInformation.exe <- NOT needed ETDTouch.exe <- hopefully not *needed* If you try to repeat what you have done more or less successfully on 8.1 on XP, very likely you will find an obstacle with ETDApix.dll Now it is almost the time to try replacing (on 8.1) the ETDApix.dll (which now is either version 11.43.5.3 or version 11.32.0.0) with the latest we have with 5.1, that should be 10.0.0.98 from Z11521. BUT the "Samsung 4.9.0.0" has a ETDApix.dll version 10.0.0.102, which may also be tried. jaclaz

Yep, here is where you need to trace a working install and compare to the failed one. Still, you can try to install the Z115203-cab "normally" and then (offline) replace the .exe and .dll's with the 5.1 version ones from the Medion. jaclaz

Actually it is whatever you want it to be, the link was not meant as "here it is exactly what you are looking for", it was intended as "here is a basic technique to use a boot manager to choose between two installs on EFI at boot". Most probably one can setup the bootmanager of choice with something similat to the "Arch" used on PXE, if I recall correctly GRUB2 can check the EFI "bitness". jacla

It is queer. Anyway, you can try, make a copy of the Z11521 and paste to it only the ETD.inf from Z115203-cab. In the meantime, I found yet another possible missing link between Neanderthal and Sapiens Download this: https://drp.su/en/devices/inputdev/elan/elan-touchpad?os=windows-xp-x86 http://dl.drp.su/driverpacks/repack/Touchpad_Elan/Elan/Allx86/OEM_nb/Medion_11.2.2.1/Elan-Allx86-OEM_nb-Medion_11.2.2.1-drp.zip Of course - being NOT an "Asus intended" driver - it has NO provisions for ETD0108, but the file versions are interesting, see the new, attached spreadsheet. Versions are extremely near to the ones in Z115203-cab, but all .exe's/.dll's are 5.1 exception made for: Apix.dll <- which unfortunately should be relevant ETDCoInstaller.dll <- that might - hopefully - be unneeded/irrelevant ETDDeviceInformation.exe <- which surely is unneeded/irrelevant So, next try is using: the ETD.inf, ETD.sys, ETD.cat, and ASUS_UI*,exe from Z115203-cab all the other files from "Medion" jaclaz

Hmmm. What I still find "difficult" to believe is that the Z11509 and the Z11521 "as they are" do not work (in 8.1). I mean, if we had *only* the Z11509 containing the ETD0108, it could have been a "glitch" or a mistake of some kind, but since we have both: Z11509 dated 29/07/2012 AND Z11521 dated 21/09/2012 with the ET0108 as "ETD_STD_Inst" it would be strange that the eventual error has not been noticed in two months and "perpetuated". Besides, we have an earlier driver, the Z10590, dated 20/02/2012 where the ETD0108 is already mentioned BUT assimilated to the ETD0107. So - somehow - the ETD0108 "existed" at least since early 2012[1] and by July 2012 it was "promoted" to ETD_STD_Inst. I seem to remember :unsure: that you never tried to install the Z11521 "as is" to the 8.1. Maybe you could try that, first without modifying anything, and then again modifying the .inf replacing "NTx86.6.2" with "NTx86.6.3", just in case. jaclaz [1] As a side note, the "divorce" between XP and 7 seems like having happened between the Z10560 (which is named for XP) and Z10590 (which is named for 7. AND that has for the first time the ETF0108 in the .inf), so, it is possible that - notwithstanding the 5.1 Major/minor versions, there are other reasons why anything after Z10560 won't run in XP (hence the need for tracing, finding dependencies, etc.) and - coincidentally - only drivers after Z10560 have a provision for ETD0108.

No, as we have seen that also the "old" versions, "surely" working on XP such as the Z10052 are also 6.1/6.1/6.1. Why do you have uninstalled it? Anyway, you can try replacing all the files originally 6.0 with the corresponding ones from Z11521: ETDApix.dll ETDCmds.dll ETDCtrl.exe ETDCtrlHelper.exe ETDFavorite.dll ETDMcpl.dll ETDService.exe And also (but this should only affect install/uninstall): ETDUninst.dll ETDUn_inst.exe Setup.exe jaclaz

Try replacing the ETDCtrl.exe with the one from "Touchpad_Elantech_Win7_32_Z11521.zip". You will probaly find other .exe's or .dll's that will do the same or similar and the only thing you can do is to try replacing them with the corresponding one from the "Touchpad_Elantech_Win7_32_Z11521.zip". jaclaz

This one? https://www.biostar.com.tw/app/en/news/news.php?S_ID=399 https://www.tomshardware.com/news/biostar-h61mhv2-motherboard-h61-chipset-new https://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=972 Or maybe this one: https://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=547#specification jaclaz

The point I was trying to make is that the Asus_UI.exe (which *somehow* runs on my XP, and that will surely run on your XP), MISSES a huge number of possible settings, among them - seemingly - the one you want to change (TapEnable). jaclaz

Good (meaning bad) so, since the Asus_UI_Win8.exe has not a provision (that I could see) to change the setting you want to change, you will need to edit the Registry. jaclaz

Maybe it is that small read thingy in the middle of the keyboard that you often find in IBM/Lenovo laptops? jaclaz

DO BEFORE THAT answer the question AND try the DellTouchpad.exe on this install. jaclaz

Good. Now - your choice - you can try directly installing this "as is" on XP (this is a shortcut, but if it works, it works). Before that, answer Question #1: AND try the DellTouchPad.exe (which is seemingly self standing AND surely works in XP) and see if it can make the changes AND if the changes are remembered/are effective in the touchpad behaviour. Sure it is, it is probably the last *all elantech* driver for ASUS hardware (ETD0108) before ASUS finished ruining the stupid software with their fork. See: https://www.asus.com/support/FAQ/1009643/ Now, please , STOP §@ç#ing calling things with their "screen name" (that noone but you can see), the "control panel" is EITHER ASUS_UI.exe/ASUS_UI_Win8.exe or SOME OTHER file, what matters is the actual file that is in use, not the "screen name". jaclaz

Ok, let's see if we can re-cap. The "main" three drivers are: Z11509 source: http://ftp.tekwind.co.jp/pub/asustw/nb/Drivers/Touchpad/Touchpad_Elantech_Win7_32_Z11509.zip Z11521 source: http://ftp.tekwind.co.jp/pub/asustw/nb/Drivers/Touchpad/Touchpad_Elantech_Win7_32_Z11521.zip Z115203-cab source: http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2015/09/20755834_3604917b6f0540c8262602489fffab4fff64986a.cab In theory I can see no reason why the Z11509 or the Z11521 shouldn't install on 8.1, as they both have the ETD0108 as "ETD_STD_Inst" AND they have a NTx86.6.2 provision (that though aimed to Windows 8 should be good as well for 8.1 ), in practice they do not work in 8.1. Still in theory these two should also - at first sight - install on XP. The Z115203-cab on the other hand is the one (and only) driver of the "11" series that installed on 8.1 (but NOT on XP). As a matter of fact in this latter there are a number of .exe's and .dll's that have Major/Minor OS/Subsystem 6.0 (and not 5.1 as the two former ones). As always there is a chance that the 6.0 is "artificially" introduced by a new version of the compiler, i.e. the actual code can work in 5.1 but has been "tagged" 6.0 onwards by the default settings of the compiler. If this is the case, changing the OS/subsystem version to 5.1 may have them installed on XP, otherwise, it is again the case of attempting a new Frankendriver, replacing in the Z115203-cab the relevant files coming from Z11521. I do not know a fast/easy method to understand if these .dll's/.exe's make any call to post-XP functions in System .dll's. Check the attached spreadsheet. The First_compare is an incomplete initial attempt, ignore it. The Second_compare is a comparison of the actual "main files" (excluding .avi, .ttf, ,tx_, etc.), that is the relevant info. Proposed approach: a. change all the 6.0 in Z115203-cab to 5.1 via CFF explorer (of course make a copy, etc.) b. attempt installing the modified Z115203-cab on 8.1 <- the only sensible way is - I believe - via Device Manager "Have disk" forcing the install c. see if it works (it should) Questions: 1) what (the heck) is Sensepoint.exe? 2) what files are not actually used in the operation of the driver/touchpad (and that can thus be removed from the .inf, together with the .avi, the .ttf and the .tx_)? You need to trace in detail the behaviour of the driver, via Filemon, Regmon, Procmon, Dependency Walker, etc. Next step: d. uninstall (in 8.1) e. remove from the .inf the lines that are not connected to ETD0108 and the lines connected to the .avi, .ttf and tx_) and remove the corresponding files from the driver source folder f. attempt re-installing g. if it works, remove the .exe's and .dll's that are not *needed* from the .inf and from the source folder h. repeat, uninstall and reinstall until you have the least possible number of files in the source and the smaller possible .inf i. when you are convinced that you cannot shrink further the source, try installing on the XP. jaclaz

Oh, yes, you are right, the volume order may be different from partition order. jaclaz

No, keep for the moment all the files that you have downloaded they may come handy (or you may need to re-download them). jaclaz

I believe that the "ASUS Smart gesture" way is the "wrong" one, as it seems from all the evidence that the good ASUS guys took the already somehow botched code from the Elantech good guys and managed to worsen it (not very easy to do, I might say). I think that the "correct" (hopefully) start point should be the "ASUS" (but actually Elantech) driver: ASUS (in the .inf) 11.5.20.3 07/20/2015 actual.sys 11.165.5.11 from the MS update catalog. This one: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1180923 Unless I lost something in the various attempts, this one works just fine in 8.1 but the .exe/.dll's have troubles on XP. The Frankendriver created with that and the "SAMSUNG" base, failed. Next would be another Frankendriver, still with the above .sys/.cat/inf but with the "11.5.09", this one: DriverDate = "07/29/2012" DriverVersion = "11.5.0.9" actual .sys 10.0.0.164 https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1180979 as "base", which should be the same as: http://ftp.tekwind.co.jp/pub/asustw/nb/Drivers/Touchpad/Touchpad_Elantech_Win7_32_Z11509.zip And we also have the "very near": http://ftp.tekwind.co.jp/pub/asustw/nb/Drivers/Touchpad/Touchpad_Elantech_Win7_32_Z11521.zip We need daniel_k's assistance on possible ways to actually track the installation (and behaviour once installed) in order to troubleshoot the likely problems and - hopefully - chack/review if the building of the Frankendriver needs some other tricks. Then this new Frankendriver should be tested on 8.1 first. And - no offence intended, Dave_H , but till now your reports have rarely gone beyond "it works" or "it doesn't work" + this or that side note, every time slightly different in contents. We need IMHO to establish a "protocol" for reports, in the form of a list of things to check and report, and in this daniel_k's assistance would also be useful. Additionally, and still IMHO, we need to remove *everything* that is not really-really needed from the former (ASUS (in the .inf) 11.5.20.3 07/20/2015 actual.sys 11.165.5.11) until it stops installing working in 8.1. Then restore to the last minimal configuration that installs in 8.1 and completely trace it. Then remove the corresponding items in the 11.5.0.9. And finally attempt creating the new Frankendriver, that at this point should as minimal as it can be. It is a lot of work and it will need some time (unless we - actually you - are exceptionally lucky). Besides that, by comparing the differences between two of the files found on the japanese ftp, namely: Touchpad_Elantech_UXseries_WinXP_32_Z10560.zip Touchpad_Elantech_Win7_32_Z10590.zip that are "very near" in versions we might understand what has changed from the "XP" and the "7" version. But we need a sort of spreadsheet to check hopefully at a glance what the changes are between the various versions. Give me some time and I will try and put together this base spreadsheet . jaclaz

Side note, and probably irrelevant, but unless you partiioned differently than usual on purpose, the volume order doesn't seem the normal one, it seems "reversed", usually first partition is "System", second is "Windows" and - if any - "Recovery" is last. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions jaclaz

Interesting findings. jaclaz

No. The problem in the given thread is with Extended Partitons and Logical Volumes inside them, no matter the filesystem used. jaclaz

Yep , ideally a command (or script) requiring parameters if run without parameters or with insufficient/incorrect ones should print to screen some usage info and do nothing else (or "switch" to interactive mode). jaclaz

The first partition starts (normally) at 2048. Actually there are a set of Registry entries for that (in Vista and later): [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\vds\Alignment] @="Alignment Settings in Bytes" "Between4_8GB"=dword:00100000 "Between8_32GB"=dword:00100000 "GreaterThan32GB"=dword:00100000 "LessThan4GB"=dword:00010000 Where 100000 means 1,048.576. i.e. 1,048.576/512=2048 sectors , the "exception" is made for less than 4 GB sized media where 10000 means 65,536 and 65.536/512=128 sectors. When the partition is aligned to MB, DO NOT EVER use Disk manager from NT. 2K or XP to change ANYTHING on the disk, DO READ this thread http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/ jaclaz

You can do that basically in two ways. One (using a "flat" structure): https://superuser.com/questions/948450/can-you-make-a-windows-10-iso-with-both-pro-home-and-32-64-bit-flavors And the other (keeping the .iso's as they are and using a bootmanager such as GRUB2): https://superuser.com/questions/1055305/installing-windows-x64-on-32-bit-uefi-efi-ia32-via-grub For the first (casually ChrisPE/Win10PE is used) you can also peruse some of the info here (which is about making a dual boot USB drive): https://www.rmprepusb.com/tutorials/127-make-dual-32-64bit-pe and then still use oscdimg to create the .iso jaclaz