4
2
I have a few bare-bones systems running legacy software on creaking hardware. I want to be able to automate a lot of tasks by using auto hotkey scripts for tasks that currently, must be performed manually. I really don't want to install any software on these machines, and in some cases can't (as they are already maxed out on resources, or running Linux builds, or running weird stripped down Windows versions from the stone age)
I need a solution whereby I can receive keystrokes on a machine in real time without installing any software on it. However, requiring drivers or software on the machine sending keystrokes is no problem.
That's the problem I need to solve. Given the restriction on the receiving machine, I can only imagine that a solution might be along the lines of the input being via something like a Bluetooth dongle or USB receiver that registers as a keyboard, but is actually receiving keystrokes originating on another computer. If anyone knows if such a piece of hardware exists, could you post below? Or alternatively, any other solution that meets the goals.
What about a bluetooth keyboard and receiver? Are you avoiding that? You'd just have to install a driver for one of those. – Datarecovery.com MK – 2015-07-07T16:54:25.167
Can you get a bluetooth keyboard which accepts external keystrokes from a second device? – Some_Guy – 2015-07-08T07:59:48.313
I posted an answer since it got too long – Datarecovery.com MK – 2015-07-08T16:08:12.367
BTW, I was in college during the computer stone age (before bluetooth), and a researcher needed essentially what you describe. He built a platform that sat on top of a keyboard, with a solenoid-activated plunger for each key. He then sent the typing instructions to his device from another computer. I'm guessing that wouldn't be a practical solution for you. – fixer1234 – 2015-07-14T17:00:02.553
hoping not to have to build anything, yeah haha. How's the question now do you think? – Some_Guy – 2015-07-14T17:05:11.983
I read the question multiple times but I just don't get it, if you can plugin a bluetooth dongle, why not just plugin a usb keyboard? – Chris.C – 2015-07-14T17:35:21.737
https://www.pjrc.com/teensy/td_keyboard.html – ssnobody – 2015-07-15T06:03:02.070
@Chris.C: the objective is to send the keystrokes from a script on another computer to automate some tasks. Without the ability to load software on the receiving computer, one suggested approach is to make the computer think it's getting keyboard input by routing input through a keyboard receiver. – fixer1234 – 2015-07-15T06:15:17.013
@ssnobody, do you know if that chip can accept keystrokes in real-time, or just preprogrammed? Also, seconding fixer, please respond as an answer :) – Some_Guy – 2015-07-15T08:57:17.250
@Some_Guy I dont really feel the problem here to be honest. If you have rights to access those computers you should be able to connect to them remotely. So why linux
ssh
and windowspsexec
are not a solution? – mnmnc – 2015-07-15T09:41:32.733@Some_Guy: 1) A dongle might not already have a native driver, which would imply loading a driver for it. Is that acceptable? 2) You don't describe the nature of the tasks you want to perform. Could these be performed by actions after mounting the hard disk during a live Linux session (boot liveDVD or RAM-resident distro on the receiving machine, mount the hard disk, do the actions on it)? This approach wouldn't even require the keyboard fake. You could use remote control software or shell commands and a LAN connection without having to install anything. – fixer1234 – 2015-07-15T18:38:15.557
2I appreciate the comments asking me to create an answer, but I wanted to seed a solution without spending the time to create a good answer. I'm sure you'll agree that a comment pointing you (and others who might be willing to write a more complete answer) in a workable direction is better than nothing. Personally, I might connect an Ethernet module and have it become a echo client over the network rather than serial or bluetooth as some others are suggesting but either way it should resolve your problem. – ssnobody – 2015-07-15T21:37:50.823
I really appreciate your contribution, thanks :) – Some_Guy – 2015-07-15T21:50:53.533
I might be being dumb here, but why don't you just SSH or RDP into the machines?
If you have scripts you can set them to run etc.
I must say personally I would suggest looking at resolving the real problem of ageing machines etc, you could clone your machines onto new machines in a virutal environment, therefore removing all this complex workaround and have a better environment.
Otherwise you are just going to constantly have to come up with more work arounds as everything get more and more redundant and old. – David Golding – 2015-07-17T09:48:07.853
Because I want a magic bullet that allows me to remote into any computer running any platform anywhere, where all it requires is a keyboard input, so I can conquer the world! – Some_Guy – 2015-07-17T12:14:54.913
But in all seriousness you may well be right. I could solve almost all my problems that way, but it would take some time to get it all working, and could well be very very buggy. If there was an out-of the box, or simple solution that someone could point me to I would have liked to just buy a thing and get going with it, for ease, and for lack of maintenance. – Some_Guy – 2015-07-17T12:17:14.847
There's also the fact that updating these systems is not really in my control, unfortunately. – Some_Guy – 2015-07-17T12:18:31.027
Added an answer with an out of the box solution, though it may be overkill for your application. – ssnobody – 2015-07-20T04:01:44.923
Were you able to attempt usage of a remote KVM? Are there any issues still left unresolved? If one of the answers worked for you, you have the option to accept it.
– ssnobody – 2015-07-29T21:42:05.573