Release v0.4.0: Added dual logger + --pretend flag

New Features

• Added a dual logger that would allow to still get log output when running a release version; Logs would be contained in the same folder as the executable
• Added a --pretend/-p flag that allows to dry-run the program without modifying the system

Enjoy!

Release v0.3.0: Standby List Cleaner & global refactor

Third release and probably the last one.

Every change that happened is contained within this PR: #1

For the record, I've been running this version of the program on my machine ©️ 24/7 for 6 months without any issues.

New Features

• Added a feature to clean the Windows Standby List
  • Drops memory usage down to 128KB over some time when the cleaning makes a pass
  • Drops CPU usage to 0.00001%. Only the OS is allowed to send a low memory notification to the program and the rest of the time is spent waiting on a lock.
  • Adds a new flag to enable the feature --islc
  • Adds 3 new options to configure the feature: --islc-timer, --cscm and --csfm
• Added an app icon, UAC manifest and so on.
• Completely refactored the install process to make use of the Windows Task Scheduler, as it was not possible to start something as Administrator from the previous method.

Changes

• Removed the default panic handler as it was essentially useless
• Global refactor to help maintenance

What's next?

• I need to add some sort of logging in case something goes wrong. I'll probably reuse the code used here OtaK/b0xx-viewer-rs#23

Enjoy!

Release v0.2.0: Install/uninstall, custom timer, service-like behavior

Second release and probably the last one.

Moved away from winapi crate for undocumented stuff to ntapi.

New Features

• Custom timer setting via the -t/--timer option.
• Install the program on your system and be ran at startup. (--install)
• Uninstall the program from your system (--uninstall)
• Read the timer range from your system (--values)

Please keep in mind that installing the program makes it run service-like. It starts with your computer and stays on. Also it cannot (I mean it, literally) crash while running.

Compared to other equivalent programs laying around, TimerSet takes around 500KB of memory to operate, with a cpu time of 0s after a whole day. Other programs are taking at least 5MB of RAM for instance, with some of them using the CPU from time to time.

Enjoy!

Release v0.1.0: First public release

First release of timerset.
CLI-only.

Current behavior is as follows:

• Query NT Kernel's NtQueryTimerResolution to get timer capabilities
• Set the current timer resolution to its maximum (frequency) possible via NtSetTimerResolution
• Exit

Next version will include an install method to put it in the %APPDATA% folder and execute it once at boot to set the timer in the least obtrusive way.