Dave-H

I'll let you know!

Update. I went to Device Manager and it said that the graphics driver was disabled. I enabled it, and it appeared to enable fine and said it was working properly. The refresh rate was still very poor though, so I went to the Display Properties and it was set to a very low resolution and colour depth (even though the display resolution and depth actually looked fine!) I then set it to the settings I wanted, and it tried to set them, but then the BSOD came back "The device driver got stuck in an infinite loop" 0x000000EA.

OK, sorry for the delay. I did a complete ISO backup of the machine, and then tried installing ATI3005. It appeared to install absolutely fine, but as expected, it doesn't work. When I boot up, I get a message saying "No AMD graphics driver is installed, or the AMD driver is not functioning. Please install the AMD driver appropriate for your AMD hardware". Rather strange considering that the installer recognised the HD8180 absolutely fine, and apparently installed the driver with no errors! I had to install the whole thing unfortunately, just running CX178340.msi gives the message "This package requires AMD Catalyst Install Manager to install. Would you like to launch AMD Catalyst Install Manager to install this package?" So like a good boy, I did!

Agreed on the naming! I will try installing ATI3005 and report back.

What a mess!

Well I did have my doubts about the Vista compatibility of that driver! I guess the only way to know is to try and install it on a Vista machine. I guess the install will fail at a very early stage if it isn't compatible. Anyone with a Vista installation brave enough to try?! I was only hoping that, as with the touchpad driver, it might be possible to combine elements from two different drivers. Of course the fundamental difference is that there were official XP drivers for Elan touchpads, but there were never any XP drivers for the HD8180 graphics hardware.

Let's hope they haven't broken anything more for XP users!

Thanks, that's a lot more sensible! FWIW, here is the driver I found which (despite the file name) is supposedly Vista compatible, and contains my hardware ID. It's the only apparently Vista compatible one which had the ID I could find, all the rest are Windows 7 or later. I downloaded it in case i did decide to switch from XP to Vista on the notebook but of course I've never tested it. https://www.amd-drivers.com/download-RadeonHD8180-mobility-driver-for-WindowsVista-32bit.html It takes forever to download BTW! Maybe Doctor Frankenstein could use it along with the XP one..........

Two more today, KB4484382 (Outlook) and KB4484458 (Word). All OK!

This is the one, claims to be an XP compatible version of Catalyst 14.4. AFAIK it's the last version of any ATI Catalyst software that's XP compatible. https://download.cnet.com/ATI-Catalyst-Software-Suite-Windows-XP-32-bit/3000-2108_4-10159621.html After adding my hardware ID to the INF, this appears to install fine, but it BSODs on reboot.

Yes, that's the machine! cdob said it was a Kabini right back at the end of March, but I'm not sure what he based that on. The driver we came closest with was the Catalyst 14.4 package, which seems to be the very last version that's compatible with XP. I'll have to see if I can find where I downloaded it from, it's so long ago! Its INF file has entries up to and including Kabini PCI\VEN_1002&DEV9838. My hardware is of course PCI\VEN_1002&DEV9839! The INF has no mention of "Temash".

@jaclaz So, are you prepared to take up this fight again now?! We seemed to be so close, just the wretched BSOD which we never resolved, if indeed it is possible to do so. Is it worth exploring any other options, if there are any? Cheers, Dave.

OK, here's a new version with the ETDDeviceInformation shortcut description amended. I also took the opportunity to add a Start Menu shortcut for ETDAniconf.exe, so there are now three ways of launching it, from that shortcut, from the Windows Control Panel icon, and by double clicking the system tray icon! http://s000.tinyupload.com/?file_id=52037400405643044948

Thanks to a suggestion from dencorso, I've uploaded it here, at least as a temporary solution. http://s000.tinyupload.com/?file_id=16043508572974155299 Do check it out and make sure that it's OK for you. Do you want to leave the description on the ETDDeviceInformation.exe shortcut as it is?!

I've done my first packaging effort. Unfortunately it's 11.5MB and I can't attach it here!

Thanks, I did know that, in fact I was in PM conversation with dencorso about it a week or two ago, but it's hardly as convenient as having numbering which is clearly visible on each post, as almost every other forum I use has!

OK, I will get to this later today. I will start a new thread for the "final result", with a link to this "experimentation" thread, if that's the usual convention here. Then I'll have to ask dencorso to split off the earlier posts relating to the graphics hardware into a separate thread for that. This is not made any easier by this forum's annoying lack of post numbering!

Thanks @jaclaz, sorry for the delay in replying, I changed the motherboard in my computer yesterday, which took quite some time! Yes, that explanatory note looks fine, so shall I package up what I think a future potential user will need to use this driver in the future? I will of course send the final result to you for checking over. Cheers, Dave.

LOL! I would agree leave the ;# REMmed lines in the INF. The file is already a huge amount smaller than the original, and I can't see any harm in leaving them there so any future experimenter can see what used to be included. I think if the batch files are included there should be some sort of readme file with them to explain how to use them and why you might want to.

OK, so if we can't get the magnifier to be invoked directly from the touchpad, if we have a shortcut to invoke it, do we now need anything else?

The Start Menu items addition and removal routine now works perfectly! I re-enabled the "cover" function, but it doesn't appear in ETDAniconf.exe and even when set to "1" it doesn't seem to do anything. I'm not quite sure how "covering" the touchpad actually works anyway, if I put my palm down on it the icon graphic just shows a four finger click. Maybe it works with different hardware, but not this hardware.

Well I still can't get it to work! Perhaps it needs multi-finger tapping enabled or something. I'm doing exactly what's shown in the video, but nothing happens. The actions are showing correctly on the system tray icon. The Start Menu items adding routine works fine, although IMO it would be better to have the two items in an "Elantech" menu item at the top level rather than in the Accessories folder. I think that if they're put there people won't even notice that they've been added, whereas if something has been added at the top level they will. They can always move them if they don't like them there, I do that all the time after I've installed something new. The removal routine doesn't work, as you feared. I tried tinkering with it, but no joy. It looks a bit vague on the MS page as to whether there should be a space between the comma and the 0x00000002. I tried both ways, but no difference.

Thanks, I will experiment with that! I still think it's strange that it seems to be impossible to invoke the magnifier from the control panel. The magnifier follows the magnification amount and area size settings on the control panel fine, but I still can't mange to actually launch it from the touchpad!

OK I restored the items in the "Click" section in the new INF to match your list, and all seems to be well. The only thing I would still like to have a go at is to put the necessary information into the INF file to add Windows Start Menu entries for ETDMag.exe and ETDDeviceInformation.exe. I looked into doing that, but had a lot of trouble getting my head around the syntax involved!

I went back to the original INF you modified and changed ClickPad_LeftCorner_Click_Enable and ClickPad_RightCorner_Click_Enable to "1". Also ClickPad_LeftCorner_Click_ShowItem and Also ClickPad_RightCorner_Click_ShowItem to "1". Uninstalled and reinstalled, and that seems to have fixed the "buttons" not working. I thought the "ShowItem" options being enabled would show the option in the control panel, but it doesn't seem to. Perhaps that has to be done elsewhere, but it's probably not necessary anyway. After all, why would you want to disable the buttons?! The Corner Tap Zone option still looks very unstable, with the corners flickering and the position indicator arrows round the edge jumping all over the place when the cursor is moved by the touchpad. I don't remember it being like that before, so I will try another install with the original INF to see if it's any better with that.