hey... not sure if this is exactly the right sub-forum, so please move if not.

anyway, i was wondering if anyone has been using the newest version of orca from the vista sdk. the version is 4.0.5299.0. when i use this version, it crashes anytime i try to modify an msi or mst file. this happens to me in xp x86 and vista x64. it crashes due to DEP and in vista this cannot be set as an exception.

anyone?

I use Orca at work, but had held off DLing the Vista SDK until it became fully RTW.

However, if it's truly crashing on XP due to DEP, then you should be able to easily workaround at least that scenario.

i thought vista sdk is rtm...

http://www.microsoft.com/downloads/details...;displaylang=en

it is easy in XP to get around though i have not tried, but since vista itself is rtm, i upgraded my main system at work to vista x64 and it will not let me add orca as an exception in the DEP list. i use orca on an almost daily basis.

what's funny is that the XP system that it did crash on doesn't even support hardware DEP.

so that leaves me wondering how they could release a version that craps out on software DEP, unless it is an x64 thing... i only have so much time to test scenarios.

i went back to version 3.1.4000.2049 and it seems ok on vista. don't really know what functionality i am missing since i mostly use it for transform files.

Yeah, when I last checked out the SDKs on November 2nd, the Vista one had not yet gone RTM. Certainly looks like it's since been released though, so good to know.

Now I haven't really checked out the DEP stuff in Vista, but I'm wondering if you can do a similar approach as XP to turn it off completely (i.e. BOOT.INI switch of /Execute -or- /NoExecute=AlwaysOff). Not sure though due to the new boot manager et al.

As for the functionality though, I doubt you're really missing anything with that old 3.1 version so long as you're also working with setups that were authored with MSI v3.1- as opposed to the new MSI v4.

bcdedit /set pae ForceDisable

-or-

bcdedit /set nx AlwaysOff

[Syntax Option] bcdedit.exe /set {current} nx AlwaysOff

...I don't have access to a Vista box at the moment, but I believe the nx AlwaysOff string is the correct one.

The PAE option is for hardware NX (no reason to rule it out thought)

Ah, good to know Phonics, so thanks for the tip.

A 64bits CPU and NO disable exec support???

All AMD64 have it (so could not be one of them..)

As far as I know the PentiumD's also support 64bits & Disable Execute, Core 2 Duo, has 64bits & diable execute bit, so i tihnk it was hardware DEP?