XP SP2 breaking compatibility with some apps

[Black Jack]

I would gather mostly because of the AMD64 NX bit solution to buffer overflows.

http://theinquirer.net/?article=14566

Yousuf Khan

 

[Never anonymous Bud]

While still snuggled in a 'spider hole', (e-mail address removed)
(Black Jack) scribbled:

I would gather mostly because of the AMD64 NX bit solution to buffer overflows.

I see no evidence that it's related to the CPU.





To reply by email, remove the XYZ.

Lumber Cartel (tinlc) #2063. Spam this account at your own risk.

This sig censored by the Office of Home and Land Insecurity....

 

[Tony Hill]

I would gather mostly because of the AMD64 NX bit solution to buffer overflows.

http://theinquirer.net/?article=14566

Yup, though the way I'm understanding it, this sort of thing will
happen regardless of what sort of CPU you're using. This suggests
that Microsoft might be implementing the no-execute through
segmentation. I dunno, not exactly a lot of details to go on here.

 

[RusH]

While still snuggled in a 'spider hole',
(e-mail address removed) (Black Jack) scribbled:


I see no evidence that it's related to the CPU.

Its not, Its mostry firewall fault - now its tight like a young virg...
;o)

Pozdrawiam.

 

[Black Jack]

Yup, though the way I'm understanding it, this sort of thing will
happen regardless of what sort of CPU you're using. This suggests
that Microsoft might be implementing the no-execute through
segmentation. I dunno, not exactly a lot of details to go on here.

I don't think so. They mentioned early on that a paging-based NX
scheme would also cause some programs to fail, namely those programs
taht don't pay too much attention to whether they are executing in
pre-designated code areas or data areas.

Also using NX necessarily means that you're using PAE mode. So
whichever programs broke in PAE mode previously, will still break
here, even without the NX bit. Program patches are required either
way.

Yousuf Khan