Jump to content

T-RHex

Member
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

2 Neutral

About T-RHex

  • Rank
    Member
  1. Hi Frank. (Apologies for taking this long to get back.) I've confirmed it is *not* due to the Classic theme as it also happens under an Aero theme. It seems to bring forward the 2nd-last focus window instead of the window which last had focus (and it happens when the notification window auto-closes, not when I manually close it). Thanks again.
  2. Awesome, thanks Frank. I kind of put up with it because I figured it probably only happens on soon-to-be-unsupported Win7 -- with the Windows Classic theme -- so probably is low priority for Emsisoft. Good idea on update notifications: I keep them on mostly out of habit (though that leads to a different issue on my Win10 tablet but that's a story for another thread).
  3. I've had this problem for months, hoping it would get resolved. Win7 Pro x64. After the notification disappears, a random window (not necessarily the last focus) will come forward.
  4. Sorry for the delay in responding ... I do have MBAM Pro 2.2 installed but not running; I do not have the Real-Time protection enabled. I think you may just have been lucky. But it looks like Emsisoft has a patch deployed now and so far after a few reboots it appears to be working okay for me. Most programs cannot detect whether or not there is a connection, they rely on timeouts: if there is no response from the server in a set time, then they assume there is no connection. But, they don't know that until they try to connect...
  5. Sorry for the delay in responding ... I did not try disabling self-protection, but it looks like Emsisoft has put out a patch as I'm now able to boot properly without debug logging enabled. (a few reboots so far, that is) Kudos to Emsisoft support for being very responsive.
  6. For me, if debug logging is enabled the problem does not occur on startup. With debug logging disabled, it takes a few minutes for the Windows logon screen to appear (seems to be frozen, but just wait 2-3 long minutes) and EIS does not start properly. To workaround, I wait for Windows to startup, then kill the a2service.exe process, and then EIS either restarts on its own or I start it manually; after, it seems to function fine. As debug logging shouldn't stay on for long periods of time, I turn it off while working, then turn it back on before shutting down. I've been able to repeat this reli
  7. I'm guessing it will come back. For me, if debug logging is enabled the problem does not occur on startup. With debug logging disabled, it takes a few minutes for the Windows logon screen to appear (seems to be frozen, but just wait 2-3 long minutes) and EIS does not start properly. To workaround, I wait for Windows to startup, then kill the a2service.exe process, and then EIS either restarts on its own or I start it manually; after, it seems to function fine. As debug logging shouldn't stay on for long periods of time, I turn it off while working, then turn it back on before shutting down. I'
  8. Thanks, Lynx, I appreciate the assistance and I've entered a bug ticket. Something I've now noticed which is kinda funny: though the hot key seems to stop working, it looks like it queues up the switch-screen requests, and now my browser window is switching screens at random and unexpected times. Thanks very much! tr
  9. (I was away for the past week, it wasn't that I gave up...) I have upgraded my nVidia drivers to the latest version from the nVidia support site. WinXP Pro 32-bit SP3 DirectX: 9.0 GeForce 8600 GT nVidia Driver version: 258.96 nVidia Components: 6.14.12.5896 nVidia Desktop Manager: 135.27 (6.14.10.13527) I cannot enable the desktop manager with EAM guard running. I shutdown the guard, enabled the desktop manager, and reboot the PC. I now have desktop manager enabled along with EAM guard. My assigned hotkey (Alt+Home) wasn't working for switching a window between monitors, so I reas
  10. Latest efforts ... I'm no longer getting errors on shutdown! That's progress. However, I've been running the last few days with nView Desktop Manager disabled. If I try to enable it, the hourglass comes up for a min or two, then goes away and nothing changes in the Desktop Manager console. I cancelled the dialog, disabled EAM protection from the right-click menu on the systray icon, and opened nView Desktop Manager again. It was enabled, and all tabs were enabled now without doing anything further! I then re-enabled EAM, checked the nView console again and saw everything was still enable
  11. (another update) The first shutdown after the above had no errors, but did not shutdown either. The only entry in the System log was this: Another attempt to shutdown actually shutdown the computer without further delay or any errors. I then turned the computer on, did some "light" use (email, browsing), and then shutdown: no errors, no delays, no problems. It shutdown the way I would hope or expect. So there may be some difference in the above two scenarios: the first usage was "typical" for me, the second was "light". "Typical usage" for me involves software development, VMWare, a l
  12. (double post) Okay, that went well (or not)... I had an opportunity to reboot, so: I used Windows Update to update the nVidia driver; that went fine (I didn't look at nVidia's support site for the update file since Windows Update picked it up) before rebooting, I thought "just to avoid the previous problem, I will exit EAM", so I chose "Shut down Guard" from the systray icon right-click menu. I manually exited all applications and dismounted all TrueCrypt volumes. I shut Windows down (not reboot) Three error windows popped up: - TrueCrypt application error - Explorer.exe applicatio
  13. True. I had no issues with just OA installed and using ESET Nod32; it wasn't until I installed EAM that the problem came up. However, now that I recall, those entries from the EventLog came on a day when it seemed "everything" was going wrong; I had several apps crash on shutting down the system, including TrueCrypt -- and I've never before had TrueCrypt crash. Maybe I should've mentioned that previously, but I didn't think it pertinent to this topic of nVidia. as a support ticket to Emsisoft developers irrespectively in case that will persist. They may ask you for additional info I wil
  14. Good call on the Event Viewer; sometimes I focus on the problem of the "new" thing and forget the basics. There's a whole bunch (page fulls) of the following error in my Application log: The 16th was probably the day I had the most trouble. However, I haven't had any entries yesterday or today, so that's not so bad. I'll keep an eye on that log. There is this in the System log: I'm thinking that had to do with the latest update; I know I suddenly got a Windows security notice that I had no virus scanner installed and noticed the EAM icon had disappeared from the systray; then it came
  15. Hi Lynx, thanks very much for the response. I have not changed the driver -- it's the one I've always been using. You mean rules within EAM? I don't see any specific rules for nVidia in the "Application Rules" tab. I'd rather not disable nView from starting up, as I use the windows-positioning hotkey quite a bit. Yes, I've been answering "allow" and "remember this" for #4. I just wanted to confirm that was expected behavior (ie. the message coming from the app itself, not from NVIDIA's nView manager). I'm not sure what you mean by this: Which rules would I check? I know there
×
×
  • Create New...