Temporary KB lag fix (G50V)

I just wanted to post how I fixed my keyboard lag to help others in the same situation. I did everything I could think of from updating the bios a million times to updating the ATK drivers. I called Asus and while friendly, they didn't fix the situation.

Through reading this message board I followed a users suggestion to disable the internal touch pad on my machine. And guess what, not a problem since. I knew it wasn't because of my typing. I forget the users name but props to that fella.

All you have to do is press F2 at when booting up your machine to enter the systems setup. Then using your arrow keys press right until you get to the "advanced" tab (it's the second choice from the left). In that menu you'll see an option to disable the internal pointing device, just disable, save and exit.

Granted, it still hasn't fixed the problem where if you hold S & D, the space bar doesn't work, but it's a ton better than what I was dealing with before!

 

Yep, hey jump in this thread and give my script a shot...

http://forum.notebookreview.com/showpost.php?p=3923293&postcount=55

Let me know if it works out for you, I've been running perfectly smooth since. But I'm in XP, follow the thread and some users have had to tweak it a bit but it's worked so far.

Also here's a screengrab for disabling the touchpad in the bios:
http://forum.notebookreview.com/showpost.php?p=3908193&postcount=17

 

Hey you're the guy! Thanks for the fix!

About your code. I'm not a super programmer-type, so I don't know if I can mess with that code. Is it in a folder that I just copy n' paste into the startup folder? If so, that's cake. But if it comes to actually having to edit something within the code...well I'm pretty much outta luck.

Oh man, I've never enjoyed being able to type so much, lol!

 

Yea, unzip and put it in your startup folder under the start menu. If needed you can drag the .vbs file into notepad or right click and select edit. I pretty much explain it in the post that I linked to but there are two wscript.sleep values which are in milliseconds and those are what you'd need to change ... if the processes don't get changed to low priority after the amount of time (55 secs by default) passes from system startup.