jaclaz

OK. So we now know that the version of ETDapix.dll 11.0.0.8 is the minimum version that works with ETDCtrl.exe 11.0.0.13 (and ETDCtrlHelper.exe 11.0.0.7) Now, what happens (keeping the ETDapix.dll version 10.0.0.98) if you try "downgrading" (in pairs) ETDCtrl.exe and ETDCtrlHelper.exe? With: ETDCtrl.exe 10.0.0.117 ETDCtrlHelper.exe 10.0.0.73 from Z11521 If - by any chance - the driver comes back to life, then try: ETDCtrl.exe 10.0.0.101 ETDCtrlHelper.exe 10.0.0.67 from Z11509. If it doesn't, restore the ETDCtrl.exe 11.0.0.13 and ETDCtrlHelper.exe 11.0.0.7 and try downgrading the .sys from the curent one (ETD.sys 11.0.0.31) to 10.0.0.188 and if it works, try again downgrading the two .exe's. @RainyShadow The (stupid) .inf of the (only currently installing without mods) Z115203-cab is huge, almost 2 MB and "as is" it is "unworkable", It must (IMHO) be trimmed down removing all the clutter before being able to do the "fine tuning", some parts are clearly needed, but I am pretty sure (but not too much) that most parts are "unneeded", several models, the Windows 10 provision, etc. As soon as I have some time I'll try looking at it. The coinstaller is a non-problem (anymore), as the Z115203-cab (which installs just fine) has it not, and the earler "Lenovo" driver currently under test (tp118w7) and that is working also has it not, and all the earlier drivers also have it not, it must have been introduced for *some reasons* in mid 2014, but we are already back to march 2013. jaclaz

Good news, The ETDUn_inst.exe and ETDUninst.dll are "irrelevant". The ETDapi.dll being 10.0.0.9 is instead a good sign. Try replacing it with the ETDapi.dll 10.0.0.8 coming from Z11521. If it still works, try with the ETDapi.dll 10.0.0.6 coming from Z11509. If it still works, try replacing the ETDapix.dll (currently 11.0.0.8) with the 10.0.0.98 from Z11521. If it still works, try replacing the ETDapix.dll with the 10.0.0.86 from Z11509. And so on. Try only a file at a time and only go back to the nearest earlier version, until the driver stops working (and than revert to the last later version one that was working). jaclaz

What you prefer, I mean, now we know that 11.1.0.0 is compatible and that 11.5.0.0 is not (with the hotkey tool) so it is only a matter of replacing the .dll forth or back depending on the experiment at hand. About those two files, they surely are not needed for the "basic" working of the driver, and the ETDAPI32.DLL is not even mentioned in the .inf, so it wouldn't be copied to the ELAN program directory anyway . But - all in all - these latest experiments seem (to me) to show that the initial assumption was valid (there are - though limited - possibilities to exchange/replace various versions of the drivers, as a whole or partially, no matter if they "originated" from Asus or from Lenovo (or Medion), etc.) so if not all. at least most of the "magic" is in the .inf of the Z115203-cab. Try doing another step (or leap ) back in time, by replacing the files in the currrent install of 8.1 with the ones from the earlier: https://pcsupport.lenovo.com/hn/en/products/laptops-and-netbooks/lenovo-g-series-laptops/lenovo-g505s-notebook/downloads/ds035770 tp118w7.exe Official version 11.4.14.1 actual .sys file 11.0.0.31. jaclaz

It is possible that - for *some reasons* the driver *needs* to be installed with the Setup.exe (and can later only be "upgraded" via the .inf, and you can *try* replacing the Setup.exe and the ETDUn_inst.exe and ETDUninst.dll from "39z502wf", BUT keeping the Setup.ini from Z115203-cab ), but I doubt that it can work . The ETDCtrlHelper.exe issue might be the actual "show stopper", but cannot really say. Unless RainyShadow and/or daniel_k come out with some new ideas, I guess that the only thing to do now is to trace completely the behaviour of the driver both under 8.1 and XP and compare results. To avoid the huge clutter of a boot time complete trace, one could try to disable the device and trace when the device is re-enabled, but cannot say if that would be enough. @RainyShadow Yep, but the driver/.inf that actually installs (Z115203-cab) has NOT any coinstaller, while the earlier driver we are testing has it , the only "pattern" I can see is a "queer" build date progression, i.e. older drivers have not any coinstaller, then they start having it, and then again the Z115203-cab have it not anymore. NOTE: the "first" (back in time) driver of the Lenovo Series that also has NOT any coinstaller is seemingly the: https://pcsupport.lenovo.com/ro/en/products/laptops-and-netbooks/lenovo-g-series-laptops/g50-70-notebook-lenovo/downloads/ds100305 tp165w73264.exe which is "officially" version 11.4.31.1, actual .sys version 11.122.4.2, intended for Windows 7, while later ones have the coinstaller. @Dave-h It would be worth the time to go back to 8.1 and try replacing the files with those coming from the above, if it works in 8.1, then it is a "better" candidate under XP. jaclaz

