Articles

F2 and F12 keys don't work during bootup

Trust / Kb-2200 keyboard
May 6, 2009 at 03:35:06
Specs: Windows XP (SP3)

I just purchased the Trust KB-2200 Multimedia Scroll Keyboard. I had problems with it at first, but I fixed everything and the keyboard works fine now. However, there is one last problem I'm having.

When I boot up, the computer doesn't recognize the F2 (BIOS settings), F8 (Safe mode), or F12 (Boot menu) keys. I know this will come back to haunt me in the future. The Trust online tech support is basically a joke. Before I installed the new Trust keyboard, I had no problem using the F2 or F12 keys when booting up, but now they don't work. I want to know how to get them to work during bootup.

Note: The keyboard has an ''F'' key that toggles the Function keys between normal mode and special mode. In special mode, the function keys carry out pre-programmed actions instead of acting as normal function keys. I don't know if this has anything to do with the problem, but when in Windows, the ''F'' key is off by default and the function keys behave normally.

For the record, I have already tried just pressing the F2 key and also pressing the special F key and then the F2 key during bootup and neither method works.

Any help would be appreciated.

My computer setup is below:

Dell 531s Computer
Athlon Core 2-Duo CPU
4 GB DDR2 RAM
500 GB SATA hard drive
Windows XP (SP3)
I have already installed the Trust 15036_01 driver.

Thank you.

Dominick Fontana


See More: F2 and F12 keys dont work during bootup

Report •


#1
May 6, 2009 at 04:52:52

If the keyboard is a USB keyboard you may need to enter the BIOS (setup) screens and enable Legusy USB Hardware.

If you can't get into the BIOS with the new keyboard then reconnect the old keyboard and use it. Check the other settings in the BIOS screens to verify they are as they should be. Pay attention to the date and time.


Report •

#2
May 6, 2009 at 05:04:05

Yes, it is a USB keyboard. Okay, I'll do what you suggested right now and then report back here in a little while.

Thanks so much.


Report •

#3
May 6, 2009 at 05:55:14

No, unfortunately, it didn't work. I have Phoenix BIOS and there was no setting for Legacy devices. The only setting was for USB configuration and the 2 settings were enabled or disabled and of course, it was set to enabled.

But that made me think of something else.

I have a 7-port USB hub plugged into one of the rear USB ports on the computer. It only came with 6 USB ports: 4 in the back and 2 in the front. So I bought the hub. It is an AC-powered hub. So I have 3 USB devices plugged in the rear, plus the 7-port hub and the hub is plugged into an AC outlet for power. The 2 front USB ports are unused.

Maybe if I say what I have plugged in, it will help. Note one thing. To troubleshoot, I already did plug the Trust keyboard into a front USB port and it didn't fix the problem.

Here's my USB setup. All devices are USB. No adapters are being used.

4 Rear USB Ports:
1) Trust Keyboard
2) Mouse
3) Logitech RumblePad (gamepad)
4) 7-port USB adapter

In the 7-port adapter I have:
LinkSys WUSB300N Wireless Network Adapter
Dock for Seagate Free Agent removable hard drive (uses 2 USB ports)

4 unused USB ports on adapter and 2 unused ports on the front of the computer.

Sorry for writing so much, but I really want to solve this problem and thought this might have something to do with it.

Any help would be appreciated.

Thanks.


Report •

Related Solutions

#4
May 6, 2009 at 06:32:50

USB is not really fully supported in the BIOS. That means that anything involving USB devices prior to booting into Windows can be iffy.

I didn't ask if the keyboard is also a wireless model? If so, I am not sure you can get it to function in the BIOS screens. If not, then try connecting the keyboard to one of the integrated ports on the back and connect by itself.

Your issue is one of the technology not being fully backward compatible. I personally think PS/2 keyboards are superior for that reason. I am still using my Microsoft Internet Pro keyboard. It is PS/2 with a 2 port USB hub built in.


Report •

#5
May 6, 2009 at 07:22:41

Thanks for helping OtheHill.

No, it's not a wireless keyboard and it is plugged into an integrated USB port in the back; not into the hub.

I agree with you. I don't like the move towards all-USB. It's good for some things, like flash drives, but not for printers and such. Plus the connection is flimsy. The funny thing is my old keyboard was PS2 and it worked fine with a PS2 to USB adapter, but the brand new Trust USB keyboard has this one glitch.

Well, I'll keep this post up here and see if anyone else can think of anything, but thank you. I appreciate that you took the time to help me.


Report •

#6
May 9, 2009 at 01:18:33

