faq:dep_data_execution_prevention_disabling
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq:dep_data_execution_prevention_disabling [2018/06/14 14:52 (6 years ago)] – swind | faq:dep_data_execution_prevention_disabling [2018/06/14 15:02 (6 years ago)] (current) – [What is DEP??] swind | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Disabling DEP ====== | ====== Disabling DEP ====== | ||
- | Data Execution Prevention has been known to interfer | + | Data Execution Prevention has been known to interfere |
+ | |||
+ | |||
+ | ---- | ||
===== To Disable DEP on a Windows Server / Windows 10 Workstation perform the following: ===== | ===== To Disable DEP on a Windows Server / Windows 10 Workstation perform the following: ===== | ||
+ | |||
+ | {{ : | ||
Open Control Panel | Open Control Panel | ||
Line 44: | Line 50: | ||
====== What is DEP?? ====== | ====== What is DEP?? ====== | ||
*More information on DEP and what it is: | *More information on DEP and what it is: | ||
- | (Taken from Mictosoft's WEB Site) | + | (Taken from Microsoft's WEB Site) |
Data Execution Prevention | Data Execution Prevention | ||
Line 128: | Line 134: | ||
When the system runs with PAE disabled, drivers for 32-bit devices never require their map registers to be backed by real memory. This means that double-buffering is not necessary, since all devices and drivers are contained within the 32-bit address space. Based on testing of drivers for 32-bit devices on 64-bit processor–based computers, it is expected that most client-tested, | When the system runs with PAE disabled, drivers for 32-bit devices never require their map registers to be backed by real memory. This means that double-buffering is not necessary, since all devices and drivers are contained within the 32-bit address space. Based on testing of drivers for 32-bit devices on 64-bit processor–based computers, it is expected that most client-tested, | ||
- | To constrain compatibility issues, Windows XP Service Pack 2 includes hardware abstraction layer (HAL) changes that mimic the 32-bit HAL DMA behavior. The altered HAL grants unlimited map registers when the system is running in PAE mode. In addition, the kernel memory manager ignores any physical address above 4 GB. Any system RAM beyond the 4 GB barrier would be made unaddressable | + | To constrain compatibility issues, Windows XP Service Pack 2 includes hardware abstraction layer (HAL) changes that mimic the 32-bit HAL DMA behavior. The altered HAL grants unlimited map registers when the system is running in PAE mode. In addition, the kernel memory manager ignores any physical address above 4 GB. Any system RAM beyond the 4 GB barrier would be made un-addressable |
As a result of these changes to the HAL and memory manager, the impact to device driver compatibility is expected to be minimal on systems running Windows XP Service Pack 2 with data execution prevention enabled. | As a result of these changes to the HAL and memory manager, the impact to device driver compatibility is expected to be minimal on systems running Windows XP Service Pack 2 with data execution prevention enabled. | ||
Line 247: | Line 253: | ||
The DisableNX compatibility fix can be applied to an application by using the Application Compatibility Toolkit. For more information about Windows application compatibility, | The DisableNX compatibility fix can be applied to an application by using the Application Compatibility Toolkit. For more information about Windows application compatibility, | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | Updated by Steve Wind June 14 2018 | ||
faq/dep_data_execution_prevention_disabling.1529013136.txt.gz · Last modified: 2018/06/14 14:52 (6 years ago) by swind