Hello Remy,
Ok, read it.
I don't understand why when adding this switch, Dooble is more stable while it should have no effect but it has here !
(adding this switch, I'm able to use Dooble without setting priorities. Without it, I need to add priorities settings)
May it be possible this constant isn't well taken into some parts of the codes ?
Could it be that this SET statement impacts other apps on your system which in turn have an impact on the QT stuff?
I have a few apps here that would fit the bill:
1) FF - where I no longer have this set, while in earlier versions I did
2) PUMONITOR - by default I'm using the hires timer to gether runtime statistics
3) DISKIO - the version I am currently working on is using this approach
Now of course if you are running/testing the QT apps w/o anything else on your OS/2 box currently running, that would at least limit that spillover effect that other apps might have.
