geekhack
geekhack Community => Keyboards => Topic started by: JohnMD1022 on Mon, 07 December 2009, 12:15:27
-
2 IBM Space Saver keyboards (Part No 1391472 1397681) do not map properly.
Daskeyboard Professional: When connected to the system, the PC will not boot.
Any thoughts on these 2 problems?
-
What exactly do you mean by "not mapping correctly"?
-
so far i ran 2 model m, one AT->PS/2 and one PS/2, on windows 7, also a unicomp customizer usb, and a abs m1 usb, so far they work normally, both in the boot sequence and in windows 7 itself, i use windows 7 ultimate, the version released in october
Edit: After thinking for a bit, i remembered something, I did encounter a temporary problem with my IBM Model M 71G4544 after leaving plugged overnight, i came back and it wasn't working, rebooted, the keyboard registered until boot sequence started to load windows, then failed, I could not get it to work, i left it there for a week, it crossed my head that it could be a ground problem or something like that that accumulated over night, because the board was working find the night before, I don't use hibernate or sleep, but i do use auto shudown of monitor and start monitor on keyboard click
then a few weeks after, I opened the board to try a few things, first thing i did was unplug the ground from the keyboard backplate, rubbed the two wires on the backplate, then scew the ground back on, first minute there was no change, I typed a few keys while thinking of other things to change, then all of a sudden it started working, the only change I had done was the ground, but i can't be sure if thats what fixed it
-
Daskeyboard Professional: When connected to the system, the PC will not boot.
I've had this happen with a PS/2 Kinesis Contour used with recent model Thinkpads (T60 and a forgotten model) within the last year. To what machine are you connecting the keyboard?
It appears to me to be a power draw issue. With a generic USB-PS/2 adapter, the Thinkpad woudl boot, but the keyboard failed to send modifier keys, such as shift, ctrl, alt, etc. Only the letter key was sent unless the timing was slowed very much.
Ctrl ... pause ... S - would save.
Shift ... pause ... A - would capitalize.
Search these forums for "blue cube" USB-PS/2 adapter for the solution that worked for me. I'm typing problem free on a Kinesis + blue cube + Thinkpad now.
-
64 bit??
I doubt that that's making much of a difference, but for the record, I've been running 64bit Windows 7 on several machines since this time last year. No problems with any keyboard I've tested it with.
The Das problem sounds like generic "Should have bought a Filco" syndrome, the Space saver thing is a bit vague and needs a more detailed explanation.
-
Your mobo could be on the way out.
-
Wouldn't jump to that conclusion so quickly. The Das causes that problem for loads of people. Fortunately they will take them back and give a full refund.
-
I suspect that power draw is indeed the issue (If it were just the DAS, it likely wouldn't be). Get a blue cube.
Having said that, I have ran 1391406's an M13 and a Wang 724 on Win7-64 without a single problem. All of them were on native PS/2. The motherboards, tended to be higher-end (P45, P35 and currently on an NF-570 chipsets).
I wonder if it's the chipset that defines the available current on PS/2 or the Manufacturers implementation of the board?
-
I need some blue cubes for my keyboards.
-
Why not use the PS/2 ports?
-
I need some blue cubes for my keyboards.
Then it might be a good idea to buy some. (If you'd need multiple ones at once, I'd rather go for the trusty Belkin instead though - I don't think two Blue Cubes will fit two adjacent USB ports.)
Why not use the PS/2 ports?
#keyboards > #computers, I guess, same here... (Plus it's nice to dig out a less-used board spontaneously and use it for a bit sometimes.)
Pity we only come with two hands, non-upgradable...
-
Why not use the PS/2 ports?
The PS/2 ports in some of my machines do not always output enough power at startup. Like I said, it's good to use USB as a last resort.
-
64 bit??
I did my tests on 64bit Win7 yes, there was no problem so far, even in virtual pc or vmware, I haven't had any problems so far, new win7 shortcuts work too
Edit: I did encounter a temporary problem with my IBM Model M 71G4544 after leaving plugged overnight, i came back and it wasn't working, rebooted, the keyboard registered until boot sequence started to load windows, then failed, I could not get it to work, i left it there for a week, it crossed my head that it could be a ground problem or something like that that accumulated over night, because the board was working find the night before, I don't use hibernate or sleep, but i do use auto shudown of monitor and start monitor on keyboard click
then a few weeks after, I opened the board to try a few things, first thing i did was unplug the ground from the keyboard backplate, rubbed the two wires on the backplate, then scew the ground back on, first minute there was no change, I typed a few keys while thinking of other things to change, then all of a sudden it started working, the only change I had done was the ground, but i can't be sure if thats what fixed it
-
I added this to my previous post above, but adding it too here, as it might be relevant
After thinking about, I did encounter some odd problem, I had used my keyboard at work on xp, worked fine, brough it home, used it on win7, then
I did encounter a temporary problem with my IBM Model M 71G4544 after leaving plugged overnight, i came back and it wasn't working, rebooted, the keyboard registered until boot sequence started to load windows, then failed, I could not get it to work, i left it there for a week, it crossed my head that it could be a ground problem or something like that that accumulated over night, because the board was working find the night before, I don't use hibernate or sleep, but i do use auto shudown of monitor and start monitor on keyboard click
then a few weeks after, I opened the board to try a few things, first thing i did was unplug the ground from the keyboard backplate, rubbed the two wires on the backplate, then scew the ground back on, first minute there was no change, I typed a few keys while thinking of other things to change, then all of a sudden it started working, the only change I had done was the ground, but i can't be sure if thats what fixed it
-
The 71s I believe have that funky pressfit connector to the controller board like the 42H - a common failure point.
I don't think so.... I assume this is the rubber dome Model M we're talking about?
-
OP has disappeared.
Yeah, his computer won't boot....lol
-
Not mapping correctly = press a key and get a wrong character... e.g., press 'm' and get '0'
Both Space Savers are PS/2
Win 7 64 bit
-
Not mapping correctly = press a key and get a wrong character... e.g., press 'm' and get '0'
Both Space Savers are PS/2
Win 7 64 bit
That's the numpad feature of the keyboard. Hit Num Lock, then try again.
There might also be an option in your BIOS that turns on Num Lock during boot--disable that one.
-
Space Savers + blue cube made no difference.
These on an Intel E8400 machine, MSI P35 MB.
The Das works on that box but not on a AMD Phenom II X3 720 machine with BioStar 790 GX MB
-
Did you try Shift+Scroll?
-
Turning off Num Lock in the BIOS solved the Space Saver problem.
Thanks for the suggestion Mnemonix... :)
-
Just to be clear the IBM Space Saver can toggle the embedded numpad at any time with SHFT+SCRLK. On mine I don't need to touch the BIOS.
No DIP switches are needed :biggrin1:
But I like my DIP switches
-
I like the ones on my printer.
-
I like the ones on my printer.
They still make papyrus for it?
-
Yes they do. Then still make the BC-02 cartridge for it too. And it's a LOT cheaper than a black cartridge for a new printer.
-
Honestly this happend to me too with my new computer that has win7 64-bit.
PS/2 mice and keyboard just would not work. I tried turning off the computer and plugging it in at that point and that did the trick for me :)