Jump to content

Phil_S

Members
  • Posts

    40
  • Joined

  • Last visited

Posts posted by Phil_S

  1. Hi, I installed v9 as an upgrade over v8 a few days ago, since when I have found that Windows Photo Viewer pauses for several seconds when trying to look through several images in a folder, using the forward or back buttons. The pauses are a bit random, in that it will sometimes behave normally for 2, 3 or 4 images, then seem to hang, but other times it seems to hang for several seconds as soon as I click to go to the next image.

     

    It also hangs for several seconds before closing after clicking the close button.

     

    Temporarily disabling protection results in WPV behaving normally. I have since completely uninstalled Nod and re-installed from scratch, but the behaviour persists.

     

    This is on a Win 8.1 Pro 64-bit machine, BTW.

     

    I know there are "better" image viewers out there, but I quite like using WPV to flick quickly between a number of images, rotate them if necessary and zoom in and out as required. I never experienced the issue with any previous versions of Nod.

  2. Dr Teeth,

     

    Do you mean that you haven't had to add the router IP to the exclusion list? I'm using an RT-N66U with Merlin 3.0.0.4.372.31 and unless I exclude it the web interface hangs with partially loaded pages, corrupts those that do load and often fails to execute tabs or links to other settings pages. Once I exclude it, everything works fine..

  3. I hesitate to say this, as it will probably start a spate of errors again, but things seem to have settled down in the last few days. One thing I have noticed is that the EAV tray icon indicates that it is checking for updates as soon as my Win 8.1 desktop comes up after login (I login straight to the desktop and bypass the start screen) but on a Win 7 machine the icon doesn't change to show EAV is checking for updates until a few seconds after I have logged in to the desktop and I haven't noticed it suffering the same error.

     

    I have an always on internet connection by the way, it's just the link between the computer and the router that goes to sleep when the PC hibernates.

  4. Peter, I had the same pop-up you show above open yesterday on booting one of my machines running a licenced copy of EAV 7.0.302.00

    On clicking the "extra benefits" link my browser opened the ESS page. Install upgrade prompted me to install 7.0.302.26. I hadn't bothered to upgrade previously as I'm sure I recall DWomack and Marcos saying in this forum that the only difference between the two versions was an updated EULA?

  5. It was when I updated to 13.9 that I got hit by the problem. For some reason this board won't let me paste, so I can't copy the link.

     

    Do a Google search for "Problem with AMD Catalyst 13.x beta drivers and Quicken" and you'll find several links. Although it mentions beta drivers, I had the problem in Quicken with 13.9 stable. I've gone back to 13.4 which solved it for me, but some of the posters reckon anything later than 13.1 has the problem.

     

    AMD acknowledged the problem and suggested it had been fixed in the release notes for 13.11 beta 3, but I haven't tried it as I'd rather stay on an older stable release.

  6. Thanks SweX

     

    I do think a short delay in starting the check for updates would solve it, as you say. I've disabled the setting on the network card to allow the computer to turn it off to save power, and experimented with disabling other power saving features on the card such as green ethernet, but it's not made any difference.

     

    Would setting the Eset service to automatic (delayed start) help, or would that cause other issues? It seems poor design that if an important update has been released in the time that the computer might have been off or asleep for several hours, that the machine could be unprotected for an hour or so on awakening!

  7. I have just started receiving this error periodically with EAV 7.0.302.26 on a fresh Win 8.1 install from bare disc. Previously, I have been running EAV on various versions of Windows from XP through to Win 7 and Win 8 without experiencing the error, which happens only on first boot of the computer or resuming from hibernation, frequently but not every time. At least I don't think I've ever had the problem before, but it isn't apparent from the taskbar notification icon, only from a red warning triangle against the update tab when opening the EAV console.

     

    I have tried flushing the cache as per SOL3189 which accurately depicts the error that I am seeing, and have also completely removed and re-installed EAV but it still occurs.

     

    I don't think it is a cache problem as even if I don't clear the cache on seeing the error, I can carry out a successful manual update straight away by clicking on the Update button, and/or subsequent updates once the machine is running occur without problem.

     

    The computer is connected to a permanently on internet connection. I am wondering if the issue is due to the network connection on the computer not being ready when EAV attempts the update, as Win 8.1 is noticeably quicker to boot or wake from hibernation that even Win 8 was on this machine.

     

    Just wondering if anyone else running on Win 8.1 is seeing this error, or if any of the Eset staff can comment on a solution? I wondered if delaying the update for a minute or so after boot or wake might fix it, but can't see a way to do that through the scheduler. It seems that if the update fails, EAV won't attempt to update again for 60 minutes (as per the scheduler) which means the system possibly running for that time without the latest signature updates if any are available.

×
×
  • Create New...