EyeFi Mobile X2 will not connect to Wifi

So new EyeFi card will not connect to my router with the error message "waiting for a network address", after some investigation the logfile shows this:

eyefi AssocResp: Error status 0x0002, aid: ffff, error/cap: 0xfffc (Auth response timeout)

Which according to this site http://forums.eye.fi/viewtopic.php?f=2&t=3347 can indicate a faulty card reader, I plugged the reader directly into my USB port and hey-presto. Everything worked.

ARMA 3, probability of presence for group

I recently wanted to create a group of units based on probability; so 50% of the time spawn a group of units at a certain position.

To do this create the group, set the probability of presence of the leader to your desired probability and then for each member of the group set a condition of presence that requires the leader to be present. So,

(alive group_leader);

Job done!



Edit - Added screenshots for clarity:

You can have as many units as you want, in this example I have a player (blue), a group leader (purple civillian in front), and 4 dependent civilians behind. Ordinarily you would have all these units grouped using the group tool (F2) so they work as a team but it is not required.

Units

 Group leader can be configured any way you want, what is required is to have a unique name (make a note of this) and to set a probability of presence (which will set the probability of the whole group spawning).

Group leader config

 Now onto setting up the dependent units. A unit will spawn when the expression in its condition of presence evaluates to true. In this case we want it to evaluate to true when the group leader is present. The syntax for this is

(alive group_leader);

making sure that group_leader is the name of the leader that you configured earlier.

Dependent unit config

Windows disk usage analysis

Having just started using windows much more frequently I needed to work out what was hogging all my disk space, this tool 

http://www.uderzo.it/main_products/space_sniffer/index.html

Did the job nicely and found a good 40Gb of crap that can be deleted. Result! 

Remove unused kernels and headers from ubuntu server

Yet again I found my system clogged up with unused kernels and headers. This time I am making a note of the one-liner to remove the unused junk.

(Found at http://tuxtweaks.com/2010/10/remove-old-kernels-in-ubuntu-with-one-command/)

You can first check that the correct packages are selected to remove with;

 dpkg -l linux-* | awk '/^ii/{ print $2}' | grep -v -e `uname -r | cut -f1,2 -d"-"` | grep -e [0-9] | xargs sudo apt-get --dry-run remove 

and if you are happy remove those with this;

dpkg -l linux-* | awk '/^ii/{ print $2}' | grep -v -e `uname -r | cut -f1,2 -d"-"` | grep -e [0-9] | xargs sudo apt-get -y purge

A word of warning, if you have installed a new kernel recently ensure you have rebooted since, and secondly ensure that your current kernel is not on the list of packages to remove of you will end up with a un-bootable system.

eth0 naming persistance

I needed to change the physical hardware for an instance of Ubuntu Server 12.04 after some hardware failed, although most of the hardware changes were seamless the network adapter name changed from eth0 to eth1, the fix for which I found here.

http://www.serenux.com/2009/11/howto-fix-a-missing-eth0-adapter-after-moving-ubuntu-server-from-one-box-to-another/

Essentially the udev rule found at

/etc/udev/rules.d/70-persistent-net.rules

Stores and makes persistent the names of the respective adapters.  By removing the line relating the that adapter is identified by such as

ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:a0:c9:78:9a:bc", NAME="eth0"

Subsequently the new adapter is then initialised with the name eth0.

Logitech G500 mouse pointer jitter fix.

Logitech G500 Mouse jitter fix

So I brought a second hand Logitech G500 mouse which had some problems with jitter, when stopping the mouse quickly movement the pointer would briefly jitter a few pixels randomly.

After some googleing I found this blog entry - http://blog.ambor.com/2011/04/logitech-g500-mouse-rattle-jerky.html - which pointed me in the direction of the laser lens. Fixing the lens in place fixed the problem, the but as the original article has quite short on images I thought I would document it here. 

The top of the laser sensor, the lens is held in place by the two transparent tabs - which you can see passing through the black sensor at in the middle of the PCB.

The lens itself, this was unstable on my mouse and as the mouse moved/stopped the lens wiggled around disrupting the view of the laser.

 The laser sensor with blobs of glue fixing the lens's plastic tabs onto the sensor itself.

Job done!