Downloads:
381
Downloads of v 1.7.14.000:
9
Last Update:
15 Apr 2024
Published Date:
15 Apr 2024
Reviewed Date:
01 May 2024
Reviewer:
Package Maintainer(s):
Software Author(s):
- Victor Poor (W5SMM)
- Rick Muething (KN6KB)
- Phil Sherrod (W4PHS)
- Peter Woods (N6PRW)
Tags:
winlink-express ham amateur radio- Software Specific:
- Software Site
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Winlink Express
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
1.7.14.000 | Updated: 15 Apr 2024
- Software Specific:
- Software Site
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
381
Downloads of v 1.7.14.000:
9
Published:
15 Apr 2024
Reviewed:
01 May 2024
Reviewer:
Maintainer(s):
Software Author(s):
- Victor Poor (W5SMM)
- Rick Muething (KN6KB)
- Phil Sherrod (W4PHS)
- Peter Woods (N6PRW)
Winlink Express 1.7.14.000
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
Winlink Express
Winlink Express (formerly RMS Express) is the preferred Winlink radio email client because it supports all new system features, and it is the only client supporting the Winlink Hybrid Network for email delivery with or without the internet. Winlink Express is designed to be easily used by single users with a single call sign but it may also be used to simultaneously send and receive mail with one or two more tactical addresses or alternate Winlink accounts. It supports a wide selection of transceivers, TNCs and multimode controllers, sound card modes using the ARDOP, and VARA HF and FM virtual TNCs (ARDOP software TNC included), Pactor, SCS Robust Packet, VHF/UHF AX.25 packet radio, and direct telnet to CMS servers or RMS Relay (for amateur radio High Speed Multimedia [HSMM], Broadband HamNet, D-Star DD mode, internet, and any other TCP/IP network).
Winlink Express is built by the Winlink Development Team and leverages its features with simplicity as the prime design objective. It uses the open B2F extension radio transfer protocol that supports attachments, multiple addresses and tactical addresses. Winlink Express may be used in the peer-to-peer mode (connecting directly via RF to other Winlink Express or Airmail clients). Winlink Express also contains manual and automated GPS position reporting abilities, support for the Winlink catalog of downloadable weather, information and help bulletins, Saildocs and Globalmarinenet for obtaining GRIB files, and a propagation prediction feature to help determine which of the participating Winlink RMS gateway HF stations are best to connect to from anywhere on earth.
Winlink Express may be used as a client for emergency communications. It has special features for EmComm, such as HTML forms creation and compact, formless content transport, plus a growing library of automatically-updated, included forms to use. Before adopting Winlink Express as your program for EmComm, please check with your local EmComm group for their plans. This may be your ARES, RACES, ACS, AuxComm, SHARES or MARS organization that will be responsible for providing training and support.
System Requirements: Microsoft-supported 32 or 64 bit Windows OS (Windows Vista, Windows 7, 8, 10 or Windows 2003 Server, or later, or under Windows on Apple Mac and Linux machines using a VM engine or dual boot arrangement. Windows XP or earlier OS are not supported. The program makes minimal CPU demands except in modes using sound card modems. The heavy DSP demands of these modes require a computer of at least 700 MHz Pentium/Celeron class and at least 512 Meg of memory. It runs well on all modern computers and Windows tablets. If multiple applications are running concurrently, we recommend a fast, late-model computer with 2-4MB RAM or more.
Winlink Express Includes:
Built-in Customizable HTML Forms allow input and reading on exact-likeness or just "pretty" forms in a browser using form widgets like selection boxes, check boxes, and more. Further, lightweight form contents can be transmitted without the form itself, then automatically read at the other end inside the electronic form with a browser. A large, automatically-updated common library of forms is included with each copy of Winlink Express. And, the forms and templates are transportable across a radio connection as attachments.
Built-in Message Log Report Generator creates automatic reports from your local Winlink Express message records. Generates ICS-309 reports for ICS compliance and comma-separated text files. Lets you choose what logs to include in the report (Inbox, Read items, Outbox, Sent items, Saved items, Drafts, Deleted items).
$ErrorActionPreference = 'Stop'
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'Winlink Express*'
fileType = 'exe'
silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
validExitCodes= @(0)
}
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)"
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Winlink Express 1.7.15.000 | 3 | Friday, April 26, 2024 |
Waiting for Maintainer
|
|
Winlink Express 1.7.14.000 | 9 | Monday, April 15, 2024 |
Waiting for Maintainer
|
|
Winlink Express 1.7.13.000 | 46 | Sunday, February 11, 2024 | Approved | |
Winlink Express 1.7.12.000 | 21 | Thursday, December 21, 2023 | Approved | |
Winlink Express 1.7.12 | 21 | Sunday, December 24, 2023 | Approved | |
Winlink Express 1.7.11.000 | 21 | Sunday, December 17, 2023 | Approved | |
Winlink Express 1.7.10.000 | 33 | Sunday, October 15, 2023 | Approved | |
Winlink Express 1.7.9.000 | 23 | Sunday, September 10, 2023 | Approved | |
Winlink Express 1.7.8.000 | 42 | Sunday, July 9, 2023 | Approved | |
Winlink Express 1.7.7.000 | 50 | Sunday, June 18, 2023 | Approved | |
Winlink Express 1.7.6.000 | 36 | Sunday, April 16, 2023 | Approved | |
Winlink Express 1.7.5.000 | 19 | Sunday, April 9, 2023 | Approved | |
Winlink Express 1.7.4.000 | 42 | Sunday, February 19, 2023 | Approved |
Copyright 2009-2022 Victor Poor, W5SMM (SK), Rick Muething, KN6KB, Phil Sherrod, W4PHS, and Peter Woods, N6PRW
Ground Rules:
- This discussion is only about Winlink Express and the Winlink Express 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 Winlink Express, 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.
penguin359 (maintainer) on 31 Mar 2024 00:03:51 +00:00:
User 'penguin359' (maintainer) submitted package.
chocolatey-ops (reviewer) on 31 Mar 2024 00:37:22 +00:00:
winlink-express has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 31 Mar 2024 00:43:42 +00:00:
winlink-express has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/03aaa79a105824155af017bddbbc0068 for details.
The package status will be changed and will be waiting on your next actions.
Windos (reviewer) on 01 Apr 2024 03:49:30 +00:00:
Verification Status Change - Verification tests have been set to rerun.
chocolatey-ops (reviewer) on 01 Apr 2024 04:06:01 +00:00:
winlink-express has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/664cfa230f30389f54a3f5aa1148e559 for details.
The package status will be changed and will be waiting on your next actions.
Windos (reviewer) on 05 Apr 2024 04:02:33 +00:00:
Verification Status Change - Verification tests have been set to rerun.
chocolatey-ops (reviewer) on 05 Apr 2024 08:48:29 +00:00:
winlink-express has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/d493c0130f780e31c6448a986419799f for details.
The package status will be changed and will be waiting on your next actions.
penguin359 (maintainer) on 15 Apr 2024 07:08:56 +00:00:
User 'penguin359' (maintainer) submitted package.
chocolatey-ops (reviewer) on 15 Apr 2024 07:40:15 +00:00:
winlink-express has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 15 Apr 2024 07:50:44 +00:00:
winlink-express has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/3b03e96f0a6cc8916ad373a401dbe0da for details.
The package status will be changed and will be waiting on your next actions.
penguin359 (maintainer) on 16 Apr 2024 04:50:07 +00:00:
I'm having trouble reproducing the failure using the Vagrant machine from the chocolatey-test-environment. I even copied the exact command from the failed logs (and added a local source), but it was successfully installed with the correct version using:
choco.exe install winlink-express --version 1.7.14.000 -fdvy --execution-timeout=2700 --allow-downgrade --source "'c:\packages;http://chocolatey.org/api/v2/'"
The "vagrant provision" command finished with a successful 1/1 packages installed and exit status 0. I am wondering if there is something funny with the version code "1.7.14.000" which is showing as 1.7.14 and causing a mismatch, but previous versions including "1.7.13.000" did not have this issue. I also tested uninstall and it successfully was removed with exit status 0.
TheCakeIsNaOH (reviewer) on 16 Apr 2024 05:05:23 +00:00:
It looks like you might be on an old version of Chocolatey CLI due to the lack of version normalization.
Can you upgrade Chocolatey CLI to v2.2.2 on your local machine, in your CI for AU, and in the test environment (additionally the test environment image is on v3.0.0 at this point)
Regards, TheCakeIsNaOH
TheCakeIsNaOH (reviewer) on 16 Apr 2024 05:22:57 +00:00:
It looks like you might be on an old version of Chocolatey CLI due to the lack of version normalization.
Can you upgrade Chocolatey CLI to v2.2.2 on your local machine, in your CI for AU, and in the test environment (additionally the test environment image is on v3.0.0 at this point)
Regards, TheCakeIsNaOH
penguin359 (maintainer) on 29 Apr 2024 23:33:26 +00:00:
Thank you for that. I've updated to the latest test environment and reproduced the failure inside it. Looking into the matter deeper, I see that the official AppVeyor images including their latest Server 2022 images all come with Chocolatey 1.4.0. I presume that this is the problem generating the unnormalized NuGet packages. I'll add a step to the CI that updates Chocolatey before starting the regular scan and build. It is a little odd that it only recently just broke as the version normalization bug seems to be a year old now.
In any case, I think I need to reject this package as the 1.7.14 is considered a different package from this?
penguin359 (maintainer) on 29 Apr 2024 23:40:12 +00:00:
Actually, I think I still had to manually fix the version for the correct upload as it extracted the .000 suffix from the upstream webpage. I think the issue caused by the older Chocolatey CLI was just that it did not detect and fail on the unnormalized version when testing the install process. Maybe there is a newer version of the AU framework I need to pull in if that is the case so the CI fills in the correct version in the NuSpec.
flcdrg (reviewer) on 01 May 2024 23:33:32 +00:00:
FYI as far as I know AU or chocolatey-au (the newer version) won't solve the normalisation problem by itself. But worth investigating
David