SGilman wrote:Good Afternoon.
Does eValid have a way of preventing two or more eValid instances from interacting?
I've tried this and one instance messed up the state of the machine and messed up my test.
Thanks for posting SGilamn.
For this kind of issue, which is not THAT unusual, you need to use the eValid Lock/Unlock capability, described here: http://e-valid.com/Products/Documentati ... nlock.html
The Lock command sets a flag in a registry location that is commonly available to OTHER eValid instances.
That flag is "owned" by the eValid instance that sets and un-sets it.
While set no other eValid instance can do anything: it (they) will wait until the Lock flag is un-set.
Hope this meets your requirement.
-- eValid Support