jaclaz

Yep. (if it installs on 8.1) but you mentioned before that you wanted to boot also Win7 on this notebook, or do I remember wrong? And the change is now recorded/shown by ETDDeviceInformation.exe? Yet the touchpad behaves as before? jaclaz

READ (already posted): https://superuser.com/questions/877664/how-do-i-make-my-asus-touchpad-behave-in-a-reasonable-way jaclaz

According to the text file, the DATA IN THE REGISTRY is 1/C8. What IS THE ACTUAL data in the Registry? 1/C8 or 0/D0? It seems like the ETDDeviceInformation.exe agter change and reboot reads the "new" info (0/D0) in the "Driver Information" BUT *something* resets it in the Registry, hence the same exported file shows the Registry path as having (again) 1/C8 (otherwise where the 1/C8 comes from in the section "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Elantech\SmartPad" of the .txt? jaclaz

I don't understand. In the file you posted "afterchangeafterreboot": Anyway, if the settings do not affect the behaviour of the touchpad, there must be *something* else going on. jaclaz

So the actual values you change in Registry are actually (after a reboot) updated on the ETDDeviceInformation.exe view under Driver Information, BUT they are reverted to 0x00000001 and 0x000000C8 in the Registry? Another reason to use Regmon or similar to understand what changes what. What happens running the .cpl? (extracted/copied manually from the driver package) jaclaz

BUT does the ETDDeviceInformation.exe see the change? Try also changing the C8 (presumably 200 milliseconds) to - say - D0 (208 millisecond). Are these changes reflected in ETDDeviceInformation.exe or not? And what happens after a reboot? jaclaz

Good. It seems like a lot of info. Try only changing the those should correspond to: jaclaz

Well, this specific version of the driver is on the Lenovo site described as 7 AND XP and I checked a couple files they have 5.0 or 5.1 as Major/Minor OS version. I also tried running (on my XP SP2) the "ETDDeviceInformation.exe" and it runs just fine (of course doing nothing), "EDTmag.exe" runs and works just fine, etc. As well the .cpl runs just fine (itr is all empty as it is not installed, and there is no hardware connected, of course). jaclaz

Check the ETD.inf of the lenovo driver: You could try removing the ";" and reinstall the driver. jaclaz

Yep. But there could be other explanations: 1) the (stupid) option tab/panel may be able to "refresh on the fly" the settings whilst without it you would need to disable/reenable driver (or reboot) and/or it is capable of only modifying a key if it already exists but the key does not exist for *whatever* glitch in hardware ID or .inf 2) the current driver you have (which works for the touchpad, at least partially) may use another path in the Registry (i.e. maybe as you say it isn't a "Smartpad" that you have currently installed) I would try, on the current driver, using regmon (I personally still prefer the old version - separated filemon and regmon to the newer all in one procmon) to see if clicking in the options panel/tab attempts to access the Registry and if yes to which path. jaclaz

Thanks. that is much better. About amber, I did have (in the good ol' days) a Toshiba T3100 and I have to say that the amber (plasma) screen together with the (very sharp) Toshiba OEM font made it a very, very readable device. For *some* reasons most of the images you can find of it nowadays don't make justice, they all seem a little out of focus and/or the background is too much lighted up/invasive, in reality it had a very good contrast/clearness. Ahh, the good ol' times, when a byte was a byte and a very good text processor/edtor was q (Qedit by Semware, 46,160 bytes of sheer editing power): https://www.pcorner.com/list/WORDP/QEDIT215.ZIP/INFO/ jaclaz

@Dave-H Yep, it is strange that the original driver, missing the hardware ID, installs nonetheless, maybe there is some "comparibility hardware" setting that acts as a sort of "catch all". However, quoting myself: Let us assume that: 1) you have the described Registry structure 2) that what the (not working) options tab does is in a nutshell: a. change some settings in the Registry path b. make the driver re-read the (changed) settings What happens if you change a setting in the Registry and EITHER: 1) disable and re-enable the driver OR: 2) reboot ? jaclaz

