jaclaz

Sure, the display keys are only to make sure that you can in ETDAniconf.exe see the settings and enable/disable them. Then as said it has to be seen if the driver and your hardware actually do anything, Anyway Tap and Press are distinct actions. Three Finger Tap is another setting (that you have anyway disabled because you disabled ALL tapping), and is in the One FInger tab, different from Three Finger Press which is in the MultiFinger tab in ETDAniconf.exe. jaclaz

That should be an "Open" dialog initially pointed to the Windows folder. If you select - say - Regedit.exe (still in the Windows folder) or navigate to another directory and select a .exe files it will be added to the list. I believe that those are Favorites that you need to "activate" somewhere in the settings panel. Check (or set) in: HKEY_CURRENT_USER\Software\Elantech\SmartpadDisplay ThreeFingerPress_Display to 1 TabUI_1F_Display to 1 TabUI_MultiFinger_Display to 1 and in: HKEY_CURRENT_USER\Software\Elantech\SmartPad You should have in Multifinger tab a "Press with three fingers" or something like that with the same settings. Those come from (and are written to): HKEY_CURRENT_USER\Software\Elantech\Favorite It remains to be seen, if you enable that if anything actually happens when you press with three fingers. jaclaz

Sure , that is the "normal" way to install grub4dos, and generally speaking just fine , but - in some cases - potentially destructive, as it writes the grldr.mbr code to the MBR and to several of the following "hidden" sectors, (15 of them in latest releaes, 17 in older ones). Usually doing that is perfectly fine , but there are possible issues: 1) some Commercial DOS and Windows programs casually use one of those hidden sectors to store their authentication code 2) some (BTW bad, really bad) BIOS simply do not "like" grub4dos code in the MBR and won't boot[1] 3) in case [2] of a GPT disk/hybrid boot disk it will destroy the GPT partition table In any case, the message is the following: 1) the MBR is one single sector, first absolute sector of the disk or LBA0 2) the grub4dos grldr.mbr code is 16 sectors long (used to be 18) so it is NOT installed to the MBR but rather to the MBR and several sectors after it 3) you better be very sure that these hidden sectors are not used by anything else Everything will work out just fine in 99% of cases, now you know what can happen in the remaining 1%. jaclaz [1] the number of these has been reduced greatly in grub4dos 0.4.5c latest versions and in grubdos 0.4.6a [2] rare, but you never know

So, summing it up the "best" settings are: UI_Theme=1 both: ETDAniconf.exe ETDmcpl.dll present in \Programs\Elantech\ folder. So the ETDAniconf.exe remains the "only" settings tool available and accessible both from double clicking the tray icon and from the Options button in the added Elan Mouse tab. At this point, possibly it makes little sense to have the added item in Control Panel "Elan Touchpad" that as is it is only a third way to call ETDAniconf.exe. jaclaz

No problem, happy to have helped even if it was boring to you. You see, the point is - specifically - that you do not know what you are talking about, which is perfectly fine, but also refuse to learn about the topic and prefer to do random things with random tools, which is also fine. of course. Of course any number of tools can change a single byte in the MBR partition table, the "difficult" part is understanding that that (in this case) is what is needed, and to do so you need to understand the processes involved, and of course know what is the correct value to write. BTW, it is not like overnight little green men accessed your MBR partition table and changed the 0x0C to 0x07, that is the result of some of the random thing you did with some random tools earlier. Just for the record there is no such thing as rewriting MBR code to point to grldr, you need to write this code (which is grlrd.mbr) to the MBR and several sectors after it, then this code does not "point" to grldr, it searches for it (it is not the same thing). But if you want to have some code that points to grldr (and fits in the MBR) it exists alright, it is called UMBR (technically it can point to the extents where grldr resides): http://reboot.pro/topic/21856-cant-install-grub-with-bootice/ Still the best (IMNSHO) approach if you have in the multiboot a Windows NT is to leave everything "standard" and add grldr in BOOT.INI or grldr.mbr in \boot\BCD. jaclaz

Sure , using randomly a sufficient number of random tools before or later you will succeed , though you won't ever learn about the matter at hand and occasionally you will botch something beyond recovery . jaclaz

Yep, but the whole stuff about double/triple booting is "low level", you need to understand and learn the basics to be able to correct issues or change settings. Get Tinyhexer here: http://reboot.pro/topic/21999-tiny-hexer-mbr-backup/ http://reboot.pro/files/file/595-tiny-hexer-mbr-backup/ that one already contains my Structure Viewer scripts, you want to install the "full" version. Alternately, if you can actually run grub4dos, it can be checked (and corrected) in grub4dos as well. At the grub> prompt (press c to get to it from a menu) run: geometry (hd0) parttype (hd0,0) Get the (now old but still good) diddy's guide (the downladable .chm version) here: https://web.archive.org/web/20110723032750/http://diddy.boot-land.net/grub4dos/grub4dos_chm.zip read about the above commands. The screenshot you posted is about a disk that is not first disk (disk 0) unless for *whatever reason* that tool names disk differently (or you changed disk order) and the partition ID is ALREADY 0x0C (which is correct) jaclaz

Try re-reading, this time slowly,: Very likely partitions ARE FAT32 BUT they have a NOT CORRESPONDING to FAT32 partition type in the MBR. This will prevent bootpart (and possibly makebs) to work correctly and won't allow booting DOS from that volume. The partition type 0x07 that traditionally corresponds to both HPFS (used in OS/2) and to NTFS (and nowadays corresponds also to exFAT) is a "protective ID" meaning essentially "something that DOS (and Windows 9x/Me do not understand and that should not even think of accessng". Check the partition type in the MBR, it surely NEEDS to be correct for DOS/Win9x/Me usage and most probably it needs to be correct for bootpart and makebs use. jaclaz

BTW, guess who wrote the little batch that you couldn't find on: http://www.boot-land.net/forums/?showtopic=2362 and that is on: http://reboot.pro/topic/2362- http://reboot.pro/topic/2362-makebscmd-alpha-release/ Possibly get the LATEST version: http://reboot.pro/topic/2362-makebscmd-alpha-release/?p=38195 jaclaz

The bootpart output says that the volume is NTFS (partition type 7). It won't ever work, you need FAT16 or FAT32. READ: https://www.winimage.com/bootpart.htm Later of course FAT32 compatibility was added. It is possible that your volume is actually FAT16 or FAT32 and that any of the tools that you (mis-)used lately changed the Partition ID in the MBR to 0x07. In any case this command line is not valid: The normal command is: bootpart <option> <fullpath\filename> "<description>" Option means the TYPE of bootsector to create, they are: dos win95 winnt win98 etc. Description is what will be added to the boot.ini as descriptive line and needs to be enclosed in double quotes. This would be a valid command line: The volume that has an asterisk in bootpart output (meaning that is the active partition) is the one in use. About grub4dos, its menu.lst (it is a small L not the number 1) is editable just fine, no idea why/how it does not work for you. In any case you do not rename menu.lst (it is a small L not the number 1) to another name as the menu.lst name is embedded in grldr (you can change its name but you need to change it alo in the embedded menu in grldr). jaclaz

Ok, these: [ETD_UIFunctionOption.AddReg] HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",InVisible_DisableExternUSB,%REG_DWORD%,0< Makes in Elan Tab the Disable when USB mouse checkbox visible/invisible HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",InVisible_DeviceListStatus,%REG_DWORD%,0< Not found what it does HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",InVisible_DisableEnableButton,%REG_DWORD%,0<Makes in Elan Tab the Activate button greyed out HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",Visible_Animation,%REG_DWORD%,0< Makes with 0 in ETDAniconf.exe the avi to NOT show, with 1 they are visible HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",DisableExclusive,%REG_DWORD%,0< Not found what it does HKLM,"%ServiceRoot%\Elantech\UIFunctionOption",UI_Theme,%REG_DWORD%,5<UI mode, OK jaclaz

