The log file does go in the %temp% directory. You can type "%TEMP%"
into your explorer bar rather than wading around for the exact
location. The files that will be generated are "NOD32PreInst.log" and
"NOD32Inst.log". "PreInst" are actions performed for the cheesy batch
script that I wrote, and likely are the source of your problem. The
NOD32Inst.log file is generated Microsoft's MSI engine, which is used by
the NOD32 installer proper.
If you do end up having a look at the logs, let me know the last couple
of lines reported so that I can see where the installer is hanging.
Bryan Fleming wrote:
> There's also a setup log file that the ESET install will generate, it
> may be worth checking there to see what it says the problem is.
> I'm drawing a blank on the exact path to find said log file though...
> I see the problem with the installer so rarely I usually just browse
> around for it. I think the temp directory perhaps. Hopefully someone
> else can chime in with that.
> Geoffrey Marchand wrote:
>> Check to see if there is another antivirus program installed on the
>> computer. If so .. Uninstall then install Eset.
>> Sent from my iPhone
>> On Nov 23, 2009, at 10:22 AM, Larry Kost <[log in to unmask]> wrote:
>>> I am trying to install NODE32 on a new MSI slim laptop and it starts
>>> off then pops up a window titled ESET NODE32 Antivirus with just the
>>> number 1 in the window and it just sets there. If I click OK, it
>>> stops the install. Any ideas? I tried running as Administrator,
>>> but that didn't help. The OS is Vista Home Premium.