Switching DLLs shouldn't be necessary

[Prisma]

Hello Rudi,

wouldn't it be better if switching the DLLs (vnchook.dll, schook.dll, w8hook.dll) depending of th OS wouldn't be necessary? You wrote vnchook.dll and schook.dll isn't allowed to be unpacked, if I want to have w8hook.dll used. Did I understand this correct? Or is it just better for testing? To be 100% sure in case of a failure no other DLL is used?

(Yes, yes I could implement a logic to switch/unpack the DLLs OS depending at my side... But I think such elementary things should be handled by winvnc itself, shouldn't it?)

[Rudi De Vos]

You can install the 3 hooks together.
w8hook..dll is only used when the OS >=win8
schook.dll replace vnchook.dll detection functions
(some vnchook functions are still active, for older OS's they are used to lock mouse/keyboard)

Yes, it was only for testing...

[Prisma]

THX for reply

[Prisma]

For older OSs we use PollFullScreen=1. Does this influence the usage and behaviour of w8hook.dll in a bad way? Is it better not setting this flag on Windows 8? Or are all polling option bypassed by the usage of w8hook.dll?

[Rudi De Vos]

Polling works like this:
If a hook ( vnc/sh/w8) tell something on the screen has changed, no polling is done.
Hook hints are first processed.
When the hook tell nothing changed, we use this time to poll the screen for changes missed by the hooks.
If no changes are found we increase the time to next poll ( we don't want to use cpu on a static screen)

THe w8hook should detcet ALL changes, so it doesn't make a lot of sense to poll.
WHen you use polling +w8hook -> a little more cpu is used for screen scanning.

[Prisma]

Thanx for the Info Rudi.