Repeat as needed: If you are building a numerical keypad or custom gaming keypad, you'll have to keep it all straight: It's probably worth making a chart or some such, to keep track of where you'll be wiring up your buttons.īut in my case, all I had to do was manage to find the two connections for one key: F1.į1 routed to the far-right pad in the first group, and the fifth one in from the left of the second group. Mark the two spots where the line hits the circuit board. Then you can trace the squiggle back to the circuit board: I recommend literally tracing, using a thin marker. Just find the key in question and see where it hits the matrix. It would be pretty difficult to figure out which pair was which, if not for the handy map provided by the two flexible matrices that live under the keys. And a different combination of pads are activated for each key press.
This will either be very simple or quite tricky, depending on how your keys are stuck into their housing: they might all lift up in one piece, or they might eagerly leap away and try to escape.īasically there are only a few pads on a small circuit board that manage to figure out which key is being pressed because two of the pads get a signal at once. Go read this, so you know how keyboards work: Īnd here's an 'ible by randofo that makes it even clearer įind a sacrificial keyboard, and pull all of the screws out of the bottom.Ĭarefully lift the keys away from the flexible plastic with the spaghetti tangle of circuit tracings. Thin permanent markers, volt meter (optional) So I assumed that the OS was smart enough to accept the F1and then ignore a "stuck key," and I decided that my silly plan was worth doing. in short, no ill effects from holding down F1. The OS loaded fine, the browser opened fine no "Help" pop up. I watched as the error popped onto the screen, then vanished. Plug in a USB keyboard, hold down F1, start PC, keeping F1 pressed. Instead, a dim light-bulb flickered above my head, and I performed the following test: Of course, some of the warnings that show up during startup can be turned off in the BIOS (like the "keyboard error"), but my BIOS had no option for "don't worry about the CPU fan." If I knew more about the world, I may have been able to grab the two unused wires from the CPU fan swap, and add a resistor or some other little bit of hardware that would fool the motherboard.
so my kiosk would sit there waiting for someone to press F1, and would be the lamest kiosk in history. So on startup, the bios would report a failed CPU fan, and stop at a prompt: F1 to continue, F2 to enter startup. The problem: the original fan was a four-wire model that talked to the motherboard, telling it soothing things like "I'm working." The replacement one I had on hand was a two-wire fan that refused to discuss anything with the motherboard.
#Im tge only one keykey Pc#
The donor PC featured a very tall heat sink/fan that just wouldn't fit, so I had to swap it out for a smaller one. The problem is, I'm building a publicly-accessible PC kiosk (mouse only, no keyboard), and the components are squeezed into a rather small space. Well, you are absolutely right (though calling me names was kind of mean). " Why not just fix the error, stupid?" you might ask, " These errors are there for a reason!"
0 kommentar(er)
