The problem with Windows XP SP2 & DIVX

[techz]

- The DivX problem is going to be repeated on quite a few applications. Anything that generates machine code into a memory buffer and then calls it will be hit, until the authors modify their software to tell Windows what they're doing. The calls for this have existed since the introduction of the Win32 API - it's just that until now, nothing went wrong if you didn't use them.

http://www.theinquirer.net/?article=17782

[DigitAl56K]

We're working on making DivX SP2-compatible. Until then, see here:

http://forums.divx.com/viewtopic.php?topic=60618&forum=5

[techz]

thanks, cant wait to get some update of some sort

[nicco]

please, release an update!

[Leolo]

Hi DigitAl56K,

You recommend to enable the "/Execute" parameter in boot.ini. Is that an undocumented parameter? What does it do?

As far as I know, the documented parameters of boot.ini regarding DEP are these:

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
OptIn(default configuration)
On systems with processors capable of hardware-enforced DEP, DEP is enabled by default for limited system binaries and applications that “opt-in,”
With this option, only Windows system binaries are covered by DEP by default. Applications that choose to enable DEP protection may do so during their installation.

OptOut
DEP is enabled by default for all processes. Users can manually create a list of specific applications which do not have DEP applied using System in Control Panel. IT Pros and Independent Software Vendors (ISVs) can use the Application Compatibility Toolkit to opt-out one or more applications from DEP protection. System Compatibility Fixes (“shims”) for DEP do take effect.

AlwaysOn
This provides full DEP coverage for the entire system. All processes always run with DEP applied. The exceptions list for exempting specific applications from DEP protection is not available. System Compatibility Fixes (“shims”) for DEP do not take effect. Applications which have been opted-out using the Application Compatibility Toolkit run with DEP applied.

AlwaysOff
This does not provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor does not run in PAE mode unless the /PAE option is present in the boot entry.

Where did you find out about the "/Execute" parameter??

Thanks a lot.
Kind regards.

[DigitAl56K]

Read KB875352

:)

[Leolo]

Thanks! Didn't know about that one.

Sometimes I wonder why does Microsoft like to scatter their documentation so much...

Now you're left wondering which set of parameters is deprecated and which one is recommended to use :(

Cheers.

[DigitAl56K]

I actually suspect that when you omit /NoExecute DEP is disabled, and /Execute is the same as omitting /NoExecute, though I haven't tested.

All I know is that it works, and that's what counts :)

[tiki4]

Originally posted by DigitAl56K
I actually suspect that when you omit /NoExecute DEP is disabled, and /Execute is the same as omitting /NoExecute, though I haven't tested.


Yep, so it is.

tiki4