jaclaz

Maybe it is only a language translation glitch, and he meant "remove by uninstalling". Isn't it fun that an Italian and a Bulgarian can debate on the exactness of the English terminology used by a Czech? jaclaz

Sure it doesn't, at the time I proposed it we were after ETDmcpl, but I left (casually) the [ETDCpl.CopyFiles] section in the .inf, so it is just a matter of adding it there and in [SourceDisksFiles]. Then we need to add the [ETD_ControlPanel.AddReg] (like in the Samsung driver) with the settings of the last posted .reg, to have rhe "added" Elan Touchpad Control Panel item. Post the last version of the .inf you have, and I will try and add these settings. Good , but you can still revert to a previously saved Registry via Erunt, cannot you? (only to see if something is still there that wasn't before). jaclaz

At least here, I can set UI_Theme=5 (so that there is no added Mouse Control Panel Tab and the driver is using the ASUS ID) and using the attached .reg I have the additional "Elan Touchpad" Control Panel item that loads ETDAniconf.exe without seemingly any need for ETDmcpl.dll. Of course this way a separate script (or .reg file) is needed to flip on/off the Tap_One_Finger_Enable value (that is the one used with UI_Theme=5 BUT that is not among the settings that ETDAniconf.exe can change. jaclaz ControlPanelAddition.zip

No particular ideas/suggestions, here is what a "normal" install Select key should look like: Having more than 2 controlsets (ControlSet001 and Controlset002) - while not necessarily an issue - is a sign that the system has been fiddled with (improperly), possibly several times and/or experienced serious corruption issues. Personally I am all about NOT reinstalling unneededly, to give you a single anecdata point I am writing this from an XP (SP2, and yes I know) that was put (transferred not installed) on this machine in 2008, and that was actually originally installed on a completely different machine in 2004 or so. As you say, you can solve 95% of the issues, evidently it is in the 5% remaining that the excess controlsets and other generic Registry weirdness reside. I believe that a system cannot boot at all without a "Current" control set selected, so you should have some value in: HKEY_LOCAL_MACHINE\SYSTEM\Select\Current and that one is the controlset which is in use when the machine is booted, all the others are not used at all and are irrelevant to the isue at hand. jaclaz

The exact string I posted is (obviously) what is in the .inf, in the Registry, it is the SCSIAdapter class: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/system-defined-device-setup-classes-available-to-vendors In the Registry you need to check: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318 } HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318 } HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318 } There is no such thing as CurrentControlSet2 that I know of in "normal operation", it must be an artifact of heaven knows which program or operation. But of course the UpperFilters was just something to check, not necessarily the actual culprit. Quick reminder about ControlSets: https://msfn.org/board/topic/181451-are-the-ssd-disks-windows-2000-compatible/page/2/?tab=comments#comment-1182267 Check which ControlSet is in use according to: HKEY_LOCAL_MACHINE\SYSTEM\Select Sorry to be blunt, but from the fact that you have a ControlSet up to 008 it means that what you call "tuned" install I would personally call "botched beyond repair" or "with so many cruft accumulated that it is hopeless". jaclaz

Generally speaking, Code 10 driver issues are often connected with UpperFilters. I love coincidences: https://msfn.org/board/topic/181596-winxp-half-working-mouse-and-keyboard-no-input-after-vmware-driver-removal/ Of course in this case you need to check: jaclaz

You don't have to, it is just "fun". Yep, this something still to solve, as it works just fine here with UI_Theme=1, and we still have the possibility of the separate added link "ETD Touchpad" in Control Panel. Filemon (when clicking on "Options" in the added to the Mouse Control Panel Elan Tab: 15.13.33 rundll32.exe:2728 FASTIO_QUERY_OPEN C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Attributes: A 15.13.33 rundll32.exe:2728 FASTIO_QUERY_OPEN C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Attributes: A 15.13.33 rundll32.exe:2728 FASTIO_QUERY_BASIC_INFO C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Attributes: A 15.13.33 rundll32.exe:2728 FASTIO_QUERY_STANDARD_INFO C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Length: 7388560 15.13.33 rundll32.exe:2728 FASTIO_QUERY_OPEN C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Attributes: A 15.13.33 rundll32.exe:2728 FASTIO_QUERY_STANDARD_INFO C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Length: 7388560 15.13.33 rundll32.exe:2728 FASTIO_QUERY_STANDARD_INFO C:\Programmi\Elantech\ETDAniConf.exe SUCCESS Length: 7388560 15.13.33 ETDAniConf.exe:5624 FASTIO_QUERY_OPEN C:\Programmi\Elantech\WINMM.dll NOT FOUND Attributes: Error 15.13.33 ETDAniConf.exe:5624 FASTIO_QUERY_OPEN C:\WINDOWS\system32\WINMM.dll SUCCESS Attributes: A jaclaz

