Posts: 1,173
	Threads: 54
	Joined: Mar 2008
	
	 
	
	
		as y6u can see frm the t6pc title, there*s a typ6, b4t the probem is 5 cannot type properly anyore all of a sudden. Soetmes 3etters are 05ss5ng or someti0es 3etters beco0e numbers. Gogle didn*t he3p 04ch I*ve tried pressing the nu3ock key, function+numl6ck, sh5ft+nu0lc2, sh5ft+function+n4mloc2 b4t they d n6t work and  am s4per p5ssed 6ff. Hep greaty appreciated Thanks
	
	
	
http://i263.photobucket.com/albums/ii130/c_fire004/imi1.png
avatar by Una
the other by xFire
 
	
	
 
 
	
	
	
		
	Posts: 2,657
	Threads: 113
	Joined: Mar 2008
	
	 
	
	
		:P i had this problem as well once. have you by any chance lf2 running in the background? in my case that caused it.
	
	
	
	
	
 
 
	
	
	
		
	Posts: 1,173
	Threads: 54
	Joined: Mar 2008
	
	 
	
	
		bloody hell. It worked zomg. I didn't even see the LF2 running as it's not on my taskbar... Only spotted it after switching on task manager! Cheers buddy
	
	
	
http://i263.photobucket.com/albums/ii130/c_fire004/imi1.png
avatar by Una
the other by xFire
 
	
	
 
Thanks given by:
		
 
	
	
	
		
	Posts: 232
	Threads: 7
	Joined: Jul 2008
	
	 
	
	
		From what I've seen, LF2 2.0 seems to automatically activate the number lock function for ease of gameplay. While in most cases this could be useful, it can cause problems such as these.
	
	
	
	
	
 
Thanks given by:
		
 
	
	
	
		
	Posts: 249
	Threads: 20
	Joined: Aug 2008
	
	 
	
	
		lolz, lf2 is so 1337 you automatically sp34k 1337 14ngu4g3 if it's running in the background
	
	
	
	
	
 
 
	
	
	
		
	Posts: 501
	Threads: 13
	Joined: Oct 2008
	
	 
	
	
		I remember I had the same problem I made a thread in some forum, someone posted a lf2.exe that fixes this problem.
~RtXaS~
	
	
	
	
	
 
Thanks given by:
		
 
	
	
	
		
	Posts: 478
	Threads: 21
	Joined: Apr 2008
	
	 
	
		
		
		10-21-2010, 06:53 PM 
(This post was last modified: 10-22-2010, 07:18 AM by SirFrog.)
	
	 
	
		So... then this is
~Solved
~Closed
PS: If anybody finds that .exe, throw me a PM and I'll put it here.
Edit: I think it probably was v.2.0a that fixed this. Not sure, though.
	
	
	
	
	
 
Thanks given by: