fernandocarvalho. I am sorry to say lot of the anti-cheat stuff would still fail anyhow. You really need to look closer at what http://bugs.winehq.org/show_bug.cgi?id=24081 is doing. SSDT monitoring is a highly risky problem. Some alter SSDT calls. Really for highly possible destructive items this even running a virtual kernel would be a issue. Beware not all wine parts send data to wine virtual kernel instead lot go direct off to Linux. Virtual machine costs overhead. If application does not need it don't do it. So a an option to run driver virtual and let everything else go direct to Linux would be a better option. Ie trap only the data streams the driver needs to know about. Best way is learn how to lie to the anti cheat drivers. Yes the SSDT are all fine. Problem is we are wine we call Linux we don't really use the SSDT for functions it only there to make you happy you darn rootkit or if we are told to. This is the better solution from the performance point of view and a secuirty one. If something does try to rootkit wine that way unless user has changed something it will fail. Virtual machine has too much overhead cost. Besides once we are running a full kernel anyhow we might as well Kvm reactos.org. Wine is not just about full compatibility it is also about speed. All native libs don't help with the speed goal.
