On 11/28/05, Simon Kirk Simon.Kirk@pinesoft.co.uk wrote:
Upon communication with their (admittedly pretty helpful) support staff it turns out the timer is internally set up to control a timeout value within their own unix driver software.
Sounds like some old-fashion Unix multi-process hacking is in order ;)