Dave-H

Now I've got a bit of a problem! I tried installing 10.5.2.0 on XP using the INF file from 15.14.4.1, just to see what happened. The same thing happened, it looked as if it installed but nothing changed, even after a reboot. Then I did the same as I did on 8.1 and tried installing through Device Manager. I was offered the Elan Input Device driver, and it installed as it had done on 8.1, after the compatibility warning. I rebooted, and the keyboard had completely stopped working! So now I'm completely stuck, as I can't put my password in, even in Safe Mode, so I can't get into Windows XP at all! Any suggestions gratefully received!

OK, I will reinstall it and try that. However, I have had a major breakthrough with Windows 8.1, I've finally found an Elan driver that works with it! It's version 15.14.4.1, the latest version I've ever tried. It didn't install at all (although it said that it had) when I tried it normally, but forcing an install in Device Manager from the INF file actually worked, despite a warning from the driver that it wasn't designed for my hardware! The mouse is now an "Elan Input Touchpad". There is no control panel icon in the Windows Control Panel, but it can be accessed from the "Elan" tab on the Mouse Properties. The device is shown there as an "Elan Smart-Pad", which proves that the "Standard PS/2 Mouse" shown in the same place in XP means that the device had not been identified correctly. At least now I have an equivalent working driver in 8.1 to compare with what's happening in XP. Sadly there is of course no chance in hell of that driver actually working in XP.

Thanks. I had already tried transplanting the whole Smart Gesture installation from 8.1 to XP, but it didn't work. I'll give this a try though, you never know! Update: OK, it installed fine as usual, but the touchpad is dead. Device Manager now says it's an "Asus Touchpad" but it's showing error 39 "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing." So, I guess AsusTP.sys won't work on XP. Its parameters in CFF Explorer are 6/2, 6/2, 6/1, so if that is to be believed it won't work on anything less than Windows 8. I can try editing them, but I very much doubt if it will make any difference. This is pretty much what I got when I tried it before.

I wouldn't worry about being given loads of faulty updates by Microsoft Update, you should only be offered the one with the latest MSO.DLL in it (KB4484126). That is faulty, the one you will have to find manually on the Update Catalogue and install manually is KB4092483, which contains the last working MSO.DLL for XP, version 14.0.7214.5000. In fact, if you can unpack it, you only need to substitute the MSO.DLL file from it in Program Files\Common Files\Microsoft Shared\Office14. If you do that, any other files that were in KB4484126 will be preserved.

Thanks! Yes, when I saw there was 11 updates for Office 2010 on Windows 10 this month I had a nasty feeling that there would be a bad one in there for XP! First time since the end of last summer though, so not too bad. I just replaced the "bad" MSO.DLL with the last working one (14.0.7214.5000) and all is well again.

That's already been tried, the drivers don't work on Windows 8.1 either. They perform exactly the same as they do on XP, the touchpad works, but there is no way to change its settings. I'm still convinced that the problem is not related to the operating system, it's related to the hardware. There just doesn't seem to be an Elan driver that works with this hardware, the only driver that does is the Asus Smart Gesture one, which cannot be made to work on XP. The latest Elan drivers may well work with it too of course, but they won't work on XP either.

Sorry, yes in that respect most of the drivers I've tried do "sort of work", in that the touchpad still functions, just as it does with the generic MS mouse driver. There are some drivers, including earlier ones I've tried recently, where it doesn't work at all, and the touchpad is dead, but it's OK with the later ones. What has never worked on this system, and is the real problem, is changing the settings of the touchpad. If I can't do that, I might as well use the generic MS PS/2 mouse driver, but I really do need to do that!

No, I haven't found any driver that works on XP with the present touchpad, with or without modding, that's the problem! The Asus Smart Gesture program works fine on Windows 8.1, but is not XP compatible.

There is no Elan driver on 8.1, only the Asus Smart Gesture program. I uninstalled the Elan driver which had been on 8.1 when I saw that it wasn't working any more (if you remember I just put the drive from the old machine into the new one). With 8.2.0.35 the result is pretty much as before, except that the Elan control panel shows no settings at all now. If I try to use the Dell control panel, the first thing is does is to swap the buttons over on the USB mouse, which really threw me until I worked out what was happening! It's one of its settings which comes up the wrong way around, and cannot be saved the other way around. It has always worked for some mouse functions, like button swapping (only on the mouse, not the touchpad) and pointer speed. None of the touchpad specific settings do anything though.

I uninstalled the driver and cleaned the system and am now back to the generic MS mouse driver. Something occurred to me which really should have before now! My previous netbook also had an Elan touchpad, and I still have the driver that I used then, which is version 8.0.5.2. Unpacking that and looking at its ETD.sys, which is version 8.2.0.35, and looking at it with CFF Explorer it shows 6/1, 6/1, 6/0. Now that driver worked perfectly on Windows 8.1 and Windows XP, with the hardware in the old netbook, an Asus 1025CE. So, at least that version of ETD.sys must have been capable of working with XP, whatever CFF Explorer says. I will give it a try again, but I suspect that it won't work with this hardware, even if I modify the INF.

