jaclaz

Try using the dud as replacement for ETDfavorite.dll. http://www3.telus.net/_/dud/ It may or it may not work, of course, it is very strange I cannot find a reference/link to ETDFavorite.dll in ETDCtrl.exe or in ETDMcpl.dll, nor in the Registry. It is entirely possible that the ETDCtrl.exe looks for it (even if it doesn't trigger any of its functions), but is strange that it doesn't error out when restarted. Anyway "keeping" it, even if it not used is not a big problem. jaclaz

Usually there is some double sided sticky tape to hold the CMOS battery. Get anyway the specific service manual: http://tim.id.au/laptops/asus/s96j.pdf each model may be slightly different. jaclaz

Good. Now you can try removing/renaming the ETDFavorite.dll and see if anything changes in the behaviour of the driver. jaclaz

From what I can understand the "modify" will work to replace the existing notepad.exe link (when that is selected), the "add" adds another program. If the list is empty "modify" and "add" do the same thing. I cannot see that exact same dialog as the only one (similar and to the same effect) is accessible via ETDAniconf.exe Multifinger 3 Finger Press, and that one has (at least here) only "Add" and "Delete". About ETDFavorite.dll cannot really say, maybe in the current configuration (ETDmcpl.dll+ETDAniconf.exe, UI_theme=1) it is not *needed*, particularly if you are removing that right click option. Dialog 4000 in ETDFavorite.dll seems a lot like the Add/Modify/Delete/Up/Down you posted in the screenshot. jaclaz

I seems like that specific Asus model has a "standard" battery connector, but you need to check anyway before ordering it, basically there are both 2 pin and 3 pin connectors, the s96J seems like having a three pin one: http://www.genuine-cmos-battery.com/asus-s96j-cmos-battery.html but it could also have a 2 pin one: https://www.bonanza.com/listings/Asus-G60-G60J-N55S-W7J-W5000-K50i-X70A-U47A-W2-Bios-Cmos-Rtc-Battery/845575237 but you can never trust these sources and must verify what you have on your hands. For the record, besides the "normal" CR-2032 there is also a version with terminals pre-spot-welded that can be used in these cases: https://uk.farnell.com/panasonic-electronic-components/cr-2032-hfn/battery-lithium-2pin-horiz-cr2032/dp/1298246 jaclaz

I have lost you. WHICH "settings" button? I cannot see any in the screeshot you posted: With UI_Theme set to 1 clicking on "Property of touchpad" should bring up the Mouse properties and there should be the added Elan tab. To remove the "My Favorite settings" you need to edit the ETDCtrl.exe. I cannot do it because I have no way to see how it behaves, if I got the right resource, etc. It should be Menu #172 either 32805,0 or 32806,1 Get Exescope: https://www.softpedia.com/get/Programming/File-Editors/eXeScope.shtml or ResHacker: http://www.angusj.com/resourcehacker/ And try and see what happens deleting the one or the other. jaclaz

I cannot see the reason for the outrage (relative to the Linux WSL, not the one againt Windows 10 which remains a pile of crap). It is an added option, having choices is IMHO always a good thing. jaclaz

It seems like Dell does not have whitelist for wi-fi cards, but it has to be checked if the card is mPCI or N2 (should be mPCI but needs to be verified) and I believe the only option is - in case - some broadcom one (and it has to be seen if a driver for those eist for XP). I had a look around but all I could find were people that removed the AC 7260 for a newer Intel card. jaclaz

Good , and on this page there are a few screenshots of PTEDIT32: https://www.goodells.net/multiboot/ptable.shtml They don't look very similar. jaclaz

It's strange, as the Lenovo.exe (that comes with the same driver) while it has not a setting for three finger tapping does have one for three finger pressing. And there is the Press_3F.avi file. Maybe there is some other setting that prevent press to work? jaclaz

I thought you were busy re-building a new barn ... jaclaz

... or unless the Dell database is wrong. or unless the web server fails, or unless the sky falls on our head ... ... naah, that may only happen tomorrow ... jaclaz

No it won't apply to tapping, because Dave has ALL tapping disabled, or if you prefer: HKEY_CURRENT_USER\Software\Elantech\SmartPad Tap_Enable set to 0 And that - seemingly - automatically disables in the driver (even if the Registy is not changed) all three possible tapping options: Tap_One_Finger_Enable Tap_Two_Finger_Enable Tap_Three_Finger_Enable and possibly also the other : TwoFinger_Double_Tap_Enable So, no tapping will work. jaclaz

It is not "Tap", it is "Press". jaclaz

Ethernet is network, you mean wireless network card drivers? Post VEN/PID or however hardware ID of the wireless card/chip you have in your Dell and also post the EXACT model of the Dell, maybe it is enough to find (hopefully) a driver. Also if you fiddle with this kind of things it won't be IMHO be a bad idea to get one of these (example only): http://max-digital.co.uk/ac600-wifi-dongle-1.html at least for temporary use until you find a driver. There are some similar thingies that include a sort of USB stick embedded with the drivers so that they are fully portable, other example: https://www.amazon.com/Aigital-Adapter-600Mbps-Wireless-Windows10/dp/B07PR9RF2H 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