Naah, they don't have real conflicts (between them). Every config panel reads the current settings from HKCU and/or from HKLM only when they are started. Then the behaviour changes, ETDAniconf.exe (and only it) changes (still in HKCU) only the setting that is changed, whilst all the other at each single change run a burst of all settings writing them all in HKCU. If you prefer, if you open two of them and change a setting in one, the change is not reflected on the other one until it is restarted. The conflict (if any) is probably with ETDCtrl.exe which is running (or in my half-@§§ed install only half running) in the background and periodically checks keys (in my case also changing some of them that it doesn't "like"). Actual config panels "conflicts" seem like being only "visual overlays", one I found is that: \SmartPadDisplay\TwoFinger_Double_Tap_ShowItem overrides \SmartPadDisplay\Tap_Two_Finger_ShowItem so that in ETDAniconf.exe, if the first is set to 1 it takes the place of the second in the "Touch" settings panel (but in ETDmcpl.dll the first is never shown). jaclaz

When the added Elan tab in the mouse is present (i.e. ETDmcpl.dll is present in \Programs\Elantech) , clicking on Options in the added tab: if UI_theme is 1 it opens the ETDAniconf.exe settings (multi-tab, One Finger, Multifinger, Additional, if the smartpad_ShowItem0x1.reg and smartpaddisplay0x1.reg are imported, that means 8 items in One finger, 12 items in Multifinger, 9 items in Additional, total 29 ). if UI_theme is 0 it opens the ETDmcpl.dll settings (a list of 14 settings (15 if you count "Copyright) in a single column on the left, ) The behaviour is sometimes "queer", cannot say exactly why, If you have ETDAniconf.exe and UI_theme=1 it opens ETDAniconf.exe but when you have already run it and change the UI_theme=0 sometimes the new setting isn't taken and it opens as well ETDAniconf.exe. If you rename ETDAniconf.exe to (say) ETDAniconf.exe_no and try again, it opens the ETDmcpl.dll fine and then you can rename back the ETDAniconf.exe and the option button will still bring up the ETDmcpl.dll. And here comes the interesting part: With UI_Theme=0 and Options in the added Elan tab brings up the ETDmcpl, with it open, if you try double clicking on the added Elan Touchpad item in Control Panel, nothing will happen (or the already opened ETDmcpl will get focus. But if you first double click the Elan Touchpad Item in Control Panel (and thus open the ETDAniconf.exe) and then click on options in the added Elan tab, the ETDmcpl is opened, so you can have both side by side and compare options in the one and in the other. Btw, if the ETDmcpl is open, even if you double click directly on the ETDAniconf.exe in \Programs\Elantech it won't run. jaclaz

Yep, you can try that simply adding manually the ETDmcpl.dll to the \Programs\Elantech folder, in the latest .inf, whilst I removed the actual copy of the ETDmcpl.dll file, I left the related Registry settings, so it should work as soon as the file is found. Try the above , then there should be a difference between UI_Theme 0 and 1. This seems the most interesting: 3 - "Dual Mode" icon, double click pops up the options "Touchpad Settings" (containing "Enable Tapping" and "Enable Slow-Motion Pointer"), "Disable Touchpad", TrackPoint Settings", "Disable TrackPoint" (both irrelevant with this hardware), and "Advanced Settings" (which launches Mouse Properties). Right clicking gives "Remove UltraNav icon from the system tray". No Mouse Properties tab. Icon identifies when hovered over as "Touchpad = Pointer, TrackPoint = Pointer". With that does the Enable Tapping (and hopefully the Disable Tapping) actually work? Too bad that it is for a laptop that also has a trackpoint, if you add the ETDmcpl.dll with UI_Option=3 the Mouse added tab will have as well provisions for the non-existing trackpoint. jaclaz

You cannot, you write one. You can find examples and snippets, but invariably you will need to modify them to suit your needs, a few examples: https://cects.com/using-the-winrar-command-line-tools-in-windows/ https://cects.com/automate-compression-tasks-cli/ https://superuser.com/questions/371384/extract-all-zips-in-a-directory-incl-subfolders-with-a-bat-file-or-dos-comm It depends of course which "base" tool you want to use, 7-zip, RAR or - say - Peazip: https://www.peazip.org/peazip-free-archiver.html I had a look around and it does exist a Commercial tool that seemingly does what you want, but it isn't exactly cheap: https://www.powergrep.com/ and probably does too much. There is this free one: https://dngrep.github.io/ but it is .Net and Windows 7 up. jaclaz

As expected the HKCU Smartpad key contains the SAME values as the HKLM one, though it misses a few that probably are "transplanted" to HKCU by the ETDCtrl,exe (or by some of the settings utilities) only when some option is activated. In other words the Tap_One_Finger_Enable=dword:00000001 is in BOTH the Registry files. Now, the test is if you delete that value in BOTH HKCU and HKLM, it shouldn't change anything and - no matter what you do with ETDAniconf.exe it will never be recreated, not in HKCU and certainly not in HKLM. Still there should be a difference, in ETDAniconf.exe you can only manage the Tap_Enable=dword:00000001 value, and that disables *all* tapping (One/Two/Three Finger tapping) , whilst, at least in theory, flipping the Tap_One_Finger_Enable you should be able (but only if UI_Theme=5, which, as we have seen, will imply renaming the ETDAniconf.exe to Asus_UI.exe) to disable only one finger tapping but keep the Two and Three finger tapping possible. It is not your case, since you want all tapping disabled, and thus you can do with *any* UI_Option that is not 5, but it may represent an option for another user. jaclaz

Yep, this is the best till now, I thought that with UI_Theme=0 the ETDmcpl.dll was needed, i.e. it forcibly opened the Mouse Control Panel thingy without the added Tab (which is provided by ETDmcpl). What happens with other values of UI_Theme? In theory the "right" setting for ETDAniconf should be 1, but try ,ore values you can go surely up to 7 or 9. And try some other values of CustomerDefinition, too. There should (might) be a setting that instead of the dialog: 200,Property of Touch-Pad 201,My Favorites Setting *somehow* opens the dialog (possibly via an "intermediate" one): 112,Remove Icon 113,Your touchpad has been enabled 114,Your touchpad has been disabled 115,Your touchpad has been disabled because the touchpad driver has detected that another pointing device has been plugged into your computer.$0A 116,Touchpad Driver Notification 117,Close 118,Version Information 119,Mouse Properties and/or: 1010,Disable Tapping 1011,Enable Tapping 1012,Disable Slow Motion Pointer 1013,Enable Slow Motion Pointer 1020,Scrolling(&S) 1021,None(&N) though maybe they depend on some other setting in either OtherSettings or UiFunctionOption I'll have a look at the last .reg files you posted . About this: I don't know, but probably the idea is that the setting is either set to 0 and then both touchpad and mouse work or it is set to 1 and then when the USB mouse is inserted the toughpad is disabled (and when the mouse is removed it is automatically re-enabled again) and when changing the setting a reboot is needed, or - if you prefer - that setting can obly be changed when there is no USB mouse connected. Try seeing what happens to other keys/settings (with Regmon) when you change that value), what I expect is the following (my guess): 1) you change the HKCU\Software\Elantech\OtherSetting\DisableWhenDetectUSBMouse to 1 2) as soon as you insert the USB mouse that action makes the ETDCtrl.exe look at the above value and if it is set to 1 then it changes some other value, that has to be found, possibly: ;TP Enable/Disable Status HKLM,"%ServiceRoot%\Elantech\SmartPad",TPStatus_Mode,%REG_DWORD%,1 3) when you detach the mouse (and DisableWhenDetectUSBMouse is still set to 1) the above is reverted but 4) if you change the DisableWhenDetectUSBMouse to 0 while the mouse is still connected, then detach the mouse, nothing "triggers" the ETDCtrl.exe to re-enable the Touchpad. And then these keys: HKLM,"%ServiceRoot%\Elantech\OtherSetting",ForceEnableStatusWhenResume,%REG_DWORD%,0 ; Force enable after resume HKLM,"%ServiceRoot%\Elantech\OtherSetting",ForceEnableStatusWhenSuspend,%REG_DWORD%,0 ; Force enable when suspend HKLM,"%ServiceRoot%\Elantech\OtherSetting",ForceEnableStatusWhenFUS,%REG_DWORD%,0 ; Force enable when FUS HKLM,"%ServiceRoot%\Elantech\OtherSetting",ForceEnableStatusWhenLogOff,%REG_DWORD%,0 ; Force enable when logoff HKLM,"%ServiceRoot%\Elantech\OtherSetting",ForceEnableStatusWhenShutdown,%REG_DWORD%,0 ; Force enable when shutdown HKLM,"%ServiceRoot%\Elantech\OtherSetting",TemporaryEnableStatusAtLoginScreen,%REG_DWORD%,1 ; Temporary enable at login screen may also come into play. jaclaz jaclaz

Maybe he missed/messed up more than one, and he is actually looking for Power Quest Editor: http://www.powerhoof.com/public/powerquestdocs/ jaclaz

There is no such thing as Asus Style, the thingy is always the same (should be ETDCtrl.exe) and changes behaviour when the UI Option keys are changed. at least the UI_theme does that, those strings I found may well be remnants of functionalities that are long gone before the current version of ETDCtrl.exe, of course. There is also a "Favorite" set of strings: is that what you see with other values of UI_theme (but 5)? It is also well possible that the behaviour is changed by other values in OtherSetting. jaclaz

No, what he asked about is perfectly clear, until you doubted about its meaning. Mind you, you are possibly being perfectly right in your doubt, still there are no elements of uncertainty in the OP question. jaclaz

Also, the *whatever* that runs the tray Icon should be ETDCtrl.exe. Having a look at the .exe it looks likes it has some options available by right-clicking on it. What happens when you right click on the tray icon? Try with different settings of UI_Theme in Registry, I see strings *like*: It is possible that some other values in UIFunctionOption affect this behaviour. jaclaz

No, it should be the exact opposite of that, The Tap_One_Finger_Enable exists in HKLM (because the .inf writes that at install): ; Tap HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_T1_Time,%REG_DWORD%,200 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Activate_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_One_Finger_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Two_Finger_ShowItem,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Two_Finger_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Two_Finger,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Two_Finger_Ex,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Two_Finger_Path,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Three_Finger_ShowItem,%REG_DWORD%,0 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Three_Finger_Enable,%REG_DWORD%,1 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Three_Finger,%REG_DWORD%,%NONE% HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Three_Finger_Ex,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Three_Finger_Path,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Four_Finger_ShowItem,%REG_DWORD%,0 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Four_Finger_Enable,%REG_DWORD%,0 HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Four_Finger,%REG_DWORD%,%NONE% HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Four_Finger_Ex,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap_Four_Finger_Path,%REG_SZ%, HKLM,"%ServiceRoot%\Elantech\SmartPad",Tap2FunStaticText,%REG_DWORD%, and does NOT exist in HKCU until *something* writes it there. jaclaz

But that is an alternative to the good ol' Partition Magic, NOT to PTEDIT. jaclaz

Well, this is the complete opposite of what you reported earlier. so what was till now "unexpected" has become "impossible". I think you may be mixing together the keys in HKLM and those in HKCU. The ones that the various control panels access and change are in HKCU. The ones in HKLM are copied to HKCU (but I believe which keys depend on the control panel used) only when you choose in the control panel to "set default" (either all settings or per tab settings). Check if the key HKEY_CURRENT_USER\Software\Elantech\SmartPad\Tap_One_Finger_Enable exists immediately after the driver is fresh installed Then, open the ETDAniconf.exe and set all the default, then check again if the key exists in HKCU. Until you run Asus_UI.exe that value should not exist in HKCU. (though it exists, thanks to the current .inf, in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Elantech\SmartPad ) We can later amend the .inf. If I remember correctly the behaviour with UI_Theme=5 was to launch from the tray icon directly Asus_UI.exe. Try making a copy of ETDAniconf.exe in \programs\Elantech folder and rename it to Asus_UI.exe. Yep, that should be HKEY_CURRENT_USER\Software\Elantech\OtherSetting\DisableWhenDetectUSBMouse try flipping it manually, if it works we can later make a .reg, .inf or batch to flip it. Otherwise you need to manually add to \Programs\Elantech folder the ETDmcpl.dll and set UI_Theme=1 jaclaz

A good alternative to PTEdit, is (was) BeeblebroxNT, here: https://web.archive.org/web/20090331222406/https://students.cs.byu.edu/~codyb/ BTW the Author, Cody Batt was one among the original Authors of PTEDIT, and later he started a new version (that was never finished/never worked). It works (used to work) just fine on XP, but lately there came out an issue on some machines with a "mysterious" conflict with some other software. In these cases, it stiil can be run but it needs to be started as a service, via SrvAny or NSSM. jaclaz