the 'Fn' key make me type numbers and symbols instead of letters when I want to.
However, it looks as if the 'Fn' key was stucked.
I can't type the 'i', 'u', 'o', and 'p'. All I get are numbers and symbols.
How do you reset the 'Fn' key? I have tried restarting the laptop with no avail.
Actually is my wife's Gateway laptop.
Fujitsu fn key always on
Fujitsu fn lock - Best answers
Keyboard typing symbols instead of numbers - Best answers
I had the same problem, with the fn key and got so flustered. On the lower part of my computer to the left of the key pad there was a little lock with an arrow pointing up on it and it was something I hadn't noticed before. Well I sat and just looked at the keys and kept hitting on them one at a time till I finally hit the right key shift and num lock key several times and the lock with the arrow went out and my computer was working just fine. I hope this will work for you
I have a fujitsu siemens and even though many people suggested pressing numlock and scroll lock at the same time it didn't work for me since num and scr lock ar on the same key one of the latter posts caught my attention and there are two types of locks...the one where you hold fn and numlock and where you press both at the same time...regrards and thanks for help anyone hope this helped someone with a slighter delicate problems just as mine...CHEERS!
On my laptop (HP) it's FN + F8 pressed at the same time. It seems as if every brand of laptop is different, so look for the little (teeny tiny) picture that looks like the keys of a calculator on one of the function buttons and press it along with fn itself. Hope this helps!
The NUM_LOCK is activated/deactivated with LEFT_SHIFT + NUM_LOCK button
The scroll lock function can be triggered in the On-Screen Keyboard. This application is normally found in Start -> Programs -> Accessories -> Accessibility
Clicking on the 'scroll lock' in the On-Screen Keyboard should have the same function as pressing a physical scroll lock key.
Regarding the Symbol's on any laptop, I got it fixed after changing the Regional Settings "English to United States", earlier it was on English United Kingdom. So, try ur luck and keep updating the post.