Okay, I guess at this point, nobody is able to offer any further assistance. Here's one last thing to mention.

When I got the keyboard last month, I had the same problem at first, but I was still tweaking things on my new computer. Then all of a sudden, the computer DID recognize the function keys during bootup. I don't know what I did, but the keyboard worked fine. So it is definitely possible for the computer to recognize the function keys during bootup.

Unfortunately, I ran into an unrelated problem and had to reinstall Windows. Now, I have the same problem with the function keys during bootup.

The bottom line is it is definitely possible for the computer to recognize the function keys during bootup because it did during my initial installation of the new computer. However, I don't know what I did to make it work the first time and that's what I'm trying to figure out.

Any help would be appreciated.


Report •

#7
May 9, 2009 at 05:05:38

Did you auto update after the first install of the keyboard? Try the venders site for updated drivers. Again I agree with othehill on legacy devices. I use the ms 4000 wireless as default but I keep 1-2 ps2 keyboards and mice around jic.

WinXp Amd 64 3000 Msi Neo2 Platinuim 1 gig ddr 400


Report •

#8
May 9, 2009 at 05:20:58

I downloaded the latest version of the software from the Trust site, but that software is just to configure some of the multimedia keys on the keyboard. It uses standard Windows drivers and when I tried to update it, it said I had the latest keyboard driver.

The only thing I am thinking is that I have the Logitech RumblePad gamepad. In Device Manager, besides being listed under Gamepads, it's also listed as an HID Compliant Device under the Mouse and Keyboard entries. I guess because the gamepad can emulate the mouse and keyboard when playing games.

Could this have anything to do with the problem?


Report •

#9
May 9, 2009 at 05:36:39

Installing Windows shouold have nothing to do with the operation of a keyboard while still in the POST screens or the BIOS.

Once you pass a certain point Windows starts to boot, even though it may not appear to do so. Hitting F8 for instance to choose the Windows mode to boot to is not part of the POST process.

Striking the proper key to enter the BIOS is.

Look at it this way. What can you do with a keyboard BEFORE you install an OS?


Report •

#10
May 9, 2009 at 06:02:53

That makes sense and is a good way to look at it. So the Rumblepad couldn't be interfering with the keyboard because the Rumblepad drivers aren't recognized during POST, right?

Also, thanks for the info about the F8 key.

And yes, I understand that installing Windows has nothing to do with the operation of the keyboard during POST or BIOS. The point I was making was that it used to work during POST/BIOS but after I reinstalled Windows, the Function keys don't work when booting up. The point was that I don't think it's the keyboard's fault, so to speak. Something happened after I reinstalled Windows that caused the problem I'm having now.

Also, I don't get a keyboard error when booting up, so the system does recognize that the keyboard is attached. If I unplug the keyboard, the system won't boot and gives me a Keyboard Not Found error. I'm just bewildered that it recognizes the keyboard, but not the function keys during bootup.

If I create a bootlog, will that help?


Report •

#11
May 9, 2009 at 06:52:04

Are the F* keys programmable? If so, that is the problem. The BIOS is hardwired to recognize some keystrokes and if those keys are programmable the BIOS may not longer be able to pickup on them.

As far as the keyboard functioning during the Windows boot mode and beyond I would guess the problem may have something to do with the gamepad. This could be especially problematic if both are on the same USB controller.

USB controllers usually serve 2 USB ports, sometimes three (card readers). If you are connecting both those devices to the same controller try moving one. I suggest moving the keyboard. Use one of the integrated (on case mounted) USB ports on the back.


Report •

#12
May 9, 2009 at 07:39:30

Well, yes, the Function keys are programmable, or I should say pre-programmed with additional functions. I mentioned that in my first post when I described the problem. Here it is again:

Note: The keyboard has an ''F'' key that toggles the Function keys between normal mode and special mode. In special mode, the function keys carry out pre-programmed actions instead of acting as normal function keys. I don't know if this has anything to do with the problem, but when in Windows, the ''F'' key is off by default and the function keys behave normally.

I already tried your suggestions. I unplugged everything, except the keyboard, and then booted up numerous times with the keyboard in each different USB port, but still had the problem.

Also, I already gave my USB configuration, showing what was plugged where. I'll post it again so we have all the pertinent info in one location:

Here's my USB setup. All devices are USB. No adapters are being used.

4 Rear USB Ports:
1) Trust Keyboard
2) Mouse
3) Logitech RumblePad (gamepad)
4) 7-port USB adapter

In the 7-port adapter I have:
LinkSys WUSB300N Wireless Network Adapter
Dock for Seagate Free Agent removable hard drive (uses 2 USB ports)

4 unused USB ports on adapter and 2 unused ports on the front of the computer.

This is baffling, huh?


Report •

#13
May 9, 2009 at 07:48:37

Perhaps you need to have those keys set to the default settings. Depends on where the programming is being done. I could imagine it could be on board the keyboard itself.

Do you even use the programmable keys?

If the keyboard has worked in the past it must be either a software or a programming issue.

One thing I never do is allow hardware updates from Microsoft. For that reason I do NOT use auto updater. Instead I manually download and use Custom. Your problem might relate to an update for the hardware.


Report •

#14
May 9, 2009 at 08:26:42

Actually, the Function keys aren't actually programmable. There's an F buttton next to them. Normally, they act as regular Function keys. When you press the F button, there is an onscreen icon and then the 12 Function keys are preprogrammed with MS Office commands, such as, New, Open, Save, Spell Check, etc.

Concerning Windows Updater, I have it set to notify me, but I choose what to download and what to install. Mostly, I install the security updates.

It probably is a software or hardware conflict, but how can I figure out what it is? Would a bootlog file help?

Thanks.


Report •

#15
May 9, 2009 at 08:32:09

I wouldn't be able to get much from it.

Did that keyboard come with a PS/2 adapter by chance?


Report •

#16
May 9, 2009 at 08:39:32

No, it didn't come with an adapter. It's USB. I have a PS/2 to USB adapter, but not a USB to PS/2 adapter. Plus my computer doesn't have any PS/2 ports on it.

Report •

#17
May 9, 2009 at 08:45:15

OK, then that won't work.

How does the F* key you mentioned that allows the keys to function in the alternate mode work? Does it lock down or something or just once for regular & again for alternate mode?

What I am lead up to is if the programming is onboard the keyboard then whatever mode it was last in may stay set that way until changed.


Report •

#18
May 9, 2009 at 08:58:52

It's a toggle switch. It doesn't stay down. It's a soft key. By default whenever I boot into Windows, it's always automatically off. When I press it, it doesn't light up, which is a mistake. It should have an imbedded LED, but doesn't. Instead a big F appears in the system tray to show it is active. Then, when you press it again, it goes back to normal.

You made a good point that it might remember its last state, except it's always off when I power down. Plus, when experimenting while booting up, I tried hitting the special F key first and then the F2 key and it still didn't take me into the BIOS settings.

And that's the story, Jerry. Don't know if you remember that commercial. ;)


Report •

#19
May 9, 2009 at 08:59:46

The only possibilty is a BIOS setting. As OtH pointed out, drivers are for Windows...they have nothing to do with POST. Check the BIOS again. There may not be a "legacy devices" option but it *may* be listed as something else such as "USB support", "Onboard USB", "USB keyboard support", etc

Report •

#20
May 9, 2009 at 09:06:11

I have Phoenix BIOS and there was no setting for Legacy devices. The only setting was for USB configuration and the 2 settings were enabled or disabled and of course, it was set to enabled.

I double-checked every setting in the BIOS and there was nothing else that appeared relevant.

This is maddening. haha As a matter of principle, I have to figure this out.


Report •

#21
May 9, 2009 at 13:33:18

What model trust keyboard is it?

WinXp Amd 64 3000 Msi Neo2 Platinuim 1 gig ddr 400


Report •

#22
May 9, 2009 at 13:40:02

Sorry should have read 1st post. 2200 lol 2.5 inch screen not so good on c/n lol

WinXp Amd 64 3000 Msi Neo2 Platinuim 1 gig ddr 400


Report •

#23
May 9, 2009 at 18:50:41

Here's the link for the keyboard:

http://www.trust.com/products/produ...


Report •

#24
May 11, 2009 at 08:33:03

Well, I guess nobody here can help me. Thanks to those who tried. I'll get to the bottom of this (I hope) and then as a courtesy, I'll post here how I solved the problem, so you can help someone else with the same or a similar problem.

Thanks.


Report •

#25
May 13, 2009 at 15:04:30

Sorry dan was offline a while. Did you try setting the bios to default settings? If not try defaulting with both keyboards hooked up. The reason I brought up drivers before is sometimes keyboards have an onboard ic and the oem utilities allow access to settings for that ic.

WinXp Amd 64 3000 Msi Neo2 Platinuim 1 gig ddr 400


Report •

#26
May 14, 2009 at 03:32:33

What I'm going to do tomorrow is try the keyboard on my friend's computer. If it works there, then I'll know it's something with my configuration. If not, then I'll take it from there.

Report •


Ask Question