okay, doing it the way you suggested fixed my problems. so I have moved on to another level... I am now connecting to client/remote machines. all went well for a few minutes... then I stopped testing and setup the interface for the 2nd remote/client machine. afterwards I was unable to receive data from the server/locel machine. I checked my hotkey.txt file and nothing had changed. I tried swapping the ip numbers in the sendpc command, and the second machine received them; however the first machine no longer received the data. here is the file I am currently using, and after is a screen shot of hotkeynet importing that same file. Pay attention to the send to IP addresses. after that is a screen shot of nslookup on those IP addresses.

<hotkey numpad1>
<sendpc 192.168.2.2><sendwin World of Warcraft>1
<sendpc 192.168.2.3><sendwin World of Warcraft>1
<hotkey numpad2>
<sendpc 192.168.2.2><sendwin World of Warcraft>2
<sendpc 192.168.2.3><sendwin World of Warcraft>2









any ideas on this one? Like I said when I first loaded everything up, all 3 machines were working atleast a little bit, I was able to send commands to both machines, but now I can only send to one machine. If I load the hotkey.txt file I was using to run both windows on 1 remote/client machine instead of 2 remote/client machines it all works fine. here is a screen shot of an earlier attempt with this issue.







it appears that the program is having an issue determining where to end the send info and where to start looking for commands to send to another system. is there a<command> I can put in there to let the program know I am trying to connact a different system instead of forwarding on the info?

(the screen shots look horrible on my computer unless you click on them to open the full size image...)