On the other hand: Non ha il palio se non chi corre. @Dave-H A I see it, specifically there are maybe three quarters of the functions that serve no useful purposes but there are a few that - should they work - seem very useful. And - besides - in theory we need not any particularly fancy control panel, we can use *any* of them (now that they all work) and supplement them (or replace them) with .reg files ot reg.exe commands. Of all the various ones, the best one (IMHO) is anyway the Aniconf.exe, as it is the one that actually "respects" the Registry settings (more or less), with possibly the only "missing" option being that of (with UI_Theme=5) to use the Tap_One_Finger_Enable, which seems like a "better" option as it allows to disable the one finger tap but - at least in theory - still allow to use 2 and 3 finger taps. Additionally, it is the easier to trace as changes in its settings are immediately, one by one, reflected in the Registry, whilst the other ones write to the registry the whole lot of keys. Anyway, it is only up to you. Attached is a scheme on how the various setting in SmartPadDisplay affect the various ETDAniconf.exe (I rduced them to only three versions as they are representative of the other ones). jaclaz SmartDisplay.zip

@Dave-H Well, imagine that your parents gave you as a kid one of these: https://www.victorinox.com/global/en/Products/Swiss-Army-Knives/Medium-Pocket-Knives/Handyman/p/1.3773 BUT you were only allowed to use the toothpick, the tweezers and the corkscrew ... What if I told you ... ... that different versions of Aniconf.exe show different possible settings? jaclaz

No, we did NOT remove "too much", what we are doing is to attempt "componentizing" the driver, the .inf and the settings tools. Good morning, Mr. de La Palice . This is actually what we are working on lately, the original issue Dave-H had has been solved since a long time. jaclaz

Ok the "defaults" (possibly not all over, but in spots) come from the HKLM "Smartpad" key. So, change the: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Elantech\SmartPad Tap_Two_Finger Setting it to 1 (Pop-up Menu) now, if you run Aniconf.exe or ETDmcpl.dll, and decide to set the defaults (for everything or just for the "Touch" panel) the corresponding key in HKCU will become 1 (instead of 0) and ETDsimpleUI-exe will not produce that error. jaclaz

Sure, and the error is: System.IndexOutOfRangeException Found it it is: HKEY_CURRENT_USER\Software\Elantech\SmartPad\Tap_Two_Finger If it is set to 0 ETDSimpleUI crashes If it is set to 1 ETDSimpleUI is fine AND drop down item is "Pop-up Menu" If it is set to 2 ETDSimpleUI is fine AND drop down item is "Middle Button" The funny (actually tragical) thing is that it if you run Aniconf.exe and set all to default, it sets the above key to 0. jaclaz

Because the result will invariably result in an automated reverse version of: https://en.wikipedia.org/wiki/English_as_She_Is_Spoke jaclaz

Try BootIce: https://msfn.org/board/topic/181587-i-see-only-2t-from-a-4t-disk/?do=findComment&comment=1182815 jaclaz

Naah, leave EasyBCD alone. Get instead BootIce if you want a GUI tool: http://reboot.pro/topic/21956-bootice-v1332/ But you can fix the issue with BCDEDIT just fine, *like*: https://forums.tomshardware.com/threads/how-to-add-windows-xp-entry-to-windows-7-vista-boot-manager.1193485/ Check (you will need to set the system to show in Explorer hidden and system files) that you have in root of C: the files: NTLDR BOOT.INI Then recreate an entry in the BCD for ntldr as in the above. With - select the BCD tab, then EasyMode, click Add, select "New Windows XP/2003 entry" and select the right disk and the C:\ partition on the right side of the window, and finally click "Save current system", have a look at this tutorial: the relevant part starts around 7:53 jaclaz

Yep, what happens here if you run RegMon with Filter/Highlight: HKCU\Software\Elantech\SmartPadDisplay;HKCU\Software\Elantech\SmartPad;HKLM\SYSTEM\CurrentControlSet\Control\Elantech\ is that when you drag the corner icons the values are set to 0, whilst the .reg sets them to 0x30: Values set by the .reg, read by Aniconf.exe: QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_Enable SUCCESS 0x1 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Func SUCCESS 0xF QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Path SUCCESS QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Width SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Height SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Func SUCCESS 0x11 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Path SUCCESS QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Width SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Height SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Func SUCCESS 0x13 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Path SUCCESS QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Width SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Height SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Func SUCCESS 0x10 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Path SUCCESS QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Width SUCCESS 0x30 QueryValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Height SUCCESS 0x30 Disable from Aniconf.exe: SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_Enable SUCCESS 0x0 Enable from Aniconf.exe: SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_Enable SUCCESS 0x1 Dragging one of the corners to enlarge it: SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Width SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TL_Height SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Width SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_TR_Height SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Width SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BL_Height SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Width SUCCESS 0x0 SetValue HKCU\Software\Elantech\SmartPad\Corner_Tap_BR_Height SUCCESS 0x0 it may well be a quirk in my installation but - say - the Toshiba.exe sets their size correctly. (the actions to be perfomed are saved correctly both in Aniconf.exe and Toshiba.exe) But, if you run the .reg they are set correctly, then it has to be seen if the feature applies to the specific smartpad model and/or to the specific driver. There is also the possibility that the setting/feature is contrasting with some other one, and the othr one is prevailing Maybe you need to set one finger Tap on or *whatever*. If it doesn't work, it makes no sense to have it in the control panel, so you can edit smartpadisplay.reg corresponding line: "CornerTap_Display"=dword:00000000 jaclaz

