I had fabricated a keyboard cable before the computer's arrival. As I recall, it uses a four-conductor phone handset cable as its keyboard cable. This was the same cable used to connect a telephone handset to its base. This is different than the cable that connected the base to the wall. All this would likely be quite foreign to anyone 45 or younger!
When I powered on the Kaypro II, I immediately noticed a few problems.
First, the diskette drive motors would spin, but the red "Read" LED on the floppy diskette drive never lit up, and the floppy diskette Read-head did not seek. That was not good. These boxes boot up quickly when everything is working with an inserted diskette. Even if the diskette is incorrect, you hear the Read-heads seeking and not finding what they want. This box did nothing; not great. The previous owner had photos of it booted into CPM, so I thought something might be unseated on the motherboard or a cable disconnected in transport. Disconnected or unseated components are common with older systems that have been shipped.
I already had the machine somewhat disassembled, so I started removing some of the connectors and used my voltmeter to check +5 and +12 voltages. Everything seemed fine, and when I plugged things back together, it started working. A likely cause was some oxidation on a connector that got worn away by plugging and unplugging things.
I later determined that if the box had been "on" for a while, it would generally boot CPM from the boot diskette but not always. If the box had been powered down for a while, it would not. Clearly, the diskette drive was somewhat marginal and affected by temperature. This is not uncommon with older machines like this.
Second, I noticed the keyboard wasn't working. I noticed this when it would boot CPM to the A: prompt, and when I entered the "DIR" command, no keystrokes would register. I surmised that the keyboard was functional, as it would make a little sound from an internal speaker contained in the keyboard when you press a key. That told me the microcontroller that decodes the keyboard keys was working, but the keystrokes were getting lost on their way to, or once on, the motherboard. I believe the protocol between the keyboard and motherboard is serial RS232, so something was likely broken in that path.