The way to tackle the CAA/EASA compliance issue with POS software (Version 32.1b) is to invoke (great?) grand father rights with your ops inspector saying that it was in place when you had an ANO AOC and the CAA promised that you could bring existing working practices into the new JAR Ops enviroment. Worked for me.The only modification required was to re-calibrate basic parameters from Imperial to Metric.
I believe the cost involved were fairly modest (32p) which includes a spare. I could let you have some of my spares if you have not already re-calibrated.