Microsoft DEP.

[Wiley Coyote - N2K]

Does anyone know how to remove MS DEP (Data Execution Protection). All of a
sudden this is on my system and has caused nothing but problems.

I couldn't even run PowereDVD (which is a KNOWN safe program).. Once I
configed DEP, I could use things like PowerDVD, WinAmp etc, but still DEP
causes my XP system to crach and burn, particularlly when using things like
DVD nurning apps (Ulead, Pinnacle etc).

This is quite annoying.

Thanks to all...

 

[Lanwench [MVP - Exchange]]

In

Does anyone know how to remove MS DEP (Data Execution Protection).
All of a sudden this is on my system and has caused nothing but
problems.
I couldn't even run PowereDVD (which is a KNOWN safe program).. Once I
configed DEP, I could use things like PowerDVD, WinAmp etc, but still
DEP causes my XP system to crach and burn, particularlly when using
things like DVD nurning apps (Ulead, Pinnacle etc).

This is quite annoying.

Thanks to all...

Ah. Well, I'd say that disabling DEP because you're getting DEP errors, is
akin to taking the batteries out of your smoke detector when it starts
making annoying beeping sounds.

The better approach is to find and correct the cause of the problem - you
may have malware on your computer, for one thing. When did this start
happening? Can you pin it down to an exact date? You might try a system
restore if it hasn't been very long, and if you can't locate the exact
application that's causing the problem.

 

[Wiley Coyote - N2K]

Microsoft sent me this link: http://support.microsoft.com/kb/886348/en-us

This is the step I took to fix it and make things go away: At the command
prompt, type the following, and then press ENTER:

SEE MY NOTE BELOW: bootcfg /raw "/noexecute=alwaysoff /fastdetect" /id
1

Note If you have multiple start entries or start options, you may have
to manually modify the Boot.ini file for your computer. To do this, follow
these steps:

a. Click Start, click Run, type sysdm.cpl, and then click OK.
b. On the Advanced tab, under Startup and Recovery, click
Settings.
c. In the Startup and Recovery dialog box, click Edit.
d. Change the /noexecute option to the following:
/noexecute=alwaysoff
e. On the File menu, click Save, and then click Exit.
f. Click OK two times.

6. Restart your computer.


Note: this returned an error: bootcfg /raw "/noexecute=alwaysoff
/fastdetect" /id 1. The system responded with a message that you can only
use /ID 1 "ONLY ONCE???"

Anyway, all is well now (or so it seems).

 

[Wiley Coyote - N2K]

It started the day before last (Sat.) after downloading (automagically I
might add) MS security updates. Nothing new has been added to this system.
It has been stable for quite some time.

Anyway, your analogy of the bateries and smoke detector are well taken, but
is sure seems like MS causes more fires that not. I've been an MS SE and MCT
for over 15 years and I like making money from MS and their "Security
Fixes", but this is just nonsense.

Having barked about that, MS was kind enuff to get back to me within 48
hours with a fix, so I guess that's a good thing.

Thanks and cheers.

"Lanwench [MVP - Exchange]"