Heikki Jussila wrote:
On Sun, Dec 12, 2010 at 18:58, HenriK<[email protected]> wrote:
HenriK wrote:
For reasons that I can not sort out, images are being blocked in SM
2.0.10 used with my 933 mHz Dell 4100 using Windows XP-Home SP3 and
Avast! security software.
Specifically, the background maps when I go to Mapquest won't appear at
all and images on e-Bay often appear for a second or two and then
disappear. In both cases, SM is set to allow images from these two
sites. Text displays correctly. Turning off Avast! doesn't fix the
problem either.
Could this problem be caused by an SM Add-On or is it more likely to be
a preference setting that I don't know about?
Any help and/or suggestions will be gratefully received.
Although I appreciate Mr. Ross' suggestion, I have now discovered that the
problem is more nuanced than I had suspected. First, image downloads from
all sites has been enabled and always has been.
If one is operating as a user with Windows XP administrative rights,
everything operates fine. If, however, you operate as a user with Windows
XP limited rights, as is generally recommended for day-to-day use, the
problem I originally described occurs. It does not matter whether Avast! is
enabled or disabled in either case. I also made certain that image
downloads were allowed from all sites in both modes of operation. In
addition, I upgraded to SM 2.0.11 and that also made no difference in the
problem.
From the above, I make the wild guess that there is something at system
level that blocks images. When you have admin rights you (the program SM in
this case) has the right to download and show everything, but when you work
with limited user rights there might be problems, since SM might use a
directory that is at system level and at this point the system does not
allow images any more. I myself found that using Win XP as a restricted user
was almost impossible. Most programs (even those of MS) require that you
have admin rights or you need to define relatively high level rights to a
user in order to get things moving.
Check if the SM has write-read rights to the temp (cache) directory at user
level when looking at the sites (also javascript etc. as some images arrive
with AJAX and if at user level javascript or any other script is stopped
that could inhibit the images.
Accordingly, it would appear to me that something really odd is going on in
the way SM v.2.x interacts with the different user modes (with admin rights
and without admin rights) of Windows XP-Home. It would be appreciated if
anyone with a really thorough knowledge of SM v.2.x can explain what may be
going on and/or can advise me how to solve the problem I have described.
I do not any more have WIN XP, but even on Windows Vista/Win 7 SM needs to
be installed as an admin and when used with limited account, windows stops
some operations (most notably updating to a new version), but also other
things. I have only used Firefox as limited user on WIN7, but found that
many things I could do as an admin on my Vista machine where not possibile,
however, the missing update was the most problematic, so to give also to the
Win7 notebook the possibility to update itself I changed the user as an
admin - the version is Home Premium.
I have the suspect that many Windows programs still need to be run as an
admin, althougth it is less safe and can create problems, but it seems that
it is the only simple way (especially with the home editions that do not
have group policy tools where you can set users rights properly, if you use
a professional/ulimate version then you can make user rights so that they
really do function, ie. like the old Win2K power user used to have).
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
Thank you for your idea. I share the view that Windows, XP and later,
seems to have some problems with limited access users. The problem is
that my system used to show graphics properly with SM v.2.x.
This leaves me to believe that since the time when everything worked:
1) a Windows XP update has caused the problem; 2) a SM v.2.x update has
caused the problem; 3) a SM add-on has caused the problem; 4) an Avast!
update has caused the problem; and/or I unwittingly changed an XP or SM
security setting and caused the problem.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey