I'd have a few questions to new TTh 4.10:
A driver is always started at system boot. In runs in ring0 or 1 depending on the OS.
The driver is just like any other program, runnning on its own. But it's only comming to live when TThrottle sends it requests.
TThrottle communicates with the driver over a text communication buffer. So sending text packages to and from it.
The driver keeps on working when TThrottle isn't closed properly, that is untill the process that it's throttling is still there at the same throtlling level
It does not regulate as it's unable to communicate with the BOINC client.
But the TThrottle is only activate on Vista and up, because XP lacks sertain driver functions.
So XP uses the "old" throttling in the exe.
In the future I want to add an extra layer, a service that communicates with BOINC and the driver.
Leaves the TThrottle.exe as a GUI only, interacting with the service, that interacts with the driver.
In the new driver mode there is a function that can suspend the entire process. This will probably halt the threads more effeciently and almost at the same time.
The driver has 16 regulators (different system threads). The GPU uses up to 8 of them, the rest is used by the CPU as cores/2, with a max of 16 cores. So 8 cores = 4 regulators.
But the CPU regulators use the same throttling interval, but a bit shifted in time. As there is no way of telling what CPU the process is running on.
The TThrottle settings are stored in the registry as user, so different users, different settings.
When I switch to a server that will change as well, but one thing at a time.
When you activate the Administrator only mode, you are not to allowed to change anything or exit the program, only the graph can be seen.
And when setup properly, you shouldn't be able to kill it.. But this is a temp fix for the switch to a service.
BOINC connection mode is needed, otherwise you need BOINC folder access as well.
When communicating with BT it is on a new connection for every request, but it keeps the same socket.
This shouldn't be any problem.
BeemerBiker uses a Lunix interface.