jaclaz

jaclaz

Only as a side note, with a USB mouse you should be able to invoke the OSK (on screen keyboard) on the login screen. jaclaz

Good, so we can now exclude that the data in the optional header of the .sys is relevant for XP compatibility. At this point - once you will have tested the 8.2.0.35 - it is probably the case of finding a later driver that works for the ETD0108 on a later system (I lost count, what do you have on 8.1 - apart the Asus software - also an Elantech driver that works)? jaclaz

Good (bad). Try to restore the value with CFF explorer (on the installed ETD.SYS) and reboot/disable/restart the device. What happens? It is possible that you need to correct the PE checksum (or something else) to have the system accept the edit? jaclaz

Next test. Use the 10.0.0.20, (with the modified .inf with the ETD0108 added) BUT try editing the .sys with CFF explorer so that the MajorSubsystemVersion to 5. To recap, this 7.0.5.5 version has; MajorOperatingSystemVersion:0006 MinorOperatingSystemVersion:0000 MajorImageVersion:0006 MinorImageVersion:0000 MajorSubsystemVersion:0005 MinorSubsystemVersion:0001 and *somehow* it works (without working touchpad). While the 10.0.0.20 has: MajorOperatingSystemVersion:0006 MinorOperatingSystemVersion:0001 MajorImageVersion:0006 MinorImageVersion:0001 MajorSubsystemVersion:0006 <- the test is with only this one changed to 0005 MinorSubsystemVersion:0001 and it works (and it doesn't) in different ways. No idea if it will make any difference. Before that, while you have the 7.0.5.5 still installed, what happens running the DellTpad.exe? jaclaz

As a side note, there is an "unified" Samsung driver (allegedly) for XP, with .sys version 10.0.0.100 that has as well 6/1; https://drivers.softpedia.com/get/KEYBOARD-and-MOUSE/Elantech/Samsung-RV515-Elantech-Synaptics-Touchpad-Driver-4100-for-XP.shtml and an earlier one https://drivers.softpedia.com/get/KEYBOARD-and-MOUSE/Elantech/Samsung-NP530U3C-A05US-Elantech-Touchpad-Driver-3900-for-XP.shtml with .sys version 10.0.0.72, also 6/1. Now the (good?) news. This one 7.0.5.4 has at least (the major/minor subsystem 5/1) https://www.hwdrivers.com/drivers/012725 And here is definitely an XP driver (DELL) version 7.0.4.9 https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=mhw9f&oscode=ww1&productcode=inspiron-mini10&lwp=rt that has as well the major/minor subsystem 5/1 7.0.5.5: https://drivers.eu/m8N2j is still subsystem 5/1 7.0.5.8 (.sys) or 7.0.5.9: https://www.techspot.com/drivers/driver/file/information/13154/ has (already) subsystem 6/0 jaclaz

I thin we need some more (better) opinions on this matter. (cdob, where are you?) I am starting to believe that the .sys having 6/0 or 6/1 in the optional header means that it is not XP compatible, and that the beginning on the .inf where XP is stated is misleading and a remnant of previous drivers/versions. It is "queer" as the OS should throw a fit instead of installing such a .sys. I found a 10.0.0.24 where the DellTpad.exe is 10.0.0.3 and the major/minor is 5/2 http://freedriver.org/drivers/notebook.php?n_firm=Asus&driver=007623.rar&n_model=K46CM As said earlier, it is a big, huge mess. On the other hand, I found on microsoft update: https://www.catalog.update.microsoft.com/Search.aspx?q=touchpad elan a couple of ELAN Dell Drivers version 0.0.0.0. dated 12/31/1899 (no they do not apply directly to this case as they are "Vista/7/8/8.1/10" and duly marked by MS as "Windows 10 and later drivers" ), that should tell us something about the reliability of versions, dates and compatibility one can find. jaclaz

Yep, maybe it is important, maybe it is not, cannot say. I find more interesting that *somehow* it decided to install the driver as the "generic" ETD0101. Now we have something to compare with trying again but with the ,inf (actually I believe both the .inf and the .infdrp) modified to use the ETD0105 with a hardware id of ETD0108. Anyway, only to state the contrary of what I just said, the actual ETD.sys version 10.0.0.20 has - as seen in CFF explorer - Major/Minor 6/1, so either: 1) the setting is incorrect (and one could try to set it to 5/1) 2) that setting is ignored/irrelevant And to further complicate the matter I found here (the file on sendspace version 11.8.19.3 is MIA, but the one version 11.8.20.3 on Softpedia is still there) http://forum.notebookreview.com/threads/installing-updated-elan-track-pad-drivers-for-y510p.751866/ some (I am afraid rather indirect) evidence that - at least these Toshiba drivers - are XP compatible, but it is not at all clear (I don't think they can work as they have completely different hardware ID in the .inf, still the Toshiba touchpad has Major/Minor 4/0 and is .NET ) As I said it is a mess. jaclaz

