1 - never seen that 😕
2 - from dnetc readme :
Q: I want to run the client at a higher priority than zero/idle.
This functionality was removed in some past version, but I *really*,
*really* need it or my other XXX program will simply hog the CPU.
What can I do?
A: It never went away. Only the help text said it did. 🙂
Hovever, be *very* careful. Windows' thread scheduling/priority
assignment is brain dead beyond belief. Read the text in the
config screen before you fiddle with the priority setting!
So go to the client config, Performance related options, line 3 :
Priority level to run at:
The higher the client's priority, the greater will be its demand for
processor time. The operating system will fulfill this demand only after
the demands of other processes with a higher or equal priority are fulfilled
first. At priority zero, the client will get processing time only when all
other processes are idle (give up their chance to run). At priority nine, the
client will always get CPU time unless there is a time-critical process
waiting to be run - this is obviously not a good idea unless the client is
running on a machine that does nothing else.
*Warning*: Running the Win32 client at any priority level other than zero is
destructive to Operating System safety. Win32's thread scheduler is not nice.
Besides, a zero priority does not mean that the client will run slower than at
a higher priority. It simply means that all other processes have a better
*chance* to get processor time than client. If none of them want/need processor
time, the client will get it. Do *not* change the value of this option unless
you are intimately familiar with the way Win32 thread scheduling works.
/edit : many ppl tried to run it at any higher priority, and never reported performance improvements higher than 1 or 2 percent. The downside being *very* slow system response : you can barely move the mouse !
