> However, this should work (I haven't tried lately):
>
> .\setup-x86 --arch=x86_64
> Assuming you aren't part of the .001% who can't run x86 executables.
That works, as soon as I have renamed setup-x86.exe to foo.exe!
That's an easy and simple solution.
Thanks,
Frédéric
--
Problem reports:
Christopher Faylor sent the following at Wednesday, September 25, 2013 1:06 PM
>On Wed, Sep 25, 2013 at 04:59:57PM +, Buchbinder, Barry (NIH/NIAID)
>[E] wrote:
>>>Does setup for 64 bit cygwin need to be 64 bit? Might all this
>>be avoided if setup-x86_64.exe were itself 32 bit application?
>
>
On Wed, Sep 25, 2013 at 04:59:57PM +, Buchbinder, Barry (NIH/NIAID) [E]
wrote:
>Does setup for 64 bit cygwin need to be 64 bit? Might all this
>be avoided if setup-x86_64.exe were itself 32 bit application?
I lost that argument. Apparently some 64-bit systems can't run 32-bit
applications.
Greetings, Larry Hall (Cygwin)!
>> In fact, what would be the issue to set the requested execution level
>> to "asInvoker" for the official setup-x86_64.exe?
>> People with admin rights will still be able to install for all users
>> and people without admin rights will be able to install for
>> th
Does setup for 64 bit cygwin need to be 64 bit? Might all this
be avoided if setup-x86_64.exe were itself 32 bit application?
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
On 9/25/2013 11:21 AM, Frédéric Bron wrote:
In fact, what would be the issue to set the requested execution level
to "asInvoker" for the official setup-x86_64.exe?
People with admin rights will still be able to install for all users
and people without admin rights will be able to install for
them
>> In fact, what would be the issue to set the requested execution level
>> to "asInvoker" for the official setup-x86_64.exe?
>> People with admin rights will still be able to install for all users
>> and people without admin rights will be able to install for
>> them-selves.
>
>
> Doesn't that mea
On 9/25/2013 10:11 AM, Frédéric Bron wrote:
In fact, what would be the issue to set the requested execution level
to "asInvoker" for the official setup-x86_64.exe?
People with admin rights will still be able to install for all users
and people without admin rights will be able to install for
t
> I just modified this:
> Index: setup64.exe.manifest
> ===
> RCS file: /cvs/cygwin-apps/setup/setup64.exe.manifest,v
> retrieving revision 2.1
> diff -r2.1 setup64.exe.manifest
> 25c25
> < uiAccess="false"/>
> ---
>>
Larry Hall (Cygwin) sent the following at Sunday, September 22, 2013 9:42 PM
>No, "All Users" is also required to set up services (like sshd, crond,
>etc.) to work for all users (i.e. switch user context). This is the
>recommended way to install so that these subsequent facilities can be
>used with
On 9/22/2013 2:18 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Correct me if I'm wrong (like I need to ask!), but my impression is that the
only thing for which setup for 'Cygwin for All Users' currently needs admin
privileges is to create shortcuts in "C:\Users\All Users\Desktop" and
"C:\Users\A
Yaakov (Cygwin/X) sent the following at Thursday, September 12, 2013 12:42 PM
>UAC Installer Detection only affects x86 binaries, so that only helps
>with setup-x86.exe. As for setup-x86_64.exe, its builtin manifest
>requires Admin privileges because otherwise it won't promote itself
>automaticall
> No. setup.exe (either 32bit or 64bit) is a native windows application, and
> if you're trying to build it within cygwin, then you MUST use a cross
> compiler -- either i686-w64-mingw32 or x86_64-w64-mingw32. when configuring
> the build, just do:
>
> configure --host=i686-w64-mingw32 --build=i686
On 9/18/2013 1:53 PM, Frédéric Bron wrote:
Is it possible to build setup64.exe from a 32bit cygwin?
As previously mentioned, despite the subject, there is no such thing as
setup64.exe. The makefile creates setup.exe. The filename gets changed
when it gets uploaded to cygwin.com to either setu
>>Is it possible to build setup64.exe from a 32bit cygwin?
>
> As previously mentioned, despite the subject, there is no such thing as
> setup64.exe. The makefile creates setup.exe. The filename gets changed
> when it gets uploaded to cygwin.com to either setup-x86.exe or
> setup-x86_64.exe.
do
On Wed, Sep 18, 2013 at 07:30:35PM +0200, Fr?d?ric Bron wrote:
>> You can build setup.exe yourself for x86_64-w64-mingw32 with the
>> requestedExecutionLevel entry removed from the manifest. The sources are in
>> cygwin-apps CVS.
>
>I got the sources and ran bootstrap.sh
>I got setup.exe but not s
> You can build setup.exe yourself for x86_64-w64-mingw32 with the
> requestedExecutionLevel entry removed from the manifest. The sources are in
> cygwin-apps CVS.
I got the sources and ran bootstrap.sh
I got setup.exe but not setup64.exe
Is it possible to build setup64.exe from a 32bit cygwin?
> You can build setup.exe yourself for x86_64-w64-mingw32 with the
> requestedExecutionLevel entry removed from the manifest. The sources are in
> cygwin-apps CVS.
do I need a password to get the sources?
I get this message:
CVS password file /home/xxx/.cvspass does not exist - creating a new
fil
> And without a proxy server:
> $ cvs -z3 -d :pserver:anon...@sourceware.org:/cvs/cygwin-apps co cygwin-setup
> cvs checkout: CVS password file /cygdrive/d/Documents/.cvspass does
> not exist - creating a new file
> cvs server: cannot find module `cygwin-setup' - ignored
> cvs [checkout aborted]: c
> do I need a password to get the sources?
> I get this message:
> CVS password file /home/xxx/.cvspass does not exist - creating a new
> file cvs [checkout aborted]: end of file from server (consult above
> messages if any)
>
> But this may be just due to our proxy server.
And without a proxy ser
On Thu, Sep 12, 2013 at 11:42:28AM -0500, Yaakov (Cygwin/X) wrote:
>On 2013-09-12 04:07, Fr?d?ric Bron wrote:
>> I would like to run setup64.exe on Windows 7 without asking for admin
>> rights but the computer asks me for admin credentials.
>> I read this: http://cygwin.com/ml/cygwin/2011-06/msg002
On 2013-09-12 04:07, Frédéric Bron wrote:
I would like to run setup64.exe on Windows 7 without asking for admin
rights but the computer asks me for admin credentials.
I read this: http://cygwin.com/ml/cygwin/2011-06/msg00286.html where
Corinna suggested to rename the .exe to foo.exe but this did
On 12/09/2013 11:52 AM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
Ryan Johnson sent the following at Thursday, September 12, 2013 11:31 AM
Try *copying* setup64.exe to foo.exe. Or download it again but save it
with the name foo.exe.
Windows may be remembering that the file used to be called setu
On 12/09/2013 11:26 AM, Frédéric Bron wrote:
Try *copying* setup64.exe to foo.exe. Or download it again but save it
with the name foo.exe.
Windows may be remembering that the file used to be called setup*.exe.
That memory might not get copied.
Doesn't work: "the requested operation requires ele
Ryan Johnson sent the following at Thursday, September 12, 2013 11:31 AM
>>> Try *copying* setup64.exe to foo.exe. Or download it again but save it
>>> with the name foo.exe.
>>> Windows may be remembering that the file used to be called setup*.exe.
>>> That memory might not get copied.
>> Doesn't
> I have vague memories that someone (Corinna?) suggested copying the file to
> a USB key and back: the FAT filesystem can't track the permissions that
> cause this behavior. Never tested it myself, though (maybe I should, it
> would be nice to lose the UAC prompt).
doesn't work.
Frédéric
--
Pro
Frédéric Bron sent the following at Thursday, September 12, 2013 5:07 AM
>I would like to run setup64.exe on Windows 7 without asking for admin
>rights but the computer asks me for admin credentials. I read this:
>http://cygwin.com/ml/cygwin/2011-06/msg00286.html where Corinna
>suggested to rename
> Try *copying* setup64.exe to foo.exe. Or download it again but save it
> with the name foo.exe.
> Windows may be remembering that the file used to be called setup*.exe.
> That memory might not get copied.
Doesn't work: "the requested operation requires elevation".
I am packaging a program wit
I would like to run setup64.exe on Windows 7 without asking for admin
rights but the computer asks me for admin credentials.
I read this: http://cygwin.com/ml/cygwin/2011-06/msg00286.html where
Corinna suggested to rename the .exe to foo.exe but this did not work.
I also do not have the rights to m
29 matches
Mail list logo