That is part of what I find "queer", maybe it is simply a difference in your setup (with the driver and all the other files installed) and my test (without them). Here in Regmon, set to monitor only DellT*,* and excluding explorer.exe it looks like it accesses the Registry directly., or it is possble that the EDTctrl.exe running in the background (automatically started at boot) makes a difference. I am attaching a regmon.log of what I see here. (BTW for *some* reasons using the DellTpad.exe automatically, sometimes, changes the settings for the external USB mouse swapping buttons) Still what needs to be traced on your system is the actual ETD.SYS, to see if it accesses the Registry to "read" the settings. That surely looks like another promising path. BUT: 1) the driver is (CFF explorer) Major/Minor 6/1 2) in the ,inf the hardware ID's are different (not any ETD01xx) Maybe there is some driver *near* version still XP compatible AND with the right hardware ID, but it is really a huge mess. I don't know, however that ETD.sys driver is 10.0.0.20 (169.256 byte), maybe all this time we were talking of two different files? jaclaz RegmonDellTpad.log

Naah, don't worry, noone is accusing you of doing (or failing to do) anything . As said I understand how each and every suggestion here - expecially mines - are more *semi-random* thoughts than real, exact advice, and as such are difficult to follow. The only one I provided with some *exact* data/behaviour for *some reasons* didn't pass through or was botched by *something else*. I asked you to confirm the behaviour of a specific file, DellTpad.exe, and *for whatever reasons* you ended up runnning and tracing ETDctrl.exe (which again I doubt is the same file, misteriously renamed by the install). The key point - completely speculative BTW - is that the ASUS driver .inf file for laters systems uses the same entry/install for BOTH ETD0105 and ETD108, so logically an ELAN driver which "covers" ETD105 might also work for ETD108 while anyone without support for ETD105 is unlikely to support ETD108. jaclaz

That is actually the *only* thing that is clear enough IMHO: [ETD0105_Inst] Include=msmouse.inf Needs=PS2_Inst Even if I cannot do further testing, the DELL touchpad utility seemingly works here, meaning that it actually attempts to connect to the Registry, actually reads and saves settings in the "right" places, the file is called (and remains called) DellTpad.exe, in the given driver folder, it is 5.728.552 bytes in size and I cannot imagine that *any* install will rename it to ETDCtrl.exe (which also exist in that folder and that is 1.994.536 bytes in size). The point remains if/when the actual driver reads the Registry settings (and which ones) and this can only be determined - maybe - by tracing its behaviour with regmon or similar, and - even if it is hard to use this adverb in this context - logically this applies to the ETD.sys which is in the same driver package, i.e. version 10.0.0.20. jaclaz

I think you haven't (yet) done any of the checkings suggested, and possibly - or at least it seems so - your current installation is far too "botched" by the various installs that you cannot (seriously) state anything definitive about the status of the driver. At least - before giving up - you could try to: 1) go to device manager 2) find the actual hardware involved 3) try to update the driver (this one), possibly expand it to a new directory: using the modified .inf as per: https://msfn.org/board/topic/181362-xp-driver-for-amd-hd8180-graphics-and-elan-ps2-touchpad/?do=findComment&comment=1180077 directly from device manager, it should throw a fit/error or actually connect it to the ETD.SYS. If it does install *something else* find where it comes form, delete it and repeat. I understand how it is difficult to follow *vague* hints, but I think you tried (completely/exactly) more or less 1/3 of what was suggested (by me and other willing members), of course there are no problems if you feel it is time to give up, sad as it might be . jaclaz

>Kind regards, I hope I helped / conveyed an important message. I wonder what actual importance your message: has. Maybe a relevant anecdotal importance. ONly for the record LTSC is a version of windows (Enterprise ONLY) that is not normally available outside large corporations that have Volume License agreements with MS, and has - last time I checked - a non-trivial cost per license. On other news, my Aston Martin Vanquish handles much better than most Fiat Panda's I see around ... jaclaz

