Beta BIOS - Possible Missing Keystroke Fix

I am running x64 Ultimate too. All DWord values are 32 bit as far as I know. You can create a QWord value which is 64 bit. The value we are talking about here is a DWord, though.

 

Yes Jody!

You is right, is QWord 64 Bits , but works...

 

I'm puzzled at why it takes a multi-billion dollar company over a year and yet they cannot fit this issue. Seems quite careless, considering the problem still exists and it's like a widespread plague to newer G73 generations. It's going to take a spectacular deal/price for me to even consider Asus again as a gaming laptop after this catastrophe (keyboard/touchpad).

At least Dell has the M11X sorted out with the hinges. Chris (Dell Rep) communicated with us, let us know the M11X has a new designed hinge, and everyone is getting a free extended warranty. Why can't Gary/Asus communicate with steady updates or find a proper fix.

 

lol let me tell you, as happy as I am with my g73, If I could return it and get something else, I would. I don't really want to deal with asus repair *if* I have to RMA it again. The computer is fine! But even thinking of having to deal with warranty work again (on the off chance I have problems in the future) makes my head hurt.

 

My keyboard seems to be not missing keystrokes anymore. I am still on the official 211 bios, as didn't want to update till there was a final solution.

Thanks for the simple registry tweak to improve things till the long awaited final keystroke-fixing bios (which I wouldn't hold my breath for!).

 

Gary tell us you status

 

I would suggest to anyone using the Registry mod be using the stock 211 BIOS, and not any of the betas. Honestly, if none of the betas are working for you, may as well be using stock.

BTW, does the trackpad also set the polling rate properly in the registry, or does it also use a default?

 

I got beta 4, and the registry mod running. Of course, beta 4 basically fixed my problem, and the registry mod *seems* to have helped some more.

 

I couldn't find any tweaks for the registry that seemed to affect the touchpad polling rate. There are some in there but the touchpad seemed to ignore them. Perhaps it was because this registry DWord was missing? I think I will go back to 211 with this new DWord and see if I can prod it into submission with polling rate adjustments.

I am typing this post on my sons Alienware m11x and this keyboard is just a pleasure to use. This laptop is nowhere near the horsepower I have and I wouldn't give up my i7 and 5870 for it. I sure would love to graft this touchpad and keyboard onto my G73, though. The funny thing is it is an island keyboard too. The problem is obviously not inherent to the island style keyboard.

 

I got confirmation that the file linked earlier is in fact the Official 213, so I linked it on my Reference page. Bon appetit everyone.

 

Castity, if 213 is official why is it not on ASUS's site? For advanced users like you and about 90% of the others on this forum, I am sure you can easily recover from problems, but for the other 10 % of us that have only 1 computer and minimal knowledge I was just wondering.

 

so last beta (beta 4) is in fact official bios 213?
i can't find nothing official on asus site

 

I know this is a stupid question but is there changelog for 213. Dont feel like flashing if it has nothing of use in it.

 

I'll be the brave soul to flash mine.

 

I hope its not official, since it neither fully succeeds in fixing dropped keystrokes ( the reg fix helped my spacebar misses though), nor in touchpad issues. Asus better not be dropping this crap on us as "official"..

 

Maybe it's just me, but my G73 seems quieter. Other than that, I don't see any difference, but then this is from someone who doesn't suffer from any of these issues, except the lack of proper working vBios/PowerPlay that Asus has yet to address.

Nevermind, my keyboard lights are gone, so I'll have to fix that, awesome.

I also have really low latency.

 

When it is installed is it reported as 213?

 

Taking a more analytical look at it, the beta 4 bios and 213 at least appear different - largely different MD5 checksums, and using file comparison tools shows some significant blocks are different (though, this doesn't mean nearly as much, since comparing code like that may show big differences that really aren't anything more than a couple of different lines and a few comments). Ill certainly give it a try once i get home.. can't be any worse than it is now.. lol

 

Everything seems fine here.

 

I see the date is 10/30/09... maybe they do that so you can't use winflash.

 

Uh... no... the date is 1/27/2011

 

Uh... yes

In this picture the date is 10/30/09....

 

Uh no it's not... Why are you reading the vBios date for ATi I have no idea. I guess the ATi logo wasn't a give away. Or that there is another thing called American Megatrends with G73jh.213 and with the date 1/27/2011...

 

LOL. I opened the picture and it says 10/30/09. I don't know why. The laptop reports it as 1/27/2011. It doesn't affect the sensitivity of the touchpad. I am starting to wonder if it's my driver doing that. I haven't missed a keystroke while typing this little message. That doesn't mean much. After I added that DWord to the registry it misses one very very seldom. So far so good!

Going to fiddle with the sensitivity settings of my Synaptics driver now.

I report no issues with the bios. It didn't let the smoke out of my computer or anything.

Edit: Just saw your post, Ruckus. I figured I was looking at the wrong date. You aren't the nicest or the most polite guy around here but you are are seldom wrong.

 

It is reported by ATI but it is clearly labeled as the motherboard system bios and right beside it is bios 213. I did not notice the other one labeled as the release date at first glance...

 

Uh.. no... Again why can't you see the 1/27/2011 date to the right? I have already updated to this Bios so i already know. Even when you update it, it says 1/27/2011.

 

which file??? where???
did i missed something

 

Its funny how the date he should be looking at is still in the picture.

What does it mean if mine averages around 200 with a max of 400???

 

Easy there big guy. I see it after you pointed it out. I edited the post. I figured it was there somewhere that I wasn't seeing. I chuckled because I popped the image open and saw what the other poster saw too. I had already updated when you did. It tells you when you choose the file that the date is 1/27/2011.

It's OK. We weren't doubting your technical prowess.

 

All this arguing about the dates, when you are both right. The HWMon program on the right is reporting the MOTHERBOARD bios as from October (Yes, there is an ATI logo on the screen, but you will notice that the date is actually next to, and related to, the mobo bios), while the other tool is reporting the correct date. Does it matter, no, but both arguments are petty.

Anyway, doesn't sound like a huge touchpad fix eh? no surprise there....

 

Agreed.

No it doesn't change my touchpad at all. It is exactly the same. I adjusted the sensitivity setting in Synaptics but I still can't use the cursor unless I get my palms clear of the palm rest. It registers every move as a two finger scroll unless I get away from the touchpad.

It's not like it's unusable. It works fine. I would call it a minor annoyance.

 

Just finished uninstalling and reinstalling my drivers just in case. Keyboard and touchpad seem perfect so far, not going nuts and the pinch/zoom and scrolling seem to be working.

 

i just want to mention that Everest shows also 10.30.2009 (213)

 

You are lucky- for me, it deteriorates to the the point where the mouse will just randomly shoot across the screen, or will ignore my finger touch, even when nothing else is around it or on the palm rest. BUT, the kicker is that it does NOT start out like that.. but i cannot say if it is heat or time that makes it freak out..

 

I could put up with it not responding when it gets confused by the proximity of another body part hovering too close as long as it recovered right away. Even after I have corrected the situation there is a lingering effect.

 

The 213 bios really seems to help here...only time will tell if it's a fix or a placebo

 

I hope you mean your touchpad is not responding when it gets confused by the proximity of another body part hovering too close. And not some uhm……….. body part hehe

 

Touchpad? Keyboard? Or both?

 

i agree with you i can see a lot of people being happy if they see a new number
placebo effect

for me i believe it didn't change nothing
but i want to mention that i don't have problems with missing keystrokes nor touchpad (sometimes resizes)

 

Touchpad. I have had zero keyboard problems, but extreme touchpad problems. Cursor moves all over the place on the slightest touch, or will sometimes not do anything without pressing quite hard. The new bios (at least for now) has improved the TP immensely (but could be from the reboot/initial flash/etc.). But I've been on it for a few hours now and have not experienced any of the issues I have been.

 

We'll see how good this BIOS is a week from now. I'll be sure to use it as much as I can.

 

WOW! OMG! My touch-pad works! i feel like hugging it now! Sweet.

 

Well, trying out the 213, and lets hope it works...

 

213 is a bust for the touchpad, for me anyway.

While I was installing Synaptics drivers for the 300th time, I noticed while I was in the Synaptics settings window tapping the OK button to finish up that it was showing every tap ( the little white arrows that appear in the settings window ) and not finishing up.... tap... tap ...tap nothing happening. I think it is significant that the tap is obviously registered by the software but not reacted on.

I also noticed that I can fairly consistently cause the touchpad to fail by resting my palms on both sides of it for about 20 seconds. I don't mind that it fails while I am doing this but once my hands are removed it should resume normal operations.

It would be interesting for someone who has a properly working touchpad to try this and report back.

I hope 213 has solved the keyboard issue for those that need it.

Cheers

 

Morecoffee, mine does not do anything with both palms resting on the TP's sides. I am on 211 BIOS (from Asus's site), synaptics 15.1.22.2 with all advance features turned off.
OFF topic if you need to post a new topic in the ASUS G73 forum on Asus's site, quote and reply to an existing thread and it WORKS!
AMAZING the last post I saw B4 I did this was Back in november!
Hope this helps

 

Mine does not doing anything when I do the same thing also. I'm running 211 BIOS and newest touchpad drivers with scrybe.

 

My Touchpad works awesomely after the update to 213. I tried the palmrest thing and it still works i am amazed wow.

 

I'm using the new BIOS 213.
My keyboard goes on as before, still missing a few keys.

 

well, it didnt brick my lappy, havent really had a chance to test the keyboard much.

 

my touchpad started to fail