Cursor beam doesn't move with arrow keys in text areas

I've experienced this on various websites, forums, etc.. where I'm typing into a text box. (Oddly it's working here just fine).

Since I find it much faster to move the "beam" cursor around with the arrow keys (and CTRL+Arrow key to jump over whole words), I frequently use that instead of the mouse to reposition the cursor, handy if I want to go back a few words and add or change something.

However on many sites, using the arrow keys fails to move the beam, yet the actual input position does change.

For example, I'll press "CRTL+Left Arrow" a few times to jump back three words. On the screen the beam stops flashing but stays put, yet if I start to type the typing starts where the beam should have ended up if it moved properly.

Follow me?

Any suggestions on fixing this would be appreciated.

Thanks.

I think that the cursor you are describing is a function of the video driver, check for an update and/or uninstall and re-install the one you are using.

Hmm.. I do have a hacked up nVidia driver so my CAD program will see my card as a Quadro and not a GeForce, but I think the problem started before that. It doesn't happen with all sites, mostly VB4 forums (this one is working fine as do most, if not all VB3 forums). It also doesn't happen in any other application. (The same webpage can work fine in Firefox but not in IE).

Does it only act up in the vb4 post editor area or are search fields impacted too?

Just tried it on the Crackberry site - it's only doing it in the post editor field. The search field at the top of the same page works fine.

Also to note, after 3-5 seconds the cursor does move to the intended spot on the screen. However if I start typing before the cursor has caught up, the typing will start from the intended spot.

Working fine in this text box.

Are you having this issue in IE8, IE9 or IE10?

Both 32 and 64 bit versions of IE9, Windows 7

If you want to got to the trouble of going back to IE8 - just for a test - then maybe going back to IE9 might fix things.