Dave-H

I'm glad the carousel videos work for you again now. I've never used the DM on Instagram so I don't know if it's working for me or not, but I don't think that entry in userContent.css should affect it. Have you got anything else in there?

Putting @-moz-document domain(instagram.com) { div._97aPb > div { display: block !important; } div.Igw0E > div { display: block !important; } div.Igw0E > div > div { display: block !important; } } into userContent.css seems to bring back the carousel videos. If there was something similar there before, replace it with this. It doesn't get rid of the scroll bars though.

Interesting about ETD.sys. I've checked the versions in version 7 and 8 of the software (there doesn't seem to be a version 9), and the ETD.sys versions in both of them are recorded as being Major/Minor 6/1 by CFF as well! Very strange, as they are definitely supposed to be XP compatible. Anyway, I uninstalled and reinstalled the driver with the INF files modified as you detailed earlier. Here's the setup log. It has recognised and used the added 0108 entry by the look of it, but the end result seems to have been the same. SetupAPI2.log

Well here's some important information! After installing the driver I ran ETDDeviceInformation.exe again, and this time I ticked the "Setupapi Log" option. Attached is the relevant section of the output. I think the critical line is "Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device." This was using an unmodified INF file. SetupAPI.log

I noticed a while ago that the versions of the files don't match the quoted versions of the driver, and I'm going by the version quoted in the INF file, not the name of the installation file, which could be wrong of course. As you say, the version of ETD.sys in the 10.5.2.0 driver is 10.0.0.20, and the version of ETDCtrl.exe is 10.0.0.9! I guess that doesn't matter. I'm not surprised to hear you say that the files in 11.4.1.6 need at least Windows 7. I didn't actually think it would install on XP, as I don't think any of the 11.x versions will, but I thought it might install on 8.1, just as a test, because I've yet to see one of these drivers actually working properly. If were possible to get a version working properly on 8.1 with the same hardware, that could be very valuable for comparison purposes. Unfortunately, all the ones I've tried on 8.1 still don't work, because I don't think they are identifying the hardware correctly, or possibly they are just not compatible with it. I will reinstall 10.5.2.0 on XP and forget about all the other versions, and we can take it from there.

When I ran DellTpad.exe, and monitored the output of RegMon, a lot of ETDctrl entries appeared. I took that to mean that DellTpad was actually running ETDctrl, and was just a display interface for it, replacing the Elan interface which would normally be used. I can't think of any other explanation for it. Anyway, if we are to carry on, should I use that Dell 10.5.2.0 driver again and forget about the others I've been experimenting with? I found a 32 bit version of 11.4.1.6 here - https://support.lenovo.com/gb/en/downloads/ds031990 This, unlike all the other drivers, doesn't just install a non-functional version of the driver. Instead, on both XP and 8.1, if I try to install it, it puts up a message saying - "The driver version doesn't suit this Touch-Pad. Please check the device in system and install the suitable driver." This is the first time I've seen any of these drivers actually saying that it's not suitable for the hardware. Now, whether a "Touch-Pad" and a "Smart-Pad" are the same or physically different things I don't know. My device ID says it's a Smart Pad, so that may be why this driver isn't installing.

OK, I'm willing to carry on and do anything you (and the others who have kindly helped with this) think is necessary, up to, but not including, installing a complete new copy of Windows XP! If I'm going to be installing any operating systems, it won't be XP again I'm afraid. I'm sorry I just don't believe that even after doing that, the behaviour will be any different. There is no fundamental OS compatibility problem as far as I can see, and my system is as clear of any previous mouse driver remnants as it can be as far as I can tell. I'm surprised to hear you say that I've only done about a third of what has been suggested. What have I missed, apart from installing a new copy of the operating system, which I've always said that I don't want to do? Do you think that the version 10.5.2.0 of the driver is the one to use, which we were using before, rather than any of the earlier ones? It is the latest 32 bit one that I've found for XP, all the 11.x versions seem to be incompatible with XP.

