similar to: Windows usbhid-ups driver

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,

> On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > (Note: running > > 'upsc ups at localhost' echoes only a blank line to the screen, as do > > both 'upsmon' and 'upsd.') > > Something is wrong here. Is the daemon upsd running? On a Unix/Linux > system, the command ps aux | grep ups gives the report > > upsd 3196 0.0 0.0 13228

On Windows 2008r2, Network UPS tools isn't starting (netstat doesn't show anything on port 3493, and WinNutClient won't connect). I eventually tried running c:\program files (x86)\NUT\bin\nut.exe -N in a command prompt window and it reports the following: -------------------------------------------------------------------------------------------------------------- C:\Program Files

Hi List, i've installed the network ups tool on one of my windows machine (server 2012 r2). My ups is an APC Back-UPS Pro 550 which is connected via USB to an Synology Diskstation DS414. I found this video https://www.youtube.com/watch?v=0l54n_37M_k My config: *nut.conf* MODE=standalone *ups.conf* [ups] driver = snmp-ups port = 192.168.2.5 community = public *upsd.users* [monuser]

On Sep 14, 2016, at 9:29 AM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > C:\Users\Admin>upsc ups at localhost > battery.charge: 100 ... > ups.status: OL If ups.status follows the state of line power, the driver is working (and upsc talks to upsd, so that connection is working as well). > So this all represents significant progress. But we're not out of the woods

Hello, I am not able to get NUT working with a APC SC1500. The ups has only a serial port and came with a 940-0272a serial to usb cable. The cable has a fake Prolific chip in it, so only works by downgrading the driver to version 3.2. I tested a 940-0024C cable without success as well. The ups works with powerchute and apcupsd with the 940-0272a cable. Have not tested it with the other one. OS:

> >> I think you have that first link working (assuming usbhid-ups is still >> running). If the server is not running, you can try starting it manually with >> one or more "-D" flags to see what is going wrong. > > Not much here: > > --------------- > C:\Users\Admin>upsdrvctl -DD start Sorry, I wasn't clear. I meant for you to try "upsd

Hello. I have problem with connecting to APC SC1000 using NUT port for windows 2.6.5-6. Last working version is NUT 2.6.1-1. With the same config files it works well. c:\NUT\bin>apcsmart.exe -a SC1000 Network UPS Tools - APC Smart protocol driver 3.1 (Windows-v2.6.5-5-7-g72f380c) APC command table version 3.1 w32_serial_open (COM3) setting initial state on COM3 0000007C = w32_serial_open

Hello, windows10pro version 1511 os build 10586.29 nut 2.6.5-6 windows binary package device ups: poweron vs 950 when I do testing shutdown it does not shutdown. Thank's. driver debug output: C:\Program Files (x86)\NUT\bin>blazer_usb -DD -a myups Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (Windows-v2.6.5-5-7-g72f380c) 0.000000 debug level is '2' 0.000000

Hi Guys, I am running ext3 on kernel v2.6.5. I have an ext3 filesystem with dir_index and data=journal for /var/spool/exim Today I noticed in the exim logs a bunch of 'failed to unlink /var/spool/exim/input/P/1BRbSP-0006hy-Jp-D' I also noticed these in the kernel logs: EXT3-fs warning (device hda12): ext3_unlink: Deleting nonexistent file (612870), 0 EXT3-fs warning (device hda12):

Hello, interesting to hear. What version of NUT, what way of installation on Windows, what sort of UPS (USB or some other)? Asking because this info is lacking and currently there are a few variants to consider: * an MSI package based on NUT v2.6.5 (last released about 9 years ago as "2.6.5-6"), * results of re-integration of that codebase into current NUT master (some months after

On Jun 29, 2013, at 9:45 AM, Mike. wrote: > On 6/29/2013 at 9:14 AM Mike. wrote: > > |NUT 2.6.5 on FreeBSD 9.1 > | > | > |Why isn't the variable outlet.1.delay.shutdown set with the following > |command? > | > | > | > |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > |# upsrw -u au -p ap -s

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

Hi! I would like to ask about current state of Windows port. Is it frozen? It will be cool to know the plans :) Where are a lot of Windows-branches at GitHub. What is the most actual one? The Windows builder looks like turned off, am I right that it is not available currently and where were no builds after version 2.6.5-6? I couldn't find any info about proper environment to build Windows

Hello! I performed lightweight review of Windows port source code (Windows-v2.6.5-7 branch). I have some ideas I would like to share with NUT community. First of all, Frederic did great job to port NUT sources to Windows platform and we have the path in dark forest. Unfortunately, the port looks like experimental. I think that the next major iteration is required. Here are many words, sorry

Hello, I have one UPS Infosec XP Pro 2500 RM and it works with windows sw RUPS2000. Now I want to install this UPS as virtual server on vmware ESXi vMA - (SUSE SLES 11SP2 linux). On this linux I have NUT 2.6.0 and I stopped now with configuration of genericups driver. Working cable (direct cable pin1-pin1 ... pin9-pin9) connection on Windows: PIN | PC | UPS

Does anybody else see the same behavior for VoipBuster connections? When I trace one of the other SIP peers, I see it sends this message: ---------------------------------------------------------------------- <--- SIP read from 82.101.62.99:5060 ---> SIP/2.0 180 Ringing Allow: INVITE,ACK,BYE,CANCEL,PRACK,SUBSCRIBE,NOTIFY,UPDATE Call-ID: 740540ee64fa957513ce89f03ef5e3f2 at sip.xs4all.nl

On Tue, Jan 27, 2015 at 5:53 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> > wrote: > > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am > using the MSI release of 2.6.5-3. > > > I am not sure why they are not listed on the main download page,

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