--- In [email protected], "entropyreduction" <[EMAIL PROTECTED]> wrote:
>
> This runs reliably for me as a standalone script:
>
> ===============================
> ;(1)
> local com_status
> win.debug(com.create_object("Shell.Application").;;+
> NameSpace(49).Items.Item(0).Name)
> com.unload
> quit
>
> then exit pp
>
> ===============================
>
> Does it for you?
In my case, strangely, it worked only at first time after logon.
After restarting PP and executing the script again, it always stuck at
com.unload and PP became irresponsive. I tried to add Wait.For()
before com.unload but didn't help the situation.
It's not that critical to me as I didn't experience any other problems
and it's rare for me to close PP (:done only when upgrading PP),
except one more thing: PP's virtual memory usage increased from ~5MB
to ~10MB, and remained so on after executing the com services,
however, I don't know if it's normal behavior with COM.
> How about:
>
> ===============================
> ;(2)
> local com_status
> local coSA = com.create_object("Shell.Application")
> local coNS = coSA.NameSpace(49)
> local coItems = coNS.Items
> local coItem = coItems.Item(0)
> win.debug(coItem.Name)
>
> then exit pp
>
> ===============================
The same symptom as before.
Sean
