windows logo program security

I've heard (although cant find) that this is part of a security effort for compliance with the windows logo program. Could someone eloborate a little more on it if you've come accross. Bearing in mind that our environment is a locked down environment maybe usefull here
Applications with hardcoded paths to Program Files/Winnt may have issues installing and running on the 64-bit version of Windows Vista Applications with hardcoded paths to Winnt may have issues installing and running on the 64-bit version of Windows Vista
Applications that unlocks files/folders/registries(HKLM or HKCR) will have issues
I cant seem to make head or tail from where this is coming from MS? Any sort of ideas would be welcome?

I replied in your other thread also, but here is the draft logo doc too since you asked
Windows Vista Logo program for software https://partner.microsoft.com/global/40018574
Here is the link to some x64 documets you will want to read
Getting ready for Windows x64 http://msdn.microsoft.com/library/en-us/dnanchor/html/64bitwindows.asp?frame=true
Running 32bit apps on x64 http://msdn.microsoft.com/library/en-us/win64/win64/running_32_bit_applications.asp?frame=true
this should help you get started
josh http://windowsconnected.com
"gv" wrote in message

I've heard (although cant find) that this is part of a security effort for compliance with the windows logo program. Could someone eloborate a little more on it if you've come accross. Bearing in mind that our environment is a locked down environment maybe usefull here
Applications with hardcoded paths to Program Files/Winnt may have issues installing and running on the 64-bit version of Windows Vista Applications with hardcoded paths to Winnt may have issues installing and running on the 64-bit version of Windows Vista
Applications that unlocks files/folders/registries(HKLM or HKCR) will have issues
I cant seem to make head or tail from where this is coming from MS? Any sort of ideas would be welcome?

On vista, the OS makes an attempt to (heuristically) detect if you are running an installer. If so, it will start the program with administrative privileges and a MIC level of high (after gettin the user's consent) Which will allow your installer to write to \windows as well as \Program Files. In case, Vista fails to detect your installer as an "installer" and runs your installer as a standard user, all the files will be copied to c:\Users\<name>\AppData\Local\VirtualStore\ from both %Program Files% as well as %WINDIR% and all the registry from HKLM\Software to HKU\<SID>\Software\Classes\VirtualStore
But you don't have to rely on Vista's heuristic capabilities, you can mark your installer as requiring admin privileges using either the app compat database or an application manifest. This will still result in the consent dialog though.
But remember, windows resource protection will still prevent you from replacing files under the \Windows directory unless you are singned by MS I think.
HTH Soumik.
On Wed, 08 Feb 2006 15:37:29 -0800, gv wrote:

I've heard (although cant find) that this is part of a security effort for compliance with the windows logo program. Could someone eloborate a little more on it if you've come accross. Bearing in mind that our environment is a locked down environment maybe usefull here
Applications with hardcoded paths to Program Files/Winnt may have issues installing and running on the 64-bit version of Windows Vista Applications with hardcoded paths to Winnt may have issues installing and running on the 64-bit version of Windows Vista
Applications that unlocks files/folders/registries(HKLM or HKCR) will have issues
I cant seem to make head or tail from where this is coming from MS? Any sort of ideas would be welcome?

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Anyone found documentation as to how to create an application manifest?
"Soumik Sarkar" <soumikUNDERSCOREsarkarATyahooDOTcom> wrote in message

On vista, the OS makes an attempt to (heuristically) detect if you are running an installer. If so, it will start the program with administrative privileges and a MIC level of high (after gettin the user's consent) Which will allow your installer to write to \windows as well as \Program Files. In case, Vista fails to detect your installer as an "installer" and runs your installer as a standard user, all the files will be copied to c:\Users\<name>\AppData\Local\VirtualStore\ from both %Program Files% as well as %WINDIR% and all the registry from HKLM\Software to HKU\<SID>\Software\Classes\VirtualStore
But you don't have to rely on Vista's heuristic capabilities, you can mark your installer as requiring admin privileges using either the app compat database or an application manifest. This will still result in the consent dialog though.
But remember, windows resource protection will still prevent you from replacing files under the \Windows directory unless you are singned by MS I think.
HTH Soumik.
On Wed, 08 Feb 2006 15:37:29 -0800, gv <gv@discussions.microsoft.com wrote:
I've heard (although cant find) that this is part of a security effort for compliance with the windows logo program. Could someone eloborate a little more on it if you've come accross. Bearing in mind that our environment is a locked down environment maybe usefull here
Applications with hardcoded paths to Program Files/Winnt may have issues installing and running on the 64-bit version of Windows Vista Applications with hardcoded paths to Winnt may have issues installing and running on the 64-bit version of Windows Vista
Applications that unlocks files/folders/registries(HKLM or HKCR) will have issues
I cant seem to make head or tail from where this is coming from MS? Any sort of ideas would be welcome?

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Try this
http://windowsconnected.com/blogs/jerry/archive/2005/12/21/97.aspx
Josh
"Greg Hamilton" wrote in message

Anyone found documentation as to how to create an application manifest?
"Soumik Sarkar" <soumikUNDERSCOREsarkarATyahooDOTcom> wrote in message On vista, the OS makes an attempt to (heuristically) detect if you are running an installer. If so, it will start the program with administrative privileges and a MIC level of high (after gettin the user's consent) Which will allow your installer to write to \windows as well as \Program Files. In case, Vista fails to detect your installer as an "installer" and runs your installer as a standard user, all the files will be copied to c:\Users\<name>\AppData\Local\VirtualStore\ from both %Program Files% as well as %WINDIR% and all the registry from HKLM\Software to HKU\<SID>\Software\Classes\VirtualStore
But you don't have to rely on Vista's heuristic capabilities, you can mark your installer as requiring admin privileges using either the app compat database or an application manifest. This will still result in the consent dialog though.
But remember, windows resource protection will still prevent you from replacing files under the \Windows directory unless you are singned by MS I think.
HTH Soumik.
On Wed, 08 Feb 2006 15:37:29 -0800, gv <gv@discussions.microsoft.com wrote:
I've heard (although cant find) that this is part of a security effort for compliance with the windows logo program. Could someone eloborate a little more on it if you've come accross. Bearing in mind that our environment is a locked down environment maybe usefull here
Applications with hardcoded paths to Program Files/Winnt may have issues installing and running on the 64-bit version of Windows Vista Applications with hardcoded paths to Winnt may have issues installing and running on the 64-bit version of Windows Vista
Applications that unlocks files/folders/registries(HKLM or HKCR) will have issues
I cant seem to make head or tail from where this is coming from MS? Any sort of ideas would be welcome?

-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/