you can include that xldr thing because it includes like a driver to me xd
Originally Posted by MemoryThePast
you can include that xldr thing because it includes like a driver to me xd
d3dref9 and xldr it's two driver how you got 3 driver lol
Originally Posted by Anger5K
d3dref9 and xldr it's two driver how you got 3 driver lol
xhunter1.sys, kgds.sys and that xldr_thing.exe like i said up here i just include that xldr_thing.exe like a driver but i didn't said that thing is a driver .
Originally Posted by [Snake]
d3dref9 isn't driver, crossfire have 3 kernel drivers xhunter1.sys , xldr and kgds.sys
- - - Updated - - -
kgds.sys checks if crossfire handle has been accessed, avoid using OpenProcess
d3dref9 run kgds.sys so it's driver lol
xldr starts as a service but is not a driver
Originally Posted by Anger5K
d3dref9 run kgds.sys so it's driver lol
wtf lol
only kgds and xhunter1 are driver running in windows kernel
for those who want to remove handle access callbacks the driver altitudes are
xhunter1.sys -> 380800
kgds.sys -> 4000
d3dref9 just do communication with the kgds serives, isnt run
Originally Posted by [Snake]
lol , patcher_cf starts kgds serives.
When i blocked patcher download d3dref9 , service kgds didn't start
Originally Posted by dreek1
d3dref9 just do communication with the kgds serives, isnt run
yea something like that
Ask?
Originally Posted by dreek1
d3dref9 just do communication with the kgds serives, isnt run
can I ask bro if you have source crossfire online cuz I need it please