jaclaz

Traditionally, when something of possible general use comes out as the result of a looong thread, a new thread is made for the "release" and the "working thread" is kept separate as "history". This way, if new issues, questions, etc. come out it is easier to understand the context and to not get confused by pages over pages of temporary files, tests, side issues, failed attempts, etc., whilst what happened is still kept accessible in case of need. In this case it would be even worse as this thread started only for the graphic card issue. And since Dencorso offered to have the driver hosted directly here, it would be much better, bar your (nice BTW ) idea about Archive.org, commonly used hosting sites tend to have issues before or later, and more often than not files hosted externally tend to go poof over time. jaclaz

Yep , you were maybe a tad bit too optimistic, I don't think you would need a 32 bit number to count people that use a Spreadtrum Phone on a nlited XP. Seriously with nlite you can (that is the idea) make big holes in an XP install, so your suspect may be correct. Which EXACT (there are 4 files on that page) driver(s) did you download and install? What do you have in SetupAPI.log? (though more often than not error/warnings in it are not accurate, sometimes they offer a hint at what is happening). If there is nothing of interest there, then your next attempt should be to trace the install. jaclaz P.S. Try also the UMDF drivers, some people reported that WMP11 alone wasn't good ( or good enough) on some machines/installs: https://forum.xda-developers.com/galaxy-s3/help/windows-xp-install-usb-drivers-t1874508/page2

I guess we will never know for sure. Actually it is officially designed for XP and later, and may partially work on Windows 2000: https://web.archive.org/web/20080916191023/http://www.nvda-project.org/documentation/nvda_0.6p2_userGuide.html#2 What about Fire-Vox/MLFire-Vox? http://firevox.clcworld.net/ It is an abandoned project: https://web.archive.org/web/20120301224425/http://visilab.unime.it/~filippo/MLFireVox/MLFireVox.htm But was seemingly continued in Click/Speak: http://clickspeak.clcworld.net/features.html NO idea if it can be made to work on pre-XP and with Retrozilla. jaclaz

Yep, maybe it is better to put the batches and the howto in a .zip within the driver .zip, so that they remain "grouped" until (if) they are used, ot they could be also a separate attachment. If you think that the how to is OK you can start a new thread with a minimum of background/history and the actual files attached, you will probably need to contact Dencorso for attachment size limits you may encounter. There is very little I can check, besided the list of needed files (that we already checked) and their versions (should you have misplaced anything) as the only "real" test/check is whether it works (and only you can test it at the moment), jaclaz

I don't get it. How are extended support dates related? From the links I posted, version 2.0 is 98 onwards, but earlier versions are Windows 95. So, IF the NVDA requires 2.0 OR IF a suitable earlier than 2.0 version is not found THEN it won't work OTHERWISE it may. Most probably this is last version working with 95: http://physics.fme.vutbr.cz/sea/download/ http://physics.fme.vutbr.cz/sea/download/win9x/msaardk.exe jaclaz

Ah well, not knowing what you attempted not the actual error(s) you get, nor the actual hardware involved, it will be a bit hard to provide you with any detailed assistance. You will need to provide some more exact report. AFAICR the "more complete" MTP drivers shipped with MediaPlayer 11. Generally speaking a VID/PID addition might be needed to the .inf for specific hardware: http://www.rimweb.in/forums/topic/36886-do-it-your-self-your-phones-mtp-drivers-for-windows-xp-sp3/ I won't go with the endless "Have tried this?" "Yes, I did and it didn't work" "Ok, and have you tried this other thing?" "Yes but it failed" ... Detail what you have done till now and the exact errors you got, hardware in use, etc., standard litany, please: https://jdebp.eu/FGA/problem-report-standard-litany.html You may also want to check and post relevant contents of the SetupAPI.log: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-logging--windows-server-2003--windows-xp--and-windows-2000- jaclaz

