I don't disagree John. But the EmComm leaders have decided that forms save critical bandwidth over the air, and forms must be used. Regrettably, forms are proprietary in Winlink, so EmComm leaders

I looked on the winlink site and the HTML and CSS for existing forms does not appear to be independently downloadable, nor do I see a quick link to the data only transport. Open things up and maybe

Whatcom county is doing something very interesting to solve these problems and it works very well on a Rpi with a UDRC controller. We are using Fldigi with Flmsg running MT-63 2000L on VHF. Flmsg

For EmComm oriented clients, there are a few key functions necessary in client software: -Forms ie: HTML/CSS Forms creation & content-only transport -Tactical Address Support Outpost, Pat, Paclink

I'm going to regret wading into this, but here I go anyway.... I've been instructing EMCOMM teams on WE for quite some time now. It can be rather challenging to say the least. While the folks in this

This is just a symptom of a larger problem, people who write software for legacy operating systems only and don't document how their software operates. Really, it should not matter that Winlink

I agree with Steve. The whole idea of Emcomm is for portability, in my opinion. I like using laptops too but I would like an option of using an OS other than WinDoze if the case arises that WinDoze

Wine has not been ported to the ARM architecture, so NO Windoze app will work on a RPi. Is the real challenge here a Winlink development team which is myopic in their support for various operating

Scott Currie <scott.d.currie@...> writes: Yes my apologies if anyone thought I was promoting that. You can NOT run WE or most/any windows apps on an ARM platform under wine. I am not a fan of

Scott Currie <scott.d.currie@...> writes: Yep. If you just want messaging then the options I mentioned will work if you need to use Winlink Express features then go with Windows. You could use

plinBPQ is not a platform you can run WE on. It can serve as a CMS gateway, or even a connection to a TNC/soundcard for WE to use, but you would still need to install WE "elsewhere". Getting WE to

None of these options support the forms function of Winlink Express. I realize there are other ways to achieve this, but that train has left. The vast majority of Winlink users are using WE and its

For most linux platforms: paclink-unix https://github.com/nwdigitalradio/paclink-unix pat http://getpat.io/ pigate http://www.pigate.net/ linbpq You have choices. Full disclosure, I'm one of the

Linux RMS Gateway will be supported and will continue to work. /Basil n7nix

[Moderator - this should be in the UDRC subgroup.] John I've been looking for an alternative platform to run Winlink Express as a client on. I've had problems running the winlink program on the

Randy, Yes, you can run LinBPQ as a Winlink Gateway on a RPi with Direwolf. There are instructions for setting up an RMS Gateway on a Pi here:

So, theoretically yes. I don't currently have a UDRC available, but I have run my plinBPQ node and pointed it to a Direwolf instance running on a different Linux machine on the local LAN. Running on

It appears that LinuxRMS may stop working in the near future when Winlink CMS stops supporting legacy mode. Has anyone made LinBPQ work with Direwolf? I’d like to do that on. RPi w/UDRC. (For

This block Diagram might help. DRAWS is based on the UDRC-II which has been shipping for 2 years.

Nothing is being 'hidden', this is a new product. What exists is available.