I suppose that it would be nice to know why the antivirus software screws up
installations, but it really doesn't matter. Just turn it off or uninstall
it or do what ever you have to do to get your particular system with your
particular antivirus to not interfere with installs.
There are few reasons to come to mind:
1. Antivirus software is designed to prevent viruses and spyware etc. from
writing to the registry. Software installs need to write to the registry.
2. Antivirus software is designed to prevent the loading of DLLs from
viruses and spyware. Software installs need to write these DLL files to the
proper locations.
3. Free antivirus software generally cannot tell the difference between good
and bad DLLs.
4. Some antivirus software can corrupt DLLs and EXE files.
5. Attempting to install using anything other than full administrator
privileges on the local machine will cause the installer to fail to write to
the registry, thereby creating an installation that will not work.
So the message here is, READ all installation instructions on both software
and service packs and hot fixes and anything else that you put on your
machine.
--
Dennis Jeffrey, Autodesk Inventor Certified Expert
Autodesk Manufacturing Implementation Certified Expert.
260-399-6615
Instructor/Author/Sr. App Engr.
AIP 11SP3, AIP 2008 SP1, PcCillin AV
HP zv5000 AMD64 ( modified)
Geforce Go 440, Driver: .8185, 2GB RAM
XP Pro SP2, Windows Classic Theme
http://teknigroup.com
wrote in message news:5712315@discussion.autodesk.com...
Hi Dennis,
Yes... I have been reading tons on this subject.
Software install manuals can be blah, blah, blah (i.e. turn off A/V, etc)...
recommended practices to cover the bases. that ideally the installer should
catch.
Everything talks about turning it off... but I would like to hear a
documented case, of what it actually does?, what *.dll get's corrupted, what
Registry files are affected, etc... and why are no warning messages thrown
by the installer!???
Think it may just be allot of theories (with no documented case of actual
installer issues created). Reinstalling IV with A/V turned off. may simply
be fixing other dll corruption from other software installs (a.k.a. dll hell
syndrome).
Anyhow... I will be following this practice in the future (and probably have
in the past)... just to insure that it eliminates any corrupted installs
without warnings. just trying to understand why?
P.S. If this continues to cause hidden install corruption issues, then a new
installer that searches for A/V status on your computer... may be ideal.