Strange timer-processing problem (inaccuracy) under QNX 4.25

David, Randy: thank you all the answers…

Gyorgy


Previously, Randy Martin wrote in qdn.public.qnx4:

internally we have been testing with this new Proc that corrects the
behaviour that Tamasi was seeing.
there are a few other things we want to check out with this Proc before we
post to beta.
It will be Proc32.425L (most likely if current numbering holds)

our server has been soaking in the new Proc for about a month now, and all
looks quite good so far.
when we go to beta we will post some info on the changes made..


David Gibbs <> dagibbs@qnx.com> > wrote:
Tamasi Gyorgy <> gtamasi@freemail.hu> > wrote:
Is there any news regarding this issue?

Randy is out of town on business until Friday, he probably won’t see
this query until at least Monday.

Is there any fix available? (Proc32 4.25K?)

I know he was talking about releasing a new Proc with some fixes. I THINK
it included a fix for this, but I don’t know. (I just fixed another timer
problem that somebody flagged with alarm() call, and I’m currently running
it on my system as an initial test. But, I don’t currently know the status
of this particular problem.)

-David

QNX Training Services
dagibbs@qnx.com


Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579