Basically you want to have an image AT LEAST 150 dpi (better 300 dpi) at 100%size. Sources: https://www.printful.com/blog/everything-you-need-to-know-to-prepare-the-perfect-printfile/ https://www.brokenarrowwear.com/digitalprinting/digital-art-requirements.html jaclaz

ONLY as a "draft" of next steps, should the thingy actually *somehow* work, the next step is using Examdiff: https://www.prestosoft.com/edp_examdiff.asp to compare (a copy of ) the .inf in Z115203-cab with (a copy of) the one in 39z502wf. You will see that there is a lot of work to: 1) remove from both *anything* that is NOT related to "ETD_STD_Inst" or to "ACPI\ETD0108" 2) remove from both *anything* that is currently (in the one or the other) REMmed by prepending a ; to the line 3) remove all the (IMHO) senseless gestures in section "[ETD_GestureAPHotKey.AddReg]" 4) understand (if possible) what (the heck) are the sections "; GroupMap_xxxx_UID_yy" 5) remove (from Z115203-cab) anything referencing NTx86.6.4 or beginning with "WIN10_" or however related to Windows 10 6) I would also remove all reated to "animations" and ".avi" files, but this is to be seen. You will see that things will start to get better in sync, and hopefully we can understand what to change in the 39z502wf .inf, making it "installable" directly. Besides the above I remain perplexed by the presence (in the Lenovo) of the "ETDCoInstaller.dll" (and relative entries in ETD.inf), I have seen that some of these drivers have this .dll, and some have it not, but I have yet to find a "logical" pattern or understand (actually making an educated guess) how it is useful and what it does. jaclaz

Yep, at the moment is the only way it can - maybe - work. 11.5.20.3 did *somehow* install on XP previously (but failed to run because of all the "6.0" files): https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1181253 It should also install now "as is" (and fail to work) then - once the "6.0" files are replaced by the "5.1" versions - it should - hopefully - start to work. Possibly a reboot/disable/enable/etc. may be needed, of course. IF we get to have it working with "install+replace", then we will be able to attempt modifying the .inf (and hopefully be able also to install "directly"). jaclaz

Yep, sorry I didn't mention it , those Lenovo drivers are InnoSetup installers and I also used good ol' Universal Extractor . It is entirely possible that the ElanTPcfg.exe and the hotkey hooking apps look for a given version (actually a function). and one of these three files (I doubt more than one) is not "seen" correctly or simply misses a function (if I had to place a bet, it would be on ETDApi.dll, with second choice ETD_DLL.dll ), from the name only it is more probable that ETDAniconf.exe serves no practical purposes (maybe it is the *whatever* that shows/updates the tray icon) . Anyway this is marginal, you can still put back the original three files, or try putting them back one at the time to see which one creates the issue. Before that, I would also try - only as an experiment - to replace also the actual "main" ETD.sys file. And now you should be ready to try repeating the install and the replacement on the XP system (remember to keep your finger crossed while you do it). Let see what happens . jaclaz NOTE: The file: https://support.lenovo.com/at/en/downloads/ds100549 39z502wf.exe Should be version 11.4.36.1 (and for Windows 7) DriverDate = "02/11/2014" DriverVersion = "11.4.36.1" The file: https://support.lenovo.com/by/en/downloads/ds100220 31tp00ww.exe Should be 11.4.38.2 (and for Windows 8.1) DriverDate = "02/18/2014" DriverVersion = "11.4.38.2" Please note how this latter is described as "Windows 8.1 (64-bit)" and 23.87 MB in size, but the download will result in a 129 MB file that contains also the x86 one. They are so near in dates/versions that probably it makes no difference anyway.

Yep , I know, and since the documentation and examples, particularly for "advanced" features is scarce or scattered around (on reboot.pro, here and there, on Steve6375's site , on Chenall's blog or this or that Chinese board - with the added difficulty of interpreting the Chinese google translations) it is also an entertaining treasure hunt, This is "queer", Older versions of grub4dos (around good ol' 0.4.4) had issues with DOS <=6.22 but always worked with DOS >6.22 AFAICR, a more common issue (in VM's) is that the newish versions (0.4.5+) need "a lot" of memory, 32 MB and if I recall correctly it already happened that the issue was a "too small" amount of memory. As a side note, when (if) you will have had enough fun and starting to get bored, an approach that may interest you: http://reboot.pro/topic/17807-release-cosmias-a-new-approach-to-g4d-images/ jaclaz

Yep. There may be some doubts about: ETD_DLL.dll ETD_Aniconf.exe ETD_Api.dll which are already (or still ) "5.1" in the Z115203, maybe you can try first replacing all the .exe's and .dll's BUT those three, and then, in a subsequent step, attempt replacing also those three. jaclaz

