you do not need spectre/meltdown disabled, there is no kernel memory accessed via nasa-tables in this project!

I just inherited the requirements from nasa-tables without thinking... 👁️ 


<img src="https://imgur.com/ForvYgs.png"/>

README.md

@@ -40,8 +40,4 @@ processes pointing at the allocated driver in the runtimebroker, thus mapping th
 Keeping your driver out of the kernels paging tables. Most driver mappers map a driver into a kernel pool (ExAllocatePool). Physmeme, Kdmapper, Drvmapper, all do this, its easily
 detected and easy to dump. This keeps your driver inside of your context :)
 
-I guess you can call this physmeme v2? You can use any driver that exposes physical memory read/write with this driver mapper, simply replace the vulnerable driver inside of raw_driver.hpp.
+I guess you can call this physmeme v2? You can use any driver that exposes physical memory read/write with this driver mapper, simply replace the vulnerable driver inside of raw_driver.hpp.
-
-# Spectre
-
-Please disable spectre/meltdown when using nasa-tables/nasa-patch/nasa-mapper. You can download a program to disable spectre/meltdown [here](https://www.grc.com/inspectre.htm).