[Nut-upsuser] Windows 7 x64 : blazer_usb.exe has stopped working

[Волька!]

Just discover, ups driver does not crash when ups.conf has not
vendorid and productid fields.
When I put these strings blazer_usd crashes.
Vladimir.

So, good ups.conf is:
# Network UPS Tools: example ups.conf
[era]
driver = blazer_usb
	port = auto
#	vendorid = 0001
#	productid = 0000
#	subdriver = krauler


And bad config and driver crash :
# Network UPS Tools: example ups.conf
[era]
driver = blazer_usb
	port = auto
	vendorid = 0001
	productid = 0000
#	subdriver = krauler



On Sat, Aug 6, 2011 at 4:48 PM, Волька! <voljka at gmail.com> wrote:
> Hello.
> I have a problem with NUT build 2.6.1-1 for Windows. UPS driver (i
> need blaser_usb.exe) go into crash on Windows 7 x64 SP1, also I tried
> Windows XP x32 in Virtual PC and in VMware Workstation, results are
> the same.
> NUT Driver installed as described : libusb-win32 devices - NUT USB
> driver. (libusb0.dll, libusb0.sys ver.1.2.2.0)
> A tred also libusb from not NUT (drv. version 1.2.5.0) Crash was in
> the same plase - Fault Module Name: msys-1.0.dll
>
> 1) Is it possible to run (test/debug)  NUT driver in x64 OS ?
> 2) And is it compatible with USB pass-through to GuestOS?
>
> Vladimir.
>
> ===============================================
> This is crash report from Windows 7 x64 with NUT 2.6.1.-1 / NUT USB
> driver ver.1.2.2.0
>
> Problem signature:
>
> Problem Event Name: APPCRASH
>
> Application Name: blazer_usb.exe
>
> Application Version: 0.0.0.0
>
> Application Timestamp: 4e1178f5
>
> Fault Module Name: msys-1.0.dll
>
> Fault Module Version: 1000.15.0.0
>
> Fault Module Timestamp: 4c33a8d2
>
> Exception Code: c0000005
>
> Exception Offset: 0005d806
>
> OS Version: 6.1.7601.2.1.0.256.4
>
> Locale ID: 1033
>
> Additional Information 1: 0a9e
>
> Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
>
> Additional Information 3: 0a9e
>
> Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
>