This one confirms that MSAA came with Windows 95. https://docs.microsoft.com/en-us/windows/win32/accessibility/accessibility-legacy BUT this one places it (maybe the current downloadable version?) on Windows 98: https://docs.microsoft.com/en-us/windows/win32/winauto/microsoft-active-accessibility or maybe it works but it is not anymore supported (or it was not anymore supported at the time the page was written) It seems like up to 1.3 was Windows 95 and starting from 2.0 it is later OS: https://books.google.it/books?id=cf0Hh3soHVUC&pg=PA258&lpg=PA258&dq=msaa+"windows+95"+version+1&source=bl&ots=dRpaAWuLHU&sig=ACfU3U3lHEXYXs4h8tjn9UXMVYwiUJzlUQ&hl=en&sa=X&ved=2ahUKEwiGjeDh3L3qAhWKDxQKHWMwC5MQ6AEwAXoECAcQAQ#v=onepage&q=msaa "windows 95" version 1&f=false https://web.archive.org/web/19991129040953/http://www.microsoft.com/enable/msaa/download.htm It has to be seen if the earlier copy of msaardk.exe is the right one: https://web.archive.org/web/20000819044325/http://www.microsoft.com/enable/download/msaa/msaardk.exe jaclaz

A Quick How To will suffice. jaclaz howtobatches.txt

I would say that everything is ready for "release", what has to be decided is whether to leave the ;# REMmed lines and section or remove them alltogether. (I would leave them, as they might be useful to someone with different hardware and willing to do experiments. As well, it is to be decided if the 6 (please read as 7 ) small batches are to be included or not. Naaah, a parrot happily jumping around will suffice . jaclaz

Sure, when Yzöwl writes something, it works. Yep , it was just something to try, I don't think anyone will miss the function , but it is logically very similar to the 4 finger, so whether it works or not (and/or it "confuses" it with a 4 finger click/tap) may also depend on some other setting, *like* Palm, STV (sensibility) or - still say - it needs to have Four Finger Move Function disabled. Until I found the flash video I never thought that "Cover" was a gesture, I thought that it was something connected with "lid" , and the default action was something like a "privacy" action of sorts, you close the lid (cover) all windows minimize showing the desktop and when you re-open it there is no risk that any sensible data is on screen. jaclaz

Some news (pretty much unuseful, but still news). I have definite proof that the good guys at Elantech use a couple of dice, a random number generator and possibly also the I-Ching to number/name things. The flash video/demo I posted a link to earlier: http://192.72.220.42/eng/tpn_sp_fun.asp http://192.72.220.42/eng/smartPad_demo/index.swf is actually (as the name implies) an index/intro video, made to cycle between each of the 9 (nine) separate videos corrsponding to the 9 (nine) items in the roll-up menu at the bottom, that consist in 12 (twelve) flash videos, according to this table (items numbered from left to right): Item Filename Title/Contents ? pa01.swf ?/One Finger gesture Edge Scrolling ? pa02.swf ?/One Finger gesture Edge Motion 1 pa03.swf 2Fingers Tapping/Two Fingers gesture Tapping 5 pa04.swf Magnifying glass/Two Fingers gesture Magnifying glass 2 pa05.swf Rotate/Two Fingers gesture Rotate 3 pa06.swf Zoom in/out/Two Fingers gesture Zoom in/out 4 pa07.swf Scrolling/Two Fingers gesture Scrolling 6 pa08.swf 3fingers Tappng/Three Fingers gesture Tapping 7 pa09.swf Switch Window/Three Fingers gesture Switch Active Window 8 pa10.swf My Computer/Three Fingers gesture Show "My Computer" 9 pa11.swf Swipe/Three Fingers gesture Page Up/Page Down ? pa12.swf ?/Palm Gesture Cover Of the three items with a question mark: http://192.72.220.42/eng/smartPad_demo/pa01.swf http://192.72.220.42/eng/smartPad_demo/pa02.swf http://192.72.220.42/eng/smartPad_demo/pa12.swf last one is actually interesting, even if it doesn't show in ETDAniconf.exe, it may work if enabled, and the corresponding action (currently %RETURN_TO_DESKTOP%) : ; Cover ;#HKLM,"%ServiceRoot%\Elantech\SmartPad",Cover_Enable,%REG_DWORD%,0 ;#HKLM,"%ServiceRoot%\Elantech\SmartPad",Cover_Func,%REG_DWORD%,%RETURN_TO_DESKTOP% may actually be changed to something else jaclaz