Maybe, but that - as well as the control panel or the mouse properties tab - is (all in all) not much relevant. As long as the driver is loaded and "pilots" the device and you can change the relevant settings (if needed through direct Registry editing) I would say it would be enough. Anyway, if I got this right, once you re-enabled the touchpad it worked even with the "Medion" "11.2.2.1" ETD.sys driver, right? Anyway I would still keep for the moment the ETD.sys (and .cat and .inf) from Z115203-cab as "base", if the ETDApix.dll and the other files in latest "5.1" version manage to "hook" that, we should be almost there. jaclaz

I.e. click here (hint: add &t=6m33s to the Youtube URL): https://www.youtube.com/watch?v=nycAujdp708&t=6m33s Nice find, BTW . jaclaz

I know you are doing what you believe is your best effort but you have to understand how I cannot see what you are doing not seeing what the effects are, anything that references "as before", "like the last time", etc. is confusing to me. But no problem , now you can follow the generic idea which is: 1) the files (as a whole) in Z115203-cab are the "lowest" version that actually install in Windows 8.1 "as they are" 2) BUT some (most) of the .dll's and .exe's in Z115203-cab are "6.0" (while they need to be "5.1" to work in XP) 3) we need to make a Frankendriver where the .inf (and the .cat and .sys, at least temporarily) come from Z115203-cab BUT all .exe's and .dll's are "5.1" 4) an almost successful (or only partially unsuccesful, it depends how you look at it ) approach has been using the "5.1" files from "Medion" or "11.2.2.1", BUT - since even in the "Medion" or "11.2.2.1" a "key" file is Apix.dll, that is "6.0", we resorted to try using the latest we had, version "10.0.0.98" coming from Z11521 5) while you were doing the above tests, I searched for LENOVO drivers and found quite a few that are higher in version than the ones in the Z11521 (good), lower in version than the ones in Z115203-cab and "5.1" and actually much nearer to the ones in version in Z115203-cab The better probabilities with this Frankendriver is with the highest version of the .exe's and .dll's that are still "5.1", it is possible that, since "only" these files: ETDApix.dll ETDCmds.dll ETDCtrl.exe ETDCtrlHelper.exe ETDDeviceInformation.exe ETDFavorite.dll ETDMcpl.dll ETDService.exe ETDUninst.dll ETDUn_inst.exe Setup.exe are 6.0 in Z115203-cab, it is enough to replace those with the corresponding ones in the highest version of the drivers that are still "5.1". Till now those were coming: ETDapix.dll -> version 10.0.98 from Z11521 All the others -> version 11.x from "Medion" or "11.2.2.1" Now we have (check the "Links" sheet in the last attached spreadsheet) a Lenovo driver which is "11.4.38.2", actual .sys version 11.122.4.8 with an ETDApix.dll which is version 11.27.4.2 (much higher than the "best" we had till now, "10.0.0.98") but that is still "5.1". Spreadsheet further updated attached, all previous versions deleted. jaclaz Elantech_drivers_comparison.xls

Wait a minute. We have another "breakthrough" with the set of Lenovo drivers I was listing. Your reports continue to be confusing. Really "all" files, or all the files BUT NOT the .sys? Otherwise WHAT is the same as WHAT? I lose you at each of these vague, incomplete reports, it is really difficult for me to understand what you did and what effects came from what you did, I have to look back n posts, then interpreter what you mean, and maybe even then I am not getting what actually happened. You need (of course if your intention is that I can understand them) in your reports to: 1) list the EXACT version of EACH file you are currently running 2) the EXACT behaviour of the touchpad (it works, it does not work) 3) what EXACTLY happens when changing the settings (and with which tool you are trying to change them, or directly via the Registry) Anyway, get this new attached spreadsheet. I haven't updated the "Second_Compare" sheet, but look at the third sheet. dates/versions seem to start making (loosely) some sense. At the moment the best bet is on a new FrankenDriver with Z115203-cab as base and this Lenovo driver: https://support.lenovo.com/at/en/downloads/ds100549 39z502wf.exe jaclaz

Best bet till now: https://pcsupport.lenovo.com/ro/en/products/laptops-and-netbooks/lenovo-g-series-laptops/g50-70-notebook-lenovo/downloads/ds100305 tp165w73264.exe ETDApix.dll is 11.27.0.0 and 5.1! And there is also a ETDDeviceInformation.exe version 11.143.0.0, also 5.1. jaclaz

And yet another one, back to the past, a Lenovo one: https://pcsupport.lenovo.com/hn/en/products/laptops-and-netbooks/lenovo-g-series-laptops/lenovo-g505s-notebook/downloads/ds035770 tp118w7.exe In the .inf: DriverDate = "02/26/2013" DriverVersion = "11.4.14.1" Haven't updated the spreadsheet, but ETDapix.dll is version 11.0.0.8, and the relevant files seem all 5.1, and "on the whole" (files dates) it seems midway between the Z11566 and the "Medion". 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