search for: setpoint

Does anyone know how to get SetPoint to run in linux, using wine or something similar? Please email any advice to rimplestultskin@gmail.com thanks.

I am new to Linux and I am trying to install my software for my Logitech G5 mouse. I was able to configure my WINE program to emulate the desk top and it opened the window ans then it closed quickly. It never does allow me to install it. I have also tried using the terminal but that does not work either. Please can any one help me with this? I can't get all my buttons on my mouse to work

...umped up to 16 bytes in size, and thus Users never get placed at less than an 8-byte boundary. However, in that case, the whole point of the "use diet" optimization is lost! I'll investigate and try to find out. I'm also still not sure why the assertion in PointerIntPair::setPointer() did not get triggered by the User::allocHungOffUses() implementation in Use.cpp. Perhaps the assertion is wrong (it looks reasonable, though) or perhaps there is something else going on I haven't seen yet. I'll look into this some more as well. Let me know if the workaround wor...

......BUT...after the UPS has shut down, I hear another clunk noise and the computer starts to power back on. Since the UPS battery is about dead at this point, the computer starts to boot up only till the UPS completely dies since its batteries are depleted. This is what is happening: - Low Battery setpoint reached --> issue computer shutdown - Shutdown commands sent --> computer starts shutting down - At some point, /etc/killpower is sent before computer fully shuts down - Computer shuts down - A few seconds later, I hear a clunk in the UPS (UPS powers off... I used a multimeter to verify no AC...

Hi all, I've located a regression that causes my project to crash. It's in revision 67979, where PointerIntPair is changed from storing the integer in the upper bits instead of the lower bits. My project is an experimental JIT-compiler in Windows. So I was wondering if anyone had any clue why the new PointerIntPair implementation might fail. It doesn't seem very safe to me to

Hello, I have a Best Ferrups 3.1KVA and I noticed that the percent battery voltage reported from upsc never gets above 69.9%. I believe there is a mistake in the driver. The battery percentage is calculated based on the High Battery Alarm Setpoint (59.6V) instead of the Ideal Voltage which is about 54V (4 batteries x 13.6V). I examined the source code and found that the variable fc.fullvolts is the result of querying parameter 67 from the UPS. This parameter is defined per Ferrups Tip 503 as: "The battery voltage at which the UPS soun...

...wired (on the PC-side) (seems to me it's for "Contact Mode", not for "Communication Mode"). So, with the Info from the "Fortress Protocol" I soldered an Adapter to Connect: (UPS <-> Sub-D 9-pin) 1 <-> 3, 2 <-> 2, 4 <-> 5. I also checked the Setpoint 7 is set to "1". However, no comms is possible with the UPS. I sent dozenz of "<cr>" and also "Q"<cr> but without getting any Reply from the UPS. However, when I switch the UPS off I get <strange Character>{0001}. I first thought this was by accident...

...fs registered lapic: Divisor 2, Frequency 50001481 Hz Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached hptrr: no controller detected. usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 acpi_tz0: _AC4: temperature 27.8 >= setpoint 0.0 acpi_tz0: _AC3: temperature 27.8 >= setpoint 0.0 acpi_tz0: _AC2: temperature 27.8 >= setpoint 0.0 acpi_tz0: switched from NONE to _AC2: 27.8C acpi_tz0: _AC4: temperature 27.8 >= setpoint 0.0 acpi_tz0: _AC3: temperature 27.8 >= setpoint 0.0 acpi_tz0: _AC4: temperature 27.8 >= setp...

...and > thus Users never get placed at less than an 8-byte boundary. > However, in that case, the whole point of the "use diet" > optimization is lost! I'll investigate and try to find out. > > I'm also still not sure why the assertion in > PointerIntPair::setPointer() did not get triggered by the > User::allocHungOffUses() implementation in Use.cpp. Perhaps the > assertion is wrong (it looks reasonable, though) or perhaps there is > something else going on I haven't seen yet. I'll look into this some > more as well. > > Let...