Welcome Guest. Please Login or Register. Apr 5th, 2018, 11:44pm
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
1. Programs using it must be Run As Administrator on Vista and Windows 7. This is due to the way shared memory is handled on those systems, and I don't know of a workaround.
Would ShellExecuteEx using SEE_MASK_NOZONECHECKS be a solution? I haven't tested this but I hope this doesn't look at time zones instead, and I don't know how this effects Shared Memory created with the File Mapping functions.
Quote:
2. Large numbers of handles are leaked. This appears to be due to ShellExecute, which on its own seems to leak handles. I don't know how to prevent it.
Also wouldn't using ShellExecuteEx give a way to return the handle to the process invoked?
Quote:
So unless solutions to these problems are found, I will archive SPAWNLIB as an interesting, but failed, experiment.
I ask for my own enlightenment rather that assuming you hadn't thought of these...
Would ShellExecuteEx using SEE_MASK_NOZONECHECKS be a solution?
What makes you think it might? The way Vista/7 handle shared memory isn't a function of how the process is launched (you can use the lower-level CreateProcess and the behaviour is the same).
Quote:
Also wouldn't using ShellExecuteEx give a way to return the handle to the process invoked?
As I said earlier in the thread, SPAWNLIB doesn't need to know the process handle. As you will appreciate, the process handle has nothing whatever to do with the handle leaks I mentioned; it is closed automatically when the process terminates.
Quote:
I ask for my own enlightenment rather that assuming you hadn't thought of these...
It's not so much that I hadn't thought of them, I don't see their relevance to the issues I mentioned (requiring to be Run As Administrator under Windows/7 and handle leaks from ShellExecute).
Logged
