Can you give me the exact version of Nod32 that would work with X-wall?

I was look for v3 but i got this back after my question to Nod 32:

The very latest version of NOD32 has a slightly different classification
style. The beta is v. 2.000.11b.... the next full version will be v.
2.12.0 and the last increment will change to 1, 2, etc.

Unfortunately, I am not a specialist in NOD version numbering.
I receive something named (nd98en3r.exe and ndnten3r.exe) about 3-4 months ago.
The bundles above include API and were tested with x-Wall. Everything was fine.
I was also promised that the API functionality would be included in regular version soon.
Special license for API access was compiled into x-Wall binaries.
Might be I confused the version numbers…..
I cannot contact them with the question now, nod32.com is down from my connection point
I will certainly ask ESET about compatible version.

The version I am currently using is:

The main sign of correct NOD32 (or any other AV) version is check passing.
For that purpose, choose desired AV in setting tab and press test button.
There are 3 consecutive test checking AV compatibility exactly in the same way as x-Wall do in the network AV scanning.

The problem with proper NOD32 version seems solved.
Beta 3.0.084
http://sphinx-soft.com/download/s-Wall-Setup.exe
works fine with NOD32 2.12

Don’t forget to manipulate with NOD options in NOD Control Center to avoid double (or triple) AV checking in x-Wall/quarantine path and directly in E-mail message box if AMON\DMON is used

I got it working

It concerns with all compatible x-Wall AVs (not only NOD32).
AV technology is very high developed. The times of simple file scanner were remained in the past. Every modern AV includes several opportunities that could interfere with x-Wall.
The interference is not dangerous and might cause only additional message boxes or slightly overload the system and nothing more.
However, it would be better to understand before than be surprised after.

Let’s examine the situation with NOD32.
There are several protecting technologies in addition to AV scanner (NOD32 itself)

- AMON – resident file monitoring.
x-Wall always temporary stores each piece of internet content in x-Wall\quarantine directory and then calls AV via API to check it for viruses. AMON (if enabled) immediately hooks the attempt to write potentially infected internet content as any other file operation. If the content (file) is infected, AMON will immediately prompt you. If you skip all possible AMON’s actions x-Wall will call NOD32 again with the same file. As the result, you will obtain double AV checking. If your action on AMON’s prompt is delete the file, x-Wall’s attempt to check the file will fail as the file has just deleted by AMON. To avoid that you could simply to disable AMON monitoring in x-Wall\quarantine at least.
Technology like AMON is certainly progressive. However, let us imagine, AMON (like any other resident monitor) will intercept each file operation. It might occur many times under the same file, each time the file is under operation. Files could be big and operations could be frequent… CPU (and possibly disk) overload is guaranteed. I know a story when AV file monitor was installed on machine with serious database. The first impression was a deadlock for unknown reason. Everything was working but inexpressible slowly….. Anyway, it is your choice. Remember, 99% of viruses arrive from the internet, but is not born on your disks.

- DMON could produce double-checking of the same data. First time the internet content is forwarded to NOD32 via API for AV conclusion, the second time, when the content become a web page or an e-mail, correspondent internet client (Internet Explorer or Outlook) might decide to check it again via DMON plug-ins. Only you could decide that you really need it.

- IMON acts similar to x-Wall, but x-Wall performs network operation at TCP-stack level (lower than socket level). Therefore, the probability of hijacking / intercepting of its operations is significantly lower. Furthermore, x-Wall does not require any port customization – all traffic detecting is automatic. As the result if you use IMON additionally to x-Wall, you will perform double-checking.

So, if you enable all of the options you will check the same up to four times in the next sequence
x-Wall – AMON – IMON – DMON.