Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by JeremyNicoll

  1. Using W8.1, 64bit, EIS 2017.5.1.7567, Stable feed.

    This problem happened again today.  Same reason -  running the 'fav' script inside Kedit, which then launches a VBS script to use

      set objShell = CreateObject("shell.application")

    to open a File Explorer view of a folder.  Just like last time EIS popped up a 'suspicious behaviour' alert, which couldn't be cancelled and never reached a decision.   I was writing notes in my text editor at the time, and could still Save those notes, but when eg I made a screenshot of the alert pane, started IrfanView and pasted that in, when I tried a SaveAs I just got a revolving blue circle and IrfanView's window title changed to 'Not Responding'.  I started a second instance of the text editor and tried to SaveAs from there, and also got the blue circle.

    Double-clicking my desktop shortcut to 'Admin Tools' (to go and look at EventViewer) produced no action at all.

    The EIS alert pane showed the same revolving blue circle whenever the mouse pointer was over it.  If I clicked anywhere on the pane it was replaced by an OS 'not responding' box, offering me the choice of waiting until it did respond (which never happened) or terminating EIS - which I didn't want to do.

    I was however able to sign-out.

    I signed-in again, and turned debug logging on.  Then from another Kedit session, issued fav prog (to get a list of 'prog' files and folders) and chose program-data (again).  The macro told me it had issued the command to run the VBS script.  But nothing at all then happened - no folder view opened, no alert pane was displayed.  Double-clicking 'AdminTools' again did nothing.  I took a screenshot of my edit session and was able to paste that into a new instance of IrfanView, but as before its File -> SaveAs just gave the blue spinner.  IrfanView's window title again said 'Not responding'.  I also tried double-clicking the desktop 'RecycleBin' shortcut - nothing happened.

    I signed-out again.

    I'll PM the debug logs to you.   For the avoidance of doubt, it's not the fact that I get an alert (at least when debug logging isn't on) that bothers me, but instead the fact that the alert pane isn't cancellable etc.

    (logs sent)


  2. You can right-click the EIS tray icon and select Application Rules, then click the BB tab - but here I find no difference in speed doing that vv opening the full GUI then choosing Protection and then BB.

    Adding BB to the systray icon context menu would only save you one click.   On the other hand it's not clear why Application Rules & Host Rules (ie Surf Protection, I suppose) get contetx menu links, but BB, File Guard and Firewall do not.  I think if I were Emsisoft I'd probably remove the two current rules options and just have a link to Protection settings as ocne you get there you can pick the tab you need.

  3. Yes you can delete them - delete the oldest ones.  Logs should be in:   C:\ProgramData\Emsisoft\Logs

    Names like:  a2service_20170205003925(1116).log   are named according to the part of the product that created the log (eg "a2service")  then the yyyymmddhhmmss date and time they were first created, and the last bit in brackets is (I think) the process id.   Just don't try to delete the log(s) that are being written to at the moment.

    • Upvote 1
  4. I know you said all your computers are using dynamic IP... but can I just check?   You do mean they're all on your network?    If they ARE on your network, why are you using dymaic IP - is it so that if/when the machines are taken elsewhere and use dynamic IP elsewhere, you don't have to change the way they're set up?

    Arthur commented above on the advisability (or not) of allowing traffic to/from all addresses... but if the machines are on a network then surely you only need to allow that traffic to/from the IP addresses that are valid on your network, not the entire outside world?   On the other hand, if one of these computers IS in the outside world then apart from rules in both machines' EIS firewalls, there might be a problem in the firewall component of your router (if you have one) - it may not be passing all the required inbound traffic to the target machine.

  5. Ok, that makes more sense.  Remember that as well as the tooltip the help file (somewhat wordier) would benefit from this more detailed explanation.   One thing though, by no means every user of an email client would thing of such files as /archives/ - if you're using an offline reader, especially if POP3 rather than IMAP, the files are (or could be) the live mails, not archived old ones.

  6. > The issue that was fixed is that when you move the main window to screen 2, shutdown the pc and start with only 1 screen connect, the main program will open on the 

    > visible desktop on screen 1

    OK.  Though... IS that an issue?  It's what I'd expect to have happen,  Surely you wouldn't want the window to open on a non-connected second screen?   (Having said that I know most/all of the multi-screen control software has facilities for moving windows around automatically.)

    > e issue you describe is 'quite' corner case however we might fix this.

    Yes!  The bottom righthand corner of the screen.   (I know what you mean... the trouble is that if it happens it's hard for anyone to know what's happened; whether they can then get out of the problem depends on their level of knowledge and/or access to programmers' utilities.)

  7. Back in the ... 1990s, if not a little earlier, the IBM mainframes I worked with all had a virtual layer in them, and you could make each one (with, say 4 cpus and specific number of other features, RAM etc) appear to be several separate 'LPAR's with proportions of the real resources allocated to each one.  The proportions could be fixed or, I think, dynamic though I don't think we (a UK bank) ever did the latter.  Around the time I stopped working (through illness) the OS and major applications (database systems etc) were being changed so they could migrate work not just between LPARs on one mainframe, but between sets of co-operating mainframes.  And as you say, the aim was to get as near as possible to 100% uptime.  

    On my PCs I've not yet tried VMs, but I do plan to, mainly because I want to get to know Linux or maybe BSD Unix.  I know (from running an emulated ARM architecture with RISC OS on it, under Windows) that beng able to switch between windows is a much easier way of playing with two OSes at once than a 'dual-boot' machine.  And I particularly like the idea of snapshots for rescuing me from accidents on a strange new OS. 

  8. Using EIS on Win8.1 x64

    That was: "Improved: Main program windows position when the program opens outside of the visible desktop".    If this is in response to my problem report:

    then I'm afraid I find no difference in behaviour.  A main window that's mostly dragged off-screen, on which one 'accidentally' clicks on the 'Emsisoft' logo and consequently has the About pane open, still opens that pane off-screen where one cannot know that that has happened (on W8.1 anyway).  There's no clue in the thumbnail one gets on the taskbar, and one can't drag the main window back on to the screen.   If it's a fix for something else, then it would help to know what that is! 

  9. Using EIS on Win8.1 x64

    There's no info in the help file about what this does.   The tickbox's label implies it is only(?) for Outlook/Thunderbird's files, so...  does that mean a particular file-extension or a few file-extensions, and does it mean ony when they are found in whatever are the typical locations that those apps would store their data files in?   What about data files for other email clients?

    Is whatever is done in the scan of these files any different from what happened previously when a custom scan looked at these files, if that scan was done with filtering by file-extension turned off?  (I suppose I'm assuming that if filtering by extension was on, those files previously got skipped.)

  • Create New...