efb@suned1.UUCP (Everett F. Batey II) (03/15/89)
Well, here it goes .. again. We were persuaded to buy into the DEC DEPCA
Ethernet interface. We still run ver 1.x PCFS / PCSA. Windows never worked
as we only had one interrupt, free. Now with the DEPCA and the HP DECNET
patch in place, even without EVER making a decnet connection the NUMERIC and
AUXILLIARY keypads, BOTH take on unpredictable meanings, standard cursor keys
take on numeric values ( between 0 and 9 ).
First problems became conspicuous when REFLECTIONS was installed. Removing
it from the SHELL in config.sys seemed to reduce the problem's frequency.
It does NOT go away. We noticed that the HP DECNET patch, at least allowed
us some control over our keyboard in the presence of the DEPCA ( E1 artwork ).
We assume the HP patch cures contention over keyboard management addresses.
PCFS installs one or more TSRs, keyb{oard}, or the like .. seems like
nothing is well behaved and as usual DEC got outside its league fooling
with non-IBM / non-DEC / ANY PCs. Has any one else confronted the drifting
num / aux keyboard map with HP or other AT clones?
Any suggestions on how to get windows on a PC with network file and host
access and not TRASH the PC and its ability to run PC programs? Have I
just asked a series of MUTUALLY exclusive questions ?? Truly frustrated,
and badly conned .. /E/
The_Main_User (So Calif SunLUG | Vta-SB-SLO-DECUS)
efb@elroy.JPL.Nasa.Gov sun!tsunami!suned1!efb efbatey@nswses.arpa
805/982-5881 (A/v: 360) Res: 983-1220 (Ans)
Statements, Opinions ... MINE ... NOT those of my US Employer
--
The_Main_User (So Calif SunLUG | Vta-SB-SLO-DECUS)
efb@elroy.JPL.Nasa.Gov sun!tsunami!suned1!efb efbatey@nswses.arpa
Statements, Opinions ... MINE ... NOT those of my US Employer hudson@dalcsug.UUCP (Bruce A. Hudson) (03/16/89)
I am not sure if it is appropriate but this sounds a lot like a
problem that I get running the SETHOST utility from DECnet-DOS. What
seems to happen is that the keyboard gets caught in a shift-lock state
where all the arrow keys enter as numerics. It only seems to happen
during periods of keyboard inactivity -- never while I am actually
typing.
If this is the same problem, the "fix" is trivial. Depressing and
releasing the shift key restores the PC to its normal function. If
anyone out there has a fix that prevents it from happening, I would
be interested in hearing it.