|
| |
Low-Level Pipeline Level Programming Services
Could you ever imagine an installation program placing your driver on a PC and modifying the driver object code during the installation so it is unique on the end user's machine? Perhaps doing this all without the user's involvement? And then communicating with a kernel mode driver using the kernel mode winsock interface, back through port 80 of possible updates or even debug information?
Just how many ways are there to communicate between processes? And just what is the limit to which we can modify the process space and portable executable files which comprise it? Is it possible to make my NT/XP/Vista driver run on 98/Millenium or vice versa?
We know these limits and a many more. We have been exploring DOS and Windows Internals since DOS was running version 3.3.
What does that translate into?
Simply put...
...Faster, smaller, better results for you!
Get started today and filling out a request for quote.