Bummer! Which driver (sort of) worked ? Link please. jaclaz

Crap! Driver could be this one (to be tested): http://dl.driverpack.io/driverpacks/repack/Touchpad_Elan/Elan/Allx86/Asus_nb/11.5.21.6/Elan-Allx86-Asus_nb-11.5.21.6-drp.zip Can you confirm that you tried this (and that it doesn't work at all)? jaclaz P.S.: Also check the following path in Registry: HKEY_CURRENT_USER\Software\Elantech\SmartPad https://superuser.com/questions/877664/how-do-i-make-my-asus-touchpad-behave-in-a-reasonable-way

Look, it was you that reported that right after install you can change resolution of the driver without BSOD's. Installing only the driver (bar the stupid Catalyst bloat around it) should be a matter of seconds. Anyway, instead of installing it automatically at each boot, it could be a batch file, so you normally boot with the VGASAVE (and have slower refresh) and only when you really *need* the better driver you install it. You are now introducing another approach, disabling it and re-enabling it, but it seems to me rather obvious that if you disable it when at 640x480 it will re-enable at that resolution, unless you disable it when working fine (just after install) at 1366x768 and when it restarts it defaults back to 640x480? jaclaz

Yep, the idea (to be tested) being: 0) install the driver 1) (re-)boot with /basevideo (VGASAVE) 2) automatically (login script or similar automatic start) uninstall and reinstall the driver (and set the right resolution) 3) loop to #1 jaclaz

Yep, they are two separate approaches. 1) be happy with the VGASAVE set at 1366x768 even if a bit slow (but again it is only a secondary OS, so it should be bearable) 2) try experimenting with the (crappy) ATI/AMD driver, I don't know, but maybe if you set it to a "standard" resolution (like - say - 800x600) it may actually boot without BSOD and then (if any of the tools work) you can change the resolution after boot (if it won't BSOD then). As a side note, there are chances that the current issues are with the "whole" Catalyst package, whilst "only" the driver maybe works. In the meantime I found a report (Russian, use Google translate) http://gallery.ru-board.com/topic.cgi?forum=81&active=11&topic=5327&start=720 which is very similar to your experience, BUT - maybe - if the driver works at "first install", we can find a way to install it at boot and uninstall it at shutdown? jaclaz

Can't you go back in time to this point? If you can have 1366x768, the VGASAVE with acceleration level 5 should be bearable, as a secondary OS. Try also: http://qres.sourceforge.net/ https://www.nirsoft.net/utils/multi_monitor_tool.html or NIRCMD setdisplay: https://nircmd.nirsoft.net/setdisplay.html jaclaz

Naah, they were on ATI/AMD site allright: http://web.archive.org/web/20150525015957/http://www2.ati.com/drivers/windows-xp-amd-catalyst-9.00.300.3005-dec9.exe jaclaz

Only to let you know how dinosaurs simply love green text on black background BUT they cannot see blue on black. jaclaz

No you cannot! That's the WHOLE point of taking sides . What you are experiencing is not entirely unlike having an alien parasite (symbiote/klyntar) taking possession of your body (and mind). (minus the increased strength and mental and healing powers) They are creepy, slimy and very, very dangerous, see: https://en.wikipedia.org/wiki/Symbiote_(comics) jaclaz

If it is a dual core, then those APU's are maybe right, leave 'em alone. I still have some doubt on motherbaord resources, but leave 'em alone. I would try deleting the monitors and see what happens. jaclaz

Whenever I see duplicated items in device manager I suspect that there is some cleaning to be done. You surely don't have three monitors, and I doubt you have two "Motherboard resources" and two "AMD A4-1200 APU. etc." jaclaz

Latest should be this one: https://ftp.webtent.net/pub/windows/Make_PE3_48.exe jaclaz

I doubt it. It is more likely that it is the file ati2dvag.dll jaclaz