Downloads:

2,633

Downloads of v 2.18.0.0:

25

Last Update:

13 Nov 2021

Package Maintainer(s):

Software Author(s):

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

Tags:

log4om log HAM radio amateur

Log4OM (Install)

  • 1
  • 2
  • 3

2.18.0.0 | Updated: 13 Nov 2021

Downloads:

2,633

Downloads of v 2.18.0.0:

25

Maintainer(s):

Software Author(s):

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

  • 1
  • 2
  • 3
Log4OM (Install) 2.18.0.0

  • 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.

Details

Scan Testing Successful:

No detections found in any package files

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

To uninstall Log4OM (Install), 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 https://community.chocolatey.org/api/v2/)


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 https://community.chocolatey.org/api/v2/. 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.install -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.install -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install log4om.install
  win_chocolatey:
    name: log4om.install
    version: '2.18.0.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


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

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller log4om.install
{
    Name     = "log4om.install"
    Version  = "2.18.0.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'log4om.install':
  ensure   => '2.18.0.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


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 14 Nov 2021.

Description

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

Note

Users of Log4OM version 1 must export an ADIF file from version 1 and import it into version 2 once a database has been created in version 2 as described in Quick_Start_Guide.pdf.

Features

  • 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 HRDLog.net
  • 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 HRDLog.net
  • ADIF import and ADIF / Excel (csv) / PDF export
  • Integrated with E-QSL, LOTW, ClubLog, HRDLog.net, 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.

screenshot


legal\LICENSE.txt
From: https://www.log4om.com/l4ong/usermanual/Log4OMNG_ENU.pdf

LICENSE

The software is freely downloadable at https://www.log4om.comand its use is free of charge and available for any purpose. 
legal\VERIFICATION.txt
VERIFICATION
 
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
Package can be verified like this:
 
1. Download:
 
   x32: https://www.log4om.com/l4ong/release/Log4OM2_2_18_0_0.zip
   x64: https://www.log4om.com/l4ong/release/Log4OM2_2_18_0_0.zip
  
2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'
 
   checksum type: sha256
   checksum32: 07B72A73AD6919E26DF0F31B0D23177C4693ED4F46B8E90A66E7AD2B5DB90F50
   checksum64: 07B72A73AD6919E26DF0F31B0D23177C4693ED4F46B8E90A66E7AD2B5DB90F50
 
File 'LICENSE.txt' is obtained from:
   https://www.log4om.com/l4ong/usermanual/Log4OMNG_ENU.pdf
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

# Remove previous setup
Remove-Item -Path "$toolsDir\*.exe" -ErrorAction SilentlyContinue

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  destination   = "$toolsDir"
  fileFullPath  = "$toolsDir\Log4OM2_2_18_0_0.zip"  
}
Get-ChocolateyUnzip @packageArgs
Remove-Item -Path $packageArgs.fileFullPath

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName  
  file          = "$toolsDir\Log4OM2_2_18_0_0.exe"
  silentArgs    = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- /components=""'
}
Install-ChocolateyInstallPackage @packageArgs

Write-Warning 'Users of Log4OM version 1 must export an ADIF file from version 1 and import it into version 2 once a database has been created in version 2 as described in Quick_Start_Guide.pdf.'
tools\Log4OM2_2_18_0_0.zip
md5: C3809F84E7671F047C49FC7BCE472075 | sha1: 6035E9E82FE7EEAAD8F706E8140DFD378B62750F | sha256: 07B72A73AD6919E26DF0F31B0D23177C4693ED4F46B8E90A66E7AD2B5DB90F50 | sha512: 108372318738F17D0AB2778D65A680D1B9014044D14BBA319983E6F08858B3FDF1F4AB3CE25C9489BB8BE7FBFB447C64E5081CFD7A5FFA19B0230F5DB6776038

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 (Install) 2.17.0.0 29 Sunday, September 5, 2021 Approved
Log4OM (Install) 2.16.0.0 34 Tuesday, August 3, 2021 Approved
Log4OM (Install) 2.15.0.0 31 Friday, July 2, 2021 Approved
Log4OM (Install) 2.14.1.00001 18 Friday, July 2, 2021 Approved
Log4OM (Install) 2.14.1.0 27 Wednesday, June 9, 2021 Approved
Log4OM (Install) 2.14.0.0 28 Monday, June 7, 2021 Approved
Log4OM (Install) 2.13.0.0 43 Saturday, April 24, 2021 Approved
Log4OM (Install) 2.12.0.0 41 Sunday, March 28, 2021 Approved
Log4OM (Install) 2.11.0.0 66 Thursday, December 24, 2020 Approved

Discussion for the Log4OM (Install) Package

Ground Rules:

  • This discussion is only about Log4OM (Install) and the Log4OM (Install) 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 (Install), 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