From: Richard Z <rz@linux-m68k.org>
To: Dan Kegel <dank@kegel.com>
Cc: cygwin@cygwin.com
Subject: Re: setup.exe problem in wine
Date: Sat, 01 Jul 2017 11:31:00 -0000 [thread overview]
Message-ID: <20170701113105.GA3986@rz.localhost.localdomain> (raw)
In-Reply-To: <CAPF-yOYqNHULYGaGBx4hhBGJCubxk_-_vy7sM5B+5u6daXX6Gg@mail.gmail.com>
On Fri, Jun 30, 2017 at 07:45:34AM -0700, Dan Kegel wrote:
thanks for the tipps and trying..
> There were lots of complaints from setup.exe (not wine) of the sort
> AddAccessAllowedAceEx(C:\cygwin64/etc/setup, group) failed: 1337
> but those can probably be ignored.
same here.
> Default install seemed to go quite well, at least until the
> postinstall scripts ran;
> each one of them complained about a stack overflow, but the gui continued:
almost same here but it was "page fault on read access to 0x00000001",
the difference might be because I am trying the 32bit mode.
> Well, shoot. So I tried again with WINEDEBUG=+relay to get a log of
> system calls,
> Wading through the noise, I saw two interesting things:
strangely WINEDEBUG does nothing for me.
I have added the info to https://bugs.winehq.org/show_bug.cgi?id=40528
Richard
--
Name and OpenPGP keys available from pgp key servers
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-01 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:26 Richard Z
2017-06-30 12:44 ` Richard Z
2017-06-30 14:45 ` Dan Kegel
2017-07-01 11:31 ` Richard Z [this message]
2017-07-01 19:01 ` Dan Kegel
2017-07-03 11:56 ` Richard Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170701113105.GA3986@rz.localhost.localdomain \
--to=rz@linux-m68k.org \
--cc=cygwin@cygwin.com \
--cc=dank@kegel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).