WinNUT release 0.45.2a download

Ready to install version:
  • WinNutUPSMonV0.45.2a.zip - Compatible with NUT versions 0.44.x and higher

    Source code (Compiles with MS Visual Studio 6.0)
  • WinNutUpsMonV0.45.2a-src.zip - Based on source for NUT release version 0.45.2. Compatable with NUT versions 0.44.x and higher
    Version Information
    This version is an update of the windows port with the most recent upsmon code from the NUT package. This updated port takes care of several problems that had been fixed in the NUT package. Also several other bugs where fixed, including one that prevented WinNutUPSMon from running in service mode under NT4.
    NOTE: WinNUT is compatible with the nut 0.50.0 release, however the default port has changed to 3493 (from 3305). You can either specify that as part of the ups specification in the upsmon.conf (ie upsname@host:port) or change the default port in the WinNUT configuration tool.

    Known Bugs

  • in the upsmon.conf, using an IP address to specify a server will probably not work. The server needs to be a DNS resolvable name. If the server does not have a name, this can be achieved by adding an entry with a name in the c:\windows\hosts (for windows 9x/ME) or the c:\winnt\system32\drivers\etc\hosts (for NT, 2000, and maybe XP) on the Windows machine running WinNUT. An entry in this file should be on a line by itself and of the form
    1.2.3.4	upsserver
    where 1.2.3.4 is the ip address of the server the ups runs on and "upsserver" is the name you want to give that server (and use this name in the upsmon.conf). Be sure this name isn't already in use (ie, don't use things like localhost or cnn.com)
    This bug will be fixed in the soon coming 0.45.2b release

    Bugs fixed & Improvements

  • Better handling of spaces in config files (from updated NUT port)
  • When insufficient power is configured it used to immediately start a shutdown. Now it displays an error message and stops.
  • Fixed issue with NT 4 not working in service mode. Gave error message (Error 2186: The service is not responding to the control function) which was caused because I was using win2k API extentions. Now they are only used if the proper version is detected
  • Now we show proper error message popups if an invalid ups is specified

    back