Yep, but until we find out how to delete the added .lnk files, creating a folder would only mess it up. Creating the folder should be however straightforward (maybe), something *along the lines of*: [Optional_Elantech_Folder] Name="ELantech", 0x00000004 but of course you are right the given MS page essentially, says: you can do 53 different things with this directive, here is an example on how to do the first one (the simplest and more straightforward one), go figure yourself how exactly the other 52 can be made. We need a couple of .inf examples using this approach (I believe rather uncommon as most programs that install and create shortcut, etc, use a dedicated program installer/uninstaller and not a .inf). I'll see what I can find, but don't hold your breath. About the gesture, no further ideas, did you try with both the two and three fingers settings? The (wrong) textual instructions (which are the same on the Flash video) seem to me like two fingers related more that to three fingers, but you never know. P.S. Just found a nice thread by ricktendo here, probably the subdirectory is created automatically when creating the .link file , and the deletion seems like using a completely different syntax/set of flags , 0x0000000A,22 : https://www.wincert.net/forum/topic/1904-tutorial-exotic-inf-profileitemsshortcuts/ P.P.S.S.: Maybe here is the answer, Yzöwl uses 0x6: this last snippet seems like it could be easily adapted to our problem, as: 1) it creates a group/folder (subfolder in start menu) 2) it creates two items in it 3) it deletes the subfolder and items in it on uninstall ... ProfileItems=Optional_ETDgroup.Add,Optional_Elantech_Mag,Optional_Elantech_DeviceInformation ... [DefaultUninstall] ... ProfileItems = ETDgroup.Del ... [Optional_ETDgroup.Add] Name = "Elantech", 0x4 [Optional_Elantech_Mag] Name="ETD Magnifier" CmdLine=16422, %TargetDir%,ETDMag.exe SubDir="Elantech" Infotip="Allows to magnify an area on the screen" [Optional_Elantech_DeviceInformation] Name="ETD Device Information" CmdLine=16422, %TargetDir%,ETDDeviceInformation.exe SubDir="Elantech" Infotip="Shows senseless info about the stupid touchpad device" ... [ETDgroup.Del] Name = "Elantech", 0x6 jaclaz

SCOOP! We have a (Flash) video here: http://192.72.220.42/eng/tpn_sp_fun.asp http://192.72.220.42/eng/smartPad_demo/index.swf showing the actual magnifying gesture tapping (around half, but there is a roll-up menu at the bottom that allows to go to the point) Try doing that, maybe it will come out as more intuitively. My guess is that (following the written instructions to the letter) you were tapping it wrong till now. I would describe what is shown in the video as: No two fingers are tapped at the same time, seemingly, quite different from: jaclaz

Should be this: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-profileitems-directive Try : [ETD_STD_Inst] ... ProfileItems=Optional_Elantech_Mag,Optional_Elantech_DeviceInformation .... .... [Optional_Elantech_Mag] Name="ETD Magnifier" CmdLine=16422, %TargetDir%,ETDMag.exe SubDir="Accessories" Infotip="Allows to magnify an area on the screen" [Optional_Elantech_DeviceInformation] Name="ETD Device Information" CmdLine=16422, %TargetDir%,ETDDeviceInformation.exe SubDir="Accessories" Infotip="Shows senseless info about the stupid touchpad device" But no ideas on how to delete them on uninstall. the: Name=link-name[,name-attributes] has to have the name-attributes explicited as flag 0x00000002 (delete item), but WHERE does this line needs to be put? Do we need a [Optional_Elantech.del] Name="ETD Magnifier", 0x00000002 Name="ETD Device Information", 0x00000002 and to add a ProfileItems=Optional_Elantech.del to the [Uninstall] section? jaclaz

Yep, all in all we can restore the original Click .inf section as it was: and call it day. No the ETDAniconf.exe needs: 1) the HKCU \Elantech\SmartPadDisplay\Click_Display set to 1 to display the page AND: 2) the various _ShowItem values set to 1 to display the single items within the page. If you have the latter ones set to 1 but the former set to 0 you won't see anything. Very likely in a reboot some (but not all) settings in HKCU are changed according to settings in HKLM, so if the Click_Display is set to 0 in HKLM but to 1 in HKCU, after a reboot the HKCU is reverted to 0, or if you prefer for this setting HKLM is prevailing. jaclaz

I cannot find any issue with this latest .inf. From all I can see it is functionally equivalent to the reference one you sent, bar the mods. No, the procedure is not entirely correct, as some values might have been changed, besides the remming with ;#. I cannot believe that the re-ordering of the groups of settings can affect the way the .inf work. Try installing the "old" .inf, export the HKLM and HKCU \Elantech to .reg files. Then uninstall and install the "latest" .inf and repeat. Then compare the two sets of .reg files. Before that, check these two (these might make sense): HKLM,"%ServiceRoot%\Elantech\SmartPad",ClickPad_LeftCorner_Click_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",ClickPad_RightCorner_Click_Enable,%REG_DWORD%,1 They are 1 in the old .inf but 0 in the modded one. (besides being remmed out). You don't need to reinstall for the moment, first try using OneFinger.cmd to make Click_display visible and ShowItemOne.cmd to make ClickPad_LeftCorner_Click_ShowItem and ClickPad_RightCorner_Click_ShowItem visible and see if you can enable them in the ETDAniconf.exe. jaclaz

Wait a minute, is it not that there is some conflict with "Corner Tap" or more likely with "Click" settings? I removed the whole "Click" settings as you reported them doing nothing, but maybe it was only the Click interface, while "undercover" the governing settings are actually the "click" ones. jaclaz

... curiouser and curiouser ... jaclaz

Yep. The lines I changed I remmed with: ;# Try un-remming them, one group at the time. the only ones that may be (how?) related seem to me: ;#HKLM,"%ServiceRoot%\Elantech\DriverOption",PSTWorkAndDisableTouchPadEnable,%REG_DWORD%,1 ; 0 = Disable, 1 = Enable ;#HKLM,"%ServiceRoot%\Elantech\DriverOption",PSTWorkAndDisableTouchPadTime,%REG_DWORD%,30 ; Unit (ms) and ; Dell System UI ;#HKLM,"%ServiceRoot%\Elantech\SmartPad",DoubleTapSpeed_Slider,%REG_DWORD%,550 ;#HKLM,"%ServiceRoot%\Elantech\SmartPad",SwapButton_Enable,%REG_DWORD%,0 ;#HKLM,"%ServiceRoot%\Elantech\SmartPad",CursorSpeed_Slider,%REG_DWORD%,10 All the other ones seem to me unrelated, but you never know. I doubt that the change (not remming, changing from 0 to 1 or 1 to 0) can be related jaclaz

Try setting all defaults from ETDAniconf.exe. "Button settings" used till now (the .inf you sent) vs. current ones: (no changes made there) Try also disconnecting the (USB) mouse. jaclaz

Sure, but the 11.4.14.1 .inf has settings for it, and they are the three finger ones (Mag_kind=2), while the instructions (that you see in ETDAniconf.exe IF Mag_kind=2 BUT NOT IF Mag_kind=1): First tap two fingers and hold one finger on the pad while double tapping with the other finger. The magnifying glass will appear. Drag a finger on the pad to move and focus the magnifying glass on the desired subject. Tap a finger to terminate the function.Magnifying glass copies the selected screen image to the clipboard when function initialized. seems a lot like a "two finger" set of instructions that you can only see if you choose the "three finger" setting ... but maybe it only works if Tap is enabled. Antway I would rather have it on the three finger press menu. BTW (out of curiosity) what happens if you add to it (say): notepad.exe AND ETDMag.exe vs. ETDMag.exe AND notepad.exe Maybe you need some practice :

A glitch in the matrix? jaclaz

OK . Try the attached. (in the file I included also the set of batch files, hopefully corrected, replace the old ones with this set) Mainly [ETD_SmartPadDisplay.AddReg] and [ETD_SmartPadUI.AddReg] are modified (hopefully) according to your reports and with items re-ordered (so that they are now more or less in the same order as the ETDAniconf.exe UI) and in some case renamed to make them human understandable (as an example the thing that is called "Gesture Effect" was called in the .inf "HID/Mouse switch" ). While I was at it, I noticed something in the .inf: The one you completely failed with was 2 (three finger). You can try your luck with the simple two finger gesture, changing HKEY_CURRENT_USER\Software\Elantech\SmartPad Mag_Kind to 1 (two fingers) jaclaz ETD_mod.zip

Good yes, I wanted your file so it is already updated to the last changes . And good , so I can remove (temprarily I will just rem them out) the Poinstick entries in the .inf. jaclaz

@Dave-H I am almost there, only a bunch of values remain to be "categorized". Can you please upload the latest-latest ETD.INF you used? And please do also another test, delete (export them to .reg before, just in case) both: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Elantech\Pointstick and: HKEY_CURRENT_USER\Software\Elantech\Pointstick There should be no changes in the behaviour of the touchpad and driver. jaclaz