April 17th, 2002
|
| |
 Something it installed broke McAfee
Quote: Originally posted by afisk
I can look into this issue further. It's most likely a conflict between our installer and Mcafee that is totally unrelated to the LimeWire program itself. Our installer uses Microsoft's new "Windows Installer Service" (hence the messages about MSIEXEC.EXE). This is the "latest in installer technology", but it's notoriously buggy and appears to conflict with Mcafee.
Just for the general clarity on these issues for those interested, pretty much every program modifies the registry when you install, as this is the default setting with most installer programs. This makes sense because the registry was invented as a sort of "hidden" place to store application data, so everyone's using it for the intended purpose. LimeWire and LimeShop make really minimal registry changes that would not be causing this conflict (in fact, as a Java program, LimeWire doesn't even have built-in access to the registry -- we'd have to add some fancy native windows code to do this).
So, again, the issue is more likely a more basic conflict between the installer and Mcaffee. I would suspect, for example, that there are other programs that use InstallShield Developer 7 as their installer that would also cause this issue. I'll look into it more, though.
Thanks for all of the info, and our apologies for the frustration. | Adam, the latest windows installer sounds like the right track. Also did not like having to install Sun Java!  |
Similar Threads 
Threaded Mode
