Like I said earlier, a *lot* on my plate. I didn't forget -- honest.
I am running slackware-current on he laptop now. It solved the keyboard problem in one swell foop. Which led to the exposure of another problem.
I could boot and run using a USB stick, but I deemed that as a suboptimum solution. I noted I didn't get any kind of elilo configuration options when I installed, unlike when I installed the pre-15.0 current for another new machine, so I tried reinstalling slackware64/a/elilo-3.16-x86_64-16.txz but it didn't change anything for either good or ill. I tried this, tried that, and tried the other, but I wasn't able to access eliloconfig through the command line, which, or locate. As my next (and, as it turned out, my last) attempt at solving this problem I copied the directory slackware64/a/elilo to /root and rebuilt the package. I reinstalled it, called eliloconfig, and saw the elilo configuration prompts. It works now. I can boot Slackware from a cold start without the USB stick. It takes a little tinkering to get it to boot Windows, but that's okay.
I did get the MD5 checksums from the released package as well as the rebuilt one
here they are:
Code:
Delivered MD5 checksum is 89c769f28e4cf4acf23f2362cb8c2aac
Rebuilt MD5 checksum is c1ad4ac037156cb5e318a2839e503344
A caveat: I only dug deep enough to find the what. I didn't go looking for the why.
I tip my cap to all that aided me in this endeavor and can now declare it "solved". Thanks to all.