From eScan Wiki
(Difference between revisions)
Revision as of 08:40, 5 June 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 08:05, 9 June 2009 WikiSysop (Talk | contribs) Next diff → |
||
Line 16: | Line 16: | ||
Please note that this is NOT an eScan problem - it is a problem between Client/32 and WinSock 2. </I> | Please note that this is NOT an eScan problem - it is a problem between Client/32 and WinSock 2. </I> | ||
+ | |||
+ | |||
+ | ---- | ||
+ | <B><I><font size=2>Email us your feedback to [mailto:solutions@mwti.net solutions@mwti.net]</font></I></B> |
Revision as of 08:05, 9 June 2009
Q. Are there any compability issues with MS-MWL?
A. The WinSock standards are very well defined & documented, and are implemented by millions of applications. eScan will work very reliably, provided that applications properly implement these standards.
Also, any application that does not properly implement these standards risks serious compatibility problems when working with many other applications also.
However, please do not hesitate to contact us immediately should you believe that you are experiencing a compatibility problem, so that we may investigate ASAP.
Noted Exceptions:
- a) We are currently in the process of resolving certain issues with Lotus notes R4.6 & SendMail NT. This work is expected to be completed shortly and an appropriate product update will be issued ASAP.
- b) We have also identified an issue for platforms running Novell Client/32 with WinSock 2 - they do not seem to interoperate. We are still seeking to resolve this issue.
Please note that this is NOT an eScan problem - it is a problem between Client/32 and WinSock 2.
Email us your feedback to solutions@mwti.net