Koosharem

Member
  • Content Count

    64
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Koosharem

  • Rank
    Active Member

Profile Information

  • Gender
    Male
  • Location
    Northern Utah, USA
  1. Magpie501, You (or DT500) may have already solved your updating problem by this time but, I thought I'd "share" any way! 'Turns out it was a case of me "crying wolf" -- I didn't do enough checking of other installed software before coming to the forum! I stumbled onto the "fix" just today. I'm running the program WinPatrol Privacy (recently changed the name to WinPatrol Firewall). I failed to notice it was blocking the EIS program "a2service.exe" -- had it listed right there in the "Blocked Programs" Tab! All I did was change it to "Allow Program"! Now, I'm not really sure I would have connected "a2Service" with blocking a server, but in "hind-sight" it would have been worth a try. Best of luck to you, too!!
  2. GT500, 'Seems like I'm having the same problem as MagPie501!! I installed the newest version of EIS (V2017.x) yesterday. As prompted by the install instructions, I immediately attempted to "check for updates" and got a pop-up saying "cannot connect to the update server" and, to "check my internet connection". The internet link is good - I used it to download the installer!! I got the same result this morning. (I also run Malwarebytes Pro (v3.0.6) -- it updates signatures every 30min -- no problem with my internet connection there!) This problem with EIS has occurred several times over the last few months with the previous version of EIS that I just replaced. Each time, after a few days, the problem just "went away" and, the program worked fine until five days ago. I had hoped switching to the newest version would "fix" this problem. Two screen-saves are attached to illustrate what I'm dealing with. I just don't know where to go from here!! I read through the posts on this topic and, went ahead and ran the Emsisoft Diagnostic Batch File you suggested to MagPie501. Per your recomendation, I'll send the Log to you via Private Message. -- Emsisoft Internet Security Full 2017.3.1.7353 stable [en-us] OS: Windows 10 (Version 10.0, Build 0, 64-bit Edition)
  3. Thomas, Thank you for your response to my last post regarding the SIM Card Alert. Yes, I am using the Google Fi "phone and wireless service" for my Nexus 6P cell phone. (My wife's Samsung S7 uses a different cell phone service.) As I mentioned previously, this false alert does not occur very often (only 3 times since last March). So, it is not a serious problem for me. And, thank you for looking into the possible causes -- I didn't know this false alert was so unusual! (Yes, I will let you know if it persists.) Also, on the other topic concerning getting EMS operational on my wife's new Samsung S7 (as a second device on my EMS account), we are fully "up-and-running" with that as well. Thanks to your help on this problem also!! Best regards
  4. Thomas, I waited awhile to reply to your last post, just to see if the "Changed Sim Card" Alert would happen again -- and it DID!! First thing this morning. I had left the device (a Google Nexus 6P) on my desk overnight (fully charged/in standby mode -- still connected to the AC charger -- that is, no rough handling or dropping/jarring the device all night). My wife (who's phone gets the call regarding a "Changed SIM Card" and, had gotten up just before me) told me she had just received "the call" !! The Nexus only has one SIM card. The device was shipped to me (by Google) with the SIM card packaged in the same "box" but, not installed. There were instructions on how to accomplish the installation which I followed. As I recall, there was a "frame or carrier" that the SIM card was to be placed in before sliding the combination ("carrier-with-card") into a "slot" on the side of the device (it "snapped" firmly into place). This assembly took place last March (2016) and, to my knowledge, the device has performed flawlesssly ever since -- no suggestion of the SIM card not functioning properly (no interruptions in service). Another observation: the device is fully enclosed on the back and, all four sides, by a very rugged plastic protective case; the "slot" where I inserted the "carrier-with-card" is completely covered by this protective case, making it quite impossible for the card to move at all. Thomas, I'm definitely NOT complaining nor disappointed with the EMS product. In fact, I was a quite surprised and impressed that, in addition to its basic antimalware scanning and web security features, it also includes Anti-Theft & Location capabilities! That's great! My wife just got a Samsung S7 device and, we're going to protect it with EMS as well. This "Changed SIM Card false-alarm thing" is something I thought you would like to know about. If it becomes more frequent, I can always delete my wife's "trusted" phone number. ;-) Best regards, Koosharem
  5. Thomas, Sorry for the delay in getting back. I believe we have made "great progress" on this issue! I had my wife sent a test "LOCATE" command from our neighbor's phone to mine and everything worked!! After sending the command, she received the proper SMS response giving her a "time stamp", the URL link for Google Maps and, a set of Lat and Long coordinates for the location of my phone. Also, she sent the "SCREAM" command to my phone and, that worked as well. I believe what happened before was I misunderstood the meaning of the two positions of the On/OFF slider-switch for the SMS command group. The "ON" position is with the blue "dot" moved fully to the RIGHT. "Off" is fully to the LEFT. What "fooled" me was, in the ON position (fully RIGHT) the "dot" is a very PALE BLUE. Whereas in the OFF position (fully LEFT) the dot is a much DARKER blue. For some reason I connected "DARK blue" with the switch being "ON". So, we're done!! Thanks for your help. Now, for something really crazy! This happened awhile ago near the beginning of this "Issue" (I ignored it because I was more concerned with "LOCATE" & "SCREAM".) One day my wife (my "trusted friend") got an EMS Anti-Theft "SIM CHANGE" alert from MY PHONE!! I didn not send that alert (at least knowingly; and perhaps its not even possible) AND, my phone's SIM card has NOT BEEN CHANGED!! This has not happened (yet) a second time.
  6. Thomas, Thank you for your response. I went to Anti-Theft > SMS CONTROL, disabled the functionality and, re-activated it (as indicated by the solid blue "slider button"). Also, I verified that I am using the correct syntax for these two commands. Next, I logged into my account at the EMS online portal, selected my mobile device and, clicked on "Anti-Theft" at the upper right. Then, I chose the gray button next to the blue "LOCATE" button. This opened a new dialog box. I entered a short "test message", clicked on the "Play Alarm" box, and then clicked "SEND". My phone did transmit a loud alarm tone and, "Google Maps" displayed a map (on my computer screen) showing my correct vicintiy, with a red "balloon" indicating the phone's approximate location. All is well so far, however, I did not get the "test" message!? Does this adequately demonstrate the LOCATE command is working properly when sent from another phone? Previously, when I sent the LOCATE command from my neighbor's phone, I did not get an "Alarm" tone (my phone was not there). But I did expect an SMS response with the web link to Google Maps, which would allow me to locate the "lost" phone. (All that came back as a response to my neighbor's phone was the command: "BD-xxxx LOCATE".)
  7. Thomas, Thank you and JeremyNicoll for your replies to my questions. I've been away from home the last two weeks but, I'm still puzzled with the responses I get using the two commands "LOCATE" and "SCREAM". I used a neighbor's iPhone to send these two commands to my phone (a Google Nexus 6P Android). In this case, I used my phone's number for "To" and, "BD-xxxx LOCATE/SCREAM" for the two (individual) SMSs ("xxxx" being my personal PIN). Each SMS was received by my phone (as individual SMS text messages e.g., "BD-xxxx LOCATE & SCREAM"). However, my phone did NOT "Scream" and, my neighbor's phone did NOT get it's expected response (SMS): "My location at 4:59PM was https://maps.google.com/maps?q=41.850336,-112.0056871". (This "expected response" is illustrated under "Mobile Security/ Dashboard/Anti-Theft/SMS Control/LOCATE" on my phone's (Trial) Emsisoft Mobile Security App.) In preparing this post, I noticed the LOCATE command (under "SMS Control") refers to the maps.Google.com website, where as the SCREAM command refers to the central.emsisoft.com website regarding tracking/locating the phone. Why are these references different??
  8. Thomas, Thanks for your reply. Yes, and sorry for being so dense on this!! Your instruction makes sense. It also caused me to realize I couldn't use my wife's NON Smartphone to test the commands! I'll have to get a friend (with a smartphone) to do that (but, just for the LOCATE & SCREAM commands). Is my thinking correct that it would NOT be wise "test" the other commands (LOCK, WIPE, CALLME) but, use them only in the event my phone is really lost or stolen? (Especially regarding the WIPE command! )
  9. Just installed Emsisoft Mobile Security 3.0.1 (Trial) and, I'm having trouble getting the Anti-Theft SMS Commands to work. Take "LOCATE" for example. The instruction is: "Send this command ("BD-xxxx LOCATE") from any phone to get the response illustrated below" . I understand the "xxxx" is my PIN but, what do I use for the SMS address/phone number ? What am I missing here??
  10. GT500, Thanks for the prompt reply. And, YES, after copying the EEK to a folder on my HD I was able to launch the program and go to the User Interface. There it showed the software was up-to-date and, I was was able to setup and run a Custom Scan. Some where in there, I also saw it update some signatures. So, in all aspects, by launching EEK from the HD, it seems to work fine. I'm a bit disappointed at losing the "isolation" (from the PC) provided by the USB flash drive but, "so be it". As an after-thought, I noticed in the Update Log (when I got to view it after the HD-launch today), a "Comm Error" is shown yesterday and, five minutes later, a second entry showing a successful update involving "a2hosts.dat" and a long list of signature updates -- all totaling an 18.7MB update. Perhaps that error was the culprit . . . but, I don't understand why/how it could prevent me from re-launching the EEK from the USB flash drive later yesterday.
  11. I also just downloaded and installed EEK (v11.0.0.6082) on a flash drive. Upon launching it the first time, I was promped to check for updates and, they too were downloaded and installed. Next, I ran Custom scan that seemed to complete successfully. About that time I got an "error" pop-up from Windows saying: "a device driver was not found/not installed successfully/device unplugged". Buy this time the user interface for EEK had "closed" so, I couldn't check the log to see if anything had been found during the scan. I attempted to re-launch EEK but it would no launch a second time!! I returned to the Newsletter that I accessed the EEK download from and saw a link for "an online version" of EEK. Have I misunderstood something here -- is the fact that I have installed my copy of EEK on a flash/thumb drive mean I cannot get the updates?? Why would I get an error about a device driver (I've been using my USB ports quite regularly with no problem). I'm running Windows 7 and the following security programs: Windows 7 PRO(64bit) SP-1; 16GB RAM Windows Defender Emsisoft Internet Security (malware & firewall) Malwarebytes Home Premium WinPatrol/WinPrivacy/WinAntiRansom Task Catcher (BillP Studios)
  12. Hello Christian, Again, I applogize for the long delay in responding -- I've been away from home again! I now have no issues regarding getting EIS installed on and running from the D:\Program Files\ path. All is well!! I may have confused things by bringing up the topic of "64bit programs" vs "32bit programs" as it relates to the Windows 7 practice of segregating them on different paths for a given drive: "Program Files\" for 64bit software and, "Program Files x86\" for 32bit software. Your first response to this post suggested I try using the "Program Files x86" path (i.e., as though EIS was programmed for 32bit words and should be there.) By the time I got to read your response, I had discovered my error and, proceded to compose the command-prompt correctly -- BUT -- I installed it in the "Program Files\ path (i.e., along with other 64bit programs) as this was my original intention. Everything seems to be working fine with this arrangement, as-is. But, have I placed EIS in the "wrong path" as far as running under Windows 7 is concerned?? Is there any operational drawback to "misplacing" it there if that is the case?? More specifically, what word size is EIS programmed for?? Thank you for your patience in answering my questions.
  13. Hello Christian, Thank you for your prompt reply! I appologize for my delay in responding -- I was away on business for the rest of last week after sending my post. In the meantime, I had an opportunity to carefully review my "failed" installation process that resulted in not getting EIS installed on the D-drive -- I failed to place quotation marks (" ") around the target-drive parameters as follows: /DIR="D:\Program Files\Emsisoft Internet Security" ! I have just finished uninstalling EIS (from C-drive) and re-installing it on the D-drive using the parameter-string as above -- and, the installation was fully successful!! So, it seems I was the "problem" all along!! However, after reading your reponse regarding use of the D:\Program Files x86 path instead, raises a follow-on question/concern. I have attempted to install all 64 bit software in the D:\Program Files path; all other software (i.e., 32 bit) in D:\Program Files x86 path. Since I have had no problem running EAM in the 64 bit path before changing over to EIS, I thought that path would be appropriate for EIS also. I scanned the on-line EIS Help File but did not find any mention of program word-size. Do you have any comment on my choice of installation folders??
  14. I'm running Win 7 Pro/64bit and SP1. I just finished "converting" from EAM + OA Premium to EIS. I use a 256GB SSD as the "C-drive" for the OS (primarily) and, a 2TB HD as the "D-drive" for application programs and data. I have found some program installers do not allow the user to select the "target" drive for installation. EAM was one of these! I got help from the EAM Forum that told me how to use the Windows Command-Prompt function (with appropriate parameters) to direct the installation to a desired drive and folder/subfolder. I attempted this same approach with EIS but was greatly disappointed!! I very carefully went through the procedure, directing the installation to "D:\Program Files\Emsisoft Internet Security". Instead, EIS was installed in "C:\Program Files (x86)"!! What am I missing?? Why does the Command-Prompt approach work as expected in one instance and not another?? (It is extremely frustrating to be forced to load-up a fast, SSD with programs that do lots of "read/writes" (i.e., updates) when there is a high-capacity disk-drive available!)
  15. I recently installed OA Premiun (V7.0.0.1866) on a new (i.e, replacement) computer running Windows 7 PRO SP1 64bit. The installation "Wizard" reported it was sucessful. I "ticked" the "Re-start your computer now" box and clicked "Finish". Windows closed and re-started. An OA "Welcome" window opened, I entered my license key and clicked "next". Then a strange thing happened. I got this ERROR notice: "Check your internet connection or contact Support. Socket error #11001. Host not found." Sure enough, I no longer had an internet connection. OA was listed in All Programs, but would not launch. I assumed this was because, with out internet access, the license key could not be verified . After about week of unsuccessful trouble-shooting (and no internet access), I un-installed OA and re-gained fully functional internet access! Is this just circumstantial? Or are there some incompatibility issues between OA and Windows 7?? Also, on this installation I included the option to install the "TLEM Network Service/Device Software". (Apparantly this is not a digitally signed driver according to Windows 7.) What is this "service", and could it have any connection with blocking my internet access?? At this point I am very hesitant to re-install OA. It's a great disappointment because I have been extremely satisfied with OA since May 2011 -- it is a lot more than just a "firewall"!!