Displaying 9 results from an estimated 9 matches for "setpointer".
Did you mean:
getpointer
2007 Mar 19
1
logitech 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.
2009 Apr 12
1
Logitech G5 mouse software install help
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
2009 May 01
0
[LLVMdev] PointerIntPair causing trouble
...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 works...
2020 Apr 28
2
Tripp-Lite SMART1500LCD: powers off with /etc/killpower...then powers back on...
Hi Everyone,
I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine,
connected via a USB cable. I installed Nut 2.7.4 from the Mint package
repository via sudo apt update && sudo apt install nut. Everything works
great: NUT issues low battery warning when it reaches the set low
battery point and then issues shutdown commands...computer shuts
down..then the UPS shuts
2009 May 01
7
[LLVMdev] PointerIntPair causing trouble
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
2013 May 11
1
Best Ferrups (bestfcom patch)
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
2005 Aug 30
1
Best Fortress LI660VA-Question(s)
Hi,
I recently got a Best Fortress LI660VA which was until then used on an
AS/400 System. It's quite old and even with minimal Load only keeps the
Line for a few seconds -- however, two new (Panasonic) Batteries cost
less than half of what a new UPS will cost and so I decided to keep it.
However, I'd like to run some Monitoring SW for the UPS. No Problem, I
found NUT and was impressed by
2012 Aug 02
1
Problem detecting Sil3124 SATA controllers off of Sandy Bridge northbridge-connected PCIe slots
Hi,
We're having some trouble with detection of a couple of Sil3124 SATA
controller cards on newer motherboard and processor combos.
Specifically, we're running a Supermicro X9SCM-F motherboard (latest
BIOS) and Intel E3-1220v2 CPU.
What we're seeing:
- Syba Sil3124 PCIe cards are only being detected when installed in PCIe
Slot 4
-- The motherboard documentation shows that this
2009 May 02
1
[LLVMdev] PointerIntPair causing trouble
...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...