Downloads:

988

Downloads of v 2.11.0.0:

25

Last Update:

24 Dec 2020

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 (Portable)

2.11.0.0 | Updated: 24 Dec 2020

Downloads:

988

Downloads of v 2.11.0.0:

25

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 (Portable) 2.11.0.0

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Exempt:

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

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

>

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

>

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

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade log4om.portable -y --source="'STEP 3 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.portable -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Ensure log4om.portable installed
  win_chocolatey:
    name: log4om.portable
    state: present
    version: 2.11.0.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'log4om.portable' do
  action    :install
  version  '2.11.0.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: log4om.portable,
    Version: 2.11.0.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller log4om.portable
{
   Name     = 'log4om.portable'
   Ensure   = 'Present'
   Version  = '2.11.0.0'
   Source   = 'STEP 3 URL'
}

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


package { 'log4om.portable':
  provider => 'chocolatey',
  ensure   => '2.11.0.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install log4om.portable version="2.11.0.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. 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 24 Dec 2020.

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

screenshot

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  destination   = "$toolsDir"
  file          = "$toolsDir\Log4OM2_2_11_0_0_portable.zip"            
}

Get-ChocolateyUnzip @packageArgs
Remove-Item $packageArgs.file
    
# Install start menu shortcuts
$programs = [environment]::GetFolderPath([environment+specialfolder]::Programs)

$shortcutFilePath = Join-Path $programs 'Log4OM 2.lnk'
$targetPath       = Join-Path $toolsDir 'portable\L4ONG.exe'
Install-ChocolateyShortcut -shortcutFilePath $shortcutFilePath -targetPath $targetPath

$shortcutFilePath = Join-Path $programs 'Log4OM NG Config Manager.lnk'
$targetPath       = Join-Path $toolsDir 'Portable\L4ONG.ConfigManager.exe'
Install-ChocolateyShortcut -shortcutFilePath $shortcutFilePath -targetPath $targetPath

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\chocolateyuninstall.ps1 
$ErrorActionPreference = 'Stop'
$programs = [environment]::GetFolderPath([environment+specialfolder]::Programs)

$shortcutFilePath = Join-Path $programs 'Log4OM 2.lnk'
if (Test-Path $shortcutFilePath) { Remove-Item $shortcutFilePath }

$shortcutFilePath = Join-Path $programs 'Log4OM NG Config Manager.lnk'
if (Test-Path $shortcutFilePath) { Remove-Item $shortcutFilePath }
tools\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.
tools\Log4OM2_2_11_0_0_portable.zip 
md5: E3143D9D532B0C01E78CCC7A01A73D23 | sha1: B3B7C78634E022EBBCDAC133F5FA94A6A173F597 | sha256: 848F153854382747719371FF866DA785F0462E1D5727535C7F0B78D605EF87C3 | sha512: EB17C12DA36BBC70DE0E026275EDA01ED34B490B2AEBEDBA0D98BA64D42749A2E50BE62880F9732B69DC89ED1F99EE1DB0001C23C7F4639BE4DC675C5571E723
tools\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_11_0_0_portable.zip
   x64: https://www.log4om.com/l4ong/release/Log4OM2_2_0_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: 848F153854382747719371FF866DA785F0462E1D5727535C7F0B78D605EF87C3
   checksum64: 334ADD564B72479BEF2017B9829AA9D3CD39B1CD530FE6CBB68DFBC038528FBD
 
File 'LICENSE.txt' is obtained from:
   https://www.log4om.com/l4ong/usermanual/Log4OMNG_ENU.pdf

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.

Version Downloads Last Updated Status
Log4OM (Portable) 2.11.0.0 25 Thursday, December 24, 2020 Approved
Log4OM (Portable) 2.10.0.0 29 Wednesday, November 18, 2020 Approved
Log4OM (Portable) 2.9.0.0 38 Monday, September 14, 2020 Approved
Log4OM (Portable) 2.8.0.0 52 Thursday, July 2, 2020 Approved
Log4OM (Portable) 2.7.0.0 34 Monday, June 8, 2020 Approved
Log4OM (Portable) 2.6.1.0 54 Friday, May 15, 2020 Approved
Log4OM (Portable) 2.5.0.0 63 Tuesday, April 21, 2020 Approved
Log4OM (Portable) 2.4.0.0 91 Wednesday, March 4, 2020 Approved
Log4OM (Portable) 2.3.0.0 67 Monday, February 3, 2020 Approved
Log4OM (Portable) 2.2.0.0 45 Sunday, January 26, 2020 Approved

MAINTENANCE RELEASE

  • 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 (Portable) Package

Ground Rules:

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