search for: 800a

I've installed the following prior to the installation: .net framework 2 jet40 mdac28 The Wizards Event Reporter gives this error on launch: "The server committed a protocol violation. Section=ResponseStatusLine" The program will then launch but will not give online connectivity.

I am new to Wine and don't really know my way round it but I thought I might try my CAD software on it, Alibre Design. It seems to have installed fine but won't start. I have discussed this in another thread already (here: http://forum.winehq.org/viewtopic.php?t=9205) but the heading is rather misleading so I thought I might start a new thread with a proper heading. Any help in getting

...tNamedSecurityInfoW L"C:\\users\\Public\\Application Data\\Apex Software\\Nexus\\Log\\NexusLog.txt" 1 536870916 (nil) (nil) 0x852fc4 (nil) fixme:process:FlushProcessWriteBuffers : stub fixme:ole:Context_CC_ContextCallback (0x1edf70/0x1edf74)->(0x7a0bf71d, 0x297cec4, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x1edf70/0x1edf74)->(0x7a0bf71d, 0x297ce54, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x1edf70/0x1edf74)->(0x7a0bf71d, 0x297ce54, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixm...

.../m/y): 0/00/0000, dlt (d/m/y): 0/00/0000 fixme:shell:URL_ParseUrl failed to parse L"UseCaseMaker.resources" fixme:shell:URL_ParseUrl failed to parse L"UseCaseMaker.resources" fixme:ole:Context_CC_ContextCallback (0x1c02b0/0x1c02b4)->(0x79f277a5, 0x297e4d8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x1c02b0/0x1c02b4)->(0x79f277a5, 0x297e46c, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x1c02b0/0x1c02b4)->(0x79f277a5, 0x297e46c, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixm...

running ubuntu 10.04 LTS with wine 1.1.44 > fixme:msi:MsiGetMode unimplemented run mode: 0 > fixme:msi:ACTION_ValidateProductID partial stub: template L"77718<````=````=````=````=`````>@@@@@" key L"JWFMGDGVMWKPVD39RX6PW2GQY" > err:module:import_dll Library sqdedev.DLL (which is needed by L"C:\\users\\leecarey\\Temp\\msi8258.tmp") not found >

...010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded fixme:ole:Context_CC_ContextCallback (0x16c058/0x16c05c)->(0x79f277a5, 0x2a3cf04, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x16c058/0x16c05c)->(0x79f277a5, 0x2a3ce98, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x16c058/0x16c05c)->(0x79f277a5, 0x2a3ce98, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixm...

device -Powercom model: BNT-800A 17 ???? 2013, ? 14:55, Charles Lepple <clepple at gmail.com> ???????(?): > On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote: > >> This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported >> by usbhid-ups. Please make sure you have an up-to-date version of NUT...

Hello! I have an UPS made by Powercom company; the model of the UPS is RPT-800A. This UPS has a USB port, which can be used to connect the UPS to a PC and read various data from the UPS (percentage of load, input voltage, output voltage, etc.). So I download the NUT binary package for Windows, install and set it up using manual. Everything works fine for a few hours (I can...

...icups upstype=13 port = /dev/bus/usb/002/006 upstype = 13 desc = "UPS" error: root at alhana:/etc/nut# /etc/rc.d/rc.ups start Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic contact-closure UPS driver 1.36 (2.6.0) UPS type: Repoteck RPT-800A, RPT-162A tcgetattr: Inappropriate ioctl for device Driver failed to start (exit status=1) Does this mean that the driver is not supported or am I missing something? Best regards, M. Ivanov

...om ULT-1000", 1.91, 0.42, 1.91, 0.42, 165, 200, 240, 275, 1 }, + { "SXL-1500A", "PowerCom SXL-1500A", 1.91, 0.42, 1.91, 0.42, 165, 200, 240, 275, 1 }, + { "SMK-1500A", "PowerCom SMK-1500A", 1.91, 0.42, 1.91, 0.42, 165, 200, 240, 275, 1 }, + { "SMK-800A", "PowerCom SMK-800A", 1.91, 0.42, 1.91, 0.42, 165, 200, 240, 275, 1 }, + { "Alpha500iC", "Alpha 500 iC", 10.7, 1.4, 13.0, 0.8, 172, 196, 252, 288, 0 }, { NULL, NULL, 0, 0, 0, 0, 0, 0, 0, 0, 0 }

...CFMonitorService"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000000,(nil),0x0001,0x00000000,0x82ba98,0x82b940): stub fixme:advapi:DeregisterEventSource (0xcafe4242) stub fixme:ole:Context_CC_ContextCallback (0x197d40/0x197d44)->(0x79f277a5, 0x299cf14, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x197d40/0x197d44)->(0x79f277a5, 0x299cea8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixme:ole:Context_CC_ContextCallback (0x197d40/0x197d44)->(0x79f277a5, 0x299cea8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, (nil)) fixm...

....0.4 Network UPS Tools - Fenton UPS driver 1.22 (2.0.4) Unknown ups - please report this ID string: #M+H SMK-800 2000 V6.2 Detected Unknown MK-800 on /dev/ttyS0 The unit is badged as a "Power Tech" unit, model number SMK-800, and is actually a Nikko/PowerTec Smart King LCD 800A. The UPS works fine using the Fenton serial cable layout, and reports almost perfect information: root@anu:~# upsc smk800@localhost battery.charge: 100.0 battery.voltage: 2.40 driver.name: fentonups driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 1.22 input.frequ...

...0.321679 - ProductID: 0002 0.321683 - Manufacturer: unknown 0.321687 - Product: unknown 0.321692 - Serial Number: unknown 0.321696 - Bus: 002 0.321700 Trying to match device 0.321707 Device does not match - skipping 0.321818 Checking device (8087/800A) (001/002) 0.370660 - VendorID: 8087 0.370668 - ProductID: 800a 0.370670 - Manufacturer: unknown 0.370672 - Product: unknown 0.370673 - Serial Number: unknown 0.370675 - Bus: 001 0.370677 Trying to match device 0.370680 Device does not match -...

...] xhci_hcd 0000:00:14.0: init 0000:00:14.0 fail, -110 [252405.903038] xhci_hcd: probe of 0000:00:14.0 failed with error -110 And it's still not there: $lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So is this a faulty Tripplite that needs to be returned?

..., 88, 132, 132, 1 }, ! { "H010K", "PowerOn 10000", 154.0, 14.0, 154.0, 14.0, 88, 88, 132, 132, 1 }, /* non-Fenton, yet compatible (Megatec protocol) models */ ! { "UPS-PRO", "PowerGuard PG-600", 0, 0, 0, 0, 170, 200, 250, 270, 1 }, ! { "SMK800A", "PowerCom SMK-800A", 1.9, 0.5, 1.9, 0.5, 165, 200, 240, 275, 1 }, ! { "ULT-1000", "PowerCom ULT-1000", 1.91, 0.42, 1.91, 0.42, 165, 200, 240, 275, 1 }, ! { "Alpha500iC", "Alpha 500 iC", 10.7, 1.4, 13.0, 0.8, 172, 196, 252, 288, 0 },...

Hi Alex, I've forwarded your request to the nut-upsuser mailing list. Please follow the discussion there. I'm also not sure to have well understood your issue. Don't hesitate to explain it a bit more if I'm wrong... Alex wrote: > ASP Linux Server II. >UPS POWERCOM SMART KING 800A. > > >Has Putted (deliver) NUT. The Driver (according to ?????) fentonups. Like works orderly. >But can not understand as correct to adjust. > >Is Necessary include/disconnect the server on timetable and at disappearing of voltage of feeding. As I has >understood to is necessar...

This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0004' option. Please report your results to the NUT user's mailing list <nut-upsuser at lists.alioth.debian.org>. No matching HID UPS found Driver failed to

On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote: > This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported > by usbhid-ups. Please make sure you have an up-to-date version of NUT. If > this does not fix the problem, try running the driver with the > '-x productid=0004' option. Please report your results to the NUT user's > mailing list <nut-upsuser at

...] xhci_hcd 0000:00:14.0: init 0000:00:14.0 fail, -110 [252405.903038] xhci_hcd: probe of 0000:00:14.0 failed with error -110 And it's still not there: $lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So is this a faulty Tripplite that needs to be returned? _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://urldefense.proofpoint.com/v2/url?u=https-3...

Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb connector. Nut does connect: $upsc ups battery.charge: 100 battery.runtime: 1407 battery.type: PbAC ... But after a half hour or so the connection is lost. Restarting nut re-establishes the connection. Any idea what might be causing the dissconnection?