Thanks @jaclaz, but I have done all this, several times! There is no error in Device Manager, the device shows as being installed and "working properly" with almost all the drivers I've tried. It appears, I assume correctly, as an "Elan PS/2 Port Smart-Pad", which is what it is. All the driver files are present and correct when checked under the Driver Details" button, including ETD.sys. The problem isn't that the driver isn't installing, it's that the driver's control panel doesn't seem to be able to communicate with the hardware, so it's impossible to change any settings, even by directly editing them in the registry. Nothing "sticks", it just reverts back to what it was before. The Elan tab on the Mouse Properties shows a device, which is "Standard PS/2 Mouse", on the PS/2 port, and it is enabled. However, it should surely be showing that it's a "Elan PS/2 Port Smart-Pad" or something very similar. As it's not recognising it as such, it's not offering any settings as as it presumably thinks that it's a device which doesn't support them. No amount of editing the installation INF files seems to change that behaviour, with any of the drivers. Where it's getting the string "Standard PS/2 Mouse" from is a bit of a mystery, as that string does not appear anywhere in the registry, or in any of the INF files in the INF folder.

Hi again. I spent a long time yesterday trying other drivers. Version 7 (7.0.6.4) seemed to be the best bet as it's a much simpler installation, without all those video files for the Elan control panel. That version has what I assume is a much simpler control panel, which does work although it only shows the button options, which don't actually work. It appears to write all its registry entries correctly, although the settings entries seem to be with the service entries on this version (HKLM\System\CurrentControlSet\Services\Elantech\SmartPad), not under the HKCU\Software\Elantech\SmartPad key. Sorry to say that I am really starting to lose enthusiasm for this now. I actually believe that the touchpad has been designed only to work with the Asus software, which cannot be made to work on XP. Even if by some remote chance a workaround was found (I only want to disable "tap to click", I couldn't care less about anything else!) there is still the graphics driver issue as well. That entry in the Elan tab on the mouse properties, where it's always identified just as a "Standard PS/2 Mouse" rather than as an Elan touchpad, is the killer I think. The driver doesn't know what it is, and therefore can't talk to it. No amount of editing of the INF files seems to ever change that with any driver. It either says that, or there is no device displayed at all. I'm sorry, but I really don't think that this would be any different on a new installation of XP, because it's not actually a problem with the operating system, it's a problem with the hardware. The fact that the drivers don't work on Windows 8.1 either, in fact doing exactly the same thing as they do on XP, would seem to prove this to me. This is probably heresy, but what I'm thinking of doing now is to "upgrade" the XP installation to Vista. That should do an update without me having to reinstall everything, unlike a Windows 7 update. Having looked in the files for Asus Smart Gesture with CFF Explorer, it does look as if it will run OK on Vista, and I'm hopeful of finding a compatible graphics driver too. Sorry to be defeatist after all the help I've been given.

Sounds like the same issue I had a week or so ago using Yahoo's e-mail system. I suddenly found I couldn't send with Eudora, although I could receive OK. Windows Live Mail 2009 wouldn't work either. I didn't try Outlook Express but I'm sure it would have failed as well. It appeared that the SMTP server had stopped accepting TLSv1 logins, and the clients concerned could not use anything higher. I fixed it with a Hermes Mail update to Eudora, which adds TLSv1.2 capability to it. Someone later reported that it was working again for him on Outlook Express, and I then confirmed that by sending from Windows Live Mail, so it might have been just a temporary glitch, but it was failing to send for several days! Even if this wasn't permanent, I'm sure ISPs will stop accepting old protocols eventually.

I tried an experiment seeing if I could update the mouse driver in Device Manager. I pointed it at the INF file in the folder where the driver files were unpacked, and something very odd happened! I wasn't offered any choice of drivers, it immediately installed something called "Finger Sensing Pad", by a company called Sentelic. This has installed another folder in Program Files called "FSP", containing a lot of dll files and a program called "FspUip.exe" which appears to be the control panel. If I run it, no window appears. The program runs for about five seconds in Task Manager, and then closes. I am at a complete loss to see where this program has come from, there is no mention of it in the INF file we've been working with, it doesn't seem to be referenced in any of the other files in the installation folder either! The Elan tab is still there in the mouse properties, but there is now no device listed. EDIT: OK, I found where it came from, there were two INF files in my INF folder with two different versions of this software. I thought if you asked the system to look for a driver in a particular folder that was the only place it would look, but it seems it looked in the whole INF folder too! I have no idea why those files were there, but they're not there any more!

Neither of the INF mods seemed to make any difference. DriverView shows ETD.sys loaded and apparently OK. Incidentally, ETDCtrl.exe is running from boot, from the registry "run" key. I guess that's normal behaviour. Attached is the INF file from the Asus driver on Windows 8.1, in case it provides any clues. AsusSmartGesture8.1.inf

OK, I will try the INF mod and report back. The Regmon log is attached. I'm not sure why the entries for RapportMgmtServ are there at the bottom, it was supposed to be filtered to only show the ETDCtrl.exe entries. Regmon.log

I didn't think that registry permissions were an issue with XP? The Dell control panel is certainly accessing the registry, and actually appears as ETDCtrl.exe, which would bear out that it's just a Dell "skinned" version of the Elan control panel. It's doing a lot of "QueryValue" entries, but not "SetValue" entries, except on the "SmartPadDisplay" key, nothing on the "SmartPad" key. I'm still thinking that the device entry on the "Elan" tab on the mouse control applet should say something other than "Standard PS/2 Mouse". Surely it should say "Elan Smart Pad" or something like that. I can't help but think that the driver still isn't working because it's misidentifying the hardware.

I tried that Dell driver, with pretty much the same result as with the others. The Dell control panel appears to work, but changing any settings on it does not "stick", when I go back to the page again the settings have reverted. It doesn't seem to be changing the relevant registry settings.

@win32 Yes, that is a pity, but thanks very much for the suggestions, this is teaching me something new every day! I may re-visit the option of trying to get just the driver and settings part of Smart Gesture working, ignoring the control panel, but I'll try the driver that @jaclaz mentions first. I'm beginning to think that we will never find a driver that just works as it is, but I haven't quite given up all hope yet! Cheers, Dave.

OK, I made the same change on AsusTPApi.dll. The error is now that FlsFree can't be found in KERNEL33.DLL. I guess that function isn't in the xompie version either?

Thanks, I made that change, and the same change on "Import Directory" on AsusTPConfigure.exe, but I'm still getting the same error about "LCMapStringEx" when I try to run it.

I assume this is the file called "kernelxp.dll"? I've renamed it to "kernel33.dll" and put it in the system32 folder. Opening dwmapi.dll in CFF Explorer, I can see something called "Import Directory" and something called "Import Adder", but no "Import Table".

With that dwmapi.dll now I'm getting "The procedure entry point LCMapStringEx could not be located in the dynamic link library KERNEL32.DLL". That looks much more like the sort of message I'd expect, but doesn't look too optimistic!

Thanks, I will give that version a try!

Ah, right! They were set to "0006" and "0000" originally, Vista of course, which looks hopeful that the program will work on Windows 7 if I end up having to go down that route. Now I've changed them both, I'm getting a different error message - "The application failed to start because dwmapi.dll was not found. Re-installing the application may fix this problem." That file does not exist on the XP drive, but does exist on the 8.1 drive in \System32. Copied that across and the message is now "The procedure entry point -CxxFrameHandler3 could not be located in the dynamic link library msvcrt.dll". Looking at the Asus file in standalone Dependency Walker there are quite a few error reported, as you would imagine. Shall I send you a copy of the file to analyse yourself? If it's possible for that file to be made to work without errors, I think there's a fair chance that the rest can be. It is part of the control panel though, so would it perhaps be better to concentrate on the actual driver files? I really couldn't care if the control panel doesn't work, the important thing is that I can change the settings and they work, even if I have to do it in the registry!

OK, with some more registry transplants from 8.1 I now have an icon for the Smart Gesture control panel in the Windows Control Panel. That runs AsusTPConfigure.exe, which reports as not a valid win32 application. Started on that with CFF Explorer VII (the version I already had, I hope that's OK) and I have changed the MajorOperatingSystemVersion value in the "Optional Header" section to "0005", and the MinorOperatingSystemVersion value to "0001". It hasn't made any difference, is that all I should need to do? The Dependency Walker section doesn't seem to show any errors. I notice it was built with Microsoft Visual C++ 8. Is that an issue?

OK, I'll do that and report back! It may be a while as I've got to go off and do some other stuff now.

Oops, our posts crossed! That driver is just AsusTP.sys as far as I can see, no settings panel or anything. As I seem to be using AsusTP.sys already, is there any reason to try a different one?