Hmmm. Reimport the two .regs in the attached, (the previous one I posted I deleted as there was a mistake in it), and then reimport the smartpad_corner_tap.reg. Then WITHOUT opening the ETDAniconf.exe or the ETDmcpl.dll try if when tapping on the corners of the touchpaf anything happens. jaclaz ResetRegs.zip

I don't know. I originally imported "your" HKCU and HKLM settings. Then (when something didn't work anymore) re-imported your HKCU settings only. Then the smartpaddisplay0x1.reg. Then the smartpad_ShowItem0x1.reg. Then experimented with the various keys. About the "Corner Tap Zone", for *some reason* the ETDAniconf sets all four corners Width and Height to 0x00, with the net effect that there are no corners to tap on. And even the graphical representation (inside ETDAniconf.exe) always shows 0 sized corners. The only tool that seems to deal with it properly is the "Toshiba.exe" (possibly also the "Lenovo.exe" but right now I cannot verify) that - even if it throws an error from time to time about the ETD_DLL.dll (so we actually found what this .dll is used for) and has other limitations, it seemingly sets corner just fine. It's madness, however try setting manually the relevant keys to a "sound" value (0x30), i.e. try importing the attached .reg and see if corner tapping does anything. Functions are: TL Start Menu TR Zoom+ BL Back to Desktop BR Zoom - jaclaz smartpad_corner_tap.zip

UI_Theme needs to be 1 here to have the Aniconf start from the mouse Properties. I also have Visible_Animation=1 and CustomerDefinition set to 5 but these seems not being relevant. Probably you need to stop ETDctrl.exe to sense the change? jaclaz

Personally I wouldn't bother with NVME (it is actually faster but it is way more epensive and I don't think it would give any advantage, at least on XP, while sure it will be a nightmare with drivers) a simpler SATA SSD should be more than enough. Which (EXACT) make/model of motherboard do you have? About making the second partition on the 4 TB disk, start by reading this thread: https://msfn.org/board/topic/176480-2-tib-limit-size-in-mbr-hard-drives/ even if you do not (yet) understand something it will give you some primer on the procedures involved. In a nutshell we need to: 1) check the current partitioning scheme (with the actual data in the MBR, i.e. exact to the byte) 2) verify that the current partition and volume are fine and if needed resize them (shrink them a little bit) so that the second partition can begin before the 2.2 TB limit 3) create manually a second partition strating just before the limit and extending to the max possible size 4) verify that this second partition is seen correctly by the windows 8.1 5) verify how this second partition is seen in XP (very, very likely it won't ever - even if seen correctly - be accessible from XP) 6) format this second partition from 8.1 (to a NTFS volume) 7) re-check how this second volume is seen in XP (very, very likely it will not be seen "properly" and even if it is attempting to access it from XP might corrupt it, so probably it will be needed to remove drive letter assignment to it) 8) check the this seconf voluem operates correctly from 8.1 jaclaz

