Find and edit the Inoculan Update.INI file. This file can found in the actual directory from which it is run. Change the server name to NONE.
The next time you run the program it will ask you if you want to configure Inoculan Update since it seems this is the first time you have run it.Back to top
Within the configuration file you can add 10 To, CC and 10 message lines MsgBack to top
This is usually cause by an invalid parameter specified in the Inoculan Update.INI. Either the wrong number of servers versus the other definitions. Examples:
[ServersName], [Inoculan Dir], [Inoculan Update Winxx] these 3 sections must be equal. If you have 4 servers in [ServersName] then you will have to have 4 entries in the both [Inoculan Dir], [Inoculan Update Winxx] sections.Back to top
Unfortunately the NT series of windows does it's own downloading and is not supported by AVUPDATE.EXE. They read the primary domain from a NT server and update themselves. So if you have a few NT's in your network you will have to use their auto download capabilities to keep them up to date.
You may do so in 1 of 3 ways. Install InoculateIT NT SERVER and create a primary domain and have the other NT's in your network to poll this primary domain (Inoculan that is) and update themselves, or download the IL0084.ZIP(EXE) and manually install the signature update , or use the built AUTO DOWNLOADER and set them up to get the updates once a month.
Please remember that the Novell version along with AVUPDATE.EXE pushes the client to the stations (they run the program) where as the NT server/workstation version pulls the signature from a primary domain setup on a InoculateIT server.
Some news for InoculateIT NT server, they have come out with a few new patches.
LO71090.CAZ: Allows the downloading of the signature more often instead of the once per month. You can chose per day, Hour, Week etc... even at specific times. (03 01 2000)
LO71094.CAZ: Most of the complaints where that after a signature update the RealMon service did not restart so it was not aware a new signature had been applied, this has been correct with this patch. (03 01 2000)
LO75699.CAZ: Hum, this patch will REPORT ONLY that it thinks it found an infected VBS file. This has caused for a few clients of mine a headache since they are also running IIS (Web server) and it detects the VBS files from IIS are possibly infected scripts, so beware you may want to think about it before applying the patch/update. (05 26 2000)Back to top
There are 2 ways to setup any program into a NT service that I know of.
1) Go to this site and read the info and download the zip and experiment http://vbwire.com/advanced/howto/service.asp
2) Get BALISERVICE from www.baliciel.comBack to top
Edit Inoculan Update V2.INI and change the following:
Rerun the program and it will now create a LOG file, Send me the INI file and LOG file so I may analyze what went wrong. I usually will get back to you within 24 hours (or less).Back to top
With version 2.5.14 a few new calls to Novell's DLL's have been added since their latest release of their ACTIVEX programming ware. All seams to work properly now. We have tested it on Professional and Server and it work just fine.
With version 2.5.16 a new directive has been added to the INI file. Some have complained that when the program tried to update the signatures it searches on the SYS volume for the directories paths specified with the configuration program when all along INOCULAN is installed on another volume like DATA or VOL1. Adding the following 2 lines to the INI file will correct this. Sorry I had hard coded SYS in the program (I assumed, I know what Benny Hill said about AssUMe).
Change DATA to suit your needs.
With version 2.5.202 there is a new command in the INI file.
Change the TimeOut to suit your needs. By default the is no timeout, so 20 seconds is quite a bit. For very slow connections or extremely congested sites increase to 60 seconds.
As a registered user (remember it is 100% free) request the "WINDOWS NT 2K UPDATE" by email and I will sent it out to within 24hrs. You may consult the DOC from here.
We will get back to you within 24hrs.
A few complaints
that it freezes on Windows NT 4 when it tries to stop the services.
This has been located and not corrected.
The local user must be an Administrator of his/her computer, If they are not then a few problems will occur:
You can get the
ADSI client from
Please follow this link all is detailed on what you should be emailing us for prompt support.