ENTER Button

avatar

Hi
I created an entry that makes a connection in rdp, start the program C:\WINDOWS\system32\notepad.exe then execute automatically the following macro:

1{ENTER}2{ENTER}3{ENTER}4{ENTER}5{ENTER}6{ENTER}

I expect something like this:

1
2
3
4
5
6
|

instead the result is the following (see also the attachment) :

1
23456




|

Why?
Thanks

Clipboard00.jpg

All Comments (6)

avatar

does {DELAY} between each change anything?

Kind Regards
Markus

======================

avatar

I also tried.
does not change anything.

avatar

did:
new entry
cmd-line: C:\WINDOWS\system32\notepad.exe
execute macro: 1{ENTER}2{ENTER}3{ENTER}4{ENTER}5{ENTER}6{ENTER}

works like a charm


how do you configured your session?
as sub-connection?
did you try: {WINDOW:Editor}

Kind Regards
Markus

======================

avatar

if I make a new entry like this:
cmd-line: C:\WINDOWS\system32\notepad.exe
execute macro: 1{ENTER}2{ENTER}3{ENTER}4{ENTER}5{ENTER}6{ENTER}
it works.


My session does not work.
I configured my session as well as attachments. No VPN, no sub-connection.
My initial idea is to create a RDP session connecting to the predetermined computer that performs the start of windows services (ex. "net start W32Time") through the command shell.
But when I use the macro in an RDP session the {ENTER} command it seems does not work properly.

01.jpg

02.jpg

03.jpg

avatar

I think it would be easier for you to use sysinternals psexec.exe and make an entry with it

gr8 tool: psexec.exe \yourpc /s /c net start w32time


so you can do somethin like: psexec.exe \yourpc /s /c net start w32time && mstsc /V:$HOST$
edited by SMG on 9/11/2013

Kind Regards
Markus

======================

avatar

I suspect that the enter key is not sent to the remote session. This is more tricky than it seems because we don't have direct access to the windows handle. I think that the SMG idea is much more robust

David Hervieux