Axys Idle Closer Files

v2020.07.25
Fixed issues:
-Better handling when Axys3 is running on a shared virtual
machine. If you run into any problems then start AxysCloser.exe
from the command prompt with the log option, example:
F:\Axys3\AxysCloser.exe -Log:C:\temp\AxysCloserLog.txt

Once you have a log file, attach it in an email to
info@opulos.com along with a description of the problem.

The most common issue is when Axys32 is running in administrator
mode (a.k.a. UAC elevated permissions), but AxysCloser.exe is
running in normal permissions. In order to work correctly,
AxysCloser needs to be running at the same permission level as
Axys32. One solution to this is to right-click on AxysCloser
and choose the "Run as administrator" option. Another option
is to setup a shortcut to start Axys32 in normal mode using
the following:

Target: C:\Windows\System32\cmd.exe /min /C "set __COMPAT_LAYER=RUNASINVOKER && start "" axys32.exe"
Start in: F:\Axys3
Run: Minimized

Change "Start in" to match your network drive letter, which might be F:, K:, P:, etc.


v2018.11.09
Fixed issues:
-Now Axys32.exe and Rep32.exe processes running are only
 included if the process session id matches the current
 process's session id. This should fix the issue for users
 on terminal machines where AxysCloser is detecting
 processes from other sessions.

v2018.10.26
Fixed issues:
-The Windows Management Instrumentation (WMI) service threw a
 "Not found" exception when requesting the username for a
 running process. The request is now wrapped in a try-catch
 statement to prevent the application from crashing. However,
 if the username of a running process is not determined then
 it is assumed to ran by the current user. On terminals
 hosting multiple users, this could means AxysCloser includes
 Axys processes from all users, rather than only the current
 user.
-Fixed issue when deleting stale AxysUser_ token text files.
 Files would be deleted if they were over a minute without
 being updated. However, the file's last write time was
 being compared to the computer's local time, instead of the
 server's local time. When a file is saved on a network,
 the server uses its local time as the last write time. So if
 a computer's local time was in the future (compared to the
 file server) by over a minute, then it would end up deleting
 all the token files.
-Added -Log or -Log:<filename> option to the starting
 arguments. If filename is not specified then the default
 folder is \Users\username\AppData\Local\Opulos\AxysCloser\

v2018.10.05
Fixed issues:
-Mapped drive delay on login. A problem happened when Axys is
 installed on a network mapped drive that is unavailable when
 AxysCloser first started. In this case, AxysCloser checked
 local and network drives for axys32.exe, e.g. D:\axys32.exe,
 D:\Axys3\axys32.exe and D:\Axys\axys32.exe. However, the last
 drive letter checked would then be the drive letter checked
 going forward. So when the network mapped drive eventually
 became available, AxysCloser was checking the wrong drive
 letter, instead of the one in the registry.

v2018.01.11
Fixed issues:
-The program now checks the user name of the other AxysCloser.exe
 processes running in order to determine to message that the
 program is already running. Terminal users should now be able
 to use AxysCloser without seeing the alert because AxysCloser.exe
 is running in another user's session.

v2017.12.04
New Features:
-Updater.exe is no longer used. Instead the program copies itself
 to the local temp folder to do the upgrade. The reason is to avoid
 the windows alert dialog that appears when launching programs
 from the network.

v2017.11.29
New Features:
-Changed the order of the ini search to look in the user's roaming
 folder first.

v2017.10.02
New Features:
-Added ability to set the default minutes idle and countdown values.
 The program looks for the AxysCloser.ini in the following location
 in order:
 1) The Axys network folder, e.g. F:\Axys3\AxysCloser.ini
 2) The users's app data roaming folder, e.g:
    C:\Users\<user>\AppData\Roaming\Opulos\AxysCloser\AxysCloser.ini
 3) The same folder as the program itself.
 The first file found is used. Thus, it is possible for a firm to
 specify the default values for all users. A sample AxysCloser.ini
 is included in the download zip file.

v2017.09.17
Fixed issues:
-This version launches from the user's local folder on login. The old
 version launched from the network folder. However, it has been
 observed that some network admins lock down launching applications
 from network folders. This new version will detect if the user has
 the launch on start option checked and automatically update the
 registry to launch from the local folder. Updater.exe is bundled
 in the zip and should be placed in the same local folder. When
 AxysCloser starts, it checks to see if Updater.exe exists, and
 if there is a new version of AxysCloser.exe in the Axys3 network
 folder. If so, AxysCloser runs Updater to copy the new file from
 the network folder to the local folder and then Updater runs the
 newly copied AxysCloser version from the local folder.

v2017.02.22
Fixed issues:
-Countdown now starts even if the tray icon is never clicked. Before
 it would only start after the icon was clicked for the first time.

v2016.12.20
Fixed issues:
-A default icon is provided if the one from axys32.exe cannot be found
 or extracted. If axys32.exe cannot be found then it could mean the
 registry settings point to the wrong folder. To check, run regedit
 and verify HKEY_CURRENT_USER\Software\Advent\Axys\3\ExePath is
 correct.