Hiballer

Member
  • Content Count

    175
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Hiballer

  • Rank
    Forum Regular
  • Birthday 07/05/1942

Contact Methods

  • Website URL
    http://intellisigsys.net

Profile Information

  • Gender
    Male
  • Location
    Ohio
  • Interests
    Over 50 years in IT. Started in computers in 1962 while in the Navy. Spent 20 years there, then retired to the private sector. Now fully retired, but still an active IT professional. I run virtual Trainz, MS FSX, and create web sites.
  1. I've since found out that if you create a BAT file using an Administrator account, it already is set to run as an administrator. But the whole thing has been negated by the small VB application I created that makes use of an INI file before running. Since it is an EXE file, I don't have the same problems that a BAT file would give me. If I need to change any of the parameters (including where the log file goes), I can run the GUI for my app and alter the INI file. Then, the EXE files runs using the Task Scheduler whenever I want it to run. Kind of the long way around the barn, but it allows a lot of flexibility. I appreciate your help, Arthur. Bill
  2. Perfect! I am assuming that the batch file(s) I might set up should be IN the EAM home directory though. otherwise Windows will reject the command (unless you add the whole path to it or add the path to the system path. I will give this some study and see what comes of it. Oddly enough, the "Run as an administrator" check box was greyed out for some reason on the BAT file. I suspect this is why my first attempt failed. Bill
  3. Excellent! Thanks, Arthur. This is just what I'm looking for. Is there a list of the various parameters available using something like the "/?" that MS uses? If something like that is closely-held I'll understand. Bill
  4. That option is already turned off. It was never activated. I use Task Scheduler all the time for backups (using MS Sync Toy) as well as several other home-grown tasks. I experimented with s2cmd, but was never able to get it to scan. I never got the parameters set up right to the command. Maybe something like naming the scan in the EAM settings, and then calling that scan from Task Scheduler. Then it could be called like this: "C:\program Files\Emsisoft Anti-Malware\a2cmd /Midnight Scan" This is the way that Sync Toy works. Since Task Scheduler allows you to choose a user to associate with the task, that would work I think. Bill
  5. I am currently running build 7125 on both a 32-bit and a 64-bit machine. Recently, I've moved most of my activity to my 64-bit machine so the 32-bit guy sits there most of the time idling. Rather than be logged on all the time, I log off, but leave the machine running. Actually both are running 24/7. If I am not logged in on the 32-bit machine I have found that when I do, EAM immediately starts a scan of my system. Now, when I was keeping myself logged in all the time, it ran normally at 0200. But since I've logged myself off, now the scan won't start until I log back in. Despite the fact that the scan runs in the background, there is a perceptive lag that is annoying, and I want to eliminate that by forcing the scan back to 0200. My question, finally, is: How do I make EAM think I am logged on so that the scan will run at the normal time? If there is a setting in the Settings page for that, I've missed it. if there isn't one, then I strongly suggest that a setting possibly marked as "Run scans even if the user is not logged on" and a check box. I am the only users on any of my systems. Bill
  6. Yes, debugging was enabled, and I was advised to run the BETA on my 64-bitter here in this forum. Fortunately, the copy software remembered where it was as continued the copy from the point at which the machine froze. Debugging logs are usually quite large even when zipped, but I can send them via email if required. Bill
  7. Bad news! When I tried to update my 64-bitter to 6754 the earlier version froze up badly. It crashed so hard that it froze my entire desktop with the "tell us what happened" dialogue box on the screen. The mouse would disappear inside the box and outside NO click would register with the OS (Windows 7 Ultimate 64-bit). I had to hold the power button to recover, which is never a good thing. I am now running version 6752 and it seems to have recovered. The problem being that I was in the middle of a 65GB transfer from one disk to another, which also came to a screeching stop. Now I will have to do the whole thing over again. Bill
  8. Hmmm. Just noticed that my 32-bitter says it hasn't updated in 19 hours. I have it set for every 4 hours. I'll do a manual and get the new version. EDIT: got it! Bill
  9. So far, version 6740 repeat 6740 on both my machines seems to be working pretty well. I haven't had any crashes yet. I've been running with debug logging enables all along just in case. Bill
  10. Now using version 6723. The non-update bug is back. I am informed this evening that my EAM has not updated in 2 days, yet I have it set for every 4 hours. This is the 32-bit computer. For some reason, the 64-bit machine is running without this problem. After a manual update, I am now running version 6731 Bill
  11. Actually, I was down in the basement working on a project and when I came back up and wiggled the mouse to kill the screensaver, there it was. It had not just popped up. It had been there for a while. However, I got this from the Event Viewer, Administrative Events. it was repeated exactly the same three times. Log Name: Application Source: a2service.exe Date: 09/18/2016 01:00:12 Event ID: 0 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Prinserver Description: The description for Event ID 0 from source a2service.exe cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Access violation at address 00390FEF. Write of address C0000000 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="a2service.exe" /> <EventID Qualifiers="0">0</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-09-18T05:00:12.000000000Z" /> <EventRecordID>16610</EventRecordID> <Channel>Application</Channel> <Computer>Prinserver</Computer> <Security /> </System> <EventData> <Data>Access violation at address 00390FEF. Write of address C0000000</Data> </EventData> </Event> : Bill
  12. Thanks for moving this. I didn't realize there was a Public area for BETAs. This morning, the logs were correctly displayed. Now running BETA 6723. Bill
  13. Just got this today in the afternoon: 32-bit machine. Unfortunately, I was not running with debug logging enabled. And, by the way, the update logging problem has not been cured. They are all showing "\manual Update" and "Unknown update error" same as version 11. I DO realize this is BETA, so all I am doing is reporting. Bill
  14. I only installed V12 BETA a day ago, but I am impressed with the changes. Most were "under the hood", but the visible ones are good. I like the gaming mode as I use both a train simulator and a flight simulator, both in full screen. The previous version would interrupt the flow of the game when it activated a scan or update. I also like the changed appearance of the notification pop-ups from the side rather than the notification area. I get a lot of notifications from various applications, so having this come out halfway up is better. Bill