by technology » Mon Sep 15, 2008 10:09 am
Thanks for posting
(1) Actually the only "known issue" is that eValid is much more
sensitive to JavaScript loops and JavaScript errors than
is IE. That's because eValid doesn't include some of IE's
tricks to kill loops and negate circular call sequences...
eValid is a QA/Testing engine and the thinking is that
it should NOT work on pages that are "broken."
If you see the little yellow symbol in the lower left corner
then you'll know there's a JavaScript fault. Also, during
playback, these will show with an appropriate message.
(2) Like any Windows executable, eValid will be vulnerable
to viruses and malware...nothing to be done about that!
(3) Don't know of any active directory policies that don't also
apply to IE. Remember, eValid uses the IE rendering engine.
(4) "Multi-user"...as in a terminal services machine with multiple
accounts...for more that one simultaneous user on that machine
you need an EPRISEnn license...but any ONE user can run (with
the MULT feature) any number of instances of eValid...
But if two instances of eValid have to share a unitary resource
(desktop, cache) then you may need to use the Lock/Unlock MUTEX
operators...
eValid Tech Support Team