Finndo, thanks very much for the report. I'll address your specific points in a moment but first let me say, you have two rename commands for the same PC for the hotkey that's triggered by <Numpad_Enter>. I don't know if you are trying to rename two different windows or whether you did this because you weren't sure which pathname to use, but either way, you need to change this. If you are trying to rename two different windows on the same PC, you have to give them different names like this:

<Rename "World of Warcraft" wow1>
<Rename "World of Warcraft" wow2>

If you have only one WoW window on that machine, you don't need to bother renaming it. You can refer to it as "World" in your files. HKN matches the first window that begins with "World."

If you have only one WoW window on that machine, and for some reason you want to rename it anyway, you have to do it like this:

<Rename "World of Warcraft" wow>

Quote Originally Posted by finndo',index.php?page=Thread&postID=38236#post382 36]Problem #1 is that when I went to setup the window name for the commands to be sent to I changed it to "wow" to make the code shorter...[/quote]If that's the only reason you're doing it, you don't need to bother. You can specify part of a window name in your definitions, and HKN will match the first window that begins that way. For example, <sendwin World> will match "World of Warcraft."

[quote='finndo
well I later noticed that when using the change the name of the window pop-up, that every window on my system was now called "wow"
What exactly did you right click when you selected the window to be renamed? Did you right-click the title bar at the top of the actual WoW window? (That's what I intended users to do. ) Or did you right-click something else?

So, I believe this to be an issue with Vista and hotkeynet not pulling the correct information (I am assuming from the registry).
HKN doesn't do anything with the registry. It just looks at open windows and picks the first one, if any, that matches what you wrote. If there's no match it doesn't do anything. The changes disappear when you close the window. They aren't recorded in any way.
as a result I would like to have a new setting in the program that allows you to add/remove renaming from specific files/folders/applications.
I think the best way to handle this is to figure out exactly what you did with the rename button, and then put in a safeguard so that can't happen. Once that is prevented, HKN only has the ability to rename specific open windows, and the user can always rename them back with the rename button or by closing the window and reopening it.

I also tried getting around this by renaming a specific program by location window (which you ned to update the command for this on the website. on the website it has "_" between every word, when I tried this hotkeynet told me I no longer need "_" between words...

Thanks for catching the out-of-date instructions. I just changed them.

The way to get around this problem is with the <rename> command. WoW doesn't alllow itself to be renamed with <RenameFromPath> . I wasn't aware of that until i tested it a minute ago. However <Rename> works fine.

Problem #2 is, after I press a hotkey locally, the remote system responds correctly. the SECOND hotkey I press usually does nothing, even if it is the same hotkey I just used.
I think this may be caused by the fact that you apparently have more than one window with the same name on that machine. I suggest you get the renaming fixed so there is only one window with the targeted name, and then see what happens. Let me know.

Thanks again for the report.