"Peter Olcott" <NoSpam@SeeScreen.com> wrote in message
news:tZPIg.7881$Tl4.1651@dukeread06...
"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:6vPIg.12152$%j7.5118@newssvr29.news.prodigy.net...
"Peter Olcott" <NoSpam@SeeScreen.com> wrote in message
news:0rPIg.7880$Tl4.652@dukeread06...
I have been researching this extensively for many years, this is
something
new and different that has not been available until recently.
Um, I believe API hooking has been around for as long as Windows
has!
Since
Windows has always been a DLL based system, Import Address Table
(IAT)
patching should have been available from the earliest days. It has
gotten
much easier with Win2K/XP supporting VirtualAlloc,
CreateRemoteThread,
ReadProcessMemory.
This is the sort of answer that I was looking for. I wanted to know
exactly what
has changed recently the effects API hooking.
Most of these earlier methods did not always work on everything, and
because of
this were not
worth the trouble if only a complete solution would do. It seems that
there is
still one case where these methods do not work, writing to an
offscreen
memory
bitmap, and then blitting this bitmap to the screen. Is this
assessment
correct?
No, these methods would work regardless of where you are writing. API
hooking allows you to hook to functions. There is no such
differentiation
that you have mentioned.
disagrees.
http://groups.google.com/group/microsoft.public.win32.programmer.kernel/msg/9038346ecd47214f
http://groups.google.com/group/microsoft.public.win32.programmer.kernel/browse_thread/thread/222660e2231e7fcd/8957e5d102cda67f?lnk=st&q=&rnum=1&hl=en#8957e5d102cda67f