Board Logo

Virus found? in NALIST.HTM ...(v 5.47)
d003232 - 11-20-2010 at 10:35 AM

My avira virus scanner is giving me an alert:

found HTML/STRATION in nalist.htm

in the c:userspublicejukebox folder? What's the nalist.html file for?


Audiosoft - 11-20-2010 at 11:43 AM

just the cached album list
no virus
EJ has always been virus free


d003232 - 11-20-2010 at 11:48 AM

Ok. I'm pacified.

btw: Why is that ejukebox folder in the folder c:userspublic ? As I noted the public folder is accessible from all pc within my home network. Means I (or my son who wants to bother me) can delete the files in that folder from every pc. :-)


Audiosoft - 11-20-2010 at 11:53 AM

It needs to be public so that the auto lookup cover image cache can be accessible to all user accounts and EJ installs.
That way it saves disk space and doesn't re-download lookup images already downloaded. The rest is the cache unique to each install folder.

if the cache is deleted it will be recreated automatically as needed from data stored in your EJ database but EJ will be slower until everything has been re-cached.


d003232 - 11-20-2010 at 12:02 PM

Quote:
Originally posted by Audiosoft
It needs to be public so that the auto lookup cover image cache can be accessible to all user accounts and EJ installs.
That way it saves disk space and doesn't re-download lookup images already downloaded. The rest is the cache unique to each install folder.


Shouldn't it then be in the folder 'c:usersall Users' (seems to be internaly assigned to 'c:ProgramData' in Windows 7) instead of 'c:userspublic' ?


Audiosoft - 11-20-2010 at 12:07 PM

i don't think so
public was the only thing the UAC accepted
and like i said before i wanted to allow C:EJukebox C:EJukebox2 etc
i remember there i couldn't have EJ installed more than once or UAC would mix the files with the other install's files.

even if it could work from where you said i couldn't change it without making everyone have to re-cache
so i don't even want to think about changing it when there would be no benefit and only potential slowdown and disruption


d003232 - 11-20-2010 at 12:25 PM

I understand. Never touch a running system.

I'm still wondering how the other applications without administrator rights could handle the UAC? My assumption was that they don't need access to 'C:Program Files (x86)' and other protected folders. That they write into the 'C:Users' area and in the 'C:UsersAll Users' ares. At least I can write within that folders without UAC warning or administrator confirmation.

But I'm not a windows developer. So I understand to less of the details.