dosn't matter how much they compress it, yes it would use alota cpu cycles, but I'm not sure that 100k keypresses takes very long at all :) and the cpu cycles are not a worry some thing, if I set my...
what?? I don't care how they do it, as long as they are using a resource I can detect the presence of one, thats all it's supposed to do, not detect "where" or "what" but just if ones there or not...
that's pretty much a side effect of my program, the true purpose is to use those hordes of crap to fish out a mysteriously increasing resource ussage which would symbolize a keylogger :)
this is true, how ever it will overlfow the hardware controller ;) and if you can't find a hardware keylogger on your comp I'd have to peg you as retarted, unless it's integrated INTO the keyboard...
I was brainstorming a program which would assist in catching any kind of keylogger no matter what method they used, my idea was to just have a program emulate keypresses as fast as it can, my...
hmmm it's in my game of life proggy (the asm prog you helped me with), I've added some more speed optimizations to the program since you've seen it :) but nothing to change how direct draw...
I have a program I made that uses DirectDraw, I've created a surface with a back buffer and I directly manipulate the back buffers memory, then use flip on the primary surface, even though I'm doing...
heh heh yeah I made a cardinal sin in DirX :) I realised that after a computer at school was experiencing the same glitch in the 32bit working version ;)
I will try pitch as soon as I get home, how ever it seems either you implimented my prog without the same rules or something went wrong because the straight line in your program should not exist,...
it is a pointer to the screen memory (void pointer), I'm well aware of pitch (surface.lPitch) how ever I have specified a 8 bit screen thus making the pitch 1, on the other prog I use the *4 in the...
hmm thanks that did help, I'm having another problem though, I have this asm code which for some reason does not work for writing 8bit video memory, instead the middle of my screen generates this...
The following code dosn't seem to clear the back buffer, but I'm currently under the impression that in full screen exclusive mode it does this automatically:
for some reason this program draws a white sqaure(which it's supposed to do) the looks to be about 50 pixels to the left and 50 pixels up.... also the very bottom of the...
lol I've seen that style too! just the name was a bit missleading, I thought it made the button flash or something.... didn't read what the SDK docs said :)
oh and I created a static window that fills the main window, and when this is done the program looks to see if the main window is brought ot the foreground...