Cygwin's spawn/exec, mintty and the "Program Compatibility Assistant"

[Corinna Vinschen]

On Feb 19 06:00, Andy Koppe wrote:
> On 17 February 2012 12:18, Corinna Vinschen wrote:
> > Bottom line:
> >
> > - From observation I assume that it's all about having a runlevel manifest
> > Â or not. Â On W7 the binary additionally needs a special W7 compatible
> > Â manifest.
> >
> > - Console applications are only affected when started directly from the
> > Â GUI. Â If they are started from a correctly-manifested console app (CMD),
> > Â they and their children are not affected anymore.
> >
> > - So we would have to create all executables with a W7-compatible
> > Â manifest. Â That is quite certainly not an option.
> >
> > - So we have to keep the CREATE_BREAKAWAY_FROM_JOB stuff in Cygwin
> > Â for the time being.
> 
> Sorry to be a bit dense, but does this mean for mintty? Do I need to
> add something to the manifest, and if so, how urgent is it?

For mintty this means you *can* extend its manifest if you like.  It
will avoid that PCA takes control of mintty.  Here's what works for me,
even on W7.  The GUIDs identify the operating system versions.  The
first one is for W7, the second one for Vista.  The GUID for W8 has not
been released yet, afaics.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  [...]
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
	<requestedExecutionLevel
	  level="asInvoker"
	  uiAccess="false"/>
	</requestedPrivileges>
     </security>
  </trustInfo>
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
    </application>
  </compatibility>
</assembly>


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat