Jump to content

RainyShadow

Member
  • Posts

    1,164
  • Joined

  • Last visited

  • Days Won

    14
  • Donations

    0.00 USD 
  • Country

    Bulgaria

Everything posted by RainyShadow

  1. Let's test this: 1. Start Win8. 1.1. Backup the driver settings. 1.2. Pick a few easily noticeable settings and change them. 1.3. Use Autoruns to disable all Asus programs and shell extensions from startup. Leave only the driver enabled. 2. Reboot to XP 2.1. Browse the Win8 drive in Explorer, find the folder containing the Asus Smart Gesture programs and rename it. 3. Reboot to Win8 3.1. Confirm that the touchpad behaves the way you last configured it. Don't try to start the mouse settings applet or any related programs! Check only by touchpad behaviour! 3.2. Restore the settings backed up in 1.1. Reboot if needed. 3.3. Check if touchpad behaviour changed according to restored settings. 4. Report here
  2. There may have been different entries on your system. That's why i suggested adding ATP manually. The .reg file replaces the previous values, it doesn't add to them. Check your backup and if it contains something else than "kbdclass" add that to your registry. --- Did your Win8 settings work on XP? Or, are they ignored again?
  3. I red history, just a suggestion if you're looking for a better driver
  4. Yes, install the one i linked previously. It's best to use the same driver on both systems. SmartGesture_Win10_32_VER4012.zip You will NOT be using any additional files and programs in XP, do the configuring in Win8 and copy from there. So, in XP the touchpad is moving and AsusTP.sys is listed among the driver files in device properties? Also, you have "ATP" as first entry for "UpperFilters" in that registry location? @Dave-H Confirm - Yes/No
  5. Many of the latest AGP cards were just PCI-E boards with AGP>PCI-E adapter chip. I have a GeForce 7600GS made this way. Drivers made for such AGP cards would probably work for you.
  6. @Dave-H You better manually add "ATP" instead of using the .reg file. I exported that from my netbook running Win7. When i tested the driver on my XP desktop, there were additional values there. Did you get a "missing signature" error when installing? I got that, because i had to modify the .inf file for my PS/2 wireless mouse, and the silent install was failing... silently :P Not sure if just .sys modification triggers it as well... About cloning settings from Win8 to XP, you can try starting the configuration applet through Revo Uninstaller or a similar tool, as if you're installing a new program. Then open the log to see what exactly changed.
  7. Use a boot manager that can inject key-presses after booting. I use XOSL and it "pushes" F8 when booting Win98 :P
  8. So, this just disables Javascript and OpenType support and calls that a fix? I have a better one: pull out all LAN cables and all WiFi & WWAN adapters out of the PC - there, instant fix for almost all vulnerabilities
  9. ^^^ WTF, dude?! Anyways... eps2.7z Modded the .sys file, fixed the .reg file, added backup function to install.bat (may fail due to regional settings). I'm done here. /OT @dencorso Any clue why my allowed attachment size shrinks more and more? Is there a fixed amount for all my posts? And, is there some sort of file browser where i can see all my previous attachments and remove the old ones? Ignore that, i found it, sorry. https://msfn.org/board/attachments/
  10. @Dave-H Try to edit it in CFF Explorer. Did you add "atp" as upper filter? (using the .reg file, or manually)
  11. eps2.7z This is just the driver from SmartGesture_Win10_32_VER4012 It seems to be a filter for the generic PS/2 driver. Looks like XP has all imports it needs. Use the .bat file to install, then import the .reg file (you may want to backup the original value first). Originally they use ATP_Reg.exe to modify the registry, but that doesn't run in XP. If this driver runs fine, you should be able to import your settings from Win8. Install the full package there.
  12. Ok, finally we're talking, lol. Could you pick one of those working drivers and try to install it on both XP and Win8? If the settings don't work on Win8 too, then try the next driver.
  13. Is there a proper fix released for any version of Windows? (i'm not asking about some half-assed workaround that just disables/deletes the affected .DLL and file associations)
  14. I thought you said previously that some driver worked... I'm not asking if you can change the driver settings or whatever. I'm asking if the cursor moves when you swipe on the touchpad! Don't tell me that a driver doesn't work when it has permanently enabled tap to click, please! By that same logic i can declare any Windows install that doesn't start with my preferred desktop background picture as non-working, LOL. Are we speaking the same language? P.S. i checked at work today for that X102BA we've had... unfortunately it is long gone. I was hoping to try these drivers myself and report some results... Well, it may come back for warranty servicing someday, lol. Then it comes straight to me (i deal with the warranties). Not holding my breath though.
  15. @Reino I already use all of these. Now waiting for 3dyd to release a working build of LAV with that new dav1d AV1 decoder, hopefully :P The newest 0.74.1 version crashes on me too. I prefer ffdshow though, it's much more configurable.
  16. So, did you find a driver (regardless of config app) that works without modding in XP? And did you try to install that same driver in Win8?
  17. Try Poweroff Plenty of options and command line support. Also, you can try to set a dedicated account with a login script which executes the WOL program and then initiates logoff on itself.
  18. Just to clarify, i was asking about the touch screen, not the touchpad. So, it works fine in Win8, but doesn't in XP? There is a "TabletPC" folder on the XP CD, do you have that installed?
  19. According to the .snp files you posted previously, it looks like both XP and 8 have installed a generic driver from input.inf for your touch screen. Does it work in Win8? At the Asus "support" site i see only BIOS updates, one app, and few documents, regardless of which OS i select... The last BIOS version mentions a fix for the "touch panel" (not 100% clear if that's the screen or pad). Are you on this BIOS version?
  20. Try that 7.0.5.5 driver on your Win8 as well. btw. Just checked how that thing looks... Seems to be of the type i absolutely hate to use, lol Single mechanical button around the middle, and it picks left/right click function based on your finger position. When i have to use these at work, i exclusively use tapping. Trying to use the button always moves the cursor, ugh. I'd rather put something inside, so depressing the touchpad surface won't trigger the damn button, lol. I see that this model is supposed to have a touch screen. Does it work fine on XP? P.S. just found an old, expired ad from my company. Turns out we had one of these netbooks last summer. Gotta check if it's still there...
  21. Lucky guys, to have the fastest CPU for socket 462... Mine is merely an AthlonXP 3000+. Still rocking on my main PC :) Are you aware of any ffdshow fork or unofficial build newer than v.4534 ?
  22. Why not use your Win8 to get the registry entries from there? Export to a .reg file, load your XP registry hives, modify the paths in the .reg and import it back. You can also check if there isn't any writes done to a separate .ini/.cfg/.whatever file when you click "apply" in the touchpad configuration app.
  23. You need only the application itself, the indexes and the Elan touchpad package. That's less than a GB. All my systems at home are 32-bit only and SDIO works just fine. I already told you that in newer versions of this driver the applications are compiled for Win7+ (NT6), why do you insist on using the latest ones? Since you've unpacked the Elan driver pack from SDIO, just go through the folders and try starting one of the included applications. If you get "not Win32 program" error, then it is too new/ not for XP. Find a version where you can run the programs, install that driver properly and try configuring it with the app/cpl. Just start it from the source folder to see if it works.
  24. Try to dig out some old Intel WiDi driver from before they scrapped the thing "because M$ added it to Win10". Not sure if one exists for XP though.
×
×
  • Create New...