Yep, I guess that doing all these tests managed to leave behind some "cruft". It can also be that the ETD.sys is loaded but not "connected" to any hardware, try looking for it in device manager, or possibly try using devcon: https://www.robvanderwoude.com/devcon.php get it from here: It would be the case to thoroughly examine the system and uninstall/delete anything that may be connected with the touchpad or maye even better, and as it was already suggested earlier, to make a (temporary) new, fresh install of XP. jaclaz

Yes and no, meaning that is possible to use grub4dos to boot from a FAT12/16/32 image (that can reside on NTFS). Whether any of the NTFS drivers is "low-level" enough to then be able to boot 9x/Me, is another thing. jaclaz

Good. Also run: https://www.nirsoft.net/utils/driverview.html and look for ETD.sys jaclaz

Sure it does (on smartpad I mean). It is very probable that the driver - for whatever reasons - is not installed or not started (or both)[1] i have no way to go "deeper", but from the driver package (expanded in a directory) if I run DellTpad.exe (and not ETDctrl.exe which is also present), depending on what setting I try to change I can see it accessing both HKEY_CURRENT_USER\Software\Elantech\Smartpad and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Elantech\Smartpad Besides HKEY_CURRENT_USER\Software\Elantech\DeviceInformation HKEY_CURRENT_USER\Software\Elantech\OtherSetting jaclaz [1] maybe trying to reinstall after having modified the .inf?: [ELAN.Mfg] ... %PS2.ELANDeviceDesc% = ETD0105_Inst, *ETD0105 ; Image Sensor adding a line: %PS2.ELANDeviceDesc% = ETD0105_Inst, *ETD0108 ; Image Sensor Also try modfying the ETD.infdrp and use dpinst.exe to install.

Try checking it with Regmon to see what it actually does. Could it be an issue with Registry permissions? jaclaz

Another - different - approach. This driver here: http://dl.drp.su/driverpacks/repack/Touchpad_Elan/Elan/Allx86/Gigabyte_nb/10.5.2.0/Elan-Allx86-Gigabyte_nb-10.5.2.0-drp.zip Contains - besides the "usual" drivers also a DELL touchpad utility that seemingly runs under XP. Actually the tool is marked Dell, but it is a re-branded Elantech. The driver has an entry for ETD0105. Of course no idea if this will work "better" or "at all", but at least runs on my XP and it tries to access the "right" Registry parhs. jaclaz

That is in two places: MajorOperatingSystemVersion 5 MinorOperatingSystemVersion 1 MajorSubsystemVersion 5 MinorSubsystemVersion 1 jaclaz

Yep. No, let's first see how the CFF modified files behave. What I was hinting is that - maybe, just maybe - there is a more complete package for XP without the ETD0108 but with the ETD0105, which this finding demonstrates using the same driver. jaclaz

It seems like ASUS has its own version of the touchpad driver, called AsusTP.SYS. Here: https://www.driverscape.com/manufacturers/asus/laptops-desktops/tp300la/186917 is such a driver - allegedly for XP - that has ACPI\ETD0108 listed. Queerly, this is seemingly a "one size fits all" driver: i.e. *any* from 0105 to 0111 use the same "ATP0105" install and driver. jaclaz

Maybe it is only a matter of the compiler, get CFF explorer and try setting 5.1 on those .exe's. Sometimes the minimum OS version is set to 6 or higher only because it is the default setting for the particular compiler used, of course if the executable calls some post-XP kernel functions, that is appropriate. jaclaz

Post a link to that installer. (maybe - just maybe - it is only one of the stupid compiling options for a single .exe) jaclaz

Yep, That would be consistent with the fact that the driver installed "the same" with or without the ETD0108 addition. Somehow the driver must have a "basic" mode, unaffected by the settings or "fixed", that is "good for all devices", and that is what you are now using, though I don't think it is an Asus thing, I believe it is more like an Elan "fallback feature". Try adding an USB mouse (personally I cannot even think of using a laptop if not in emergencies/quick things, without a mouse), two possible scenarios: 1) the USB "prevails" i.e. the "fixed" mode is set to DisableWhenUSBMouse (I doubt it as the setting in "Driver Status Information" is 0x00000000 (0)) 2) you can disable the port and use the mouse All in all, it may be that the driver has "inside" these "default" settings, still I would try tracing the files with Regmon/Filemon. jaclaz