Amon fails to start - low spec machine

My daughters PC is low spec (PIII 866 with 128 MB RAM running XP SP2). As expected it runs very slow but it has been running KAV 5.0388 on it but I thought I'd give NOD32 a try to see if it helps the performance a little.

NOD installs fine but AMON doesn't always start. I've tried uninstalling and reinstalling but after a couple of reboots it generally fails. I notice on the Eset website that this problem can be used by low memory or disk space.

Is 128MB too low for NOD32?

BTW, the PC is a Compaq Deskpro Workstation AP250 and memory upgrades seem to be more expensive than the price of a second-hand higher spec PC!! But I did get the PC for free so I can't complain!

 

I had computer with 128MB RAM and no problems occurred.

 

It's more that it's too low for XP SP2...

 

Try increasing your virtual memory

 

Yeah I know but it does manage to struggle on and afterall it does still run KAV which is supposed to be 'heavier' than NOD

Thanks, I'll give that a try.

 

It is, but that doesn't mean that XP always likes to play nicely
How did you go increasing the virtual memory - can you tell if it has helped?

 

My daughter was in bed asleep by the time I got home from work last night, I'll have to try another evening. I'm not worried about doing urgently as I'd already shown her how to manually start it - and when it is manually started it it stays on until the PC is rebooted.

I'll report back how it goes.

 

Try to see NOD32's Event log. Maybe you can find why AMON isn't starting automatically.

 

It may be worth looking @ Services (services.msc) to see if the NOD32 Kernel Service is set to Startup type: Automatic. The Recovery tab should also have Restart the Service for all failures.

 

So your computer now has KAV and NOD32 on it? You didn't say that you uninstall KAV so I assumed you now have both AV activated?

 

I had previoulsy checked it and I think all it said was something like resident protection failed to start {or words to that effect}

Thanks, another thing I can try

I'm not that daft I definitely uninstalled KAV first

 

I tried increasing the swap file and checked that the service was set at auto. But o I guess it was just a stretch too far for the low RAM.

I decided to restore the acronis image I took before I uninstalled KAV and have put it back as it was. Thanks to those for the tips I did receive though.