Wow, just had the same issue pop up for me. Never thought it could be connected to updating the Sling Player software, but it did start occuring right after I updated. Why on earth would Sling software cause this type of a problem? I ended up removing Symantec and going with AVG (free), which is a pretty popular anti-virus software.
All;
I am experiencing a install problem on three different WinXP systems. The result seems to all be the same. If anyone has identified a more elegant solution, please share. This happens when upgrading from ver 1.4 or a clean install of 1.5. After the install is complete, whenever I right click on a desktop icon, the MSI installer for SAV launches (very annoying). The only workaround, I can find, and not sure it is comprehensive is to re-install SAV.
My systems are basically as follows
WinXP SP2
SAV 10.0.2.2000
Sygate Security Agent 4.1 b3607
WinXP SP2
SAV 10.0.2.2000
SCS 3.x
brianb
not sure what the relationship is, aside from suspecting that the install of SlingPlayer does something different than previous versions as relates to registration within the system. Switching is not really an option for me, as I am employeed by SYMC. Will eventually figure it out, though. Hoping for some insight from SlingPlayer software development.
My gut sez that it is realted to how this version of SlingPlayer is registering itself with the Add/ Remove portion of the system registry. Something with this installer is not right.
brianb
bbrotschi said: not sure what the relationship is, aside from suspecting that the install of SlingPlayer does something different than previous versions as relates to registration within the system. Switching is not really an option for me, as I am employeed by SYMC. Will eventually figure it out, though. Hoping for some insight from SlingPlayer software development. My gut sez that it is realted to how this version of SlingPlayer is registering itself with the Add/ Remove portion of the system registry. Something with this installer is not right. brianb
I am having the exact same problem. Has anything been found to resolve the problem as of yet?
Thanks.
adeppisch said:bbrotschi said: not sure what the relationship is, aside from suspecting that the install of SlingPlayer does something different than previous versions as relates to registration within the system. Switching is not really an option for me, as I am employeed by SYMC. Will eventually figure it out, though. Hoping for some insight from SlingPlayer software development. My gut sez that it is realted to how this version of SlingPlayer is registering itself with the Add/ Remove portion of the system registry. Something with this installer is not right. brianbI am having the exact same problem. Has anything been found to resolve the problem as of yet? Thanks.
I have not seen a response to this issue. I am however in the process of installing SEP-11, which is the replacement product for SAV-10 on the same system, after which I will attempt to re-install the SlingPlayer application.
brianb
arrow,
You probably need to put an exception into Symantec to hand;e the Slingbox port. I can't help you with it cause don't run it. But a review of the help files should show you how to do it.
Have a Sansa device or MP3 player, then check out The latest!
Follow Me on Twitter
Brandon C. said: arrow, You probably need to put an exception into Symantec to hand;e the Slingbox port. I can't help you with it cause don't run it. But a review of the help files should show you how to do it.
Sorry to be dim... but I'm not sure what this has got to do with ports?
The problem is "After the install is complete, whenever I right click on a desktop icon, the MSI installer for SAV launches (very annoying)."
Right clicking on a desk top icon shows the problem - any desktop icon.
This isn't a problem with connections or firewalls - we can watch sling player just fine.
It seems to be an interaction with the slingplayer install and symatec: "whenever I right click on a desktop icon, the MSI installer for SAV launches"
the problem can not be replicated with SEP-11 (the product which replaces SAV-10). Therefore, I would suggest that the problem is with the SlingPlayer installer used for v1.5 and the manner in which SAV-10 hooks into the operating system. Sure would be nice if someone from SlingMedia would chime in. If necessary, I could provide them with the SAV-10 software.
The solution that worked for me was to get access to the Symantec install files directly, run setup.exe and select "repair"... this took some pleading with the IT dept.
The problem seems to be an interaction between the KBox asset manager, Symantec and Slingplayer... something like: installing sling player trips Symantec AV's updater. But the updater wants access to files that KBox does not install so it just tries over and over again whenever you right click a directory.


RSS
