Downloads:

278

Downloads of v 7.3.33:

16

Last Update:

9/19/2019

Package Maintainer(s):

Software Author(s):

  • Colin Morris
  • G0CUZ

Tags:

winlog32 log HAM radio amateur

winlog32

7.3.33 | Updated: 9/19/2019

Downloads:

278

Downloads of v 7.3.33:

16

Maintainer(s):

Software Author(s):

  • Colin Morris
  • G0CUZ

winlog32 7.3.33

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall winlog32, 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 winlog32 -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 winlog32 -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 winlog32 installed
  win_chocolatey:
    name: winlog32
    state: present
    version: 7.3.33
    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 'winlog32' do
  action    :install
  version  '7.3.33'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: winlog32,
    Version: 7.3.33,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller winlog32
{
   Name     = 'winlog32'
   Ensure   = 'Present'
   Version  = '7.3.33'
   Source   = 'STEP 3 URL'
}

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


package { 'winlog32':
  provider => 'chocolatey',
  ensure   => '7.3.33',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install winlog32 version="7.3.33" 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 was approved as a trusted package on 9/19/2019.

Description

This software has been in development for many years and the author (G0CUZ) provides this software FREE to use by all Radio Amateurs and SWL's in true 'Ham Spirit', as such no warranty is implied or given as to it's suitability or reliability.

Although Winlog32 is general purpose logging software, it has a definite slant on DX'ing on both HF and VHF with comprehensive tracking of various awards programs like DXCC, IOTA, WAZ etc. and includes all the features you would expect from good quality logging and DXing software and more.....

Features

Winlog32 logging software for all Windows platforms.

Do you want to know if Winlog32 will suit your purposes? - please read on.....

  • FREE, unrestricted use with no limitations of any kind
  • Works on all Windows platforms, 95, 98, ME, 2000, XP, Vista, W7, W8, W8.1, W10
  • Includes all regular logging, DXCluster, rig control features
  • Dedicated web-site, info, download plus well supported Forum
  • Regular updates
  • Well established, respected and has been in development for over 20 years
  • Suitable for general logging purposes, with emphasis on award chasing and HF-VHF DXing
  • Used world-wide for many years
  • Simple and intuitive operation and uncluttered layout
  • Works within single container window
  • Logs
    • Versatile and secure log database system using established MS Access Jet 3.5
    • Multiple logs in each log database
    • Multiple log databases
    • Unlimited number of log entries
    • Remote logging capable
  • Separate award tracking for each individual log database
  • Real-time log input
  • Last entered QSOs always displayed
  • Auto-date and time function
  • Auto-search and display previous QSOs
  • Automatic database updates and checks made during QSO input

screenshot


legal\LICENSE.txt

From: http://www.winlog32.co.uk

LICENSE

This software is completely free to download and use without losing any of the programs functionality and without limitations of any kind. It is free to distribute on a one-to-one basis, providing all original files are intact and not modified in any way and that no charge is made for this. Any bulk distribution is prohibited without specific permission from the Author.
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: http://www.winlog32.co.uk/files/wl32v73.exe
   x64: http://www.winlog32.co.uk/files/wl32v73.exe
  
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: 6142236DE437B3A31E126974F5D878EDCD9F979EFAB49719B713212098DF71B0
   checksum64: 6142236DE437B3A31E126974F5D878EDCD9F979EFAB49719B713212098DF71B0
 
File 'LICENSE.txt' is obtained from:
   http://www.winlog32.co.uk
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

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

Install-ChocolateyInstallPackage @packageArgs
tools\wl32v73.exe
md5: 5F3AAE26EFDFF4E69876EAA49DC81CF7 | sha1: 66B4A6EF170C5F22D632BE84973B6A2A91F01240 | sha256: 6142236DE437B3A31E126974F5D878EDCD9F979EFAB49719B713212098DF71B0 | sha512: C12D2C5C97689CCDD337453F8AEC32DD9275BD82EF43D2C029B8C8E5A5FE73976D299EFA093293366C1D7A3BA44061B87DC16886CDCD1A9731EA49AAD13999F4

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
winlog32 7.3.32 65 Saturday, June 22, 2019 Approved
winlog32 7.3.31 29 Thursday, June 13, 2019 Approved
winlog32 7.3.29.20190504 50 Saturday, May 4, 2019 Approved
winlog32 7.3.29 39 Wednesday, April 3, 2019 Approved
winlog32 7.3.28 31 Sunday, March 31, 2019 Approved
winlog32 7.3 48 Wednesday, March 13, 2019 Approved

This package has no dependencies.

Discussion for the winlog32 Package

Ground Rules:

  • This discussion is only about winlog32 and the winlog32 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 winlog32, 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