Some news. I finally understood why I had issues with both ETDmcpl and ETDAniconf, for *some reasons* the ETDCtrl.exe (on my half-@§§ed "fake" install) periodically accesses the: HKEY_CURRENT_USER\Software\Elantech\SmartpadDisplay and sets each and every value in it to 0x0. The net effect is that with those values set to 0 both the ETDmcpl and the ETDAniconf panes become completely blank. So, re-importing in the Registry the whole set of values (set to 0x1) makes not only both settings panel functional, but makes visible a number of options never seen before. Moreover, as expected, there are differences in Aniconf.exe, the version that I tested till now (10.0.0.20) that I had tested till now, for *some reasons* when using the "set as default button" wrote "absurd" values in the Registry: HKEY_CURRENT_USER\Software\Elantech\Smartpad values and this is at least part of the reason why the two based on (stupid) .Net tools Asus_UI.exe and ETDSimpleUI.exe throw errors. Some errors in ETDSimpleUI may remain, just set the defailts from it (and then change back to your settings and they shoudl disappear. I can now run the most recent ETDAniconf.exe (version 11.59.0.0) coming from the 11.5.20.3 driver) and not only it has more sane "default" values, it has also a number of added settings/features, again here for *some reasons* periodically Aniconf.exe itself disables some settings making them invisible, possibly they are someting that is/was experimental. Also the ETDmcpl.dll from the "Medion" driver (11.5.2.1) which is version 11.20.0.0 is probably "better". It is very possible that some functions are mutually exclusive (or not suitable for the specific SmartPad at hand) but surely there are quite a few very interesting possibilities (if they work on your smartpad). To see them: 1) get the Aniconf.exe 11.59.0.0 from 11.5.20.3 or (IMHO better) the 11.20.0.0 from the "Medion" driver 2) import the two attached .reg files 3) Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Elantech\UIFunctionOption UI_Theme=1 Visible_Animaton=1 <- the effect of this one is not clear, but it is the default driver setting in the "Medion" driver 3) run the Aniconf.exe by double clicking it OR from the Elan tab on the mouse control panel 4) explore the several new possibilities. jaclaz

32 bit or 64 bit is irrelevant when it comes to size accessible on disk. A disk that has been partitioned as MBR won't normally allow to access anything beyond the 2.2 TB limit, this limit is not in the processor or OS bit width but rather in the partitioning scheme. To access the whole 4 TB you will need to re-partition the disk as GPT, but then XP won't be able anymore to access it, though third party tools exist for working around the issue. Anyway, the disk won't ever be bootable in XP, and it will only be bootable in 8.1 IF you have a UEFI firmware (as opposed to BIOS). Again there are solutions (actually more workarounds than solutions) for these problems, but they tend to be complex to implement and to mantain. No offence intended of course , but - from your questions - you do not appear to have (at the moment) the knowledge and experience to apply them. Briefly, it is possible on a 4 TB disk to create two partitions each one slightly smaller than 2 TB keeping the MBR partitioning scheme, then 8.1 should be able to access both of them whilst XP will only be able to access the first one, but the procedure is manual and prone to errors/issues, If you want I can assist you but you have to be aware that the whole stuff is at an "advanced" level. jaclaz

You mean like HAL? jaclaz

Yep, reimport in Registry the HKCU .reg you posted earlier, it should fix the issue: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1182617 jaclaz

Very likely you need the ETDMag.exe (from -say - Z11521) in the Programs\Elantech folder. In Aniconf.exe setting it makes HKCU\Software\Elantech\SmartPad\Mag_Enable 0x1 And there are other keys involved: HKCU\Software\Elantech\SmartPad\Mag_Enable 0x1 HKCU\Software\Elantech\SmartPad\Mag_Kind 0x2 <- this is misterious In ETDmcpl.dll: HKCU\Software\Elantech\SmartPad\Mag_P 0x0=2x 0x1=3x 0x2=6x 0x3=7x 0x4=9x But in Aniconf.exe: HKCU\Software\Elantech\SmartPad\Mag_P 0x0=2x 0x1=3x 0x2=4x 0x3=5x 0x4=6x 0x5=7x 0x6=8x 0x7=9x 0x8=10x 0x9=12x 0xA=14X 0xB=16x And in Aniconf.exe BUT NOT in ETDmcpl.cpl: HKCU\Software\Elantech\SmartPad\Mag_X 0x1=96 0x2=128 0x3=256 etc. HKCU\Software\Elantech\SmartPad\Mag_Y as above The ETDmag.exe does access keys: HKCU\Software\Elantech\SmartPad\Mag_X HKCU\Software\Elantech\SmartPad\Mag_Y HKCU\Software\Elantech\SmartPad\Mag_P and through them you can set magnification level and size of the magnifier window. (actually if you set it very thin and very wide, it may even be useful at 2x or 3x ) Still it is well possible that making it visible in SmartPadDisplay is only part of the story and another key *somewhere* is needed. Try changing to 0x1 only HKEY_CURRENT_USER\Software\Elantech\SmartpadDisplay\FourFinger_Display ETDSimpleUI.exe shows an additional "Four-Finger" Swipe option. Checking the checkbnox keys: HKCU\Software\Elantech\SmartPad\FourFingerMoveUp_Enable HKCU\Software\Elantech\SmartPad\FourFingerMoveDown_Enable are set to 0x1 setting HKEY_CURRENT_USER\Software\Elantech\SmartpadDisplay\FourFinger_Display back to 0x0 the option disappears. jaclaz P.S.: unless I am mistaken the ETDAniconf.exe that works here (it is the version 10.0.0.20 from Z10590) seems to me like being far better in capabilities than the ETDmcpl.dll and than the ETDSimpleUI.exe, and even if it actually tries to access the .avi files, it works just fine without them.