All aspects of eValid product installation and licensing.


Postby Rafe08 » Thu Aug 28, 2008 5:08 pm

Can someone elaborate on the following two items:

1) ... ility.html

We are using Windows Server 2003 R2 for deployment.

WS2003 tends to be problematic for eValid, but WS2003/SP2 seems to
be OK. The problems are that some low-level I/O stuff is just
enough different...but that seems to be OK with SP2.

2) Also, I saw something about the eValid Programmatic Interface (EPI) I
can't find any useful documentation on it though.
Posts: 36
Joined: Mon Jun 02, 2008 9:39 am

Re: Questions

Postby Installation » Fri Aug 29, 2008 5:11 pm

Thanks for asking.

The eValid Programmatic Interface (EPI) is described in detail in this
this introductory page: ... ction.html

Here are some eValid Programmatic Interface (EPI) fully worked examples
in the CPP/C++ context: ... e.cpp.html

That capability needs the EPI feature key. Neither it nor the PAGEMAP feature
(which includes all of the fancy AJAX synchronization and DOM polling features)
were part of the original purchases...let me know if you want to consider an
eValid Tech Support Team
Posts: 29
Joined: Tue Mar 11, 2008 1:46 pm

Return to Product Installation, Licensing & Support

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons