Hi Ron, I am just pressing enter on the script names and it connects to window-eyes, registers a hotkey and says "hello world all done" when that hotkey is pressed. I am using the Wscript.ScriptName property to check on the exact scriptName with the InStr function. Warm regards. Martin Webster.
--- On Mon, 3/22/10, Ron Parker <[email protected]> wrote: > From: Ron Parker <[email protected]> > Subject: Re: making my unhosted VBScript known to the script manager? > To: [email protected] > Date: Monday, March 22, 2010, 12:14 PM > > How are you running your script? If Window-Eyes isn't > running it for you, ClientIdentify won't do anything. All > ClientIdentify does is tell Window-Eyes "I'm that script you > just started, so please tell me when I should shut down." > > (Also, what happens to your script when your machine has > more than one instance of wscript.exe running?) > > On 3/22/2010 8:04 AM, martin webster wrote: > > Hi all, > > How do I get my unhosted VBScript to show up in the > script manager?. According to the docs I should use > the ClientIdentify method of the Application Object > inconjunction with ClientInformation but I don't seem to be > getting it right. Below is Doug's example script he > left us with on friday only I wrote a function using win32 > process wish does give me the Script's PID but when I give > this to the ClientIdentify method nothing shows up in the > script manager still. I know that it is giving the correct > information because if you remove the "'" from the three > lines with in the function you get full path name of where > the script was run from and Object name (the object process > that started the script).. Please help. > > > >
