First of all, many thanks for the 0.93 kit for NT4 !!

I tried installing the new kit over 0.92 and also did a fresh install from scratch with the same results. During the installation, a pop up window comes up indicating it can not find the MSVCR80.dll file. I clicked OK and the installation seemed to complete. If I try double clicking on the desktop icon, I get the same pop up windows with the same error message. I tried to find the dll file in my C: drive at no avail. Is this a MS C++ dll file ? I do not have MS C++ installed on the box.

I was able to go back to 0.92 and get back to where I was before the 0.93 installation attempt just to prove the possibility of reverting. But I removed 0.92 again and did another fresh install of 0.93. I am open to any suggestions to get over this issue on 0.93. I understand NT4 is not officially supported but I am willing to try anything to make this new version work at my end. I am willing to wait for suggestions from anyone when there is time available to look into the issue. Please advise at your earliest convenience.

Sorry. I missed this... I was able to find

C:\WINNT\System32\msvcr71.dll

This box sits at WinNT 4 SP6a and can not be upgraded with any later NT4 Service Packs. I guess I might be out of luck if a later Service pack is required.

try copying files from C:\Program Files\ClamWin\bin\Microsoft.VC80.CRT to c:\winnt\system32

during the installation? it's strange, also no need for crt80 builds are made with mingw and static linked crt8
dynamic crt is not compatible with nt4 due to missing symbols
I'll try to add msvcrt71 (I think for python stuff)
I've got no problems on nt4 sp6, but It's an old installation in vmware so it may differ from the one you have

can you please tell me exactly what the message box says?

ops I think I've made something wrong in the installer
I have included crt8 binaries instead of the mingw ones

I'll fix the build soon

The error message seems to be truncated since it displays the complete PATH for the process. This is what I get

The dynamic link library MSVCR80.dll could not be found in the specified path C:\Program Files\ClamWin\bin;.;C:\WINNT\System32;C:\WINNT\system;C:\WINNT;C:\mks\mksnt;C:\WINNT\System32;C:\WINNT;.

This is all that is displayed in the error window. If you click OK, the window goes away but the gui does not come up on the screen.

Let me know if you need any other information.

Unless the installation did not complete properly, there is no such directory or file(s) at that source location:

C:\Program Files\ClamWin\bin\Microsoft.VC80.CRT to c:\winnt\system32

Nothing like that under the \bin subdirectory.

I've fixed the installer the new file is called 93b, to make me forgive I've implemented dns check on nt4
https://sourceforge.net/project/showfiles.php?group_id=105508 https://sourceforge.net/project/showfiles.php?group_id=105508

I copied the new kit and ran the installation. This time everything seemed to run fine. It copied the database but indicated some issue with the DNS reply. But it failed back to HTTP mode. I don't know if this warning is relevant.

ClamAV update process started at Wed May 07 17:19:13 2008
WARNING: Invalid DNS reply. Falling back to HTTP mode.
nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 209.170.150.7)
Trying host database.clamav.net (64.142.100.50)...
main.cvd updated (version: 46, sigs: 231834, f-level: 26, builder: sven)
daily.cvd updated (version: 7051, sigs: 48777, f-level: 26, builder: ccordes)
Database updated (280611 signatures) from database.clamav.net (IP: 64.142.100.50)

The reason I took so long to get back is that a full scan of C: and D: under version 0.92 took over 80 minutes. The same scan I ran today under 0.93b took 43 minutes 41 seconds. I then ran individual scans for each drive and the numbers added up. Disk space has not changed on either C: or D: since my last 0.92 scan. I can't explain the speed gain of close to 50% in execution. I am not complaining, but just curious.

I did not test the scan scheduler since I assume nothing has changed since 0.92. Let me know if you want me to check the scan scheduler. The email notifications worked in "test" mode. There was no virus detection to trigger in a real case scenario.

Looks like NT4 legacy 0.93b Virus Scanner works fine. I'll follow up if I find anything else.

Thanks again for your help and support !

dns reply is still a mistery for nt4, I currently look
at


for NameServer or DhcpNameServer
as ipconfig does

do you have something in the registry keys?

nonblock_connect: giving up due to excessive bogus loops
Can't connect to port 80 of host database.clamav.net (IP: 209.170.150.7)
Trying host database.clamav.net (64.142.100.50)...

this mean that 209.170.150.7 mirror has some troubles, the second tried is ok

I would still investigate about the dns stuff, can you look please at registry?
and if you will help later I may give you some instructions to debug the problem

Inside ...\Parameters there is a NameServer key with my two valid dns server IP addresses (Primary and secondary) separated by a space.

NameServer "00.00.0.00 00.00.0.00"

I replaced the actual numbers by zeros. If you need them, I can sent them via email.

There is no DhcpNameServer key present.

oh so I need to parse them then and pick only the first, you quick can fix dns issue in freshclam by setting only 1 ip in that key
unfortunately this stuff is undocumented for these os I think at the time of nt4 no one was thinking
about making direct queries to dns

can you please try this binary?
https://oss.netfarm.it/clamav/files/freshclam.exe https://oss.netfarm.it/clamav/files/freshclam.exe

It picks only the first dns now, I've also added a new key that overrides NameServer and DhcpNameServer
it's called ClamWinNameServer
you can use it if you don't want to touch your network settings

if it works I can make a 93c

I've got a psapi version of memory scan working on nt4
next release will have memory scan

I tested the new freshclam.exe from the gui and my NT4 scheduler job and they worked fine. I did not get the WARNING: anymore.


Note the last instance of the update. I used to get the warning every time.

Looking forward to the memory scan feature on the next release. Thanks again !!