After putting the ETD.sys parameter back to the normal "0006" on the copy in the Drivers folder, disabling/re-enabling the device did not make it functional again, but the error was now 10, "Device cannot start". Uninstalling it in Device Manager and re-scanning then produced an "Unknown Device". Manually reinstalling the driver in Device Manager and rebooting as instructed produced a dead touchpad again. I checked the ETD.sys file in the Drivers folder, and it still had MajorSubsystemVersion set to 0005, so I guessed it must have reinstalled the changed version from the installation folder. I then changed the version in the installation folder back, and tried again, and still ended up with a dead touchpad, so I guess it's still picking up the modified ETD.sys from somewhere. I will try a complete uninstall and reinstall and see if that produces some semblance of life again.

@jaclaz Running the Dell control panel with 7.0.5.5 installed still doesn't save any settings, I can change them but when I re-run the program they have gone back to as before. Interestingly, the "tap to click" function seems to be fixed at "off" now, it was fixed "on" with the other drivers. The "Device Select" screen is fixed at "disable", which does appear to be correct at the moment! Manually changed registry entries don't "stick" after a reboot. I reinstalled 10.5.2.0 (with ETD.sys 10.0.0.20) after doing the CFF Explore modification. The touchpad is now dead with that version, and I have a code 39 error in Device Manager, "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing."

Oops, sorry I misread your post! I haven't manually installed anything to support the touchscreen, but it does seem to be working OK in 8.1, but not in XP. I will have a look at that folder on the CD, but not until after I've got as far as I can with the touchpad and graphics. I may still end up going to Vista! My full Windows Defender scan on 8.1 took about 8 hours BTW, it didn't find anything, and annoyingly hasn't actually registered has having taken place, the program still says that my last scan was on March 29th, and it's still telling me I need to run a scan!

Windows 8.1 is using the "Asus Smart Gesture" program, which works fine, although it took me ages to find a 32 bit version of it! I assumed it included a driver, but maybe it's just a control panel. As you've seen I'm sure, the machine is actually a 64 bit machine, although I'm running 32 bit operating systems on it. You're right that there seem to be hardly any drivers on the Asus site for the machine, in fact selecting any OS for me brings up nothing on the first page. Whether that is correct or a fault I don't know. I got the 8.1 drivers from here - http://freedriver.org/drivers/notebook.php?n_firm=Asus&n_model=X102BA I also found XP compatible drivers for the audio, wi-fi, and Ethernet, just the graphics and touchpad are eluding me so far! I do have the last BIOS installed, version 219. It was already on the machine when I got it. @jaclaz I'm doing a full Windows Defender scan on Windows 8.1 at the moment, which is taking forever (6 hours and counting!) I'll get back on the touchpad driver investigations tomorrow.

It does indeed have a touch screen, which is the right resolution for Windows 8.1 apps, unlike my previous netbook (designed for Windows 7), which only had a 1024x600 screen. That's the reason I bought it, but I'm now starting to have regrets! Quite apart from the physically inferior touchpad, the fact that it's AMD based and not Intel based has caused a lot of driver problems, although the touchpad and the graphics are the only ones I haven't yet found for XP. When I bought it, it had been "upgraded" from Windows 8 (which it was designed for) to Windows 10, presumably by its previous owner, but it was crawlingly slow. It has 4GB of (non-expandable) memory, but the processor is only single core 1 GHz, unlike its predecessor, which was a dual core 1.6 GHz Intel Atom, so that's another area where the hardware is actually inferior to the previous machine. Not surprisingly, the touch screen doesn't work on XP! Whether it can be made to I don't know.

It certainly is a terrible mess. Trawling around looking for drivers I've found many forum posts complaining about Elan drivers, with many people really wishing that their machines had Synaptics touchpads instead! Apparently Synaptics drivers are much better. Anyway, I tried version 7.0.5.5, with interesting results. I didn't modify the INF file at all (which is very bare in the device list section compared with the others) and the driver installed OK, but the touchpad is completely dead! It appears in Device Manager as an "Elan PS/2 Port Input Device", and says it's working properly (which it obviously isn't!) Interestingly, the tab in the Mouse Properties is now labelled "Elan Smart-Pad" rather than just "Elan" as with the other drivers. The Elan control panel still only shows the mouse button settings, but unlike with the other driver versions they can now be changed and are actually remembered, which they weren't before.

Sorry I'm afraid I can't help with this, as I said it's not an issue for me as I don't use DM on Instagram. I can only think that perhaps "div.Igw0E" is being also used in the DM code and that is causing the problem. Perhaps @mixit has a suggestion?

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.