nut
nut copied to clipboard
networkupstools
Windows: Try installing libUSB manually.
NUT at windows installed. copy sbin\libgcc_s_dw2-1.dll bin Download https://indy.fulgan.com/SSL/Archive/openssl-0.9.8e-i386-win32.zip extract to NUT\bin and NUT\sbin
bin\nut-scanner.exe
Cannot load USB library (libusb) : Nie mo┐na odnalečŠ okreťlonego modu│u.. USB search disabled.
Cannot load SNMP library (libnetsnmp) : Nie mo┐na odnalečŠ okreťlonego modu│u.. SNMP search disabled.
Cannot load XML library (libneon) : Nie mo┐na odnalečŠ okreťlonego modu│u.. XML search disabled.
Cannot load NUT library (libupsclient) : Nie mo┐na odnalečŠ okreťlonego modu│u.. NUT search disabled.
Add/Remove Programs \ NUT \ Repair button
NUT UPS driver installer.
-------------------------
Searching for known UPS...
Found UPS : vendor ID = 51D - Product ID = 3
Extracting driver files...
Success
USB\VID_051D&PID_0003&REV_0001: Installing driver
Requested resource not found
An error occured while installing driver.
Try installing libUSB manually.
Hit enter to continue
At others 3 ISSUE here I not found a solution. Where is a proper USB LIB package, or not exist ?
Can someone fix this basic install issue. I see the same errors on a 64bit winpro machine with a USB connection to the APC UPS. Very frustrating.
Hello, to help investigate, can you please link to the Windows package of NUT you are trying? AFAIK, there were spin-offs to enable Windows builds, last branched from v2.6.5, so about a decade ago. It would be interesting to revive that ability with modern NUT codebase, but contributors may be needed.
On Sun, Nov 28, 2021, 05:07 Buxton @.***> wrote:
Can someone fix this basic install issue. I see the same errors on a 64bit winpro machine with a USB connection to the APC UPS. Very frustrating.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/networkupstools/nut/issues/1145#issuecomment-980836484, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMPTFGKBUISEKLI52Z3UWTUOGTGVANCNFSM5GVDB23A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
I use https://networkupstools.org/download.html#_binary_packages : Windows (complete port, Beta): Windows MSI installer 2.6.5-6
There is only one link that I'm aware of: https://networkupstools.org/download.html#_binary_packages. If there are other builds, it would be great if you could link to them on the download page.
Hello, to help investigate, can you please link to the Windows package of NUT you are trying? AFAIK, there were spin-offs to enable Windows builds, last branched from v2.6.5, so about a decade ago. It would be interesting to revive that ability with modern NUT codebase, but contributors may be needed. … On Sun, Nov 28, 2021, 05:07 Buxton @.***> wrote: Can someone fix this basic install issue. I see the same errors on a 64bit winpro machine with a USB connection to the APC UPS. Very frustrating. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1145 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMPTFGKBUISEKLI52Z3UWTUOGTGVANCNFSM5GVDB23A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-6.msi I not know anything about newer package for windows.
Me neither, just wondered if there was an "unaccounted for" effort newer than the 2.6.5-based branch.
On Fri, Dec 3, 2021, 13:21 4SiB @.***> wrote:
http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-6.msi I not know anything about newer package for windows.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/networkupstools/nut/issues/1145#issuecomment-985475348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMPTFH7GMTRZJX3YQSPACDUPCY3JANCNFSM5GVDB23A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Same here. Even messing around with the manual libusb and copying the dlls over doesn't work. Was trying to follow this guide: https://titanwolf.org/Network/Articles/Article?AID=2ee344ef-6bec-440d-8d1c-d21777ffea12 but couldn't get past the usb search error.
Correction: I just failed to follow the instructions fully and missed renaming one of the dlls. Nut-scanner.exe shows it correctly and the service is running successfully.
Haven't tried connecting a client to it yet.
upsc.exe is returning an error of: 'Error: Connection failure: Unknown error' and trying WinNut isn't working either so something is still amiss.
Event Viewer is showing a periodic warning message of:
usbhid-ups - libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.
I'm having the same issue with Windows MSI installer 2.6.5-6:
> C:\Program Files (x86)\NUT\others\wdi-simple.exe
NUT UPS driver installer.
-------------------------
Searching for known UPS...
Found UPS : vendor ID = 764 - Product ID = 501
Extracting driver files...
Success
USB\VID_0764&PID_0501&REV_0001: Installing driver
Requested resource not found
An error occured while installing driver.
Try installing libUSB manually.
Hit enter to continue
It does warn that it's a Beta I guess.
Edit: Oh, apparently 2.6.5 is ancient. Why even have that on the Downloads page anymore? It's clearly not a "beta" so much as it is abandoned.
During the past months I've revived an effort to merge that old branch made from NUT 2.6.5 with current codebase, with progress covered in issue #5 abd getting more and more drivers built. I did not touch the installer yet, however, so can't comment on it well. More able hands are welcome =)
During the past months I've revived an effort to merge that old branch made from NUT 2.6.5 with current codebase,
Thanks for the info @jimklimov, great to hear! Is there any drawback to using nut installed on Windows/Ubuntu via the Windows Subsystem for Linux WSL?
Did not try WSL with local-access devices (usb/serial), so no idea if you can pass-through the connections to that VM or how.
A WSL Ubuntu did suffice for me to build NUT (same as for other Linux, no relation to a Windows-binary build). Probably network drivers (snmmp, netxml...) would work and then no quick ideas how to shut down Windows from the Ubuntu session (or if it runs at all until you open a terminal).
libwdi code we use to install driver on Windows is from over 11 years ago. I think it's about time we update it.
So far MSI packaging was not re-explored, so practically we don't use that, yet. If something is doable to improve it, and usable on at least modern Windows (XP+?), be our guest to try. Maybe makes sense to revive what allegedly worked first though, might be a simpler stepping stone.
Unfortunately, none that I know of. I've tried for a few hours to understand the installer tech used before, and how the template could be extended to cover the many new files and groupings we have in current codebase (they seem to list UUIDs and maybe hashes of the delivered files, so there gotta be some tooling which would collect the info from the built proto-install area), but left not much wiser and had other priorities since.
Generally I summarized the current state of NUT for Windows effort at https://github.com/networkupstools/nut/wiki/NUT-for-Windows