[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] vista testing...



Nice one.

Yeah, I think uninstall gets broken on vista with the .exe ones.  I
haven't tried it, but that's what it seems to be trying to do -
install a registry key so it can uninstall it later.


On Mon, Mar 17, 2008 at 9:25 AM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
> yeah, msi seems the way to go. I think it's also better for 64-bit
>  windows. The original wininst developer posted in a thread that he
>  thinks it had a good life, and is fine with it being replaced by
>  bdist_msi.
>
>  I just installed vista recently, and I've been working today on making
>  my automated builds use msi.
>
>  ... but for what it's worth, the vista install errors with the .exe
>  installers are generally fine to ignore, they don't affect pygame's
>  functionality in any way I've been able to tell.
>
>
>
>  On Sun, Mar 16, 2008 at 2:37 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
>  > Hi,
>  >
>  >  I've tried to add a manifest with mt.exe but have not been able to get
>  >  it to work.  It kept creating an executable with only 60KB size.
>  >
>  >  I think the manifest needs a bunch of tweaking.
>  >
>  >  However then I started reading up about blue screens caused by the
>  >  manifests on windows XP...
>  >
>  >  So, let's use the msi build instead?  Python uses a msi build anyway,
>  >  so the requirement is there already.  The msi build installs ok on
>  >  vista, and asks for permission.
>  >
>  >  I guess the only issue with that is the version string renaming,
>  >  because the msi doesn't like our version strings.  I think that could
>  >  be fixed with someway to tell the installer to use a different naming
>  >  scheme.  Or I guess we could ditch our old naming scheme, and change
>  >  it a little.  But for this 1.8 release I think we should just stick
>  >  with the current naming, and change it for after pygame 1.8.
>  >
>  >  cheers,
>  >
>  >
>  >
>  >
>  >  On Sun, Feb 17, 2008 at 6:40 AM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
>  >  > I couldn't find mt.exe in the platform SDK or .NET SDK's I've got
>  >  >  installed - but I found it bundled with Visual Studio 2005.
>  >  >
>  >  >  so I posted it here:
>  >  >  thorbrian.com/mt.zip
>  >  >
>  >  >  I think the usage to change a manifest is:
>  >  >  mt -manifest <manifestfilename.xml> -outputresource:<target.exe>
>  >  >
>  >  >  and the usage to extract a manifest is:
>  >  >  mt.exe -inputresource:<target.exe> -out:<manifestfilename.xml>
>  >  >
>  >  >  attached is a manifest I've used at work for installer-type-programs
>  >  >
>  >  >  ... as a side note it looks like there is no manifest for the
>  >  >  installer bdist_wininst makes for me, and without setup or installer
>  >  >  in the name windows probably isn't auto-detecting and triggering it's
>  >  >  "treat as an installer" behavior, so I'm kind of surprised it isn't
>  >  >  virtualizing the environment for the installer and letting it think it
>  >  >  has full access...
>  >  >
>  >  >
>  >  >
>  >  >
>  >  >  On Feb 15, 2008 9:18 PM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
>  >  >  > There's an command line mt.exe tool by microsoft that does it - I
>  >  >  > think it comes with either the .NET or the Platform SDK, but I'm not
>  >  >  > sure. You just create an xml manifest file with the right
>  >  >  > requestedExecutionLevel, then run mt -manifest with some args or
>  >  >  > something like that. all it does is embed the xml file as a resource.
>  >  >  >
>  >  >  > It can also be done with any old resource editor if you know the right
>  >  >  > name and id for the resource (you can figure that out by using the
>  >  >  > editor to look at a file that does have a manifest - like an inno
>  >  >  > setup installer for instance)
>  >  >  >
>  >  >  >
>  >  >  > On Feb 15, 2008 6:33 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
>  >  >  > > ah, cool.
>  >  >  > >
>  >  >  > > Here's a couple of links from a search for more info:
>  >  >  > > http://channel9.msdn.com/Showpost.aspx?postid=211271
>  >  >  > > http://channel9.msdn.com/Showpost.aspx?postid=209647
>  >  >  > > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=463884&SiteID=1
>  >  >  > >
>  >  >  > > I think it should be fairly straight forward... but I can't seem to
>  >  >  > > find out to actually add the manifest to an exe.
>  >  >  > >
>  >  >  > > Do you know how to add a manifest to an exe?
>  >  >  > >
>  >  >  > > cheers,
>  >  >  > >
>  >  >  > >
>  >  >  > > On Feb 16, 2008 11:29 AM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
>  >  >  > > > On Vista if a program doesn't have a "manifest" that tells Vista
>  >  >  > > > whether it wants to ask for permissions or not, the default behavior
>  >  >  > > > is for Vista to let it think that it is writing and doing a bunch of
>  >  >  > > > things that would affect all users on XP, but virtualize them in a way
>  >  >  > > > that is per user (and can be lost or wiped as well). The manifest can
>  >  >  > > > tell the OS to either ask for elevation of privilege to let it do
>  >  >  > > > things for all users (the trust box), or to have the app run with
>  >  >  > > > whatever it can get, or to have the app run without special prvileges.
>  >  >  > > >
>  >  >  > > > It sounds like maybe the install has a manifest, but the manifest is
>  >  >  > > > set to not ask to elevate.
>  >  >  > > >
>  >  >  > > > manifests can be modified/added/deleted from finished built exe's as
>  >  >  > > > long as the exe isn't signed, so if you wanted to play around with the
>  >  >  > > > manifest settings you could.
>  >  >  > > >
>  >  >  > > >
>  >  >  > > > On Fri, Feb 15, 2008 at 4:17 PM, René Dudfield <renesd@xxxxxxxxx> wrote:
>  >  >  > > > > - the pygame installer brings up a bunch of messages about things it can't
>  >  >  > > > > do... but then manages to install ok.  I think it's trying to do things like
>  >  >  > > > > set registry keys, but vista is blocking it.  I think this is more the fault
>  >  >  > > > > of the distutils install maker.  Anyone know about changes needed for vista
>  >  >  > > > > installers?  For most installers vista pops up a message about "do you trust
>  >  >  > > > > this installer".  This doesn't happen for the pygame one... so maybe we have
>  >  >  > > > > to ask vista for permission.
>  >  >  > > > >
>  >  >  > > >
>  >  >  > >
>  >  >  >
>  >  >
>  >
>