[Nut-upsuser] How to setup the NUT client on Windows?

[planet.et at gmail.com]

Hi guys,

Thanks very much for your answers!

> ...but there's only so much documentation that can cover all the workarounds.
> At some point, you need a Windows developer to fix the issues, and to propose
> ways to handle things in the source tree that can work for both Windows and
> POSIX systems.
>
> There were some serious problems with the original Windows port branch that
> rendered it un-mergeable (it was prior to the Git conversion). That and other related
> issues are linked here: https://github.com/networkupstools/nut/issues/5

Thanks for pointing this issue on Github!

But I'm not sure to well understand your comment. Tell me if I'm wrong:
- WinNUT dev was stopped in Feb 2011
- March 2011, 1st mention about the Windows port in the Changelog
- Sept. 2011: Windows port version 2.6.1-1 beta
- Oct. 2011: Arnaud: "Advertise more the official Windows port, with
regard to WinNUT"
- June 2012: Windows port version 2.6.4-1
- August 2012: Windows port version 2.6.5-1
- Sept. 2012: Windows port version 2.6.5-2
- Sept. 2012: Windows port version 2.6.5-3
- Feb 2013: Github ticket open to ask to complete the port of NUT to Windows
- Feb 2013: Arnaud announce in the ticket that the port is almost done
- May 2015: Windows port version 2.6.5-6
But... what you are basically saying is that this Windows port in 2019
is still not usable, still has "major issues" so there's not point
trying to install it and write a documentation about how-to install
it?

You may be right but it's a bit surprising.

Also, is your comment still valid taking into consideration I only
need the client functionality?
I don't really know what the full port includes, but remember that I'm
not looking for an advance usage of NUT, mastering the server side for
example, I'm only looking for the client part to allow a Windows PC
wait for messages coming from the NUT server on the NAS and taking
actions to safely shutdown the computer.

> IPP-Unix (NUT) was listed as a supported protocol in IPP last I saw, and
> it's still listed in the user manual.
> http://pqsoftware.eaton.com/explore/eng/ipp/default.htm

True. But I don't really know what those 2 mentions of NUT in the manual mean.
On the other hand, I directly asked the technical support of Eaton and
they told me IPP does not include any NUT client.
And I tried to discover the NAS NUT server via IPP but it didn't worked too.

So the tech guy of the support may have answered me wrong, I may also
have made a mistake in the way I tried to discover the NAS NUT server
using IPP or trying to discover the NAS NUT server was maybe not the
right thing to do, but so far I don't know how to confirm or not if
there's any way via IPP.

So to try to make some progress, earlier today (before your 2 answers)
I tried to get directly in touch with Arnaud Quette. I'll see if he
answers me.
He should be able to answer all my questions, including for IPP as he
works for Eaton.

Thanks anyway for your answers!

Le mar. 12 nov. 2019 à 14:22, Charles Lepple <clepple at gmail.com> a écrit :
>
> On Nov 12, 2019, at 3:49 AM, planet.et at gmail.com wrote:
> >
> > If they can help me, I would be happy to write and release a How-to to
> > help others looking for information like me.
>
> I admire your persistence in trying to find and write documentation on the Windows port, but there's only so much documentation that can cover all the workarounds. At some point, you need a Windows developer to fix the issues, and to propose ways to handle things in the source tree that can work for both Windows and POSIX systems.
>
> There were some serious problems with the original Windows port branch that rendered it un-mergeable (it was prior to the Git conversion). That and other related issues are linked here: https://github.com/networkupstools/nut/issues/5
>
>