Text Overwriting in Windows Driving Me Nuts

[Edwe]

As I usually consider myself to be at least reasonably knowledgeable about computers, having grown up around them and being able to program in 2 languages, I am somewhat embarassed to ask this question, but I cannot for the life of me figure out what is causing this problem (if it is a problem to begin with, rather than a setting).

In nearly all applications on my new PC, running Windows XP SP2, text gets overtyped by default, instead of inserted, when I move the cursor between bits of text and start typing. This is the kind of behaviour I expect to see in an application such as MS Word with the "Overtype" option enabled, but this is not the cause.

I even get the problem while typing a post for this forum using Opera 9, so I assume it is some kind of universal Windows setting that I am unaware of. I know that I am able to toggle overtyping with the insert key, but as soon as I stop typing for a while, my PC resumes its overtyping behaviour. I even thought it may be a virus causing the problem, but the latest update of McAfee doesn't find anything.

Can somebody please tell me how to disable overtyping, as it is driving me completely nuts.

 

[werner]

the insert button on your kb is responsible for this behaviour. there isnt a universal windows setting to control this.
try another kb.

 

[w1z4rd]

push the "insert" button on your keyboard

What he said Pushing "Insert" toggles between overtype and insert.

 

[bekdik]

try pressing the ins key, this should toggle the setting. also check that the regional settings match your keyboard. also do a google for an answer

 

[feo]

He jus said it comes back after a while even if he does press it..

 

[w1z4rd]

Then he might be pressing it accidently? Looks like this chap had the same problem: http://www.wirelessforums.org/alt-comp-hardware/ins-key-toggle-1688.html

Might be a dodge keyboard?

 

[werner]

What he said Pushing "Insert" toggles between overtype and insert.

stop reading my first instinct posts before I have had a time to edit them so they make sense you caught me red-handed, hehe

 

[ld13]

Youre supposed to be able to turn Overtype off by:
Turning Num Lock OFF.
Then pressing the Numpad 0/Ins key.

Then turning the Num Lock ON again, if you want.

This i how i do it. Unless its some other keyboard problem or something you have...

 

[werner]

Youre supposed to be able to turn Overtype off by:
Turning Num Lock OFF.
Then pressing the Numpad 0/Ins key.

Then turning the Num Lock ON again, if you want.

This i how i do it. Unless its some other keyboard problem or something you have...

so....in laymans terms.....you're pushing the INSERT button....

 

[mh348]

Check if the "insert" key is stuck

 

[bekdik]

Another thought - if you are on a notebook, your numlock key might be locked, try Fn Numlock to clear it.

 

[Edwe]

I know that I am able to toggle overtyping with the insert key, but as soon as I stop typing for a while, my PC resumes its overtyping behaviour.

By stating that I meant to imply that I had already tried all variations of the accidental insert key press. I wouldn't be posting here if it were as simple as that. I'm using a cheap Gigabyte keyboard, so the keyboard may be faulty. I don't seem to encounter the problem with a more expensive Microsoft ergonomic keyboard.

 

[werner]

By stating that I meant to imply that I had already tried all variations of the accidental insert key press. I wouldn't be posting here if it were as simple as that. I'm using a cheap Gigabyte keyboard, so the keyboard may be faulty. I don't seem to encounter the problem with a more expensive Microsoft ergonomic keyboard.

ok, there are two possiblities here.
1) one of the keyboard is usb and the other is ps2. usb has a limit of 6 characters pressed at a time, then it goes spastic. you may just be doing it fast enough to trigger $spastic$ mode

2) the gigabyte keyboard matrix is badly designed. think of an 8x8 grid (in reality it is more like 12x8 but whatever...). hitting a key causes an x and a y axis to touch in a certain place, thereby triggering a keystroke which the keyboard encoder passes to the machine as the required symbol. if e.g. x2y3 is already pressed and then x2y4 is pressed, the keyboard encoder is meant to work around this and show the pc x2y4. i;m thinking the gigabyte keyboard is getting messed up trying to do this correctly.

check this url
http://www.extremetech.com/article2/0,1697,1610434,00.asp especially the "ghost key" bit

throw it in the bin.

 

[Edwe]

Thank you for the link, Werner. THe keyboard is PS/2 and no obvious ghosting is happening, but that's the most likely suggestion so far. I think I'll get rid of the keyboard and see what happens with a new one. Thank you for all the suggestions, everyone.