Downloads of v


Last Update:

29 Oct 2022

Package Maintainer(s):

Software Author(s):

  • Daniele Pistollato IW3HMH
  • Terry G4POP
  • Chuck K7PT
  • Rolf LA9FFA
  • Doug W7DRM
  • Peter G3ZSS
  • Claus OE6CLD


log4om log HAM radio amateur


  • 1
  • 2
  • 3 | Updated: 29 Oct 2022



Downloads of v



Software Author(s):

  • Daniele Pistollato IW3HMH
  • Terry G4POP
  • Chuck K7PT
  • Rolf LA9FFA
  • Doug W7DRM
  • Peter G3ZSS
  • Claus OE6CLD

  • 1
  • 2
  • 3

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Dotnet4.6.2 is exempted of verification because it requires a reboot after KB2919355


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Log4OM, run the following command from the command line or from PowerShell:


To upgrade Log4OM, run the following command from the command line or from PowerShell:


To uninstall Log4OM, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade log4om -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade log4om -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install log4om
    name: log4om
    version: ''
    state: present

See docs at

chocolatey_package 'log4om' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller log4om
    Name     = "log4om"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'log4om':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 29 Oct 2022.


Log4OM is developed by IW3HMH Daniele Pistollato.

Software focused on Ham Radio activity and requires very low resources from the host computer.

It has been tested on all Windows operating systems from Windows Vista to the latest version available. Log4Om runs on Window Tablets with its full features and can be executed from a memory stick, it’s installation doesn’t use system registry to store information. Windows XP SP3 support terminated with release 1.32.1


  • Interfaced with QRZ.COM and HAMQTH.COM for rapid searches and QSO data enhancements (massive (Bulk) updates are supported).
  • Innovative graphic DX Cluster management, with SPOT real time view on world map and auto tuning of the radio with CAT support.
  • Super Cluster: An alternative cluster based on online data sent by users to
  • Complete and unique SOTA support
  • MySQL support for large databases and multi operator operations.
  • CAT support for numerous radios, through HAMLIB and OMNIRIG
  • Cluster integrated with propagation informations by
  • ADIF import and ADIF / Excel (csv) / PDF export
  • Integrated with E-QSL, LOTW, ClubLog,, HamQth, QRZ.COM, SOTA, IOTA
  • Complete log searching features, Log4OM enables the OM to update QSO’s offline with updated information.
  • Optimized for “paper to electronic” log conversion, with features that drammatically speed up the time taken to insert a QSO (auto-time functions with predefined QSO separations, automatically set timings for fast pile-up management)
  • Language selectable English or Italian
  • Complete label print feature
  • SO2R support
  • Innovative NET CONTROL support
  • Complete statistics set with support for main awards (ARRL and RSGB IOTA)
  • Full K1EL Winkeyer Support
  • Huge Award System with more than 50 official awards and an infinite number of user created awards
  • Resources and external services are automatically updated
  • Software Voice Keyer

Package Parameters

  • --installargs "'/DIR=c:\\path\\to\\folder'" - Install LogOM in the specified folder.


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Log4OM 40 Friday, July 1, 2022 Approved
Log4OM 41 Saturday, May 21, 2022 Approved
Log4OM 30 Saturday, April 9, 2022 Approved
Log4OM 23 Tuesday, April 5, 2022 Approved
Log4OM 59 Monday, February 14, 2022 Approved
Log4OM 50 Tuesday, January 25, 2022 Approved
Log4OM 55 Saturday, November 13, 2021 Approved
Log4OM 59 Sunday, September 5, 2021 Approved
Log4OM 44 Tuesday, August 3, 2021 Approved
Log4OM 57 Friday, July 2, 2021 Approved
Log4OM 42 Friday, July 2, 2021 Approved
Log4OM 55 Wednesday, June 9, 2021 Approved
Log4OM 49 Monday, June 7, 2021 Approved
Log4OM 73 Saturday, April 24, 2021 Approved
Log4OM 61 Sunday, March 28, 2021 Approved
Log4OM 88 Thursday, December 24, 2020 Approved
Log4OM 90 Wednesday, November 18, 2020 Approved
Log4OM 95 Monday, September 14, 2020 Approved
Log4OM 102 Thursday, July 2, 2020 Approved
Log4OM 117 Monday, June 8, 2020 Approved
Log4OM 132 Friday, May 15, 2020 Approved
Log4OM 150 Tuesday, April 21, 2020 Approved
Log4OM 154 Sunday, March 22, 2020 Approved
Log4OM 113 Wednesday, March 4, 2020 Approved
Log4OM 128 Monday, February 3, 2020 Approved
Log4OM 113 Sunday, January 26, 2020 Approved
Log4OM 92 Tuesday, January 21, 2020 Approved
Log4OM 93 Monday, January 20, 2020 Approved
Log4OM 89 Friday, January 17, 2020 Approved
Log4OM 126 Friday, January 17, 2020 Approved
Log4OM 1.40.0 133 Thursday, October 24, 2019 Approved
Log4OM 1.39.0 138 Thursday, August 15, 2019 Approved
Log4OM 1.38.0 134 Saturday, June 15, 2019 Approved
Log4OM 1.37.0 141 Monday, May 27, 2019 Approved
Log4OM 117 Thursday, March 14, 2019 Approved
Log4OM 1.36.0 195 Monday, March 4, 2019 Approved


  • Added support to QARTest direct QSO import in Log4OM Communicator (Inbound settings, default port is 9458)
  • Added support to N1MM direct QSO import (UDP Broadgast -> CONTACT option in N1MM settings) in Log4OM Communicator (Inbound settings, default port 12060)
  • Added new CAT mode in settings (Source: N1MM – selection: External) that overrides Omnirig and Hamlib (requires a running communicator instance)
  • Set autofocus over search fields of QSO Management and QSL Management forms
  • Added Aircraft Scatter in the propagation mode list and moved the whole list to external configuration file (propagation.csv)
Discussion for the Log4OM Package

Ground Rules:

  • This discussion is only about Log4OM and the Log4OM package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Log4OM, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus