Is there any particular reason why ClamWin is available on just about everything but NT4.0? Has anyone come up with a way to successfully run it on NT4.0?

one of the libraries used in python code (py-win32) is not compatible with NT 4.0. Clamscan and freshclam will run on nt4 but the GUI won't.

Thanks for this info. Would you happen to know which library is not compatible?

py-win32

Yeah, I noted your mention of py-win32 after my last post. Don't know how I missed it. Sleep deprevation probably.

Whatever, is there a knowledge base or something I can refer to concerning this that has some specific information on the difficulties?

Also, am I safe to assume the installer is what actually prevents a physical install of ClamWin on NT4 rather than the incompatibility with the py-win32 lib?

no, clamwin gui will not run on Nt 4.0 due to a missing export function form a dll. That's why installer blocks attempts to install on NT 4

Okay, we seem to be getting to the nitty-gritty. Do you have any idea which specific dll we are talking about here?

I don't remember to be honest. Try running portable clamwin from https://www.portableapps.com on nt 4.0 and you will see which one.

Okay. I get the drift. It's the MSVC*80 DLL's. M$ intentionally left out one simple instruction in building these so they will not work in NT4.0 so they can make something that still serves many useful purposes even more obsolete. Another ploy to force customers to buy up. My idea of going up is Fedora Core 5. Whatever, I think I'll just scuttle a little project I was going to attempt to do with the mail server on that box and just convert it over to a FC5 setup. That day has been coming for quite a while. I have just been procrastinating on that one box because it's the mail server and I pretty much will have to set it up from scratch. Several domains, lots of users, lots of rules, etc. and it's not a matter of just transferring current data over. I'll be busy for a bit. I appreciate your information.

ok there's a big hack alch pls don't hit me, I can make a more elegant soluition using some spare time, but for now this work
download the archive at https://oss.netfarm.it/clamav/clamwin/ClamWin-0.88.3-nt4.7z https://oss.netfarm.it/clamav/clamwin/ClamWin-0.88.3-nt4.7z
you need 7zip to extract
put ClamWin directory in you program files, then edit bin/Clamwin.conf e fix paths
also edit ShellExt.reg with correct paths and merge it in the registry
if you are using c:\Program Files\ClamWin
all paths are already fixed

now you can run clamwin with also the shell extension on winnt4

alch also note that vs2005 builds on winnt4 are not working since msvcrt8 is not compatible with nt4, so I've included
vs6 builds

alch I hope you never call the function in shell.pyd that calls SHGetSettings hihi you may have weird results, since I've re-routed it
to a random function in shell32

pywin32 version 209 doesn't need this hack since it grabs function with GetProcAddress

any feedback?