Update README.md

merge-requests/1/head
xerox 5 years ago
parent 10cec9cd2a
commit a94df1d1e7

@ -50,6 +50,8 @@ This scanning takes under a second since each physical range is scanned with a s
There are four functions that need to be altered to make this mapper work for you. I will cover each one by one. These functions are defined inside of a `physmeme.hpp` and need There are four functions that need to be altered to make this mapper work for you. I will cover each one by one. These functions are defined inside of a `physmeme.hpp` and need
to stay inside of this file. This allows people to make different `physmeme.hpp` files for each driver they want to abuse. Modular code. to stay inside of this file. This allows people to make different `physmeme.hpp` files for each driver they want to abuse. Modular code.
When writing your driver you will need a custom entry point just like every other driver mapper.
### `HANDLE load_drv()` ### `HANDLE load_drv()`
Load driver must take zero parameters and return a handle to the driver. Here is an example of this: Load driver must take zero parameters and return a handle to the driver. Here is an example of this:
@ -148,6 +150,3 @@ right now your entry point should look like this:
```cpp ```cpp
NTSTATUS DriverEntry(PVOID lpBaseAddress, DWORD32 dwSize) NTSTATUS DriverEntry(PVOID lpBaseAddress, DWORD32 dwSize)
``` ```
You can change this as you see fit. Note you need a custom entry point like any other driver mapper requires.

Loading…
Cancel
Save