![]() I'm sure it's one of the more modern commands but it just shows there's still "buried treasure" out there. When running a script on a remote computer through a program as psexec (or beyondexec (it is necessary, specially when sending strokes to a program launch by the script with a Run() function, to use ControlSend() or other ControlXXX functions to directly communicate with the control. Unix is amazing - I've been using it for scripting etc since 1985 (on and off) and I've never come across the expect command. Wow, the "expect" command looks very interesting! I have to go through that man entry thoroughly to get a grip on it.I'll have to investigate this one further. Hmm.I never thought about whether killing a process would result in the loss of an application software license - I was only concentrating on the fact that it frees up a SCO license.(To be honest it's a while since I've seen the error message so I can't recall whether it looks like an OS message or not.) Once started, ELinks allows a user to do almost all it is capable of by means of its menu. We have 40 SCO user licenses and 40 application software licenses, so I guess we run out of both.I can currently trace a pid on unix back to a user terminal.I'm not sure what a distributed session on a local server is, but I think the answer would be "no".Send keystrokes to a specific window using PowerShell. Does anybody have any suggestions for how I can send keystrokes to an existing process and have it react to them? Can a process take input from two sources (i.e. AFAIK keystrokes (whether invoked from any sort of Send-Keys (SendKeys in WinAPI) method, always go to the active window. I have tried coming at this from a few different angles but keep hitting dead ends. Then if I could just keep sending the "end" string to that process until it eventually logged out my problem would be solved. I need to send up and down arrow keys to another app with VB. I could have a continuously running script that uses a "finger" command or something similar to detect sessions that have been idle for say an hour. Every screen and every menu is backed out of by simply pressing a Function key which sends the string "end" and a carriage return to whatever field is awaiting input. The solution is so tantalisingly close and yet, I suspect, so far. ![]() Currently I have a crude method of killing any sessions before the overnight processes start but sometimes even that can cause data corruption. (We are in a factory environment so it is hard to raise the care factor very high in the users - once the siren goes for clock-off they're out of there!) Too many sessions and we run out of licences, and worse there are overnight processes that can cause data corruption if there are any logged in sessions. If Windows Virtual keycodes don't work for a game, you can try sending DIKEYBOARD constants (like DIKEYBOARDA etc.) and if it still doesn't work keep trying. It is very important to know what keycodes to send. It posts the input on a level lower then DirectInput. The third-party ERP system used by our company has no idle-out facility and we sometimes have issues because users simply walk away from their computers and leave sessions logged in for hours or even go home without logging out. You can use the unmanaged SendInput function for this.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |